The format does not show the optionality of MMDD. 27 Section Example is incorrect, Example: MSH-11 Processing 4.17 updated from MSH-10 to ID: |D| or |P| or |T|. MSH-11. “Example: MSH-10 Processing ID: |D| or |P| or |T|.” 28 Section SN-3 and Added Condition Usage: C(RE/X) 4.19 SN-4 Predicate for the SN data type to identify the Condition Predicate: If required order of component 2 (Numeric Value 1) components to be used. is valued. New condition predicate to require the 2nd component to be present if the before the 3rd and 4th components. 29 Section Added conformance CONFORMANCE STATEMENT 4.19 statement for SN data CN-003: If <num1> and <num2> type to require the are both non-null, then the separator/suffix if both separator/suffix MUST be <num1> and <num2> are non-null values. 30 Table MSH-7 For consistent use of Conformance statement 5.2.1 date/time sent in specific added for MSH-7: date/time fields the date CONFORMANCE STATEMENT format was updated to CN-006: MSH-7 (Date/Time of align with a specific level Message) SHALL follow the of precision to seconds. format:
The format does not show the optionality of MMDD. 27 Section 4.17 Example is incorrect, updated from MSH-10 to MSH-11. “Example: MSH-10 Processing ID: |D| or |P| or |T|.” Example: MSH-11 Processing ID: |D| or |P| or |T|. 28 Section 4.19 SN-3 and SN-4 Added Condition Predicate for the SN data type to identify the required order of components to be used. New condition predicate to require the 2nd component to be present if the before the 3rd and 4th components. Usage: C(RE/X) Condition Predicate: If component 2 (Numeric Value 1) is valued. 29 Section 4.19 Added conformance statement for SN data type to require the separator/suffix if both <num1> and <num2> are non-null values. CONFORMANCE STATEMENT CN-003: If <num1> and <num2> are both non-null, then the separator/suffix MUST be 30 Table 5.2.1 MSH-7 For consistent use of date/time sent in specific date/time fields the date format was updated to align with a specific level of precision to seconds. Conformance statement added for MSH-7: CONFORMANCE STATEMENT CN-006: MSH-7 (Date/Time of Message) SHALL follow the format:
PHIN_Messaging_Guide_for_Case_Notification_v3.0_Release%201_20161018.docx