HL7 BAR_P02 (Purge Patient Accounts) | Integration Soup HL7 Reference Guide

HL7 BAR_P02 Purge Patient Accounts

A high-risk notice that billing account records should be removed or purged.

HL7 message structure BAR_P02 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
EVN	Event Type	Yes	No
BAR_P02.PATIENT	Patient group	Yes	Yes
PID	Patient Identification	Yes	No
PD1	Patient Additional Demographic	No	No
PV1	Patient Visit	No	No
DB1	Disability	No	Yes

BAR_P02 is used when a patient account or set of accounts needs to be purged from a patient accounting or financial system. In many organizations purging is an internal billing-system function, so an external P02 feed is less common than add, update, or end-account messages.

When it is used, treat it carefully. This is not a normal demographic correction and it is not a voided charge line. It tells the receiver that account-level billing records may need to be deleted, suppressed, or otherwise removed according to local financial policy.

A small BAR_P02 example

MSH|^~\&|REG|CITYHOSP|BILLING|CITYHOSP|20260715111500||BAR^P02^BAR_P02|BAR020001|P|2.5.1 EVN|P02|20260715111400 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F||||||||||ACC000789^^^CITYHOSP^AN PV1|1|O|CLINIC^12^1^CITYHOSP||||12345^Careful^Clara|||||||||||VN000345^^^CITYHOSP^VN

What systems do with it

The sender may be a registration, ADT, account correction, or conversion system. The receiver decides whether the identified account can be purged, archived, marked inactive, or rejected. In regulated billing environments, a true delete may be replaced by a local inactive or correction status.

In an interface engine such as Integration Soup, this is a message I would route with more logging than usual. If the receiver rejects the purge, operations should see the failure clearly rather than discovering later that billing and registration disagree.

How to read the structure

The local structure has MSH, EVN, and one or more patient groups. Each patient group requires PID and may include PD1, PV1, and DB1. The key practical question is which patient/account identifiers the receiver uses to find the account being purged.

Implementation traps

The standard allows a series of accounts in one event, but the reference note recommends only one PID per event. That is a good operational rule too. One account purge per message is much easier to audit, retry, reject, and explain.

Do not use P02 to reverse a single charge. Use the site's DFT correction, void, reversal, or adjustment workflow for charge-level correction.

Reference notes

The HL7 v2+ BAR_P02 page describes this event as a notice of account deletion that may be processed by the patient accounting or financial system, and recommends sending only one PID segment per event.