as constrained. The HL7 required SPM-4 remains required but the other fields are sent only if available. 5 Segment OBX The OBX segment is The Observation (OBX) Profile Segment tightly constrained to constraints have been segment’s Attributes only allow and relaxed to allow the more “question and usage of the OBX. answer” pattern does not allow for some of the fields that ELR messages use. 6 HL7 All of the Notes and The Notes and Comments (NTE) Message Comments (NTE) segment has been included structure segments were under the OBX segment to allow attributes constrained out/not comments associated with supported. Laboratory Observations to be in the message. 7 Segment Throughout The message was very Many fields in used segments Profile constrained to set many have been set to with “optional” Attributes fields to the comment that if the field is “not supported.” In theory, this will kick optional, it is not defined in this out a lot of messages if document and not expected to be the receiver profile is not processed by the receiver. relaxed. Fields that remained constrained as are those that “not supported” are no longer used for this HL7 version or ones that potentially contain PII data that should not be sent for this use case. 8 Message ORU^R01 ORU^R01^ORU_R01 ORU^R01^ORU_R01 Message Structure Message Message definition was Syntax has been updated to align Syntax a very simplified with the ELR version of the structure that only message syntax. showed the required fields and segment groups.
as constrained. The HL7 required SPM-4 remains required but the other fields are sent only if available. 5 Segment Profile Attributes OBX Segment The OBX segment is tightly constrained to only allow “question and answer” pattern and does not allow for some of the fields that ELR messages use. The Observation (OBX) segment’s constraints have been relaxed to allow the more usage of the OBX. 6 HL7 Message structure attributes All of the Notes and Comments (NTE) segments were constrained out/not supported. The Notes and Comments (NTE) segment has been included under the OBX segment to allow comments associated with Laboratory Observations to be in the message. 7 Segment Profile Attributes Throughout The message was very constrained to set many fields to “not supported.” In theory, this will kick out a lot of messages if the receiver profile is not relaxed. Many fields in used segments have been set to “optional” with the comment that if the field is optional, it is not defined in this document and not expected to be processed by the receiver. Fields that remained constrained as “not supported” are those that are no longer used for this HL7 version or ones that potentially contain PII data that should not be sent for this use case. 8 Message Structure ORU^R01 Message Syntax ORU^R01^ORU_R01 Message definition was a very simplified structure that only showed the required fields and segment groups. ORU^R01^ORU_R01 Message Syntax has been updated to align with the ELR version of the message syntax.
PHIN_Messaging_Guide_for_Case_Notification_v3.0_Release%201_20161018.docx