MajwareMAJWARE
BAR
^P06
Financial4 required / 1 optional segments

BAR^P06End Account

BAR^P06 signals the billing system to close and finalize a patient billing account. It marks the end of the financial relationship for that visit and triggers final billing or claim generation processes.

When Is This Sent?

When an account is closed or finalized for billing — typically triggered when the patient is discharged (ADT^A03) and the account is ready for final claim submission.

Real-World Usage

BAR^P06 is the financial end-of-visit signal. It triggers the billing system to finalize the account, run coding validation, and submit the claim to the payer. If BAR^P06 is not sent or is delayed, claims may not be submitted on time, impacting cash flow. In modern EHR environments, the billing system often derives this signal from ADT^A03 rather than requiring a separate BAR^P06.

Message Structure

Segment names link to their field-level reference pages.

#SegmentPurpose in this messageReqRepeat
1MSHMessage header with BAR^P06 in MSH.9R
2EVNEvent type with P06 trigger and account close timestampR
3PIDPatient demographicsR
4PV1Visit information with discharge date/time and dispositionR
5DG1Final discharge diagnosesOYes

Example Message

Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.

HL7 v2.x Message
1MSH||^~\&|EPIC|HOSPITAL_A|BILLING_SYSTEM|HOSPITAL_A|20260311093000||BAR^P06^BAR_P06|BAR00020|P|2.5.1
2EVN||P06|20260311093000
3PID||1||123456^^^HOSP_A^MR||Smith^John^M^^Mr.||19850315|M
4PV1||1|I|4A^201^1^^^HOSP_A||||1234^Ahmed^Dr.^Khalid|||MED|||||01||||||||||||||||||||20260310143000|20260311093000

Troubleshooting Scenarios

Claims not being generated after patient discharge

Cause

BAR^P06 is not being sent to the billing system after ADT^A03. The billing system is waiting for a P06 to trigger claim generation.

Fix

Verify whether the ADT^A03 channel to the billing system is also sending a corresponding BAR^P06. If not, configure the interface engine to generate and route a BAR^P06 triggered by each A03 event. Alternatively, configure the billing system to accept A03 as the account-close signal.

Account closed prematurely — patient readmitted before BAR^P06 processed

Cause

BAR^P06 was sent for a discharge that was later reversed (ADT^A13 - cancel discharge). The billing account was closed before the correction arrived.

Fix

Configure the interface to send an ADT^A13 (cancel discharge) equivalent to the billing system — either a BAR^P05 update or an ADT^A13 if the billing system accepts it. This re-opens the account for the continued stay.

Common Confusions

BAR^P06 (End account) vs ADT^A03 (Discharge). Both signal the end of a patient visit but to different system types. ADT^A03 notifies clinical systems (PACS, pharmacy, lab) that the patient has left. BAR^P06 notifies the billing system to close the financial account and initiate claim submission. In integrated environments, the billing system may listen to A03 directly and not require a separate P06.

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 BAR^P06.

View HL7 Integration Toolkit →
← Back to HL7 Message Types Reference