The Detail Financial Transaction (DFT) - Expanded message is used to describe a financial transaction transmitted between systems, that is, to the billing system for ancillary charges, ADT to billing system for patient deposits, etc. It serves the same function as the Post Detail Financial Transactions (event P03) message, but also supports the use cases described below.
Use case for adding the INx and GT1 segments inside the FT1 repetition:
If the insurance and/or the guarantor information is specific to a certain financial transaction of a patient and differs from the patient's regular insurance and/or guarantor, you may use the INx and GT1 segments related to the FT1 segment. If being used, the information supersedes the information on the patient level.
Example: Before being employed by a company, a pre-employment physical is required. The cost of the examinations is paid by the company, and not by the person's private health insurance. One of the physicians examining the person is an eye doctor. For efficiency reasons, the person made an appointment for these examinations on the same day as he already had an appointment with his eye doctor in the same hospital. The costs for this eye doctor appointment are being paid by the patient's private health insurance. Both financial transactions for the same patient/person could be sent in the same message. To bill the examination for the future-employer to that organization, you need to use the GT1 segment that is related to the FT1.
| Segment | Cardinality | Implement | Status |
|---|---|---|---|
 DFT^P11^DFT_P11 | |||
| [1..1] | SHALL | ||
| v2.9 | |||
| [0..1] | |||
| [1..1] | SHALL | ||
| [1..1] | SHALL | ||
| [0..1] | |||
| B | |||
 VISIT |
[0..1] | ||
| [0..1] | |||
| [0..1] | |||
| B | |||
| COMMON_ORDER |
|||
| [1..1] | SHALL | ||
 TIMING_QUANTITY |
|||
| [1..1] | SHALL | ||
| ORDER |
[0..1] | ||
| [1..1] | SHALL | ||
 OBSERVATION |
|||
| [1..1] | SHALL | ||
| DIAGNOSIS |
|||
| [1..1] | SHALL | ||
| [0..1] | |||
| INSURANCE |
|||
| [1..1] | SHALL | ||
| [0..1] | |||
| B | |||
| [0..1] | |||
| FINANCIAL |
[1..*] | SHALL | |
| [1..1] | SHALL | ||
 FINANCIAL_PROCEDURE |
|||
| [1..1] | SHALL | ||
| B | |||
| FINANCIAL_OBSERVATION_STANDALONE |
|||
| [1..1] | SHALL | ||
| FINANCIAL_ORDER_STANDALONE |
|||
| [1..1] | SHALL | ||
| FINANCIAL_OBSERVATION_2 |
|||
| [1..1] | SHALL | ||
| FINANCIAL_COMMON_ORDER |
|||
| [1..1] | SHALL | ||
| FINANCIAL_TIMING_QUANTITY |
|||
| [1..1] | SHALL | ||
| FINANCIAL_ORDER |
[0..1] | ||
| [1..1] | SHALL | B | |
| FINANCIAL_OBSERVATION |
|||
| [1..1] | SHALL | ||
| DIAGNOSIS_FT1 |
|||
| [1..1] | SHALL | ||
| [0..1] | |||
| FINANCIAL_INSURANCE |
|||
| [1..1] | SHALL | ||
| [0..1] | |||
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | ACK^P11^ACK |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^P11^ACK | - |
| NE | AL, SU, ER | - | ACK^P11^ACK |
| AL, SU, ER | AL, SU, ER | ACK^P11^ACK | ACK^P11^ACK |
Note: The ROL segment is optionally included after the PD1 to transmit information for patient level primary care providers, after the PV2 for additional information on the physicians whose information is sent there (i.e., Attending Doctor, Referring Doctor, Consulting Doctor), and within the insurance construct to transmit information for insurance level primary care providers.
Note: There is an information overlap between the FT1, DG1 and PR1 segments. If diagnosis information is sent in an FT1 segment, it should be consistent with the information contained in any DG1 segments present within its hierarchy. Since the procedure code field within the FT1 does not repeat, if procedure information is sent on an FT1 it is recommended that the single occurrence of the code in FT1 equates to the primary procedure (PR1-14 - Procedure Priority code value 1).
The error segment indicates the fields that caused a transaction to be rejected.
The Demo site for our new HL7 Version 2+ (plus) Standard
