| PCD-Vol2-001 | OBX-3 shall be expressed as an HL7 Coded Element With Exceptions (CWE) data type |
| PCD-Vol2-002 | OBX-4 shall be expressed as the containment level of a particular item expressed in OBX-3 |
| PCD-Vol2-003 | Ordinal numbers in OBX-4 are not normative for a given parameter and may vary between implementations. They shall be unique within a given containment, however, numbers may change between messages. |
| PCD-Vol2-004 | Source for nomenclature codes is IEEE 11073-10101 current version. Additional codes not yet standardized are contained in the RTMMS |
| PCD-Vol2-005 | Periodic versus aperiodic data shall be distinguished by the IEEE 11073 Metric Access code in OBX-17 |
| PCD-Vol2-006 | The value in MSH-2 Encoding Characters shall be ^~\& |
| PCD-Vol2-007 | MSH-3 Sending Application shall uniquely identify the software application implementing the actor sending the message |
| PCD-Vol2-008 | If MSH-4 Sending Facility is populated, the first component shall identify the organizational entity responsible for sending the message, the second component if present shall identify the Universal ID of the organizational entity responsible for the sender of the message, the third component if present shall identify the Universal ID Type |
| PCD-Vol2-009 | If MSH-5 Receiving Application is populated, the first component shall identify the organizational entity responsible for receiving the message, the second component if present shall identify the Universal ID of the organizational entity responsible for the sender of the message, the third component if present shall identify the Universal ID Type. |
| PCD-Vol2-010 | If MSH-6 Receiving Facility is populated, the first component shall identify the organizational entity responsible for the receiving facility, the second component if present shall identify the Universal ID of the organizational entity responsible for the sender of the message, the third component if present shall identify the Universal ID Type |
| PCD-Vol2-011 | In MSH-7 Date/Time of Message time zone shall be included in the field content |
| PCD-Vol2-012 | In field MSH-11 Processing ID, the first component shall be present and be a value based upon HL7 Table 0103. The second component if present shall be a value based upon HL7 Table 0207. |
| PCD-Vol2-013 | Field MSH-12 Version ID shall contain 2.6 |
| PCD-Vol2-014 | If MSH-17 County Code is present it shall contain a three Character alphabetic value from ISO 3166 |
| PCD-Vol2-015 | For MSH-18 Character Set, if the character set is ASCII then the field can be empty, or shall contain the value ASCII. If the character set is other than ASCII the field shall contain a value from HL7 Table 0211 |
| PCD-Vol2-016 | For MSH-19 Principal Language of Message if the field is empty then en^English^ISO639 is assumed. If present the value shall be from ISO 639. |
| PCD-Vol2-017 | If PID-13 Phone Number - Home is present the field is constrained to a maximum of two repetitions to allow for a phone number and an e-mail address. |
| PCD-Vol2-018 | If PID-15 Primary Language is populated the value shall be from ISO 639. |
| PCD-Vol2-020 | In field OBR-2 Placer Order Number the first component shall be populated with the Entity Identifier (EI-1). If the third and fourth components are populated with the Universal ID (EI-3) and the Universal ID type (EI-4) then the second component namespace ID (EI-2) is not required to be present else it shall be required to be present. |
| PCD-Vol2-021 | For field OBR-3 Filler Order Number the Universal ID (EI-3) and Universal ID Type (EI-4) components shall be populated. |