<strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Device</strong> <strong>Technical</strong> <strong>Framework</strong>, Vol. 2: Transactions________________________________________________________________________..[{NK1}] Next of Kin/Associated Parties X [0..0] 3[ --- VISIT beginPV1 <strong>Patient</strong> Visit O [0..1] 3[PV2] <strong>Patient</strong> Visit – Additional Info X [0..0] 3] --- VISIT end] --- PATIENT end{ ---ORDER_OBSERVATION begin[ORC] Order Common X [0..0] 4OBR Observation Request R [1..1] 7[{NTE}] Notes and Comments O [0..1] 2[{ --- TIMING_QTY beginTQ1 Timing/Quantity O [0..1] 4[{TQ2}] Timing/Quantity Order Sequence X 4{] --- TIMING_QTY end[CTD] Contact Data X [0..0] 11[{ --- OBSERVATION beginOBX Observation Result R [1..1] 7[{NTE}] Notes and comments 2}] --- OBSERVATION end[{FT1}] Financial Transaction X [0..0] 6[{CTI}] Clinical Trial Identification X [0..0] 7[{ --- SPECIMEN beginSPM Specimen X [0..0] 7[{OBX}] Observation related to Specimen X [0..0] 7}] --- SPECIMEN end} --- ORDER_OBSERVATION end} --- PATIENT_RESULT end[DSC] Continuation Pointer X [0..0] 23.1.7.1 Trigger eventsThe ORU^R01_ORU_R01 message is an unsolicited update. An application whichimplements the DOR receives data from one or more PCDs using either standards basedor proprietary protocols which are outside the current scope of the <strong>IHE</strong> PCD TF.In general, the DOR sends periodic reports at a minimum interval of 10 seconds (highacuity) and a maximum interval of 24 hours (chronic, home health) with a typical intervalof 1 minute. The minimum and maximum intervals are configured at implementation.Rev. 1.1 TI: 2006-08-1517Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA
<strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Device</strong> <strong>Technical</strong> <strong>Framework</strong>, Vol. 2: Transactions________________________________________________________________________The DOR may also send aperiodic reports for "event type” information. The DOR doesnot do interpolation of data received from the PCD source.The DOF receives messages from the DOR and provides the same capabilities as theDOR regarding sending of reports. The DOR adds the service of filtering the messagestream based on a predicate negotiated at run-time.3.1.7.2 Message Semantics10Refer to the HL7 standard for the ORU message of HL7 2.5 Chapter 7 and the generalmessage semantics.The ORU^OR1^ORU_R01 message structure provides the mechanisms for mapping thehierarchical structure of an IEEE 11073 containment tree to a series of OBX messageseach of which is optionally qualified by an a note which immediately follows therespective OBX.See Appendix A ISO/IEEE Nomenclature mapping to HL7 OBX-3 for furtherinformation on the mapping rules.Examples of ORU^R01^ORU_R01 messages implemented in both HL7 ER and XMLare provided in Appendix E Examples of messages.3.1.7.3 Expected Action20The ORU^R01^ORU_R01 message is sent from the DOR to the DOC, DOF, or both.Upon receipt the DOC and DOF validate the message and respond with anacknowledgement as defined in Appendix G.2 Acknowledgment Modes.3.2 Transaction PCD-02 Subscribe to PCD Data30This section corresponds to Transaction PCD-02 of the <strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Device</strong><strong>Technical</strong> <strong>Framework</strong>. Transaction PCD-02 is used by the <strong>Device</strong> Observation Filter, and<strong>Device</strong> Observation Consumer actors.Common HL7 segments (MSH, MSA, ERR, NTE, PID, PV1, OBR, OBX, QPD, RCP)and data types (CE, CX, EI, HD, PL, TS, XPN, XTN) used in <strong>IHE</strong> PCD transactions aredefined in Appendix B Common Message Segments for the <strong>Patient</strong> <strong>Care</strong> <strong>Device</strong><strong>Technical</strong> <strong>Framework</strong> and Appendix C Common Data Types.3.2.1 ScopeThis transaction is used by a <strong>Device</strong> Observation Consumer (DOC) to subscribe for PCDData from a <strong>Device</strong> Observation Filter (DOF).Rev. 1.1 TI: 2006-08-1518Copyright © 2005-2006: ACC, ACCE, HIMSS, and RSNA