ADT Messages Overview

adt messages overview the healthcare facility (adt system) may send surescripts an adt hl7 message when any of the following events occur at their facility adt^a01 hospital admission/check in adt^a03 patient discharge/end visit adt^a04 register a patient adt^a08 update patient information adt^a28 add person information adt^a31 update person information adt^a37 unlink patient information adt^a40 merge patient see the adt message flow use cases docid\ zpgygqnsz lcraog8et51 section for details on how these messages could be processed depending on the use case adt message flow use cases rle mpi load adt message flow this message flow is used when a vendor system sends an adt message to load patients to the rle mpi to make them available for record locator services note the adt^a01, adt^a04, adt^a08, adt^a28, adt^a31, and adt^a40 message types can be used for this use case the vendor initiates a request to load the patient to the surescripts rle mpi by sending an adt message via their vendor system note the adt^a01, adt^a04, adt^a08, adt^a28, adt^a31, and adt^a40 message types can be used for this use case surescripts creates an entry into the rle mpi that links the requesting location with the patient demographics surescripts responds with an ack if the update was successful or a nack if the message contained errors rle unlink patient adt message flow this message flow is used when a vendor system sends an adt message to unlink the patient in the surescripts mpi this can be used to remove a patient from the rle mpi or the cen mpi the adt^a37 message type can be used for this use case, or any of the accepted adt events can be used by setting pd1 11 to "n" to indicate the patient data should not be shared 1\ the vendor initiates a request to unlink the patient from the surescripts rle mpi or cen mpi by sending an adt message via their vendor system to unlink from rle notifications mp i the msh 5 field should be populated with "s00000000000004" when the portal is configured for both the rle and cen mpi to unlink from the rle mpi the msh 5 field should be populated with "s00000000000004" 2\ surescripts updates the rle mpi and/or cen mpi to remove the patient link links are removed by setting an expiration date on the record in the mpi once a record is deactivated, it is no longer shared with any requesting system 3\ surescripts responds with an ack if the patient removal was successful or a nack if the message contained errors update surescripts mpi based on adt message depending on the adt message type sent, the surescripts mpi will be updated in the following manner add/update patient information adt^a01, adt^a04, adt^a08, adt^a28, and adt^a31 the home community id from msh 4, assigning authority, and patient id from the message will be used to search for the patient in the mpi if the patient sent in the message does not already exist in the mpi, surescripts will add the patient to the mpi if the patient does exist, demographic information will be updated from the incoming message unlink patient adt^a37 when surescripts receives this message type and matches the patient information to the mpi, surescripts will then deactivate the patient record so that the record is no longer returned in mpi searches merging patient ids adt^a40 surescripts will update the mpi with the patient information found in segment pid 3 the patient information found in the mrg segment will be deactivated so that the record is no longer returned in mpi searches note if an adt^03 is sent for a patient discharge, surescripts will audit, but not process the message in this instance, the message will not be used to load or update the surescripts mpi adt message error processing in instances where surescripts receives a message that has errors or is unrecognizable, surescripts will respond with an hl7 ack that indicates an error (aka a nack or negative acknowledgment)