net.ihe.gazelle.assets.SearchCriteria : 245 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 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 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-006to be reviewedTestable 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.16Section 3.1.4.1.2 Trigger events2/26/16 10:23:34 AM by mpattillo
DEC-Vol2DEC-Vol2-007to be reviewedTestable 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.16Section 3.1.4.1.4 Expected Actions2/26/16 10:23:35 AM by mpattillo
DEC-Vol2DEC-Vol2-008to be reviewedTestable 4 4 For PCD-01 messages MSH-9 Message Type shall contain ORU^R01^ORU_R01.78Section B.1 MSH – Message Header Segment2/26/16 10:23:36 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
ITI38ITI38-001reviewedTestable 1 1 Initiating Gateway shall specify the homeCommunityId attribute in all Cross-Community Queries which do not contain a patient identifier.125Section 3.38.19/17/19 11:53:27 AM by aeschlimann
ITI38ITI38-003reviewedTestable 1 1 The homeCommunityId attribute is required on the Cross Gateway Query127Section 3.38.4.1.2.19/17/19 11:53:41 AM by aeschlimann
ITI38ITI38-004reviewedTestable 1 2 homeCommunityId is structured as an OID limited to 64 characters and specified in URI syntax127Section 3.38.4.1.2.19/17/19 11:53:44 AM by aeschlimann
ITI38ITI38-005reviewedTestable 1 1 The Initiating Gateway shall specify the homeCommunityId parameter within all queries which do not include a patient identifier parameter.127Section 3.38.4.1.2.19/17/19 11:53:47 AM by aeschlimann
ITI38ITI38-006reviewedTestable 1 1 Each Cross Gateway Query request can have at most one homeCommunityId value.127Section 3.38.4.1.2.19/17/19 11:53:51 AM by aeschlimann
ITI38ITI38-007reviewedTestable 1 1 If multiple entryUUID or uniqueID values are specified they must all be associated with the same homeCommunityId value127Section 3.38.4.1.2.19/17/19 11:53:58 AM by aeschlimann
ITI38ITI38-008reviewedTestable 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.128Section 3.38.4.1.2.29/17/19 11:54:29 AM by aeschlimann
ITI38ITI38-009reviewedTestable 1 1 FindDocuments Stored Query is required for Responding Gateway128Section 3.38.4.1.2.39/17/19 11:54:18 AM by aeschlimann
ITI38ITI38-010reviewedTestable 1 1 GetDocuments Stored Query is required for Responding Gateway128Section 3.38.4.1.2.39/17/19 11:54:20 AM by aeschlimann