Standard details

Keyword: HL7v2.6

Name: HL7 Version 2.6

Version: 2.6

URL

Network Communication Type HL7v2

Assertion Id	Description
DEC-Vol2-001	The Communicate PCD Data [PCD-01] transaction references the following chapters from the HL7 Version 2.6 standard: Chapter 7 Observation Reporting
DEC-Vol2-004	The static definition for the PCD-01 Communicate PCD Data message is defined in the unnamed table in this section of the doument
DEC-Vol2-005	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.
DEC-Vol2-006	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.
DEC-Vol2-007	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.
DEC-Vol2-008	For PCD-01 messages MSH-9 Message Type shall contain ORU^R01^ORU_R01.
DEC-Vol2-009	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
DEC-Vol2-010	For PCD-01 messages the ORC segment use is X, i.e. not sent.
DEC-Vol2-011	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.
PCD-Vol2-002	OBX-4 shall be expressed as the containment level of a particular item expressed in OBX-3
PCD-Vol2-003	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.
PCD-Vol2-005	Periodic versus aperiodic data shall be distinguished by the IEEE 11073 Metric Access code in OBX-17
PCD-Vol2-006	The value in MSH-2 Encoding Characters shall be ^~\&
PCD-Vol2-007	MSH-3 Sending Application shall uniquely identify the software application implementing the actor sending the message
PCD-Vol2-008	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 Type
PCD-Vol2-009	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.
PCD-Vol2-010	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 Type
PCD-Vol2-011	In MSH-7 Date/Time of Message time zone shall be included in the field content
PCD-Vol2-012	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.
PCD-Vol2-013	Field MSH-12 Version ID shall contain 2.6

List standards