| 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 |
|
| ITI38 | ITI38-001 | reviewed | Testable |
1
|
1
| | Initiating Gateway shall specify the homeCommunityId attribute in all Cross-Community Queries which do not contain a patient identifier. | 125 | Section 3.38.1 | 9/17/19 11:53:27 AM by aeschlimann |
|
| ITI38 | ITI38-003 | reviewed | Testable |
1
|
1
| | The homeCommunityId attribute is required on the Cross Gateway Query | 127 | Section 3.38.4.1.2.1 | 9/17/19 11:53:41 AM by aeschlimann |
|
| ITI38 | ITI38-004 | reviewed | Testable |
1
|
2
| | homeCommunityId is structured as an OID limited to 64 characters and specified in URI syntax | 127 | Section 3.38.4.1.2.1 | 9/17/19 11:53:44 AM by aeschlimann |
|
| ITI38 | ITI38-005 | reviewed | Testable |
1
|
1
| | The Initiating Gateway shall specify the homeCommunityId parameter within all queries which do not include a patient identifier parameter. | 127 | Section 3.38.4.1.2.1 | 9/17/19 11:53:47 AM by aeschlimann |
|
| ITI38 | ITI38-006 | reviewed | Testable |
1
|
1
| | Each Cross Gateway Query request can have at most one homeCommunityId value. | 127 | Section 3.38.4.1.2.1 | 9/17/19 11:53:51 AM by aeschlimann |
|
| ITI38 | ITI38-007 | reviewed | Testable |
1
|
1
| | If multiple entryUUID or uniqueID values are specified they must all be associated with the same homeCommunityId value | 127 | Section 3.38.4.1.2.1 | 9/17/19 11:53:58 AM by aeschlimann |
|
| ITI38 | ITI38-008 | reviewed | Testable |
2
|
1
| | If the patient identifier is unknown by the Responding Gateway’s community, the Responding Gateway shall return either a successful response with no elements or an error with errorCode XDSUnknownPatientId, depending on local policy. | 128 | Section 3.38.4.1.2.2 | 9/17/19 11:54:29 AM by aeschlimann |
|
| ITI38 | ITI38-009 | reviewed | Testable |
1
|
1
| | FindDocuments Stored Query is required for Responding Gateway | 128 | Section 3.38.4.1.2.3 | 9/17/19 11:54:18 AM by aeschlimann |
|
| ITI38 | ITI38-010 | reviewed | Testable |
1
|
1
| | GetDocuments Stored Query is required for Responding Gateway | 128 | Section 3.38.4.1.2.3 | 9/17/19 11:54:20 AM by aeschlimann |
|