of the Message Control instance from the sending application. ID to uniquely identify The unique record identifier for the message and the notification as created by the updates to indicate sending surveillance system is a appending a timestamp good candidate for this string. If is an example to ensure the local record identifier is not uniqueness but not unique (if the record is updated), required. as an example a timestamp can be appended to ensure a unique identifier. 35 Various Removal of the Various. Places reference to “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 literals for indicating the replaced with: “The conformance statements for profile and MMG to be NOT115 SHALL be obtained used for a given from the program specific message. The MMG.” conformance statement was removed and added to each MMG instead of in this messaging guide, because each conformance is unique to each MMG. 37 Table 5.2.4 OBR-4 Updated the CONFORMANCE STATEMENT conformance statement CN-014: There SHALL be one and only one occurrence of to clearly state and “one OBR-4 (Universal Identifier) only occurrence of one” valued ‘68991-9^Epidemiologic the all types of Information^LN‘in Case Notification Messages.
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. 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 guide, 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 CONFORMANCE STATEMENT CN-014: There SHALL be one and only one occurrence of OBR-4 (Universal Identifier) valued ‘68991-9^Epidemiologic Information^LN‘in all types of Case Notification Messages.
PHIN_Messaging_Guide_for_Case_Notification_v3.0_Release%201_20161018.docx