Hi,
Do I understand that HL7v2 conformance profiles -- and, correspondingly, the Gazelle validator based on them -- cannot handle NULL values (pairs of double quotes "") in composite fields?
NB: support for such NULL values shall be actually allowed only at special places like OBR-2, ORC-2, INV-1, OBX-5, etc.
Example:
Expected behavior:
The following segments shall pass the validation:
INV|substanceId^^HL70451|OK^^HL70383
The following segment shall not pass the validation, because NULL cannot belong to any coding system:
INV|""^^HL70451|OK^^HL70383
Observed behavior:
The following segments pass the validation:
INV|substanceId^^HL70451|OK^^HL70383
INV|""^^HL70451|OK^^HL70383 (false positive)
The following segment does not pass the validation, because INV-1-3 "Coding System ID" is missing:
INV|""|OK^^HL70383
Proposal:
/HL7v2xConformanceProfile/HL7v2xStaticDef/Segment/Field/@nullAllowed
shall be introduced and respected by the IPF-Gazelle validator: when set to "true", NULL will be accepted instead of whatever was originally defined for the field. This attribute will never occur in "official" conformance profiles published by IHE and HL7, thus this local extension will not break anything.
Your opinions?
Thanks and bets regards
Dmytro