HL7 DFT Messages: 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.
DFT^P03 Message Structure
Section titled “DFT^P03 Message Structure”| 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.
FT1 Segment Key Fields
Section titled “FT1 Segment Key Fields”| 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 (CR), Payment (PA) |
| 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) |
Transaction Type Codes (FT1-6)
Section titled “Transaction Type Codes (FT1-6)”| Code | Meaning | Use Case |
|---|---|---|
| CG | Charge | Standard charge posting |
| CR | Credit | Charge reversal or adjustment |
| PA | Payment | Payment received |
| AJ | Adjustment | Billing adjustment |
| CO | Co-payment | Patient co-pay collected |
| DE | Deposit | Advance deposit |
Sample DFT^P03 Message
Section titled “Sample DFT^P03 Message”A charge posting for an emergency department visit:
DFT^P03 — ED Charge Posting (3 Line Items)
Header Patient Clinical Order/Result Financial
| Field | Name | Value | Note |
|---|---|---|---|
MSH-3 | Sending Application | ED_SYS | Emergency department system |
MSH-5 | Receiving Application | BILLING | Revenue cycle / billing system |
MSH-9 | Message Type | DFT^P03^DFT_P03 | Post Detail Financial Transaction |
| Field | Name | Value | Note |
|---|---|---|---|
EVN-1 | Event Type Code | P03 | Post Detail Financial Transaction |
| Field | Name | Value | Note |
|---|---|---|---|
PID-3 | Patient Identifier List | MRN12345^^^MAIN_HOSP^MR | |
PID-5 | Patient Name | DOE^JOHN^ALEXANDER |
| Field | Name | Value | Note |
|---|---|---|---|
FT1-2 | Transaction ID | CHG001 | |
FT1-4 | Transaction Date | 202603011415 | Service at 2:15 PM |
FT1-6 | Transaction Type | CG | Charge — standard charge posting |
FT1-7 | Transaction Code | 99284^ED Visit Level 4^CPT | CPT 99284 — high-complexity ED visit |
FT1-10 | Quantity | 1 | |
FT1-22 | Unit Cost | 350.00 |
| Field | Name | Value | Note |
|---|---|---|---|
FT1-7 | Transaction Code | 85025^CBC with Diff^CPT | CPT 85025 — CBC with differential |
FT1-13 | Department Code | LAB | |
FT1-22 | Unit Cost | 45.00 |
| Field | Name | Value | Note |
|---|---|---|---|
FT1-7 | Transaction Code | 71046^Chest X-ray 2 Views^CPT | CPT 71046 — chest X-ray, 2 views |
FT1-13 | Department Code | RAD | |
FT1-22 | Unit Cost | 225.00 |
| Field | Name | Value | Note |
|---|---|---|---|
DG1-3 | Diagnosis Code | R50.9^Fever, unspecified^I10 | ICD-10 primary diagnosis |
DG1-6 | Diagnosis Type | A | Admitting diagnosis |
| Field | Name | Value | Note |
|---|---|---|---|
IN1-2 | Insurance Plan ID | BCBS001^BLUE CROSS BLUE SHIELD | |
IN1-8 | Group Number | GRP54321 | |
IN1-17 | Relationship | SELF | Patient is the subscriber |
Key Implementation Considerations
Section titled “Key Implementation Considerations”Charge Reconciliation
Section titled “Charge Reconciliation”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 = CR) must reference the original charge for proper netting
Institutional vs Professional Billing
Section titled “Institutional vs Professional Billing”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.
Modifier Handling
Section titled “Modifier Handling”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.
Related Resources
Section titled “Related Resources” HL7 Integration Services HL7 v2 charge integration — DFT interfaces, revenue cycle connectivity, and billing system integration.
HL7 Workbench Parse and validate DFT messages online with segment highlighting and field lookup.
HL7 Resource Center Message types, segments, reference guides, and integration tools.