| DEC-Vol1-001 | Each actor implementing this Patient Care Device (PCD) profile shall be grouped with the IT Infrastructure Consistent Time profile Time Client Actor for the purpose of consistent time-stamping of messages and data |
| DEC-Vol2-001 | The Communicate PCD Data [PCD-01] transaction references the following chapters from the HL7 Version 2.6 standard: Chapter 7 Observation Reporting |
| DEC-Vol2-002 | The Communicate PCD Data [PCD-01] transaction references the IEEE 11073-10201 Domain Information Model standard |
| DEC-Vol2-003 | The Communicate PCD Data [PCD-01] transaction references the IEEE 11073-10101a Nomenclature standard |
| DEC-Vol2-004 | The static definition for the PCD-01 Communicate PCD Data message is defined in the unnamed table in this section of the doument |
| DEC-Vol2-005 | The PCD-01 message structure differs from the basic HL7 version 2.6 by allowing for the appearance of PRT segments, a segment new in HL7 version 2.7, in certain locations. |
| DEC-Vol2-009 | Device to Enterprise Communications PCD-01 Communicate PCD Data message (also used for observations in response to a PCD-02 PCD Data Query) shall contain in MSH-21 Message Profile Identifier the value 1.3.6.1.4.1.19376.1.6.1.1.1 |
| DEC-Vol2-010 | For PCD-01 messages the ORC segment use is X, i.e. not sent. |
| PCD-Vol2-001 | OBX-3 shall be expressed as an HL7 Coded Element With Exceptions (CWE) data type |
| 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 |