HL7 ADT_A08 Update Patient Information

Something changed, but no more specific ADT trigger event fits.
HL7 message structure ADT_A01 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
MSH
 Message Header Yes No
SFT
 Software Segment No Yes
EVN
 Event Type Yes No
PID
 Patient Identification Yes No
PD1
 Patient Additional Demographic No No
ROL
 Role No Yes
NK1
 Next of Kin / Associated Parties No Yes
PV1
 Patient Visit Yes No
PV2
 Patient Visit - Additional Information No No
ROL
 Role No Yes
DB1
 Disability No Yes
OBX
 Observation/Result No Yes
AL1
 Patient Allergy Information No Yes
DG1
 Diagnosis No Yes
DRG
 Diagnosis Related Group No No
ADT_A01.PROCEDURE
 Procedure group No Yes
PR1
 Procedures Yes No
ROL
 Role No Yes
GT1
 Guarantor No Yes
ADT_A01.INSURANCE
 Insurance group No Yes
IN1
 Insurance Yes No
IN2
 Insurance Additional Information No No
IN3
 Insurance Additional Information, Certification No Yes
ROL
 Role No Yes
ACC
 Accident No No
UB1
 UB82 No No
UB2
 UB92 Data No No
PDA
 Patient Death and Autopsy No No

ADT_A08 is the general update-patient-information event. It is used when patient or encounter information changes and there is not a more specific ADT event for the change. In practice, it is one of the busiest ADT messages because names, addresses, phone numbers, language, insurance, visit details, care teams, and local registration fields all change after the first registration message.

The message usually appears as ADT^A08^ADT_A01. The A08 trigger tells you this is an update; the ADT_A01 structure tells the parser which segment layout to use. The structure panel below uses ADT_A01 for that reason.

A small A08 example

MSH|^~\&|REG|CITYHOSP|EHR|CITYHOSP|20260715102000||ADT^A08^ADT_A01|ADT080001|P|2.5.1 EVN|A08|20260715101900|||REGCLERK^Riley^Morgan PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F|||88 New Street^^Auckland^^1010^NZ^H||^PRN^CP^^64^21^5552222~^NET^Internet^jane.smith@example.org PV1|1|O|ED^OBS02^1^CITYHOSP||||12345^Careful^Clara|||||||||||VST440001^^^CITYHOSP^VN|||||||||||||||||||||||||20260715081200 IN1|1|PLAN123^City Health Plan^L|CHP|City Health Plan|100 Benefit Road^^Auckland^^1010^NZ

What systems do with it

The sender is usually registration or the EHR. Receivers use A08 to keep patient and visit data synchronized after an A01, A04, or A05. A08 may update PID demographics, PD1 patient-level details, PV1 visit details, insurance, guarantor, allergies, diagnoses, or local observations.

Good A08 handling is usually a matter of merge policy. Some receivers overwrite demographics from every A08. Others protect fields from more trusted sources. Some only accept certain segments. An integration engine such as Integration Soup often ends up enforcing those receiver-specific rules.

How to read the structure

A08 uses the ADT_A01 structure, so the core is MSH, EVN, PID, and PV1, with optional patient, visit, procedure, insurance, guarantor, allergy, diagnosis, and observation content. The event code in MSH-9 is what tells the receiver this is an update rather than an admit or registration.

When the update is visit-specific, keep the visit identifier stable. When the update is person-level, be clear whether the receiving system should apply it across all active encounters, only this visit, or only the patient master record.

Implementation traps

A08 is useful, but it is also easy to overuse. If a patient location changes, use the transfer or location event the interface expects. If a discharge is canceled, use A13. If a merge occurs, use A40. A08 should not quietly replace more specific events just because it is easy to generate.

The second trap is sending partial updates to a receiver that treats each A08 as a full snapshot. If a blank field means "delete this value" in one interface and "unknown/not sent" in another, you have a data-loss problem waiting to happen. Document whether the A08 is a snapshot, a delta, or a profile-specific mix.

Reference notes

The HL7 v2+ patient-administration material describes A08 as the event for changed patient information when no other trigger event has occurred, and recommends using more specific trigger events when they exist. The CDC syndromic surveillance addendum shows A08 using the ADT_A01 message structure, and iNTERFACEWARE's ADT overview summarizes ADT messages as the high-volume feed used to synchronize demographics and patient state.