structure were constrained out/not OBX segment to allow comments attributes supported. associated with Laboratory Observations to be in the message. 7 Segment Throughout The message was very Many fields in used segments have Profile constrained to set many fields been set to with the comment “optional” Attributes to In theory, that if the field is optional, it is not “not supported.” this will kick out a lot of defined in this document and not messages if the receiver expected to be processed by the profile is not relaxed. receiver. Fields that remained constrained as are “not supported” 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 ORU^R01 ORU^R01^ORU_R01 ORU^R01^ORU_R01 Message Syntax Structure Message Syntax Message definition was a has been updated to align with the ELR very simplified structure that version of the message syntax. only showed the required fields and segment groups. 9 1.4 Formerly described the use of Reworked to clarify and correct the HL7 Summary the 6 categories of data. content change descriptions of Changes 10 6 Appendix Technical Only contained a discussion Added a section to discuss repeating A Considerations about repeating groups variables (that is, the use of the tilde in the field for a multi-select answer). 11 7 Appendix Messaging Messages were conformant Revised the messages Examples to specifications. 12 5.2 All CE fields Maximum length CE fields Maximum length increased to 841. This Segment were not consistence. increase affected other datatypes that and Field contain a CE datatype as a component, such as VID and XPN. 13 5.2 All CWE fields Maximum length CE fields Maximum length increased to 1063. Segment were not consistence. This increase affected other datatypes and Field that contain a CWE datatype as a Description component, such as XCN. 14 5.2.4 OBR OBR-22 Status The cardinality of OBR-22 Technical correction to the cardinality of Segment Chg/Update was [1..1]. OBR-22 from [1..1] to [0..1]. This is not Detail Date/time an HL7 required field so it is only required per Condition Predicate: If OBR-4 is populated with Information^LN’
Description structure attributes were constrained out/not supported. 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. 9 1.4 Summary of Changes Formerly described the use of the 6 categories of data. Reworked to clarify and correct the HL7 content change descriptions 10 6 Appendix A Technical Considerations Only contained a discussion about repeating groups Added a section to discuss repeating variables (that is, the use of the tilde in the field for a multi-select answer). 11 7 Appendix Messaging Examples Messages were conformant to specifications. Revised the messages 12 5.2 Segment and Field All CE fields Maximum length CE fields were not consistence. Maximum length increased to 841. This increase affected other datatypes that contain a CE datatype as a component, such as VID and XPN. 13 5.2 Segment and Field All CWE fields Maximum length CE fields were not consistence. Maximum length increased to 1063. This increase affected other datatypes that contain a CWE datatype as a component, such as XCN. 14 5.2.4 OBR Segment Detail OBR-22 Status Chg/Update Date/time The cardinality of OBR-22 was [1..1]. Technical correction to the cardinality of OBR-22 from [1..1] to [0..1]. This is not an HL7 required field so it is only required per Condition Predicate: If OBR-4 is populated with Information^LN’
PHIN_Messaging_Specification_for_Case_Notification_v3%200_Release_2-1_20180119.docx