22 Section Update CWE, CE-PH, Component 1: “Standard 4.1, 4.2, and CE data types to coding system identifier must 4.4 include reference to be used.” using standard codes for Component 3: “Standard component 1. Also coding system identifiers or added the reference to OIDs MAY be sent for Coding OIDs MAY be used for Systems, both are supported.” component 3. 23 Section Added wording for CWE It is strongly recommended that 4.2, 4.4 and CE-PH text text SHOULD be sent to component 2 to indicate accompany any identifier. recommendations to send text and bolded key words, to be consistent with intended usage across CE and CWE data types. 24 Section Update wording for Component 1, Component 4 4.1, 4.2, CWE, CE-PH, and CE 4.4 data types to use and “component” removed CE or CWE. For consistency and clarification. 25 Section 4.7 Correction to example |199503| specifies March 1995. for incorrect date for DT (date) data type. Removed “April 1999”. 26 Section 4.8 Corrected example date time format. “Example: |199904| specifies April 1999. Format:
22 Section 4.1, 4.2, 4.4 Update CWE, CE-PH, and CE data types to include reference to using standard codes for component 1. Also added the reference to OIDs MAY be used for component 3. Component 1: “Standard coding system identifier must be used.” Component 3: “Standard coding system identifiers or OIDs MAY be sent for Coding Systems, both are supported.” 23 Section 4.2, 4.4 Added wording for CWE and CE-PH text component 2 to indicate recommendations to send text and bolded key words, to be consistent with intended usage across CE and CWE data types. It is strongly recommended that text SHOULD be sent to accompany any identifier. 24 Section 4.1, 4.2, 4.4 Update wording for CWE, CE-PH, and CE data types to use “component” and removed CE or CWE. For consistency and clarification. Component 1, Component 4 25 Section 4.7 Correction to example for incorrect date for DT (date) data type. Removed “April 1999”. |199503| specifies March 1995. 26 Section 4.8 Corrected example date time format. “Example: |199904| specifies April 1999. Format:
PHIN_Messaging_Guide_for_Case_Notification_v3.0_Release%201_20161018.docx