HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

BAR: Add/change billing account

This page lists the structures and trigger events BAR defines, taken from the standard. The written commentary that theADT page carries has not been written for BAR.

Recognising BAR messages

BAR announces itself in MSH-9 like this:

MSH-9BAR^P01^BAR_P01
  1. MSH-9.1BARmessage code: what kind of message this is
  2. MSH-9.2P01trigger event: what happened in the real world: add patient account
  3. MSH-9.3BAR_P01message structure: which segments to expect, and in what order

How to use these specifications explains MSH-9 in full, with a worked example.

Message structures

BAR takes 6 structures. The first 4 are shown in full; the rest are listed below.

BAR_P01: Add Patient Account

Sent when one thing happens: P01: Add Patient Account.

You must always send: MSH, EVN, PID. Everything else is optional, or required only inside a group you chose to send.

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
EVNR1..1
PIDR1..1
PD1O0..1
ROLO0..*
VISITa group of 15 segments, repeated togetherR1..*
PV1O0..1
PV2O0..1
ROLO0..*
DB1O0..*
OBXO0..*
AL1O0..*
DG1O0..*
DRGO0..1
PROCEDUREa group of 2 segments, repeated togetherO0..*
PR1in PROCEDURER1..1
ROLin PROCEDUREO0..*
GT1O0..*
NK1O0..*
INSURANCEa group of 4 segments, repeated togetherO0..*
IN1in INSURANCER1..1
IN2in INSURANCEO0..1
IN3in INSURANCEO0..*
ROLin INSURANCEO0..*
ACCO0..1
UB1O0..1
UB2O0..1

R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 3 such groups: VISIT, PROCEDURE, INSURANCE.

BAR_P02: Purge Patient Accounts

Sent when one thing happens: P02: Purge Patient Accounts.

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
EVNR1..1
PATIENTa group of 4 segments, repeated togetherR1..*
PIDR1..1
PD1O0..1
PV1O0..1
DB1O0..*

R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 1 such group: PATIENT.

BAR_P05: Update Account

Sent when one thing happens: P05: Update Account.

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
EVNR1..1
PIDR1..1
PD1O0..1
ROLO0..*
VISITa group of 18 segments, repeated togetherR1..*
PV1O0..1
PV2O0..1
ROLO0..*
DB1O0..*
OBXO0..*
AL1O0..*
DG1O0..*
DRGO0..1
PROCEDUREa group of 2 segments, repeated togetherO0..*
PR1in PROCEDURER1..1
ROLin PROCEDUREO0..*
GT1O0..*
NK1O0..*
INSURANCEa group of 4 segments, repeated togetherO0..*
IN1in INSURANCER1..1
IN2in INSURANCEO0..1
IN3in INSURANCEO0..*
ROLin INSURANCEO0..*
ACCO0..1
UB1O0..1
UB2O0..1
ABSO0..1
BLCO0..*
RMIO0..1

BAR_P06: End Account

Sent when one thing happens: P06: End Account.

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
EVNR1..1
PATIENTa group of 2 segments, repeated togetherR1..*
PIDR1..1
PV1O0..1

Other BAR structures

StructureNameEvents
BAR_P10P10
BAR_P12Update Diagnosis/ProcedureP12

Trigger events

The trigger event is the real-world thing that made the message get sent. BAR defines 6.

EventNameStructure
P01Add Patient AccountBAR_P01
P02Purge Patient AccountsBAR_P02
P05Update AccountBAR_P05
P06End AccountBAR_P06
P10P10BAR_P10
P12Update Diagnosis/ProcedureBAR_P12