HL7 ADT_A43 Move Patient Information - Patient Identifier List
ADT_A43 is a move event at the patient identifier list level. It is used when patient information or subordinate data sets were associated with the wrong patient identifier and need to be moved to the correct target identifier.
This is different from a merge. A merge says two identifiers represent the same patient. A move says a set of data was filed under the wrong identity and needs to be reassigned.
A small A43 example
What systems do with it
The sender is usually an MPI or registration correction workflow. Receivers move subordinate patient data from the prior patient identifier context in MRG to the target patient identity in PID, according to the precise profile rules.
Clinical repositories, document indexes, billing systems, image archives, and analytics stores may each need their own correction behavior. This is one of those messages where an interface engine should make failures loud.
How to read the structure
The local structure has MSH, EVN, and one or more patient groups. Each group requires PID and MRG, with optional PD1. The absence of required visit or account identifiers is intentional: this event is at the patient identifier list level.
Implementation traps
The trap is treating A43 as a synonym for A40. A move is not a merge. Before updating durable links, verify which data set is moving, which identifiers are superior or subordinate in the local model, and whether the receiver can reverse the operation if the source sends a correction.
Reference notes
The HL7 v2+ ADT_A43 page describes moving records identified by MRG-1 from an incorrect source patient ID to the correct target patient ID.