HL7 ADT_A50 Change Visit Number
ADT_A50 changes an incorrectly assigned visit number. It is not a move to another patient, and it is not a merge. The patient and account context should match; the correction is at the visit identifier level.
This event matters because visit number is often the practical join key for orders, results, documents, charges, images, and patient movements. A small visit-number typo can scatter data across systems.
A small A50 example
What systems do with it
The sender is typically the PAS/EHR or registration correction workflow. Receivers update correlation tables and visit-scoped records from the prior visit number in MRG to the corrected visit number in PV1.
How to read the structure
The structure is MSH, EVN, PID, optional PD1, required MRG, and required PV1. MRG-5 carries the prior visit number. PV1-19 carries the corrected visit number.
Implementation traps
Do not create a second visit. A50 is a change of identifier on the same visit. Also be careful with partial identifiers: if assigning authority or identifier type is missing, a receiver may update the wrong visit in a multi-facility environment.
Reference notes
The HL7 v2+ ADT_A50 page describes changing an incorrectly assigned visit number, with the incorrect value in MRG-5 and the correct target value in PV1-19.