Message type

Original document notification

Notifies recipients that a new document has been created, without including the document content. The TXA segment carries document metadata such as type, status, and author. Document management and clinical repository systems consume this to register the new document.

18segments

8required

1group

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'MDM^T01^MDM_T01|MSG001|P|2.9\r' \
      'TXA|1|HP^H and P|TX|||20260701||||||DOC001\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M'

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

# .. whose fields we can now access.
doc_type = msg.txa.document_type
doc_id = msg.txa.unique_document_number
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

Python examples

Build and parse MDM^T01 messages in Python

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

Parse an incoming MDM^T01 message

Demonstrates receiving and extracting key fields from a original document notification transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'MDM^T01^MDM_T01|MSG001|P|2.9\r' \
      'TXA|1|HP^H and P|TX|||20260701||||||DOC001\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M'

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

# .. whose fields we can now access.
doc_type = msg.txa.document_type
doc_id = msg.txa.unique_document_number
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

Tutorials

Learn by building

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

MLLP

Receive and parse HL7 v2 messages

Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.

Start tutorial Build

Build and send HL7 v2 messages

Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.

Start tutorial

FAQ

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||MDM^T01^MDM_T01|MSG00001|P|2.9\rEVN|T01|20260401120000\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rPRT|1||AT^Attending||1234^CHEN^DAVID^L^^^MD\rPV1|1|I|MED^201^A^^^MAIN||||1234^CHEN^DAVID^L^^^MD|5678^PATEL^NINA^R^^^MD|||MED|||||||VN-90001|||||||||||||||||||||20260401\rTXA|1|HP^History and Physical^HL70270||20260401|1234^CHEN^DAVID^L^^^MD|||||DOC-5001||||||AU\rCON|1|GENERAL^General consent^HL70496|Y'
msg = HL7Message.parse(raw)

doc_type = msg.txa.document_type
doc_id = msg.txa.unique_document_number

Beyond the mandatory MSH header, the required segments are: EVN, PID, PV1, ORC, TQ1, OBR, TXA. 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.

Reference

MDM^T01 segment composition

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

#	Segment	Usage	Repeats	Description	Group
1	`MSH`	Required	No	Message header	-
2	`ARV`	Optional	Yes	Access restriction	-
3	`SFT`	Optional	Yes	Software segment	-
4	`UAC`	Optional	No	User authentication credential	-
5	`EVN`	Required	No	Event type	-
6	`PID`	Required	No	Patient identification	-
7	`PRT`	Optional	Yes	Participation information	-
8	`PV1`	Required	No	Patient visit	-
9	`PRT`	Optional	Yes	Participation information	-
10	`ORC`	Required	No	Common order	COMMON_ORDER
11	`PRT`	Optional	Yes	Participation information	COMMON_ORDER
12	`TQ1`	Required	No	Timing / quantity	COMMON_ORDER
13	`TQ2`	Optional	Yes	Timing / quantity relationship	COMMON_ORDER
14	`OBR`	Required	No	Observation request	COMMON_ORDER
15	`PRT`	Optional	Yes	Participation information	COMMON_ORDER
16	`NTE`	Optional	Yes	Notes and comments	COMMON_ORDER
17	`TXA`	Required	No	Transcription document header	-
18	`CON`	Optional	Yes	Consent	-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python