| 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-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 |
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 |
|
| ITI30 | ITI30-001 | validated | Testable |
2
|
2
| | Systems which claim support of the Merge option for the Patient Administration Management profile shall support the following messages: Create new patient, Update patient information, Change patient identifier list, Merge two patients | 13 | Section 3.30.4.1 | 4/4/16 12:18:08 PM by aberge |
|
| ITI30 | ITI30-002 | validated | Testable |
2
|
2
| | Systems which claim support of the Link/Unlink option for the Patient Administration Management profile shall support the following messages: Create new patient, Update patient information, Change patient identifier list, Link patient information Unlink patient information | 13 | Section 3.30.4.2 | 4/4/16 12:16:35 PM by aberge |
|
| ITI31 | ITI31-004 | validated | Testable |
2
|
2
| | Both the Patient Encounter Supplier and Patient Encounter Consumer actors shall be able to cancel only a current movement. | 43 | Section 3.31.4 | 4/4/16 12:24:34 PM by aberge |
|
| ITI31 | ITI31-005 | validated | Testable |
2
|
1
| | A system implementing either Patient Encounter Supplier or Patient Encounter Consumer, shall support these 5 trigger events:
Admit inpatient, Discharge patient, Register outpatient, Cancel admit/visit, Cancel discharge | 44 | Figure 3.31-1 | 4/4/16 12:24:36 PM by aberge |
|
| ITI31 | ITI31-006 | validated | Testable |
2
|
2
| | A system implementing Inpatient/Outpatient encounter management option shall support the 11 trigger events and messages defined in table 3.31-2. | 45 | Table 3.31-2 | 4/4/16 12:26:39 PM by aberge |
|
| ITI31 | ITI31-009 | validated | Testable |
2
|
2
| | A system implementing Advanced Encounter Management Option shall support the12 trigger events and messages defined in table 3.31-4 | 47 | Table 3-31-4 | 4/4/16 12:31:47 PM by aberge |
|
| ITI31 | ITI31-012 | validated | Testable |
4
|
2
| | The ZBE segment is required for the following trigger events : A01, A02, A03, A04, A05, A06, A07, A11, A12, A13, A14, A15, A16, A21, A22, A25, A26, A27, A38, A52, A53, A54, A55, Z99 if the historic movement management option is supported | 49 | Section 3.31.5.6 | 4/4/16 12:25:24 PM by aberge |
|
| ITI31 | ITI31-015 | validated | Testable |
2
|
1
| | A Patient Encounter Supplier or Patient Encounter Consumer supporting the Maintain Demographics Option shall support these 7 trigger events and messages :
Admit inpatient, register outpatient, discharge patient, update patient information, merge patient identifier list, Cancel admission, Cancel Discharge | 51 | Section 3.31.5.9 | 4/4/16 12:27:29 PM by aberge |
|