format requirement replacing the condition predicate. 34 Table 5.2.1 MSH-10 Additional wording was added This field contains a string that to clarify the use of the uniquely identifies the message instance from the sending application. Message Control ID to The unique record identifier for the uniquely identify the message notification as created by the sending and updates to indicate surveillance system is a good appending a timestamp is an candidate for this string. If the local example to ensure record identifier is not unique (if the uniqueness but not required. record is updated), as an example a timestamp can be appended to ensure a unique identifier. 35 Various Removal of the reference to Various. Places “From Reference to a specific ELR guide may be misleading to requirements to how to provide the laboratory information. 36 Table 5.2.1 MSH-21 Removal of the specific Conformance statement replaced with: literals for indicating the conformance statements for “The NOT115 SHALL be obtained from the profile and MMG to be used program specific MMG.” for a given message. The conformance statement was removed and added to each MMG instead of in this messaging specification, because each conformance is unique to each MMG. 37 Table 5.2.4 OBR-4 Updated the conformance CONFORMANCE STATEMENT statement to clearly state There SHALL be one and only one occurrence of OBR-4 (Universal and only “one one” Identifier) valued occurrence of the all Information^LN‘in types of Case Notification Messages. will be Information^LN‘ allowed, instead of “an occurrence”. 38 Table 5.2.4 OBR-4 Removal of the Treatment CONFORMANCE STATEMENT Information conformance There MAY be zero to many additional and optional instances of statement because it is Notification Sections from the currently not used, replaced the reference to any other C value set () as indicated by an MMG specific section header for where the OBR-4 Universal Service ID OBR-4 to a more generic
format requirement replacing the condition predicate. 34 Table 5.2.1 MSH-10 Additional wording was added to clarify the use of the Message Control ID to uniquely identify the message and updates to indicate appending a timestamp is an example to ensure uniqueness but not required. This field contains a string that uniquely identifies the message instance from the sending application. The unique record identifier for the notification as created by the sending surveillance system is a good candidate for this string. If the local record identifier is not unique (if the record is updated), as an example a timestamp can be appended to ensure a unique identifier. 35 Various Places Removal of the reference to “From Reference to a specific ELR guide may be misleading to requirements to how to provide the laboratory information. Various. 36 Table 5.2.1 MSH-21 Removal of the specific literals for indicating the profile and MMG to be used for a given message. The conformance statement was removed and added to each MMG instead of in this messaging specification, because each conformance is unique to each MMG. Conformance statement replaced with: “The conformance statements for NOT115 SHALL be obtained from the program specific MMG.” 37 Table 5.2.4 OBR-4 Updated the conformance statement to clearly state “one and only one” occurrence of the Information^LN‘ will be allowed, instead of “an occurrence”. CONFORMANCE STATEMENT There SHALL be one and only one occurrence of OBR-4 (Universal Identifier) valued Information^LN‘in all types of Case Notification Messages. 38 Table 5.2.4 OBR-4 Removal of the Treatment Information conformance statement because it is currently not used, replaced the reference to any other specific section header for OBR-4 to a more generic CONFORMANCE STATEMENT There MAY be zero to many additional and optional instances of Notification Sections from the value set () as indicated by an MMG where the OBR-4 Universal Service ID C
PHIN_Messaging_Specification_for_Case_Notification_v3%200_Release_2_20170815.docx