Search Criteria : 35 assertions found for this search Review filtered assertions

Assertion

Applies to

Applied to
Not applied to

Coverage

Covered by
Not covered by
Id scheme
Assertion id
Status
Testable?
#Coverage
#Applies to
Comment
Predicate
Page
Tags
Last changed
Actions
DEC-Vol1DEC-Vol1-001to be reviewedTestable 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 data10Table Table 2.5-1: Patient Care Device Integration Profile Dependencies2/26/16 10:23:28 AM by mpattillo
DEC-Vol2DEC-Vol2-001to be reviewedTestable 4 7 The Communicate PCD Data [PCD-01] transaction references the following chapters from the HL7 Version 2.6 standard: Chapter 7 Observation Reporting13Section 3.1.3 Referenced Standards2/26/16 10:23:29 AM by mpattillo
DEC-Vol2DEC-Vol2-002to be reviewedTestable 4 6 The Communicate PCD Data [PCD-01] transaction references the IEEE 11073-10201 Domain Information Model standard13Section 3.1.3 Referenced Standards2/26/16 10:23:30 AM by mpattillo
DEC-Vol2DEC-Vol2-003to be reviewedTestable 4 6 The Communicate PCD Data [PCD-01] transaction references the IEEE 11073-10101a Nomenclature standard13Section 3.1.3 Referenced Standards2/26/16 10:23:31 AM by mpattillo
DEC-Vol2DEC-Vol2-004to be reviewedTestable 4 7 The static definition for the PCD-01 Communicate PCD Data message is defined in the unnamed table in this section of the doument14Section 3.1.4.1.1 PCD-01 Communicate PCD Data (ORU^R01^ORU_R01) static definition2/26/16 10:23:32 AM by mpattillo
DEC-Vol2DEC-Vol2-005to be reviewedTestable 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.14Section 3.1.4.1.1 PCD-01 Communicate PCD Data (ORU^R01^ORU_R01) static definition2/26/16 10:23:33 AM by mpattillo
DEC-Vol2DEC-Vol2-009to be reviewedTestable 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.181Section B.1 MSH – Message Header Segment2/26/16 10:23:37 AM by mpattillo
DEC-Vol2DEC-Vol2-010to be reviewedTestable 4 6 For PCD-01 messages the ORC segment use is X, i.e. not sent.129Section B.9 ORC – Common Order Segment2/26/16 10:23:38 AM by mpattillo
PCD-Vol2PCD-Vol2-001to be reviewedTestable 12 9 OBX-3 shall be expressed as an HL7 Coded Element With Exceptions (CWE) data type 72Section Appendix A Mapping ISO/IEEE 11073 Domain Information Model to HL72/28/16 8:44:27 AM by mpattillo
PCD-Vol2PCD-Vol2-003to be reviewedTestable 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.73Section Appendix A Mapping ISO/IEEE 11073 Domain Information Model to HL72/28/16 8:44:35 AM by mpattillo
PCD-Vol2PCD-Vol2-004to be reviewedTestable 12 9 Source for nomenclature codes is IEEE 11073-10101 current version. Additional codes not yet standardized are contained in the RTMMS75Section A.1 ISO/IEEE Nomenclature mapping to HL7® OBX-32/28/16 8:44:39 AM by mpattillo
PCD-Vol2PCD-Vol2-005to be reviewedTestable 12 10 Periodic versus aperiodic data shall be distinguished by the IEEE 11073 Metric Access code in OBX-1775Section A.1 ISO/IEEE Nomenclature mapping to HL7® OBX-32/28/16 8:44:40 AM by mpattillo
PCD-Vol2PCD-Vol2-006to be reviewedTestable 12 11 The value in MSH-2 Encoding Characters shall be ^~\&77Section B.1 MSH – Message Header Segment2/28/16 8:44:42 AM by mpattillo
PCD-Vol2PCD-Vol2-007to be reviewedTestable 12 11 MSH-3 Sending Application shall uniquely identify the software application implementing the actor sending the message77Section B.1 MSH – Message Header Segment2/28/16 8:44:43 AM by mpattillo
PCD-Vol2PCD-Vol2-008to be reviewedTestable 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 Type77Section B.1 MSH – Message Header Segment2/28/16 8:44:44 AM by mpattillo
PCD-Vol2PCD-Vol2-009to be reviewedTestable 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.77Section B.1 MSH – Message Header Segment2/28/16 8:44:45 AM by mpattillo
PCD-Vol2PCD-Vol2-010to be reviewedTestable 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 Type78Section B.1 MSH – Message Header Segment2/28/16 8:45:16 AM by mpattillo
PCD-Vol2PCD-Vol2-011to be reviewedTestable 12 11 In MSH-7 Date/Time of Message time zone shall be included in the field content78Section B.1 MSH – Message Header Segment2/28/16 8:45:18 AM by mpattillo
PCD-Vol2PCD-Vol2-012to be reviewedTestable 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.79Section B.1 MSH – Message Header Segment2/28/16 8:45:19 AM by mpattillo
PCD-Vol2PCD-Vol2-013to be reviewedTestable 12 11 Field MSH-12 Version ID shall contain 2.679Section B.1 MSH – Message Header Segment2/28/16 8:45:20 AM by mpattillo