--- title: ADT Message Examples slug: record-locator-exchange-adt/guide/adt-message-examples docTags: createdAt: 2026-06-02T15:11:18.746Z --- ## RLE Enrollment Example :::ExpandableHeading ## Incoming ADT Message Example The message below is an example of an incoming ADT message that could be used to load the RLE MPI. MSH|^\~\\&|P00000000000000|urn\:oid\:urn\:oid:2.16.840.1.555555.3.5555|S00000000000004|2.16.840.1.113883.3.2054.2.1|20181004100753||ADT^A01|20181004100753HS100002510402|P|2.5.1| EVN|A01|20181004100640|20181004100640|01||20181004100640|| PID|1||25104^^^2.16.840.1.55555.3.3490.4.5555.2|25104^^^2.16.840.1.55555.3.3490.4.5555.2| Smith^John^R ||19200101|M||AMERICAN INDIAN OR ALASKA NATIVE|123 MAIN STREET^^LOUISVILLE^KY^40202^^PATIENT'S HOME/RESIDENCE^^||6195551990|| PD1|||||||||||Y|| PV1|1|O|MAIN STREET AGENCY^^^ABC\&BRANCH HS1^^^^^HOSPICE 1|READMISSION|||1912052614^WROBZZZLESKI^CHERI^^^^MD|^^^^^^||||||||||HOSPICE|28027||||||||||||||||||||||CURRENT|||20180905000000||||||||| DG1|1|ICD10|C20^MALIGNANT NEOPLASM OF RECTUM|MALIGNANT NEOPLASM OF RECTUM|20180826000000|O|||||||||1||||| ::: :::ExpandableHeading ## ACK Example The message below is an example of ACK message sent in response to the RLE Enrollment message above. MSH|^\~\\&|S00000000000004|2.16.840.1.113883.3.2054.2.1|P00000000000000|urn\:oid:2.16.840.1.555555.3.5555|20181004090753.868-0500||ACK^A01^ACK|1|P|2.5.1 MSA|AA|20181004100753HS100002510402 ::: ## Patient Activity Example :::ExpandableHeading ## Incoming ADT Message Example The message below is an example of an incoming ADT message used to notify Surescripts RLE of activity on a patient seen at the sender’s location. MSH|^\~\\&|P00000000000000|urn\:oid:1.2.555.666.77|RLENotification|2.16.840.1.113883.3.2054.2.1|20181017141403||ADT^A01|df328c59-40b2-4890-acfd-49aa436ea2f1|P|2.5.1| EVN|A01|20181017141156|20181017141156|01||20181017141156|| PID|1||987654321^^^2.16.840.1.55555.3.5555.4.3333.2|12554^^^2.16.840.1.44444.3.4444.4.4444.2|Miller^Anne^||19881103|F|||123 MAIN STREET^^LOUISVILLE^KY^40202^^^^||6195551990|| PD1|||||||||||Y|| PV1|1|O|PatientLocation^^^TreatmentFacility^^^^^FacilityDescription|NEW ADMISSION|||1444448870^ZZZTESTDoctor^SARAH^^^^MD|^^^^^^|1255887774^ZZZJones^Lucas^^^^M.D.|||||||||HOME HEALTH|VisitNumber12345||||||||||||||||||||||CURRENT|||20180905000000||||||||| DG1|1|ICD10|C26.0^MALIGNANT NEOPLASM OF INTESTINAL TRACT, PART UNSPECIFIED|MALIGNANT NEOPLASM OF INTESTINAL TRACT, PART UNSPECIFIED|20180905000000|O|||||||||1||||| ::: :::ExpandableHeading ## ACK Example The message below is an example of an ACK message sent in response to the Patient Activity message above. MSH|^\~\\&|RLENotification|2.16.840.1.113883.3.2054.2.1|P00000000000000|urn\:oid:1.2.555.666.77|20181004075459.212-0500||ACK^A01^ACK|939|P|2.5.1 MSA|AA|df328c59-40b2-4890-acfd-49aa436ea2f1 ::: :::ExpandableHeading ## Outgoing ADT Message Example The message below is an example of an outgoing message Surescripts would generate in response to the incoming inbound patient activity message example shown above. The differences between the inbound and outbound patient activity message examples include the following: 1. **Home community ID** of the intended recipient is in the receiving facility (MSH.6). 2. A **new message ID** is included. 3. In PID.3 for the outbound notification there be 2 or more patient identifiers. The first is the receiving system’s Patient ID and Assigning Authority at the location where the system has enrolled the patient for notifications. The second is the **sending system’s Patient ID and Assigning Authority** at the location where the patient event occurred. If the sending system has multiple patient IDs they will be included here as well. - The recipient Patient ID would be used to match the patient in the recipient’s system. - The **sender’s Patient ID and Assigning Authority** would be used to send an XCA Query or FHIR® document search for the patient. 4. Any trailing empty fields or empty sub-fields (|| or ^^^) are not included on the outgoing ADT message. MSH|^\~\\&|P00000000000000|2.16.840.1.113883.3.2054.2.1|RLENotification|**urn:oid:1.2.555.666.77**|20181017141403||ADT^A01|**390c60c6-3d35-4983-8ae0-ebfc4f54922b**|P|2.5.1| EVN|A01|20181017141156|20181017141156|01||20181017141156|| PID|1||1400001^^^2.16.999.7.1111.1\~**987654321^^^2.16.840.1.55555.3.5555.4.3333.2**|12554^^^2.16.840.1.44444.3.4444.4.4444.2|Miller^Anne||19881103|F|||123 MAIN STREET^^LOUISVILLE^KY^40202||6195551990|| PD1|||||||||||Y|| PV1|1|O|PatientLocation^^^TreatmentFacility^^^^^FacilityDescription|NEW ADMISSION|||1444448870^ZZZTESTDoctor^SARAH^^^^MD||1255887774^ZZZJones^Lucas^^^^M.D.|||||||||HOME HEALTH|VisitNumber12345||||||||||||||||||||||CURRENT|||20180905000000||||||||| DG1|1|ICD10|C26.0^MALIGNANT NEOPLASM OF INTESTINAL TRACT, PART UNSPECIFIED|MALIGNANT NEOPLASM OF INTESTINAL TRACT, PART UNSPECIFIED|20180905000000|O|||||||||1||||| ::: ## Patient Merge Example :::ExpandableHeading ## Incoming ADT Message Example The message example below is of an incoming ADT message used to merge two patient IDs into a single patient ID. MSH|^\~\\&|P00000000000000|urn\:oid:2.16.840.1.55555.3.5555|S00000000000004|2.16.840.1.113883.3.2054.2.1|20160902233701||ADT^A40|1538657421899|P|2.5.1| EVN|A40|20160902233701||||20160902604701|| PID|1||FV0EQNWNAX^^^2.16.840.1.113883.4.391.33.1701D^^^||Ek^Hanna^3OCXO3K8NN||19450608|F||Caucasian|3500 Cedar Ave^^Minneapolis^MN^55407||6125289462^^^^^^|||Single|| PD1||||^Bob^Ross^M^^^^^VAL||||||||| MRG|V7MQ4R0O59^^^&2.16.840.1.113883.4.391.33.1701D^||||||| ::: :::ExpandableHeading ## ACK Example The message example below is of an ACK message sent in response to the patient merge message example above. MSH|^\~\\&|S00000000000004|2.16.840.1.113883.3.2054.2.1|P00000000000000|urn\:oid:2.16.840.1.55555.3.5555|20181004075021.969-0500||ACK^A40^ACK|610|P|2.5.1| MSA|AA|1538657421899| ::: ## Unlink a Patient Example :::ExpandableHeading ## Incoming ADT Message The message example below is of an incoming ADT message used to unlink a patient from the Surescripts MPI. MSH|^\~\\&|P00000000000000|urn\:oid:3.3.3.3.3.3.3333.3.3.3333|RLENotificationEnrollment|2.16.840.1.113883.3.2054.2.1|20180607154500|GetKmr|ADT^A37|MASADT11528744550|P|2.5.1| EVN|ADT^A37|20180611604701||||20180611604701|| PID|1|3117101508|3117101508^^^&2.16.840.1.113883.3.333^^^&2.16.840.1.113883.4.391.33|222|DEVINTTWO^KELLI^||19860317|F|||A37 KELLI COURT ^^LOCKER^ND^65886||6511112222^^^^^^|| PD1|||^Care^Primary^M^^^^^NPI|||||||||| PV1|1|O|||||^Attending^CARL^N^^^^^NPI||^Consulting^Carl^L|||||||||HOME HEALTH|VisitNumber12345||||||||||||||||||||||CURRENT|||20180905000000||||||||| ::: :::ExpandableHeading ## ACK Example The message example below is of an ACK message sent in response to the message above. MSH|^\~\\&|RLENotificationEnrollment|2.16.840.1.113883.3.2054.2.1|P00000000000000|urn\:oid:3.3.3.3.3.3.3333.3.3.3333|20180611141550.549-0500||ACK^A37^ACK|102|P|2.5.1| MSA|AA|MASADT11528744550| ::: ## Discharge a Patient Example :::ExpandableHeading ## Incoming ADT Message The message example below is of an incoming ADT message used to notify a vendor that there was activity of a patient discharge on a patient they enrolled in RLENotifications. MSH|^\~\\&||urn\:oid:2.16.840.1.113883.3.2054.2.1|RLENotification|2.16.840.1.113883.3.2054.2.1|20171025123115|CMB220|ADT^A03^ADT\_A03|27558|P|2.5.1| EVN|A03|20171025123115||ADT\_EVENT|^Skyjumper^Luke^^^^^^OHSA^^^^^RMH1|20171025123100|| PID|1||123456789^^^2.16.840.1.113883.3.2054.3.1||Smith^John^R||19520318|M|||406 W\.DandridgeSt^Suite A^Anywhere^AR^77777||(651)123-4567^^^name\@domain.com|(612)999-8888| PD1|||Taylor Hospital^^1014100|26172^Jones^Jenny^Sue^^^^^STARPROV^^^^STARPROV||||||||| PV1|1|INPATIENT|420^4201^01^DMH1^D^^^^^^DEPID|EL|||22897^INC^Central^Taylor Primary Care^^^^^STARPROV^^^^STARPROV|||Internal Med||||Phys/Clinic|||11178^Deep^Luke^Cage^^^^^STARPROV^^^^STARPROV||6097431924|SELF||||||||||||||||HOME||||||||20171025102421|20171025123100|||||24172980001||| ::: :::ExpandableHeading ## ACK Example The message example below is of an ACK message sent in response to the Patient Discharge message above. MSH|^\~\\&|RLENotification|2.16.840.1.113883.3.2054.2.1||urn\:oid:2.16.840.1.113883.3.2054.2.1|20180308092622.522-0600||ACK^A03^ACK|401|P|2.5.1| MSA|AA|27558| ::: ## Error Examples :::ExpandableHeading ## Error Example 1: Missing Date/Time Stamp The message example below is of an error message that would be returned in response to an RLE enrollment request that did not include a Date/Time stamp. MSH|^\~\\&|RLENotificationEnrollment|2.16.840.1.113883.3.2054.2.1||urn\:oid:3.3.3.3.3.3.3333.3.3.3333|20180606153116.825-0500||ACK^A01^ACK|5|P|2.5.1| MSA|AR|060100A01405 ERR|||207^Application internal error^HL70357^^^^^^Validation failed: 'null' required to be a HL7 datetime string and a valid datetime value (e.g no month greater than 12) (Date/Time Of Message) at MSH-7(0)-1-1|E| ::: :::ExpandableHeading ## Error Example 2: Missing Message Control ID The message example below is of an error message that was sent in response to an incoming ADT message that did not include the Message Control ID. MSH|^\~\\&|RLENotificationEnrollment|2.16.840.1.113883.3.2054.2.1||urn\:oid:3.3.3.3.3.3.3333.3.3.3333|20180606153400.562-0500||ACK^A08^ACK|10|T|2.5.1 MSA|AR ERR|||207^Application internal error^HL70357^^^^^^Validation failed:  'null' required to be not empty (Message Control ID) at MSH-10(0)-1-1|E | ::: :::ExpandableHeading ## Error Example 3: Missing Assigning Authority The message example below is of an error message that was sent in response to an incoming ADT message that did not include the Assigning Authority information. MSH|^\~\\&|RLENotificationEnrollment|2.16.840.1.113883.3.2054.2.1||||urn\:oid:3.3.3.3.3.3.3333.3.3.3333|20180606153948.552-0500||ACK^A31^ACK|17|T|2.5.1 MSA|AR|060100A311805 ERR|||207^Application internal error^HL70357^^^^^^Validation failed: Assigning Authority is Missing at PID-3-4|E| :::