HL7 ADT_A43 Move Patient Information - Patient Identifier List

HL7 message structure ADT_A43 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

SegmentNameRequiredRepeatable
Message Header Yes No
Software Segment No Yes
Event Type Yes No
ADT_A43.PATIENT
Patient group Yes Yes
Patient Identification Yes No
Patient Additional Demographic No No
Merge Patient Information Yes No

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

MSH|^~\&|MPI|CITYHOSP|EHR|CITYHOSP|20260715154000||ADT^A43^ADT_A43|ADT430001|P|2.5.1 EVN|A43|20260715153900 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F MRG|999888^^^CITYHOSP^MR

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.