Schedule a demo
Message type

Observation report alert acknowledgment

Acknowledges receipt of an observation report alert. The MSA segment confirms processing of the alert notification.

6segments
2required
0groups
v2.9HL7 version
ora-r41.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ORA^R41^ORA_R41|MSG001|P|2.9\r' \
      'MSA|AA|MSG001\r' \
      'SFT|ACME^Software|v4.1|EHR System|BIN001'

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

# .. whose fields we can now access.
ack_code = msg.msa.acknowledgment_code
msg_control_id = msg.msa.message_control_id
vendor = msg.sft.software_vendor_organization
version = msg.sft.software_certified_version_or_release_number

Build and parse ORA^R41 messages in Python

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

1

Parse an incoming ORA^R41 message

Demonstrates receiving and extracting key fields from a observation report alert acknowledgment transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ORA^R41^ORA_R41|MSG001|P|2.9\r' \
      'MSA|AA|MSG001\r' \
      'SFT|ACME^Software|v4.1|EHR System|BIN001'

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

# .. whose fields we can now access.
ack_code = msg.msa.acknowledgment_code
msg_control_id = msg.msa.message_control_id
vendor = msg.sft.software_vendor_organization
version = msg.sft.software_certified_version_or_release_number

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||ORA^R41^ORA_R41|MSG00001|P|2.9\rMSA|AA|MSG00001\rERR|||0|I|\rPRT|1||AT^Attending||1234^CHEN^DAVID^L^^^MD'
msg = HL7Message.parse(raw)

ack_code = msg.msa.acknowledgment_code
control_id = msg.msa.message_control_id

Beyond the mandatory MSH header, the required segments are: MSA. 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.

ORA^R41 segment composition

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

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2SFTOptionalYesSoftware segment-
3UACOptionalNoUser authentication credential-
4MSARequiredNoMessage acknowledgment-
5ERROptionalYesError-
6PRTOptionalYesParticipation information-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python