5.26 Event A31-Update Person Information (ADT^A31)
.
An A31 event can be used to update person information on an MPI. It is similar to an A08 (update patient information) event, but an A08 (update patient information) event should be used to update patient nformation for a current episode. An A28 (add person information) or A31 can also be used for backloading MPI information for the person, or for backloading person and historical information.
The message is as follows:

MSH..[{SFT}]..[UAC]..EVN..PID..[PD1]..[{ARV}]..[{ROL}]..[{NK1}]..PV1..[PV2]..[{ARV}]..[{ROL}]..[{DB1}]
..[{OBX}]..[{AL1}]..[{DG1}]..[{DRG}]..[{PR1}]..[{ROL}]..[{GT1}]..[IN1]..[IN2]..[{IN3}]..[{ROL}]..[ACC]
..[UB1]..[UB2]

5.27 Event A32-Cancel Patient Arriving-tracking (ADT^A32)
.
The A32 event is sent when an A10 (patient arriving-tracking) event is cancelled, either because of erroneous entry of the A10 event or because of a decision not to receive the patient after all.
The message is as follows:

MSH..[{SFT}]..[UAC]..EVN..PID..[PD1]..PV1..[PV2]..[{DB1}]..[{OBX}]

5.28 Event A33-Cancel Patient Departing-tracking (ADT^A33)
.
The A33 event is sent when an A09 (patient departing-tracking) event is cancelled, either because of erroneous entry of the A09 event or because of a decision not to send the patient after all.
The message is as follows:

MSH..[{SFT}]..[UAC]..EVN..PID..[PD1]..PV1..[PV2]..[{DB1}]..[{OBX}]

5.29 Event A34-Merge Patient Information-Patient ID Only (ADT^A34)
.
Event A34 has been retained for backward compatibility only. From V2.3.1 onwards, event A40 (Merge patient - patient identifier list) should be used instead. Only the patient identifier list has changed as a result of the merge.
An A34 (merge patient information-patient ID only) event was intended for merging or changing patient identifiers. It was used to change patient identifiers on all of this patient’s existing accounts.
The message is as follows:

MSH..[{SFT}]..[UAC]..EVN..PID..[PD1]..[{ARV}]..MRG

5.30 Event A35-Merge Patient Information-Account Number Only (ADT^A35)
.
Event A35 has been retained for backward compatibility only. From V2.3.1 onwards, event A41 (Merge patient - patient account number) should be used instead. Only the patient account number has changed as a result of the merge.
An A35 (merge patient information-account number only) event was intended for merging or changing an account number only.
The message is as follows:

MSH..[{SFT}]..[UAC]..EVN..PID..[PD1]..MRG

5.31 Event A36-Merge Patient Information- Patient ID and Account Number (ADT^A36)
.
Event A36 has been retained for backward compatibility only. From V2.3.1 onwards, events A40 (merge patient - patient identifier list) and A41 (merge patient - patient account number) should be used instead. Both patient identifier list and the patient account number have changed as a result of the merge.
The message is as follows:

MSH..[{SFT}]..[UAC]..EVN..PID..[PD1]..[{ARV}]..MRG

5.32 Event A37-Unlink Patient Information (ADT^A37)
.
The A37 event unlinks two patient identifiers.
The message is as follows:

MSH..[{SFT}]..[UAC]..EVN..PID..[PD1]..[PV1]..[{DB1}]..PID..[PD1]..[PV1]..[{DB1}]

*** Please consult LINKMED® Technical Manual for Event Type A38 to A62 ***