| DEC-Vol1 | DEC-Vol1-001 | to be reviewed | Testable |
5
|
4
| | 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 | 10 | Table Table 2.5-1: Patient Care Device Integration Profile Dependencies | 2/26/16 10:23:28 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-001 | to be reviewed | Testable |
4
|
7
| | The Communicate PCD Data [PCD-01] transaction references the following chapters from the HL7 Version 2.6 standard: Chapter 7 Observation Reporting | 13 | Section 3.1.3 Referenced Standards | 2/26/16 10:23:29 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-002 | to be reviewed | Testable |
4
|
6
| | The Communicate PCD Data [PCD-01] transaction references the IEEE 11073-10201 Domain Information Model standard | 13 | Section 3.1.3 Referenced Standards | 2/26/16 10:23:30 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-003 | to be reviewed | Testable |
4
|
6
| | The Communicate PCD Data [PCD-01] transaction references the IEEE 11073-10101a Nomenclature standard | 13 | Section 3.1.3 Referenced Standards | 2/26/16 10:23:31 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-004 | to be reviewed | Testable |
4
|
7
| | The static definition for the PCD-01 Communicate PCD Data message is defined in the unnamed table in this section of the doument | 14 | Section 3.1.4.1.1 PCD-01 Communicate PCD Data (ORU^R01^ORU_R01) static definition | 2/26/16 10:23:32 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-005 | to be reviewed | Testable |
4
|
7
| | 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. | 14 | Section 3.1.4.1.1 PCD-01 Communicate PCD Data (ORU^R01^ORU_R01) static definition | 2/26/16 10:23:33 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-006 | to be reviewed | Testable |
4
|
4
| | The period for periodic reporting shall be several times a minute for high acuity reports and maximum interval of once every 24 hours, with a typical interval of 1 minute. | 16 | Section 3.1.4.1.2 Trigger events | 2/26/16 10:23:34 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-007 | to be reviewed | Testable |
4
|
4
| | Upon receipt of a PCD-01 message the DOC actor validates the message and shall respond with an acccept acknowledgement message as defined in Appendix G.11 Acknowledgement Modes. | 16 | Section 3.1.4.1.4 Expected Actions | 2/26/16 10:23:35 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-008 | to be reviewed | Testable |
4
|
4
| | For PCD-01 messages MSH-9 Message Type shall contain ORU^R01^ORU_R01. | 78 | Section B.1 MSH â Message Header Segment | 2/26/16 10:23:36 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-009 | to be reviewed | Testable |
4
|
6
| | 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 | 81 | Section B.1 MSH â Message Header Segment | 2/26/16 10:23:37 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-010 | to be reviewed | Testable |
4
|
6
| | For PCD-01 messages the ORC segment use is X, i.e. not sent. | 129 | Section B.9 ORC â Common Order Segment | 2/26/16 10:23:38 AM by mpattillo |
|
| DEC-Vol2 | DEC-Vol2-011 | to be reviewed | Testable |
0
|
7
| | Pulse Oximetry Integration (POI) device observations shall include an observation of oxygen saturation of blood gas as a percentage numeric data type. Given the variety of available device designs (dedicated function SPO2 monitor or modular component to a physiologic monitor), the variety of sensor capabilities, and that the observation identification can include the sense point body part, i.e. left/right arm, etc. there is no single observation definition for all devices and all use cases. Any communicated SPO2 observation shall appear in RTMMS. A non-exclusive example is 150456^MDC_PULS_OXIM_SAT_O2^MDC. | 165 | Section E.1.1 Example of PCD-01 Observation Report (Physiological Monitor) | 3/11/16 7:49:00 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-001 | to be reviewed | Testable |
12
|
9
| | OBX-3 shall be expressed as an HL7 Coded Element With Exceptions (CWE) data type | 72 | Section Appendix A Mapping ISO/IEEE 11073 Domain Information Model to HL7 | 2/28/16 8:44:27 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-002 | to be reviewed | Testable |
12
|
9
| | OBX-4 shall be expressed as the containment level of a particular item expressed in OBX-3 | 72 | Section Appendix A Mapping ISO/IEEE 11073 Domain Information Model to HL7 | 2/28/16 8:44:34 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-003 | to be reviewed | Testable |
12
|
10
| | 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. | 73 | Section Appendix A Mapping ISO/IEEE 11073 Domain Information Model to HL7 | 2/28/16 8:44:35 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-004 | to be reviewed | Testable |
12
|
9
| | Source for nomenclature codes is IEEE 11073-10101 current version. Additional codes not yet standardized are contained in the RTMMS | 75 | Section A.1 ISO/IEEE Nomenclature mapping to HL7® OBX-3 | 2/28/16 8:44:39 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-005 | to be reviewed | Testable |
12
|
10
| | Periodic versus aperiodic data shall be distinguished by the IEEE 11073 Metric Access code in OBX-17 | 75 | Section A.1 ISO/IEEE Nomenclature mapping to HL7® OBX-3 | 2/28/16 8:44:40 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-006 | to be reviewed | Testable |
12
|
11
| | The value in MSH-2 Encoding Characters shall be ^~\& | 77 | Section B.1 MSH â Message Header Segment | 2/28/16 8:44:42 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-007 | to be reviewed | Testable |
12
|
11
| | MSH-3 Sending Application shall uniquely identify the software application implementing the actor sending the message | 77 | Section B.1 MSH â Message Header Segment | 2/28/16 8:44:43 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-008 | to be reviewed | Testable |
12
|
11
| | 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 | 77 | Section B.1 MSH â Message Header Segment | 2/28/16 8:44:44 AM by mpattillo |
|