Message type

Post detail financial transaction

Posts a detailed financial transaction to the billing system. The PID segment identifies the patient, FT1 carries the financial transaction detail, and PV1 identifies the visit. Charge capture and billing systems consume this.

59segments

19required

9groups

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'DFT^P03^DFT_P03|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'FT1|1||20260701||CG|99213^Office visit^CPT|1'

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

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
charge = msg.ft1.transaction_code
charge_date = msg.ft1.transaction_date

Python examples

Build and parse DFT^P03 messages in Python

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

Parse an incoming DFT^P03 message

Demonstrates receiving and extracting key fields from a post detail financial transaction transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'DFT^P03^DFT_P03|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'FT1|1||20260701||CG|99213^Office visit^CPT|1'

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

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
charge = msg.ft1.transaction_code
charge_date = msg.ft1.transaction_date

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||DFT^P03^DFT_P03|MSG00001|P|2.9\rEVN|P03|20260401120000\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rPD1|||Family Health Clinic^^12345\rPRT|1||AT^Attending||1234^CHEN^DAVID^L^^^MD\rROL|1|AD|AT^Attending^HL70443|1234^CHEN^DAVID^L^^^MD\rDB1|1||N\rDRG|'
msg = HL7Message.parse(raw)

name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

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

DFT^P03 segment composition

Segments that make up the DFT^P03 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	`PD1`	Optional	No	Patient additional demographic	-
8	`PRT`	Optional	Yes	Participation information	-
9	`ROL`	Optional	Yes	Role	-
10	`PV1`	Optional	No	Patient visit	VISIT
11	`PV2`	Optional	No	Patient visit - additional info	VISIT
12	`PRT`	Optional	Yes	Participation information	VISIT
13	`ROL`	Optional	Yes	Role	VISIT
14	`DB1`	Optional	Yes	Disability	-
15	`ORC`	Required	No	Common order	COMMON_ORDER
16	`PRT`	Optional	Yes	Participation information	COMMON_ORDER
17	`TQ1`	Required	No	Timing / quantity	COMMON_ORDER
18	`TQ2`	Optional	Yes	Timing / quantity relationship	COMMON_ORDER
19	`OBR`	Required	No	Observation request	COMMON_ORDER
20	`PRT`	Optional	Yes	Participation information	COMMON_ORDER
21	`NTE`	Optional	Yes	Notes and comments	COMMON_ORDER
22	`OBX`	Required	No	Observation result	COMMON_ORDER
23	`PRT`	Optional	Yes	Participation information	COMMON_ORDER
24	`NTE`	Optional	Yes	Notes and comments	COMMON_ORDER
25	`FT1`	Required	No	Financial transaction	FINANCIAL
26	`PRT`	Optional	Yes	Participation information	FINANCIAL
27	`ROL`	Optional	Yes	Role	FINANCIAL
28	`NTE`	Optional	Yes	Notes and comments	FINANCIAL
29	`PR1`	Required	No	Procedures	FINANCIAL
30	`PRT`	Optional	Yes	Participation information	FINANCIAL
31	`ROL`	Optional	Yes	Role	FINANCIAL
32	`OBX`	Required	No	Observation result	FINANCIAL
33	`PRT`	Optional	Yes	Participation information	FINANCIAL
34	`NTE`	Required	Yes	Notes and comments	FINANCIAL
35	`OBR`	Required	No	Observation request	FINANCIAL
36	`PRT`	Optional	Yes	Participation information	FINANCIAL
37	`NTE`	Optional	Yes	Notes and comments	FINANCIAL
38	`OBX`	Required	No	Observation result	FINANCIAL_OBSERVATION_2
39	`PRT`	Optional	Yes	Participation information	FINANCIAL_OBSERVATION_2
40	`NTE`	Optional	Yes	Notes and comments	FINANCIAL_OBSERVATION_2
41	`ORC`	Required	No	Common order	FINANCIAL
42	`PRT`	Optional	Yes	Participation information	FINANCIAL
43	`TQ1`	Required	No	Timing / quantity	FINANCIAL_TIMING_QUANTITY
44	`TQ2`	Optional	Yes	Timing / quantity relationship	FINANCIAL_TIMING_QUANTITY
45	`OBR`	Required	No	Observation request	FINANCIAL_ORDER
46	`PRT`	Optional	Yes	Participation information	FINANCIAL_ORDER
47	`NTE`	Optional	Yes	Notes and comments	FINANCIAL_ORDER
48	`OBX`	Required	No	Observation result	FINANCIAL_OBSERVATION
49	`PRT`	Optional	Yes	Participation information	FINANCIAL_OBSERVATION
50	`NTE`	Optional	Yes	Notes and comments	FINANCIAL_OBSERVATION
51	`DG1`	Required	No	Diagnosis	DIAGNOSIS
52	`DRG`	Optional	No	Diagnosis related group	-
53	`GT1`	Optional	Yes	Guarantor	-
54	`IN1`	Required	No	Insurance	INSURANCE
55	`IN2`	Optional	No	Insurance additional info	INSURANCE
56	`IN3`	Optional	Yes	Insurance additional info - certification	INSURANCE
57	`PRT`	Optional	Yes	Participation information	INSURANCE
58	`ROL`	Optional	Yes	Role	INSURANCE
59	`ACC`	Optional	No	Accident	-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python