18.4.27 BAR/ACK - Add Patient Account (Event P01) (6.4.1)

Data are sent from some application (usually a Registration or an ADT system, for example) to the patient accounting or financial system to establish an account for a patient's billing/accounts receivable record. Many of the segments associated with this event are optional. This optionality allows those systems needing these fields to set up transactions that fulfill their requirements and yet satisfy the HL7 requirements.

When an account's start and end dates span a period greater than any particular visit, the P01 (add account) event should be used to transmit the opening of an account. The A01 (admit/visit notification) event can notify systems of the creation of an account as well as notify them of a patient's arrival in the healthcare facility. In order to create a new account without notifying systems of a patient's arrival, use the P01 trigger event.

From Standard Version 2.3 onward, the P01 event should only be used to add a new account that did not exist before, not to update an existing account. The new P05 (update account) event should be used to update an existing account. The new P06 (end account) event should be used to close an account. With the P01 event, EVN-2 - Recorded Date/Time should contain the account start date.

• Message
• ACK Choreography
• FHIR Structure Definition
• v2.xml XSD
• ER7 Example
• XML Example

Segment	Cardinality	Implement	Status
BAR^P01^BAR_P01
MSH Message Header	[1..1]	SHALL
ARV Access Restriction			v2.9
SFT Software Segment
UAC User Authentication Credential Segment	[0..1]
EVN Event Type	[1..1]	SHALL
PID Patient Identification	[1..1]	SHALL
PD1 Patient Additional Demographic	[0..1]
PRT Participation Information
ROL Role			B
VISIT	[1..*]	SHALL
PV1 Patient Visit	[1..1]	SHALL
PV2 Patient Visit - Additional Information	[0..1]
PRT Participation Information
ROL Role			B
DB1 Disability
OBX Observation/Result
PRT Participation Information
AL1 Patient Allergy Information
DIAGNOSIS
DG1 Diagnosis	[1..1]	SHALL
DRG Diagnosis Related Group	[0..1]
PROCEDURE
PR1 Procedures	[1..1]	SHALL
PRT Participation Information
ROL Role			B
GT1 Guarantor
NK1 Next of Kin / Associated Parties
INSURANCE
IN1 Insurance	[1..1]	SHALL
IN2 Insurance Additional Information	[0..1]
IN3 Insurance Additional Information, Certification
PRT Participation Information
ROL Role			B
ACC Accident	[0..1]
UB1 Uniform Billing Data 1	[0..1]		B
UB2 Uniform Billing Data 2	[0..1]

 

BAR_P01

MSH-15	MSH-16	Immediate ACK	Application Ack
Blank	Blank	-	ACK^P01^ACK
NE	NE	-	-
AL, SU, ER	NE	ACK^P01^ACK	-
NE	AL, SU, ER	-	ACK^P01^ACK
AL, SU, ER	AL, SU, ER	ACK^P01^ACK	ACK^P01^ACK

We need some ER7 examples...

We need some XML examples...

• Message
• ACK Choreography
• FHIR Structure Definition
• v2.xml XSD
• ER7 Example
• XML Example

Segment	Cardinality	Implement	Status
ACK^P01^ACK
MSH Message Header	[1..1]	SHALL
SFT Software Segment
UAC User Authentication Credential Segment	[0..1]
MSA Message Acknowledgment	[1..1]	SHALL
ERR Error

 

ACK

We need some ER7 examples...

We need some XML examples...

The error segment will indicate the fields that caused a transaction to be rejected.