APPENDIX REVISIONS V2.0 – Location Field Name Topic in v2.0 Revision in V3.0 1 HL7 ORDER_OBSERVATION The message no longer specifies Message groups were hard-coded to subject type or notification type in this structure expect one OBR where manner. Subject type is derived from attributes defined the subject type and looking at the PID segment (i.e., one OBR where OBR-4 whether the person or the defined the notification type. fields are populated) and notification type is specified in MSH-21 Profile ID. 2 HL7 ORDER_OBSERVATION The new message specifies that one Message groups were hard-coded to OBR the one that conveys – structure expect one OBR where - is required “epidemiologic information” attributes defined the subject type and and is the source of truth for notification one OBR where OBR-4 variables that are tied to the OBR defined the notification type. segment (OBR-3, OBR-7, OBR-22, OBR-25, OBR-31.) Other OBRs are used for clinical, demographic, laboratory, treatment, or vaccine category information as needed. 3 HL7 The Next of Kin/ Associated The Next of Kin/ Associated Parties Message Parties (NK1) segment was (NK1) segment has been included to structure not supported. allow additional subjects or parent or attributes owner information. 4 HL7 The Specimen (SPM) The Specimen (SPM) segment has Message segment was not supported been added, as the message supports it structure and it may be included in the attributes ORDER_OBSERVATION group specific to laboratory reporting. The definition follows the ELR Implementation Guide but is not as constrained. The HL7 required SPM-4 remains required but the other fields are sent only if available. 5 Segment OBX Segment The OBX segment is tightly The Observation (OBX) segment’s Profile constrained to only allow constraints have been relaxed to allow Attributes and the more ELR-like usage of the OBX. “question answer” pattern and 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) segments segment has been included under the
APPENDIX – REVISIONS V2.0 Location Field Name Topic in v2.0 Revision in V3.0 1 HL7 Message structure attributes ORDER_OBSERVATION groups were hard-coded to expect one OBR where defined the subject type and one OBR where OBR-4 defined the notification type. The message no longer specifies subject type or notification type in this manner. Subject type is derived from looking at the PID segment (i.e., whether the person or the fields are populated) and notification type is specified in MSH-21 Profile ID. 2 HL7 Message structure attributes ORDER_OBSERVATION groups were hard-coded to expect one OBR where defined the subject type and one OBR where OBR-4 defined the notification type. The new message specifies that one OBR – the one that conveys “epidemiologic information” - is required and is the source of truth for notification variables that are tied to the OBR segment (OBR-3, OBR-7, OBR-22, OBR-25, OBR-31.) Other OBRs are used for clinical, demographic, laboratory, treatment, or vaccine category information as needed. 3 HL7 Message structure attributes The Next of Kin/ Associated Parties (NK1) segment was not supported. The Next of Kin/ Associated Parties (NK1) segment has been included to allow additional subjects or parent or owner information. 4 HL7 Message structure attributes The Specimen (SPM) segment was not supported The Specimen (SPM) segment has been added, as the message supports it and it may be included in the ORDER_OBSERVATION group specific to laboratory reporting. The definition follows the ELR Implementation Guide but is not 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 ELR-like usage of the OBX. 6 HL7 Message All of the Notes and Comments (NTE) segments The Notes and Comments (NTE) segment has been included under the
PHIN_Messaging_Specification_for_Case_Notification_v3%200_Release_2-1_20180119.docx