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

18.4.22 ADT/ACK - Change Visit Number (Event A50) (3.3.50)

A change has been done at the visit identifier level. That is, a PV1-19 - Visit Number has been found to be incorrect and has been changed.

An A50 event is used to signal a change of an incorrectly assigned visit number value. The "incorrect source visit number" value is stored in the MRG segment (MRG-5 - Prior Visit Number) and is to be changed to the "correct target visit number" value stored in the PV1 segment (PV1-19 - Visit Number).

Each superior identifier associated with this visit number identifier level, i.e. PID-3/MRG-1 and PID-18/MRG-3 should have the same value in both the PID and MRG segments.

See sections 3.5.2, "Merging patient/person information," and 3.5.2.1.4, "Change identifier," for a discussion of issues related to the implementation of change 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.

Segment Cardinality Implement Status
ADT^A50^ADT_A50
MSH

Message Header

 [1..1] SHALL
ARV

Access Restriction

  
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]  
MRG

Merge Patient Information

 [1..1] SHALL
PV1

Patient Visit

 [1..1] SHALL

 

ADT_A50

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank - ADT^A51^ADT_A50
Blank Blank - ADT^A50^ADT_A50
NE NE - -
NE NE - -
AL, SU, ER NE ACK^A51^ACK -
AL, SU, ER NE ACK^A50^ACK -
NE AL, SU, ER - ACK^A51^ACK
NE AL, SU, ER - ACK^A50^ACK
AL, SU, ER AL, SU, ER ACK^A51^ACK ACK^A51^ACK
AL, SU, ER AL, SU, ER ACK^A50^ACK ACK^A50^ACK
We need some ER7 examples...
We need some XML examples...