Schedule a demo
Message type

Laboratory order for additional work up

Requests additional laboratory work-up on a previously collected specimen. The ORC and OBR segments define the add-on order, and SPM references the existing specimen.

66segments
19required
9groups
v2.9HL7 version
oml-o59.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'OML^O59^OML_O59|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'OBR|1||ORD001'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
order_control = msg.orc.order_control
order_number = msg.orc.placer_order_number
order_id = msg.obr.placer_order_number
test = msg.obr.universal_service_identifier

Build and parse OML^O59 messages in Python

How to construct, send, receive, and extract fields from real-world OML^O59 messages.

1

Parse an incoming OML^O59 message

Demonstrates receiving and extracting key fields from a laboratory order for additional work up transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'OML^O59^OML_O59|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'OBR|1||ORD001'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
order_control = msg.orc.order_control
order_number = msg.orc.placer_order_number
order_id = msg.obr.placer_order_number
test = msg.obr.universal_service_identifier

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

Frequently asked questions

Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.

from zato.hl7v2 import HL7Message

raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||OML^O59^OML_O59|MSG00001|P|2.9'
msg = HL7Message.parse(raw)

order_control = msg.orc.order_control
order_number = msg.orc.placer_order_number

Beyond the mandatory MSH header, the required segments are: PID, PV1, IN1, ORC, TQ1, OBR, OBX, SPM. Optional segments provide additional detail when available.

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.

OML^O59 segment composition

Segments that make up the OML^O59 message, in order. Groups are shown with their child segments.

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5NTEOptionalYesNotes and comments-
6PIDRequiredNoPatient identificationPATIENT
7PD1OptionalNoPatient additional demographicPATIENT
8PRTOptionalYesParticipation informationPATIENT
9NTEOptionalYesNotes and commentsPATIENT
10NK1OptionalYesNext of kin / associated partiesPATIENT
11PV1RequiredNoPatient visitPATIENT
12PV2OptionalNoPatient visit - additional infoPATIENT
13PRTOptionalYesParticipation informationPATIENT
14IN1RequiredNoInsurancePATIENT
15IN2OptionalNoInsurance additional infoPATIENT
16IN3OptionalNoInsurance additional info - certificationPATIENT
17GT1OptionalNoGuarantorPATIENT
18AL1OptionalYesPatient allergy informationPATIENT
19ORCRequiredNoCommon orderORDER
20NTEOptionalYesNotes and commentsORDER
21PRTOptionalYesParticipation informationORDER
22TQ1RequiredNoTiming / quantityORDER
23TQ2OptionalYesTiming / quantity relationshipORDER
24OBRRequiredNoObservation requestORDER
25TCDOptionalNoTest code detailORDER
26NTEOptionalYesNotes and commentsORDER
27PRTOptionalYesParticipation informationORDER
28CTDOptionalNoContact dataORDER
29DG1OptionalYesDiagnosisORDER
30RELOptionalNoClinical relationship segmentORDER
31OBXRequiredNoObservation resultOBSERVATION
32PRTOptionalYesParticipation informationOBSERVATION
33TCDOptionalNoTest code detailOBSERVATION
34NTEOptionalYesNotes and commentsOBSERVATION
35SPMRequiredNoSpecimenSPECIMEN
36NTEOptionalYesNotes and commentsSPECIMEN
37OBXRequiredNoObservation resultSPECIMEN
38PRTOptionalYesParticipation informationSPECIMEN
39SACRequiredNoSpecimen container detailSPECIMEN
40NTEOptionalYesNotes and commentsSPECIMEN
41OBXRequiredNoObservation resultCONTAINER_OBSERVATION
42PRTOptionalYesParticipation informationCONTAINER_OBSERVATION
43IPCOptionalNoImaging procedure control segmentORDER
44SGHOptionalNoSegment group headerORDER
45PIDRequiredNoPatient identificationPRIOR_RESULT
46PD1OptionalNoPatient additional demographicPRIOR_RESULT
47PRTOptionalYesParticipation informationPRIOR_RESULT
48PV1RequiredNoPatient visitPRIOR_RESULT
49PV2OptionalNoPatient visit - additional infoPRIOR_RESULT
50PRTOptionalYesParticipation informationPRIOR_RESULT
51AL1OptionalYesPatient allergy informationPRIOR_RESULT
52ORCRequiredNoCommon orderPRIOR_RESULT
53PRTOptionalYesParticipation informationPRIOR_RESULT
54OBRRequiredNoObservation requestPRIOR_RESULT
55NTEOptionalYesNotes and commentsPRIOR_RESULT
56PRTRequiredNoParticipation informationOBSERVATION_PARTICIPATION_PRIOR
57DEVOptionalYesDeviceOBSERVATION_PARTICIPATION_PRIOR
58TQ1RequiredNoTiming / quantityTIMING_PRIOR
59TQ2OptionalYesTiming / quantity relationshipTIMING_PRIOR
60OBXRequiredNoObservation resultOBSERVATION_PRIOR
61PRTOptionalYesParticipation informationOBSERVATION_PRIOR
62NTEOptionalYesNotes and commentsOBSERVATION_PRIOR
63SGTOptionalNoSegment group trailerORDER
64FT1OptionalYesFinancial transactionORDER
65CTIOptionalYesClinical trial identificationORDER
66BLGOptionalNoBillingORDER

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python