Almost every description of the ADT notification rule gets at least one detail wrong.

The RealityThe message says admitted. The handoff is a different problem.

⚠️

The Problem

A feed that reports location, not clinical context.

Notifications arriving with the minimum required content and nothing that helps the receiving clinician.

🔧

The Solution

Get the regulation right, then build past it.

Four notification points, the correct trigger events, and a deliberate decision about what else travels with them.

✅

The Resolution

Transitions the next clinician can act on.

The right people notified, at the right moments, with enough to be useful.

What the patient event notification rule actually requires

Start with the text, because the summaries disagree with each other.

42 CFR 482.24(d) applies where a hospital uses an electronic medical records system or other electronic administrative system conformant with the content exchange standard at 45 CFR 170.205(d)(2). Where it applies, the hospital must demonstrate that the system’s notification capacity is fully operational, and that notifications include at least patient name, treating practitioner name, and sending institution name.

The notification points are four, not three. The system must send at the time of the patient’s registration in the emergency department and the patient’s admission to inpatient services, and either immediately prior to or at the time of discharge or transfer from the emergency department and from inpatient services. All four are qualified with “if applicable”.

The fifth subparagraph covers recipients: the hospital must make a reasonable effort to ensure notifications reach all applicable post-acute care services providers and suppliers, plus the patient’s established primary care practitioner, primary care practice group or entity, or another practitioner or entity identified by the patient as primarily responsible for their care.

Three things this rule does not say

Each of these is asserted regularly and none of them is in the regulation.

It does not mandate HL7 v2.5.1 as the message format. Conformance with that standard is what makes the condition apply to you. CMS states directly, in its interoperability and patient access FAQs, that hospitals are not required to use a specific standard or technology to implement the notification, and may use messages based on different versions of HL7 messaging standards, summary care records using the C-CDA standard, or make notification information available via a FHIR-based API.

It does not require delivery into a physician’s EHR inbox. The AMA’s guidance on this is explicit: hospitals are not required to deliver electronic patient event notifications directly to a physician’s electronic health record inbox. The regulation permits sending through an intermediary that facilitates exchange of health information.

And it does not apply to physician practices. The condition binds hospitals, psychiatric hospitals and critical access hospitals, and only those whose systems meet the conformance trigger. A practice appears in this regulation as a recipient and carries no obligation under it.

Trigger events, and the one everybody gets wrong

ADT stands for admit, discharge and transfer, and the specific trigger events are published.

HL7’s terminology publication lists the event type codes. A01 is admit or visit notification. A02 is transfer a patient. A03 is discharge or end visit. A04 is register a patient. A05 is pre-admit. A08 is update patient information. A11, A12 and A13 are the cancellations of admit, transfer and discharge respectively.

And A06 is “change an outpatient to an inpatient”. That is the trigger that models an ED-to-inpatient conversion in many implementations, not A01. Writers and vendors routinely describe the ED admission as an A01, and if your downstream logic keys off A01 alone it will miss conversions in any system that models them properly. Worth checking rather than assuming, and exactly the sort of thing that surfaces during interface work.

Handoff communication, with the current number

There is a widely cited statistic here that is now more than a decade out of date, and the current one is worse.

The Joint Commission’s Sentinel Event Alert on inadequate hand-off communication, September 2017, estimated that a typical teaching hospital may experience more than 4,000 hand-offs every day, and cited a 2016 study finding communication failures responsible at least in part for 30 per cent of all malpractice claims, resulting in 1,744 deaths and 1.7 billion dollars in malpractice costs over five years.

That 30 per cent figure covers 2009 to 2013. A November 2025 benchmarking report from the same source, covering 2014 to 2024, finds such breakdowns now factor into 40 per cent of asserted cases, that communication-related cases had 39 per cent greater odds of closing with an indemnity payment, and that breakdowns are more common in ambulatory settings at 52 per cent than inpatient at 41 per cent. If you are citing the 30 per cent number, you are citing the older baseline.

The same Joint Commission alert notes that the Accreditation Council for Graduate Medical Education found 69 per cent of clinical learning environments did not have a standardised hand-off process, and that nine medical centres implementing a structured programme across 10,740 patient admissions reduced preventable adverse events by 30 per cent and medical errors by 23 per cent.

Intermediary exchange, and what a practice can actually do

Given the practice is not the regulated party, the useful question is what to ask for.

Most hospitals discharge this obligation through an intermediary — a health information exchange or a notification vendor — because the regulation permits it and because it is far easier than point-to-point delivery to every practice. That means the first question is usually not “will you send us notifications” but “which intermediary are you using, and are we registered with it as the established primary care practice for our patients”.

The second question is about content. The regulation’s minimum is patient name, treating practitioner name and sending institution name. That is enough to know something happened and not enough to act. Whether more travels with the notification is a local decision, and asking for it is reasonable. Where a practice wants notifications inside the clinical record rather than in an email, that is an interface project and belongs with managed IT support rather than with whoever answers the hospital’s helpdesk.

• Four notification points, not three. ED registration and discharge, inpatient admission and discharge.
• Do not key downstream logic on A01 alone. A06 carries the conversion.
• Ask which intermediary. Most hospitals meet this through one.
• Quote 40 per cent, not 30. The older figure is 2009 to 2013 data.

Qventive provides HL7 ADT feed emergency department services for New Jersey practices, usually within IT support for emergency medicine practices rather than as a standalone project.

Interface and integration work of this kind runs through emergency medicine EHR and IT support, and every inbound feed belongs in your HIPAA risk analysis alongside everything else that carries patient data.

ADT feeds: common questions