Chapter 07: Observation Reporting
This chapter covers results sent back to the system that asked for them. It defines how lab values, vital signs, imaging reports and device readings travel.
This chapter covers results. A result is anything measured or observed about a patient: a lab value, a vital sign, an imaging report or a device reading. The main message type is ORU, which sends a result without a request. Each result travels in an OBX segment. The OBR segment above it says what was ordered and when. Most clinical data in HL7 v2 passes through this chapter.
What is in this chapter
- 16 trigger eventsthe real-world things that cause one of these messages to be sent
- 12 segmentsthe lines these messages are built from, and the fields on each
- 42 code tablesthe value sets the fields in this chapter draw from
- 8 message typesCRM, CSU, ORF, ORL, ORU, OUL, PEX, SUR
Message types defined here
CRMClinical study registration message1 structure, fired by 0 trigger events.
CSUUnsolicited study data message1 structure, fired by 0 trigger events.
ORFQuery for results of observation1 structure, fired by 1 trigger event.
ORLLaboratory acknowledgment message (unsolicited)3 structures, fired by 3 trigger events.
ORUUnsolicited transmission of an observation message2 structures, fired by 4 trigger events.
OULUnsolicited laboratory observation message4 structures, fired by 4 trigger events.
PEXProduct experience message1 structure, fired by 1 trigger event.
SURSummary product experience report1 structure, fired by 1 trigger event.
Segments defined here
These 12 segments are defined in chapter 07. Messages in other chapters may still carry them.
CSPClinical Study Phase SegmentCSRClinical Study Registration SegmentCSSClinical Study Data Schedule SegmentCTIClinical Trial Identification SegmentFACFacilityOBXObservation/Result SegmentPCRPossible Causal Relationship SegmentPDCProduct Detail Country SegmentPEOProduct Experience Observation SegmentPESProduct Experience SenderPSHProduct Summary Header SegmentSPMSpecimen Segment
Trigger events
A trigger event is the thing that happens in the hospital and causes a message to be sent. Chapter 07 defines 16 of them.
C01Register a patient on a clinical trialC09Automated time intervals for reporting, like monthlyO22general laboratory order response message to any OMLO34Laboratory order response message to a multiple order related to single specimen OMLO36Laboratory order response message to a single container of a specimen OMLP07Unsolicited initial individual product experience reportP09Summary Product Experience ReportR01Unsolicited Observation MessageR04Response to query; transmission of requested observationR21Unsolicited Laboratory Observation MessageR22Unsolicited Specimen Oriented Observation Message –R23Unsolicited Specimen Container Oriented Observation MessageR24Unsolicited Order Oriented Observation Message –R30Unsolicited Point-Of-Care Observation Message Without Existing Order - Place An OrderR31Unsolicited New Point-Of-Care Observation Message - Search For An OrderR32Unsolicited Pre-Ordered Point-Of-Care Observation