| 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 |
|
| ITI10 | ITI10-001 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager shall notify a Patient Identifier Cross-reference Consumer when there is a change in a set of cross-referenced patient identifiers for any of the patient identifiers belonging to Patient Identifier Domains of interest to the consumer. | 69 | Section 3.9.4.1.1 | 4/4/16 4:12:59 PM by aberge |
|
| ITI10 | ITI10-003 | validated | Testable |
0
|
1
| | The information provided by the Patient Identifier Cross-reference Manager to Patient Identifier Cross-reference Consumers shall only contain a list of cross-referenced identifiers for the domains of interest as configured with the Patient Identifier Cross-reference Manager in two or more of the domains managed by the Patient Identifier Cross-reference Manager. | 70 | Section 3.10.4.1.2 | 4/4/16 4:13:12 PM by aberge |
|
| ITI10 | ITI10-008 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager configuration is expected to have configuration indicating which Consumers are interested in receiving the PIX Update Notification transactions. This configuration information shall include identification of the identity consumer systems interested in receiving notifications and, for each of those systems, a list of the patient identifier domains of interest. | 70 | Section 3.10.4.1.2 | 4/4/16 4:13:37 PM by aberge |
|
| ITI10 | ITI10-011 | validated | Testable |
0
|
1
| | Each ITI-10 message shall be acknowledged by the HL7 ACK message sent by the receiver of ADT message to its sender. Acknowledgement shall respect ITI TF-2x C.2.3. | 71 | Section 3.10.4.1.2 | 4/4/16 4:14:20 PM by aberge |
|
| ITI10 | ITI10-014 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager Actor shall provide only those attributes within the PID segment that are required by the HL7 standard: PID-3-Patient Identifier List and PID-5-Patient Name. | 71 | Section 3.10.4.1.2.3 | 4/4/16 4:15:25 PM by aberge |
|
| ITI10 | ITI10-015 | validated | Testable |
0
|
1
| | The Patient Identifier Cross-reference Manager Actor shall use the field PID-3 Patient Identifier List to convey the Patient IDs uniquely identifying the patient within each Patient Identification Domain for which a Patient ID exists for the specified patient. Each resulting ID returned in PID-3 shall include a fully qualified Assigning Authority component. In other words, the Assigning Authority component returned shall include ALL subcomponents (namespace ID, Universal ID, and Universal ID type). | 71 | Section 3.10.4.1.2.3 | 4/4/16 4:16:11 PM by aberge |
|
| ITI10 | ITI10-016 | validated | Testable |
0
|
1
| | To eliminate the issue of multiple name values between Patient Identifier Domains, the Patient Identifier Cross-reference Manager Actor shall return a single space character in field PID-5-Patient Name. | 71 | Section 3.10.4.1.2.3 | 4/4/16 4:16:23 PM by aberge |
|
| ITI10 | ITI10-017 | validated | Testable |
0
|
1
| | A single PID segment is sent in which one repetition of PID-3-Patient Identifier List is populated for each of the identifiers in the notification. If the Patient Identifier Cross-reference Manager Actor chooses to send multiple identifiers associated with the same domain, it shall return these identifiers grouped in successive repetitions within the PID-3-Patient Identifier List. | 72 | Section 3.10.4.1.2.3 | 4/4/16 4:16:30 PM by aberge |
|