You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even if a message does not contain a segment, the repetitions used property can be still 1.
E.g. in the test called TestOBR5RepeatingValuesMessage (in ParserTest.cs), the ORU message does not contain NK1 segments, but adding the following assert fails the test:
Assert.AreEqual(0, oru.GetPATIENT_RESULT(0).PATIENT.NK1RepetitionsUsed);
I have the problem with all sort of messages (2.4 version too).
The text was updated successfully, but these errors were encountered:
This seems like a pretty deep problem within the code generator / parser when handling groups. The behaviour is that for a group (i.e. in this case the ORU_R01_Patient group), all of it's known message structures get added (regardless of whether or not they exist), and then parsed into / extra segments created as needed.
So you'll always get a count of at least 1 for segments in a group, whether they exist or not. And since there is no easy way to determine if a segment is actually populated ... this can't be easily resolved.
Even if a message does not contain a segment, the repetitions used property can be still 1.
E.g. in the test called TestOBR5RepeatingValuesMessage (in ParserTest.cs), the ORU message does not contain NK1 segments, but adding the following assert fails the test:
Assert.AreEqual(0, oru.GetPATIENT_RESULT(0).PATIENT.NK1RepetitionsUsed);
I have the problem with all sort of messages (2.4 version too).
The text was updated successfully, but these errors were encountered: