HL7 DFT (DFT^P03), SIU^S12, MDM^T02, VXU^V04 & RDE^O11 Messages: Financial, Scheduling, Document & Pharmacy HL7 v2 Guide

An HL7 DFT (Detail Financial Transaction) message is the specialized HL7 Version 2 (HL7 v2) message family used to transmit patient billing charges, procedure codes, and financial adjustments from clinical and ancillary hospital systems to a patient accounting or revenue cycle system. Alongside core ADT and HL7 ORU result interfaces, hospital integration engines such as Mirth Connect and Epic Bridges rely on five specialized operational HL7 v2 message families—DFT (Financial), SIU (Scheduling), MDM (Medical Document Management), VXU (Immunization), and RDE (Pharmacy Encoded Orders)—to synchronize clinical and administrative data.

What Is an HL7 DFT (Detailed Financial Transaction) Message?

Defined in Chapter 6 (Financial Management) of the HL7 v2.5.1 and v2.8 specifications (https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185), the HL7 DFT message transmits itemized financial transactions between an ancillary system (such as a radiology PACS/RIS, surgical perioperative module, laboratory information system, or clinical trial management system) and the central hospital billing engine before an ASC X12N 837 claim is generated.

The two primary DFT trigger events in clinical production are:

• DFT^P03 — Post Detail Financial Transaction: The standard unsolicited charge-posting message sent when a billable clinical service, supply item, or diagnostic procedure is completed.
• DFT^P11 — Post Detail Financial Transactions – Expanded: An expanded financial message structure introduced in later HL7 v2 versions to group multiple financial orders and diagnosis pointers under complex inpatient episodes.

Anatomy of the FT1 (Financial Transaction) Segment

The core payload of a DFT^P03 message is the repeating FT1 (Financial Transaction) segment, accompanied by PID (Patient Identification), PV1 (Patient Visit), DG1 (Diagnosis), PR1 (Procedures), GT1 (Guarantor), and IN1 (Insurance):

FT1 Field	Field Name	Data Type	Clinical Billing & Research Function
FT1-2	Transaction ID	ST	Unique line-item identifier assigned by the originating ancillary system for idempotency and audit tracking.
FT1-4	Transaction Date	DR	Date and timestamp (`YYYYMMDDHHMMSS`) when the clinical service or procedure was performed.
FT1-6	Transaction Type	IS	Classifies the financial action: CG (Charge), CD (Credit), PY (Payment), or AJ (Adjustment).
FT1-7	Transaction Code	CE	Hospital Chargemaster (CDM) item code or internal billing service identifier.
FT1-10	Transaction Quantity	NM	Number of billable units, hours, or drug dosage units administered.
FT1-19	Diagnosis Code – FT1	CE	Links the specific charge line to its supporting ICD-10-CM diagnosis code(s).
FT1-20	Performed By Code	XCN	NPI and name of the rendering physician or clinician who performed the procedure.
FT1-25	Procedure Code	CE	Standardized CPT-4 or HCPCS Level II procedure code alongside modifiers (FT1-26, e.g., clinical trial modifiers Q0/Q1).

MSH|^~&|RAD_RIS|UNIV_HOSP|EPIC_BILLING|UNIV_HOSP|20261109142000||DFT^P03^DFT_P03|MSG99201|P|2.5.1
EVN|P03|20261109142000
PID|1||8849201^^^UNIV_MRN^MR||DOE^JOHN^A||19620814|M
PV1|1|O|RAD^102^01||||1234567890^SMITH^SARAH^^^MD
FT1|1|TXN20261109-01||20261109140500|20261109142000|CG|71046^CHEST XRAY 2 VIEWS^CDM|||1|||RAD|||RAD^102||O|R91.8^Other nonspecific abnormal finding of lung field^I10|1234567890^SMITH^SARAH|||||71046^Radiologic exam chest 2 views^C4|26
DG1|1|I10|R91.8^Other nonspecific abnormal finding of lung field^I10||20261109140500|F

How Do SIU^S12 and MDM^T02 Messages Handle Scheduling and Clinical Notes?

While DFT^P03 governs post-encounter charge capture, clinical workflows before and during the visit rely on SIU (Scheduling Information Unsolicited, Chapter 10) and MDM (Medical Document Management, Chapter 9) messages:

1. HL7 SIU Scheduling Messages (SIU^S12, S13, S14, S15, S26)

Practice management systems, patient intake portals, and ambient AI scribes subscribe to SIU feeds to maintain real-time appointment rosters:

• Trigger Events: SIU^S12 (Notification of New Appointment Booking), SIU^S13 (Appointment Rescheduling), SIU^S14 (Appointment Modification), SIU^S15 (Appointment Cancellation), and SIU^S26 (Notification That Patient Did Not Show Up for Appointment).
• Core Segments:
  • SCH (Schedule Activity Information): Carries the placer/filler appointment IDs (`SCH-1`/`SCH-2`), appointment reason (`SCH-7`), duration (`SCH-9`/`SCH-10`), start/end timestamps (`SCH-11`), and filler status code (`SCH-25`, e.g., `Booked`, `Arrived`, `Cancelled`).
  • AIL (Appointment Information – Location Resource): Identifies the clinic department, exam room, or surgical suite (`AIL-3`).
  • AIP (Appointment Information – Personnel Resource): Identifies the scheduled attending physician or technician (`AIP-3`).
  • AIG (Appointment Information – General Resource): Identifies scheduled medical equipment (such as a 3T MRI scanner).

