| DEC-Vol1 | DEC-Vol1-001 | to be reviewed | Testable |
6
|
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-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-011 | to be reviewed | Testable |
2
|
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-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 |
|
| PCD-Vol2 | PCD-Vol2-009 | to be reviewed | Testable |
12
|
11
| | 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. | 77 | Section B.1 MSH â Message Header Segment | 2/28/16 8:44:45 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-010 | to be reviewed | Testable |
12
|
11
| | 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 | 78 | Section B.1 MSH â Message Header Segment | 2/28/16 8:45:16 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-011 | to be reviewed | Testable |
12
|
11
| | In MSH-7 Date/Time of Message time zone shall be included in the field content | 78 | Section B.1 MSH â Message Header Segment | 2/28/16 8:45:18 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-012 | to be reviewed | Testable |
12
|
11
| | 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. | 79 | Section B.1 MSH â Message Header Segment | 2/28/16 8:45:19 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-013 | to be reviewed | Testable |
12
|
11
| | Field MSH-12 Version ID shall contain 2.6 | 79 | Section B.1 MSH â Message Header Segment | 2/28/16 8:45:20 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-014 | to be reviewed | Testable |
12
|
11
| | If MSH-17 County Code is present it shall contain a three Character alphabetic value from ISO 3166 | 80 | Section B.1 MSH â Message Header Segment | 2/28/16 8:45:20 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-015 | to be reviewed | Testable |
12
|
11
| | 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 | 80 | Section B.1 MSH â Message Header Segment | 2/28/16 8:45:21 AM by mpattillo |
|
| PCD-Vol2 | PCD-Vol2-016 | to be reviewed | Testable |
12
|
11
| | 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. | 81 | Section B.1 MSH â Message Header Segment | 2/28/16 8:45:22 AM by mpattillo |
|