It runs on days, not months
Every other branch tolerates a monthly list. This one does not. An event that reaches the practice on day five has already lost the contact window, and an event that reaches it by claims has lost the whole thing.
A working guide for practice administrators, care coordinators, and analysts: what a transition is and why it runs on a different clock, where the events come from, the windows that count, who owns each step, how the work is measured honestly, where it breaks, and what the platform does and does not do for it today.
By Jonan Portal Alvarez, Chief Executive Officer, Alara Healthcare (management services) · Updated September 10, 2026 · About 8 minutes
A transition of care is the stretch between one setting and the next: a hospital discharge to home, an emergency visit that ends without an admission, a move from a skilled nursing facility back to the practice's care. It is the most dangerous week in a member's year and the most expensive one in a contract's. Readmissions inside thirty days are what plans measure, what Star Ratings score, and what a risk contract pays for twice.
It is its own branch of population health because it runs on a different clock. Risk adjustment and quality run on the calendar year. A transition runs on days: an event today, a contact within two business days, a visit within a week or two, a window that closes at thirty. A monthly cadence cannot see it. Only a daily one can.
Every other branch tolerates a monthly list. This one does not. An event that reaches the practice on day five has already lost the contact window, and an event that reaches it by claims has lost the whole thing.
The practice does not generate a discharge. A hospital, an exchange, a plan, or the member tells it, and each of those sources arrives at a different speed with a different share of the events. The first job of the branch is receiving.
The follow-up visit, the medication review, and every care decision belong to the practice's clinicians. The administrative work is everything around them: receiving the event, finding the member, booking the visit, and measuring whether it happened in time.
| Source | What it tells you | How fast | What to watch |
|---|---|---|---|
| Hospital event notifications | Admission, discharge, and transfer messages from the hospital or a health information exchange, with the member, the facility, and the event time. | Same day, often within hours. | Hospitals are required to send these to a patient's primary care practitioner when they can identify one. If the practice is not registered with the exchange, or the hospital does not know the member is yours, the message never comes. |
| The plan's census and authorization data | Members the plan knows are inpatient, from authorizations and concurrent review. | Daily to weekly. | Coverage depends on the plan's process. Not every admission is authorized in advance, and emergency visits usually are not on it at all. |
| Claims | The admission or the emergency visit, with diagnoses, dates, and the facility. | Weeks to months. | Too late to act on. Useful for the denominator, the readmission rate, and finding the events the notifications missed. |
| The member or the family | A call, a portal message, a walk-in. | Whenever they think of it. | The most common source in a practice with no feed, and the least reliable one. |
These are the windows of the Medicare transitional care management service. Most practices use them as the template for every transition, whether or not that service applies.
The discharge happens. The clock starts whether or not the practice knows, which is why the source table above decides everything that follows.
An interactive contact with the member or the caregiver by the practice's clinical staff, by phone, secure message, or in person. An attempt is recorded as an attempt. What counts for the service is the practice's rule to apply, and a voicemail is not a contact for the purposes of the work.
A face-to-face visit, within seven days for the higher-complexity transitions and fourteen for the rest. The clinician decides the clinical content, including the medication review. The scheduler decides whether it happens at all.
The stretch the plan measures. A member readmitted inside it counts against the practice's rate whether or not the follow-up happened, which is why the visit is only the middle of the branch, not the end.
The event closes. Contact and visit timing, the readmission outcome, and the owner are recorded, and the month's events roll into the figures the administrator reads.
Owns the event from receipt to closure: the contact inside two business days, the questions the clinician wants asked, the record of what was said, and the handoff to scheduling. Clinical staff, employed by the practice, making clinical judgments.
Owns the visit. A follow-up slot inside the window has to exist before it can be booked, which means the schedule holds capacity for discharges it does not know about yet.
Owns the visit's content, the medication reconciliation, the decisions, and whether the member needs more than a visit. Everything else on this list prepares that half hour.
Owns the denominator and the figures: every admission and emergency visit from every source, matched to the member, with the contact date, the visit date, the readmission outcome, and the owner. Reports the share received on time against the share found later by claims.
Owns the feed: the registration with the exchange, the provider mapping the hospital uses to route the message, and the identity match between the notification and the member. When an event reaches nobody, this is where the fault usually is.
The share of admissions and emergency visits the practice learned about before day two, by source. The first figure to fix, because every other one is measured only on the events you knew about.
Interactive contacts, not attempts, as a share of discharges. Read beside the attempts figure: a high attempt count and a low contact count is a phone number problem, not a staffing one.
Visits kept inside seven or fourteen days, as a share of discharges. A visit booked for day twenty is a miss that looks like a success on the schedule.
From claims, months later, with the denominator from the same claims. It is the plan's measure, and the only one on this list that says whether the branch worked rather than whether it ran.
The share of events with a named owner and a current status. An event nobody owns is a report, and in this branch a report is a readmission waiting to happen.
Care Bridge is the platform's transitions module, and it is in development. It appears in the platform's navigation, but no screens sit behind it yet, and its scope and timing will be published when it ships. This guide is about the work, which does not wait for software, and the boundary below is stated so that nobody reads a plan as a feature.
Where Care Bridge sits among the other modules, and its current status: Care Bridge on the platform page
Any move between settings that puts the member at risk in the days that follow: a hospital discharge, an emergency visit that ends without admission, a discharge from a skilled nursing or rehabilitation facility, and an observation stay. Plans measure the readmissions that follow an inpatient stay; a practice that wants fewer of them treats every one of these as an event with an owner.
With registration. Hospitals are required to send electronic event notifications to a patient's primary care practitioner when they can identify one, usually through a health information exchange. Find out which exchange your hospitals use, register the practice and its clinicians, and check that the hospitals have the right clinician on file for your members. Until then, ask the plan for its census data and use claims to measure how much you are missing.
It is an interactive contact by the practice's clinical staff, which can be a call, a secure message the member answers, or an in-person conversation. An attempt is recorded as an attempt. Whether an unsuccessful attempt counts for a billable service is the practice's rule to apply under its own billing guidance; for the purposes of the work, a voicemail is not a contact.
The clinician. The visit's content, the medication reconciliation, the orders, and whether the member needs more than a visit are clinical decisions and belong to the practice's clinicians alone. The administrative work is making sure the visit exists inside the window and that the discharge information reached the clinician before it.
From claims, months later. Claims give both the admissions and the readmissions, so the rate has a denominator, which the notification feed alone never does. Report the rate with its denominator and its period every time, and report separately how many of those admissions the practice knew about before the member came home.
It is in development. It appears in the platform's navigation, no screens sit behind it yet, and its scope and timing will be published when it ships. Nothing in this guide depends on it: the windows, the owners, and the measures are the work, and the work runs in the practice's own process until the module carries it.
Bring the process you have, even if it is a phone tree, and we will map it to the windows, the owners, and the measures.