2. HL7 MDM Medical Document Management Messages (MDM^T02 and T04)

External transcription platforms, ambient scribes, and specialty reporting modules use MDM messages to push unstructured or Base64-encoded clinical notes into the EHR chart:

• Trigger Events: MDM^T01 (Original Document Notification without content), MDM^T02 (Original Document Notification and Content), MDM^T04 (Document Status Change Notification and Content), and MDM^T08 (Document Edit Notification and Content).
• Core Segments:
  • TXA (Transcription Document Header): Specifies the document type (`TXA-2`, such as `HP` for History & Physical, `DS` for Discharge Summary, or `PN` for Progress Note), activity date/time (`TXA-4`), primary activity provider (`TXA-5`), unique document number (`TXA-12`), and document completion status (`TXA-17`, e.g., `AU` Authenticated, `DI` Dictated, `IP` In Progress).
  • OBX (Observation/Result): Following the `TXA` header, one or more `OBX` segments carry the actual document body using value type `TX` (Text data), `FT` (Formatted text), or `ED` (Encapsulated Data, such as a Base64-encoded PDF report).

How Are Immunization Registries and Pharmacy Orders Updated Using HL7 VXU and RDE Messages?

Two additional HL7 v2 message types handle public health immunization reporting and inpatient/outpatient medication dispensing:

• HL7 VXU^V04 (Unsolicited Vaccination Record Update): Governed by the CDC HL7 v2.5.1 Implementation Guide for Immunization Messaging (https://www.cdc.gov/vaccines/programs/iis/technical-guidance/hl7.html), VXU^V04 transmits vaccine administrations and historical immunization records from EHRs to state Immunization Information Systems (IIS). It uses RXA (Pharmacy/Treatment Administration) to record the administered CVX vaccine code (`RXA-5`), dose quantity (`RXA-6`), lot number (`RXA-15`), and MVX manufacturer code (`RXA-17`), paired with RXR (Pharmacy/Treatment Route) and OBX segments for Vaccine Information Statement (VIS) dates and VFC (Vaccines for Children) funding eligibility.
• HL7 RDE^O11 (Pharmacy/Treatment Encoded Order): Transmits verified, pharmacist-encoded medication orders from Computerized Provider Order Entry (CPOE) or pharmacy information systems to automated dispensing cabinets (such as Pyxis or Omnicell) and smart infusion pumps. Its central segment is RXE (Pharmacy/Treatment Encoded Order), which specifies the normalized NDC or RxNorm drug code (`RXE-2`), give amount min/max (`RXE-3`/`RXE-4`), give units (`RXE-5`), dosage form (`RXE-6`), and administration frequency (`RXE-1`), accompanied by RXR (route) and RXC (IV additive/base component segments).

HL7 v2 Message	Primary Trigger	Anchor Segment(s)	HL7 FHIR R4 Equivalent Resource
DFT (Financial)	DFT^P03	FT1, PR1, DG1	ChargeItem, Claim, Account
SIU (Scheduling)	SIU^S12	SCH, AIL, AIP, AIG	Appointment, Schedule, Slot
MDM (Documents)	MDM^T02	TXA, OBX (TX/FT/ED)	DocumentReference, Composition, Binary
VXU (Immunization)	VXU^V04	ORC, RXA, RXR, OBX	Immunization
RDE (Pharmacy Order)	RDE^O11	ORC, RXE, RXR, RXC	MedicationRequest, MedicationDispense

Frequently Asked Questions

What is an HL7 DFT (Detailed Financial Transaction) message?

An HL7 DFT message (most commonly DFT^P03) is an HL7 v2 financial interface message that transmits itemized patient charges, Chargemaster codes, CPT/HCPCS procedure codes, and ICD-10-CM diagnosis pointers within the FT1 segment from clinical ancillary systems to a hospital’s billing system.

How do SIU^S12 and MDM^T02 messages handle scheduling and clinical notes?

SIU^S12 broadcasts new appointment bookings using the SCH, AIL, and AIP segments to synchronize patient schedules across third-party apps, while MDM^T02 transmits clinical documents using a TXA metadata header followed by OBX segments carrying formatted text or Base64-encoded PDF clinical notes.

How are immunization registries updated using HL7 VXU messages?

EHRs send VXU^V04 (Unsolicited Vaccination Record Update) messages formatted to the CDC HL7 v2.5.1 Immunization Implementation Guide—containing RXA segments with CVX vaccine codes, MVX manufacturer codes, and lot numbers—to state Immunization Information Systems (IIS).