HL7 ADT A07 Message: Change an Inpatient to an Outpatient

HL7 ADT A07is the HL7 Version 2 trigger event used to change a patient's status from inpatient to outpatient. It communicates a change in patient classification without necessarily indicating that the patient has been discharged or that a new encounter has been created.

The corresponding reverse event is ADT A06: Change an Outpatient to an Inpatient. A07 is important for hospital registration, electronic health records, patient accounting, billing, and revenue cycle management systems.

What Is an HL7 ADT A07 Message?

A07 tells connected systems that an admitted patient has been reclassified as an outpatient while their episode of care continues. It belongs to the HL7 ADT event family and is processed mainly through the patient class in PV1-2.

HL7 ADT A07 Message Example

MSH|^~\&|HIS|HOSPITAL|EHR|MAIN|20261022160000||ADT^A07^ADT_A06|MSG07001|P|2.5
EVN|A07|20261022155500
PID|1||MRN070001^^^HOSPITAL^MR||SMITH^JOHN||19850412|M
PV1|1|O|OPD^ROOM1^BED1

In this example, PV1-2 = O identifies the patient's updated outpatient classification. The receiving application must also reconcile the existing encounter and any financial or administrative consequences according to the interface agreement. All patient information is fictional.

Explore each segment and its key fields:

How A07 Works in Healthcare Systems

An A07 event is sent when a patient is no longer classified as admitted but continues receiving care during the same episode. The updated location belongs in PV1-3, and the previous location, when different, belongs in PV1-6. The interface agreement determines whether the account continues or a new account is opened.

Because a class change can affect billing and census, receivers should apply it to the existing encounter rather than creating a new visit. Our HL7 v2 integration services cover these patient-class workflows.

Important HL7 A07 Fields

Field-level rules for patient class, location, and account number should be documented in the interface specification. Our HL7 parsing and data mapping team can help define them.

A07 vs A06 vs A03

A07 should not automatically close the patient's encounter. The receiving system must apply the agreed patient-class and account-handling rules. To end a visit, the sender uses an A03 discharge instead.

Mirth Connect A07 Filter

var messageType =
    msg['MSH']['MSH.9']['MSH.9.1'].toString();

var triggerEvent =
    msg['MSH']['MSH.9']['MSH.9.2'].toString();

var structure =
    msg['MSH']['MSH.9']['MSH.9.3'].toString();

var patientClass =
    msg['PV1']['PV1.2']['PV1.2.1'].toString();

return messageType === 'ADT' &&
       triggerEvent === 'A07' &&
       structure === 'ADT_A06' &&
       patientClass === 'O';

The filter assumes the agreed interface uses O for outpatient. Production processing should additionally validate patient and encounter identifiers, sender authorization, account-handling rules, and the applicable HL7 profile. Mirth Connect development services can help implement this.

Frequently Asked Questions

Need HL7 ADT A07 Integration?

Taction Software provides HL7 ADT interface development, Mirth Connect integration, EHR connectivity, and patient administration workflow automation. Explore our HL7 interface messaging services and EHR and EMR integration services.