^P05
BAR^P05 — Update Account
BAR^P05 updates an existing patient billing account with changes to charges, diagnoses, or insurance information. It is used throughout the visit lifecycle to keep the billing account current as clinical information evolves.
When Is This Sent?
When charges, diagnoses, or insurance information on an existing account is updated. This may be triggered by coding updates, insurance verification results, additional procedures, or corrections to earlier information.
Real-World Usage
BAR^P05 is common in concurrent coding workflows where diagnoses and charges are added or updated throughout an inpatient stay rather than all at discharge. Revenue cycle systems rely on BAR^P05 to maintain accurate claim data. Missing BAR^P05 updates can result in undercoding or billing delays.
Message Structure
Segment names link to their field-level reference pages.
Example Message
Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.
1MSH||^~\&|EPIC|HOSPITAL_A|BILLING_SYSTEM|HOSPITAL_A|20260311120000||BAR^P05^BAR_P05|BAR00010|P|2.5.1 2EVN||P05|20260311120000 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|||||||||IP||||||||||||||||||||||||||20260310143000 5DG1||1||J18.9^Pneumonia, unspecified organism^ICD10CM|Pneumonia||F
Troubleshooting Scenarios
Billing system not reflecting updated diagnoses after BAR^P05
Cause
BAR^P05 is received but the billing system treats it as a full account replacement rather than an incremental update, overwriting previously added charges.
Fix
Confirm with the billing system vendor how BAR^P05 processes updates — additive (append only new DG1/FT1 segments) or replace-all (overwrite the account). If replace-all, ensure the BAR^P05 always includes the complete current set of diagnoses and charges.
Insurance update in BAR^P05 not propagating to claim
Cause
The claim was already generated before the BAR^P05 arrived. The billing system does not reprocess submitted claims based on incoming HL7 updates.
Fix
Review the billing system's claim lifecycle — BAR^P05 updates may need to arrive before the claim generation batch runs. For post-submission corrections, the billing system may require a manual claim correction rather than an HL7 update.
Common Confusions
BAR^P05 (Update account) vs ADT^A08 (Update patient info). ADT^A08 updates patient demographics and visit information across clinical systems. BAR^P05 updates billing-specific data (charges, diagnoses, insurance) in the financial system. They may carry similar data but target different system audiences. Also: BAR^P05 vs DFT^P03 — P05 is a batch-style account update; DFT^P03 posts individual transaction-level charges in real time.
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^P05.
View HL7 Integration Toolkit →