HL7 DFT Message: Financial Transactions

HL7 DFT (Detailed Financial Transaction) messages communicate charge data between clinical systems and revenue cycle management (RCM) platforms. The DFT HL7 message, often written as HL7 DFT or DFT^P03 (Post Detail Financial Transaction), is the primary trigger event, carrying procedure codes, diagnosis codes, and charge amounts from ancillary systems to billing systems.

Segment	Name	Required	Purpose
MSH	Message Header	Yes	Sender, receiver, message type, version
EVN	Event Type	No	Transaction event details
PID	Patient Identification	Yes	Patient demographics and identifiers
PV1	Patient Visit	No	Visit context for the charge
FT1	Financial Transaction	Yes	Charge details (repeating)
PR1	Procedure	No	Procedure information
DG1	Diagnosis	No	Diagnosis codes for billing
GT1	Guarantor	No	Responsible party for payment
IN1	Insurance	No	Payer information
IN2	Insurance (Additional)	No	Extended insurance details

The FT1 segment repeats for each charge line item in the transaction.

Field	ID	Description
Set ID	FT1-1	Sequence number for multiple FT1 segments
Transaction ID	FT1-2	Unique charge identifier
Transaction Date	FT1-4	Date of service
Transaction Type	FT1-6	Charge (CG), Credit (CD), Payment (PY)
Transaction Code	FT1-7	CPT/HCPCS procedure code
Transaction Amount	FT1-11	Charge amount
Department Code	FT1-13	Originating department
Diagnosis Code	FT1-19	ICD-10 diagnosis
Performed By	FT1-20	Provider who performed the service
Ordered By	FT1-21	Ordering provider
Unit Cost	FT1-22	Per-unit charge amount
Quantity	FT1-10	Number of units
Procedure Code	FT1-25	CPT code (v2.3+)
Modifier	FT1-26	CPT modifiers (repeating)

Code	Meaning	Use Case
CG	Charge	Standard charge posting
CD	Credit	Charge reversal or adjustment
PY	Payment	Payment received
AJ	Adjustment	Billing adjustment
CO	Co-payment	Patient co-pay collected
DE	Deposit	Advance deposit (site-defined extension, not in HL7 Table 0017)

A charge posting for an emergency department visit:

DFT interfaces must include reconciliation logic to prevent duplicate charges and catch missed charges:

• Duplicate detection: Match on transaction ID (FT1-2), procedure code, date of service, and patient MRN
• Late charges: Handle charges posted after the billing cycle closes, typically flagged with a late-charge indicator
• Charge reversals: Credit transactions (FT1-6 = CD) must reference the original charge for proper netting

Healthcare billing uses two distinct claim forms:

• Institutional (UB-04): Facility charges: room, supplies, technical component. Uses revenue codes alongside CPT/HCPCS.
• Professional (CMS-1500): Provider charges: professional component of services. Uses CPT codes with modifiers.

DFT interfaces often need to split charges between institutional and professional feeds, each routed to different billing systems or accounts receivable workflows.

CPT modifiers (FT1-26) are critical for correct reimbursement. Common modifiers in DFT messages:

• -26: Professional component only
• -TC: Technical component only
• -59: Distinct procedural service
• -25: Significant, separately identifiable E/M service
• -LT/-RT: Left side / right side

Modifiers repeat in FT1-26, and each modifier affects how payers adjudicate the claim.