5.8 Event A08-Update Patient Information (ADT^A08)

This trigger event is used when any patient information has changed but when no other trigger event has occurred. For example, an A08 event can be used to notify the receiving systems of a change of address or a name change. We strongly recommend that the A08 transaction be used to update fields that are not updated by any of the other trigger events. If there are specific trigger events for this update, these trigger events should be used. For example, if a patient's address and location are to be changed, then an A08 is used to change the patient address and the appropriate patient location trigger event is used to change the patient location. The A08 event can include information specific to an episode of care, but it can also be used for demographic information only.The Update Patient Information 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]

(ADT Event A09 Patient Departing - Tracking and ADT Event A10 Patient Arriving - Tracking are not included in this tutorial. Please refer to your LINKTools® Technical manual for detail)

5.9 Event A11-Cancel Admit/Visit Notification (ADT^A11)

For "admitted" patients, the A11 event is sent when an A01 (admit/visit notification) event is cancelled, either because of an erroneous entry of the A01 event, or because of a decision not to admit the patient after all.
For "non-admitted" patients, the A11 event is sent when an A04 (register a patient) event is cancelled, either because of an erroneous entry of the A04 event, or because of a decision not to check the patient in for the visit after all. To cancel an A05 (pre-admit a patient) event, use the A38 (cancel pre-admit), which was new for Version 2.3 of this Standard.
The Cancel Admit/Visit Notification message is as follows:

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

5.10 Event A12-Cancel Transfer (ADT^A12)

The A12 event is sent when an A02 (transfer a patient) event is cancelled, either because of erroneous entry of the A02 event or because of a decision not to transfer the patient after all. PV1-3 - Assigned Patient Location must show the location of the patient prior to the original transfer.
The Cancel Transfer message is as follows:

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

5.11 Event A13-Cancel Discharge/End Visit (ADT^A13)

The A13 event is sent when an A03 (discharge/end visit) event is cancelled, either because of erroneous entry of the A03 event or because of a decision not to discharge or end the visit of the patient after all. PV1-3 - Assigned Patient Location should reflect the location of the patient after the cancellation has been processed. Note that this location may be different from the patient's location prior to the erroneous discharge. Prior Location could be used to show the location of the patient prior to the erroneous discharge.
The Cancel Discharge/End Visit message is as follows:

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

{ADT Event A14-Pending Admit, ADT Event A15-Pending Transfer and ADT Event A16-Pending Discharge are not included in this tutorial. Please refer to your LINKTools® Technical manual for detail)

5.12 Event A17-Swap Patient (ADT^A17)

When it is decided that two patients will exchange beds, an A17 event is used.

The Swap Patient message is as follows:

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

5.13 Event A18-Merge Patient Information (ADT^A18)

Event A18 has been retained for backward compatibility only in version 2.3.1. Refer to sections 3.3.40, 3.3.41 and 3.3.42 instead. The A18 event was used to merge current and previous patient identification numbers: PID-3 - Patient Identifier List, PID-2 - Patient ID, PID-4 - Alternate Patient ID-PID, and PID-18 - Patient Account Number. This procedure is required, for example, when a previous patient is registered under a new patient identification number because of an error, or because there was insufficient time to determine the actual patient identification number. The merge event occurs when a decision is made to combine the information under either the new or the old identifier(s). The PID segment contains the surviving patient ID information. The MRG segment contains the non-surviving information.
From V2.3.1 onwards events A40 (merge patient-patient identifier list), A41 (merge account-patient account number), and A42 (merge visit-visit number) should be utilized in place of the A18 event.
This merge event is non-specific in that, as a result of the merge, several patient identifiers may or may not have changed. For sites requiring (or desiring) greater specificity with regard to this type of message, new events A40 (merge patient-patient identifier list), A41 (merge account-patient account number) and A42 (merge visit-visit number) are now available as alternatives. See section 3.6.2, "Merging patient/person information," for a discussion of issues related to implementing patient merge events.
The Merge Patient Information message is as follows:

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

Note: LINKTools® IDK Mapper can be configured to automatically update merged patient information to its intermediate database or vendor system database

5.14 Event A19-QRY/ADR - patient query

The following trigger event is served by QRY (a query from another system) and ADR (a response from an Patient Administration system.)
Another application determines a need for Patient Administration data about a patient and sends a query to the Patient Administration system.

The QRY/ADR 19 Patient query message is as follows:

MSH..QRD..[QRF] (Query Request message)

MSH..MSA.. [QAK]..QRD.. [QRF].. [EVN].. PID.. [PD1].. [{ROL}].. [{NK1}].. PV1.. [PV2].. [{ROL}].. [DB1]...
(HL7 ADT query response message)