Billing Account Record

An HL7 Billing Account Record (BAR) message is used to make changes to a patient’s billing account information, or to add new patient accounts. This message type is typically used when data is sent from an ADT or registration system to a patient accounting system in order to create or add to a patient’s account receivable/billing record. Many segments within this data type are optional. The BAR message has 5 different message types that are used to transmit this data:

      • BAR^P01:  Add patient accounts.
      • BAR^P02:  Deleted patient accounts. 
      • BAR^P05:  Update patient account. 
      • BAR^P06:  End account.
      • BAR^P10:  Transmit Ambulatory Payment Classification (APC) grouping.

Below is an example of an HL7 version 2.3 BAR^P01 message, used to create a new patient account:

GT1|0||DOE^JOHN^E||756 E FANNIN ST^^LAGRANGE^TX^789450000|9799660489|||||M|||||CARE INN|457 NMAIN^^LAGRANGE^TX^78945|





Message Header. The header contains information about the sending system and location, the receiving system and location, the date and time of when the message was created, the type of trigger event being communicated, and the HL7 message version being used. This segment is required.


Event Type. Communicates the event that occurred in order for the message to be generated. This is a crucial part of the data flow, as it indicates where and when a message is sent based on the type of event.This segment is required.


Patient Identification. Important patient identification information, including patient demographics. This segment is required.


Patient Visit. Contains information about patient visit details such as servicing facility, attending doctor, and visit ID. This segment is required.


Guarantor Information. This segment contains information about the person or organization financially responsible for the patient’s account. This segment is optional and can be repeated.



Policy Coverage. Information about the patient’s insurance policy is listed here and is used to create patient and insurance bills. This segment is required.

[ ] = optional, { } = repeating


For more information on implementing various HL7 message types, please refer to the HL7 Messaging Standard Implementation Guides corresponding to your required version. 






Other HL7 Message Types:

      • HL7 ADT (Admit, Discharge and Transfer)
      • HL7 ORM (Order Entry)
      • HL7 ORU (Observation Result)
      • HL7 MDM (Medical Document Management)
      • HL7 DFT (Detailed Financial Transactions)
      • HL7 BAR (Billing Account Record)
      • HL7 SIU (Scheduling Information Unsolicited)
      • HL7 RDS (Pharmacy/treatment Dispense)
      • HL7 RDE (Pharmacy/Treatment Encoded Order)
      • HL7 ACK (Acknowledgement Message)


Integration with HL7

HL7 is great standard, but anyone with first hand experience knows it's not without its challenges. We're here to help!

Let's talk

The ''non-standard" Standard

In practice, you'll find that everyone formats HL7 messages slightly different, even though it has a standard structure in place. With iNTERFACEWARE's integration engine, you can ensure that all data is normalized as intended for full compliance.


Version Compatiblity

What happens when the source destination is sending one version of HL7, while the recipient's system can only handle an older version of HL7? With Iguana you can convert HL7 versions on the fly.


Data Extraction

As you've seen, HL7 messages can contain a lot of information -- sometimes much more than you need. Simplify things using Iguana, by extracting the data from the specific HL7 fields you need. 


Future Proofing

The HL7 organization is always working on improving the standard and new versions will keep coming in the future. Ensure that your data always remains compatible with iNTERFACEWARE's integration engine, Iguana.