Search Criteria : 28 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
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-002to be reviewedTestable 12 9 OBX-4 shall be expressed as the containment level of a particular item expressed in OBX-372Section Appendix A Mapping ISO/IEEE 11073 Domain Information Model to HL72/28/16 8:44:34 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
PCD-Vol2PCD-Vol2-014to be reviewedTestable 12 11 If MSH-17 County Code is present it shall contain a three Character alphabetic value from ISO 316680Section B.1 MSH – Message Header Segment2/28/16 8:45:20 AM by mpattillo
PCD-Vol2PCD-Vol2-015to be reviewedTestable 12 11 For MSH-18 Character Set, if the character set is ASCII then the field can be empty, or shall contain the value ASCII. If the character set is other than ASCII the field shall contain a value from HL7 Table 021180Section B.1 MSH – Message Header Segment2/28/16 8:45:21 AM by mpattillo
PCD-Vol2PCD-Vol2-016to be reviewedTestable 12 11 For MSH-19 Principal Language of Message if the field is empty then en^English^ISO639 is assumed. If present the value shall be from ISO 639.81Section B.1 MSH – Message Header Segment2/28/16 8:45:22 AM by mpattillo
PCD-Vol2PCD-Vol2-017to be reviewedTestable 12 10 If PID-13 Phone Number - Home is present the field is constrained to a maximum of two repetitions to allow for a phone number and an e-mail address.89Section B.5 PID - Patient Identification segment2/28/16 8:45:24 AM by mpattillo
PCD-Vol2PCD-Vol2-018to be reviewedTestable 12 10 If PID-15 Primary Language is populated the value shall be from ISO 639.90Section B.5 PID - Patient Identification segment2/28/16 8:45:26 AM by mpattillo
PCD-Vol2PCD-Vol2-019to be reviewedTestable 12 8 If PV1-51 Visit Indicator is populated the value shall be either A or V. The absence of a value implies A.96Section B.6 PV1 - Patient Visit Segment2/28/16 8:45:28 AM by mpattillo
PCD-Vol2PCD-Vol2-020to be reviewedTestable 12 10 In field OBR-2 Placer Order Number the first component shall be populated with the Entity Identifier (EI-1). If the third and fourth components are populated with the Universal ID (EI-3) and the Universal ID type (EI-4) then the second component namespace ID (EI-2) is not required to be present else it shall be required to be present.98Section B.7 OBR – Observation Request segment2/28/16 8:45:30 AM by mpattillo