visit the hl7 website The Demo site for our new HL7 Version 2+ (plus) Standard

18.4.20 ADT/ACK - Move Account Information - Patient Account Number (Event A44) (3.3.44)

A move has been done at the account identifier level. That is, a PID-18 - Patient Account Number associated with one PID-3 - Patient Identifier List has been moved to another patient identifier list.

An A44 event is used to signal a move of records identified by the MRG-3 - Prior Patient Account Number from the "incorrect source patient identifier list" identified in the MRG segment (MRG-1 - Prior Patient Identifier List) to the "correct target patient identifier list" identified in the PID segment (PID-3 - Patient Identifier List).

The account number involved in identifying the account to be moved (MRG-3 - Prior Patient Account Number) may or may not have visits. In any case, all subordinate data sets associated with the account number in MRG-3 - Prior Patient Account Number are moved along with the account number, from the "incorrect source" ID (MRG-1 - Prior Patient Identifier List) to the "correct target" ID (PID-3 - Patient Identifier List).

No identifiers subordinate to the account number (visit number, alternate visit ID) are valued in this message.

This event and the message syntax do, however, allow for the specification of a "new identifier" (PID-18 - Patient Account Number), which may be application and/or implementation-specific and therefore require site negotiation.

All of the identifiers superior to the account number should be valued in both the MRG segment and the PID segment. In this message, the PID-3 - Patient Identifier List is superior to the account number.

See sections 3.5.2, "Merging patient/person information," and 3.5.2.1.3, "Move," for a discussion of issues related to the implementation of move messages.

The fields included when this message is sent should be the fields pertinent to communicate this event. When demographic data in other fields change, it is recommended that the A08 (update patient information) event be used in conjunction with this message. However, all PID data associated with the "account number" are treated as updated information.

Segment Cardinality Implement Status
ADT^A44^ADT_A44
MSH

Message Header

[1..1] SHALL
ARV

Access Restriction

 
UAC

User Authentication Credential Segment

[0..1]  
EVN

Event Type

[1..1] SHALL
PATIENT [1..*] SHALL
PID

Patient Identification

[1..1] SHALL
PD1

Patient Additional Demographic

[0..1]  
ARV

Access Restriction

  B
MRG

Merge Patient Information

[1..1] SHALL

 

ADT_A44

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank - ADT^A47^ADT_A44
Blank Blank - ADT^A44^ADT_A44
NE NE - -
NE NE - -
AL, SU, ER NE ACK^A47^ACK -
AL, SU, ER NE ACK^A44^ACK -
NE AL, SU, ER - ACK^A47^ACK
NE AL, SU, ER - ACK^A44^ACK
AL, SU, ER AL, SU, ER ACK^A47^ACK ACK^A47^ACK
AL, SU, ER AL, SU, ER ACK^A44^ACK ACK^A44^ACK
We need some ER7 examples...
We need some XML examples...