^P03
DFT^P03 — Post Detail Financial Transaction
Used to submit detailed financial transactions (charges) from a clinical department to the billing system. It carries the charge code, quantity, and service date.
When Is This Sent?
When a chargeable service is performed — a lab test is resulted, a radiology exam is completed, a medication is administered, or a procedure is performed. Usually triggered automatically by the ancillary system.
Real-World Usage
DFT^P03 is the financial bridge between clinical systems and billing. In radiology, the RIS sends a DFT^P03 when a radiology report is finalized, triggering charge capture in the billing system. Missing or duplicate DFT messages directly impact revenue. If charges are not appearing in billing, trace back whether DFT^P03 is being sent and received.
Message Structure
Segment names link to their field-level reference pages.
| # | Segment | Purpose in this message | Req | Repeat |
|---|---|---|---|---|
| 1 | MSH | Message header with DFT^P03 in MSH.9 | R | — |
| 2 | EVN | Event type | R | — |
| 3 | PID | Patient demographics | R | — |
| 4 | FT1 | Financial transaction details: charge code, quantity, amount | R | Yes |
| 5 | PV1 | Visit context (required by most billing systems) | O | — |
| 6 | DG1 | Diagnosis supporting medical necessity | O | Yes |
| 7 | IN1 | Insurance information | O | — |
| 8 | PR1 | Procedure codes | O | Yes |
Example Message
Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.
1MSH||^~\&|RIS|HOSPITAL_A|BILLING|HOSPITAL_A|20260310160500||DFT^P03^DFT_P03|DFT00001|P|2.5.1 2EVN||P03|20260310160500 3PID||1||123456^^^HOSP_A^MR||Smith^John^M^^Mr.||19850315|M 4PV1||1|I|4A^201^1^^^HOSP_A||||1234^Ahmed^Dr.^Khalid 5FT1||1|||20260310160000|20260310160000|CG|71046^Chest 2 Views^CPT4|Chest 2 Views||1|||||||1234^Ahmed^Dr.^Khalid
Troubleshooting Scenarios
Charges not appearing in billing system
Cause
DFT^P03 messages are not reaching the billing system. Either the interface isn't configured or the charge code (FT1.7) doesn't match the billing system's charge master.
Fix
Verify DFT^P03 is being sent by checking interface engine logs. Then verify FT1.7 (transaction code) matches the billing system's charge master. Build a procedure-to-charge code crosswalk if needed.
Common Confusions
DFT^P03 (Post financial transaction) vs BAR^P01 (Add patient account). DFT^P03 posts individual charges to an existing account. BAR^P01 creates the account itself. The account must exist (via A01 or BAR^P01) before DFT^P03 charges can be posted against it.
Related Message Types
Segment Reference
Paste this message into our viewer
Interactive HL7 parser. Decodes every field, validates structure, highlights errors. Free, no signup.
Open HL7 Message Viewer →Need mapping templates?
The HL7 Integration Toolkit includes field mapping worksheets and interface spec templates for every major HL7 message type including DFT^P03.
View HL7 Integration Toolkit →