Clarity Beacon · care-transition alerts
Know the moment your patient moves
The day a patient leaves your building, you stop hearing about them, but Medicare keeps scoring you for another 30 days. Beacon will send one alert, with a named owner and a deadline, when that patient shows up at another hospital or ED. It will watch only while your care relationship lasts: a hard 31-day window after discharge, with auto-unsubscribe.
Treatment purposes onlyOne alert per real-world eventNo patient details in pings
- For
- SNF and CCRC leadership
- Status
- Early-access cohort forming · built on rails Clarity operates in production
How Beacon will work
Catch, resolve, route
From a raw signal on the network to one alert with an owner.
- 01
Catch the signal
Beacon will watch three rails, in order of lead time. The first is record queries on the nationwide networks Clarity operates on: when another organization asks the network about your patient, that request is the earliest signal, and it is what Beacon launches with. The second is the hospital event feeds that federal rules already require, connected market by market during your pilot. The third is events from Clarity’s own referral network.
- 02
Resolve the identity
Every raw event will go through the identity graph, which matches a patient’s many medical record numbers to one person and merges duplicates. Then comes the guardrail check: with no active enrollment, there is no alert and nothing is kept. An enrollment is the 31-day window after a SNF or CCRC discharge.
- 03
Route with a deadline
The rules engine will match each event to the right team by population, event type and provider type, then send one alert with an owner and a deadline. It will arrive in the Clarity app, as a text or email nudge with no patient details, or through a webhook.
Timing
An alert that can come before the admit
Standard notification starts once an admit message exists, which means at or after the admission. Beacon’s query rail is designed to start earlier, when another organization asks the network about your patient and the disposition can still change.
Awareness rail
Claims data
Typical time until the team knows
~90 days
What’s still possible when you find out
Retrospective reporting only
Awareness rail
Hospital admit notifications
Typical time until the team knows
hours after admit
sometimes next-day batch
What’s still possible when you find out
Discharge planning, since the admit has already happened
Awareness rail
Beacon query signal
launch capability
Typical time until the team knows
minutes-scale target
often before an admit exists
What’s still possible when you find out
Shape the disposition: treat and return, redirect in network, or step up care in place
| Awareness rail | Typical time until the team knows | What’s still possible when you find out |
|---|---|---|
Claims data | ~90 days | Retrospective reporting only |
Hospital admit notifications | hours after admit sometimes next-day batch | Discharge planning, since the admit has already happened |
Beacon query signal launch capability | minutes-scale target often before an admit exists | Shape the disposition: treat and return, redirect in network, or step up care in place |
These are typical latencies for each rail. They are not contractual commitments.
How it could play out
Illustrative scenario · synthetic patient- 01On the evening of day 9 after discharge, your patient walks into an out-of-network ED.
- 02The ED queries her record on intake. Beacon is designed to detect that query on the network.
- 03The identity graph confirms it is your patient and that her 31-day window is active.
- 04Your team is alerted with an owner and a deadline, before the admit decision.
- 05Your team reaches out within the hour with care context, the med list and disposition options. When the admit message arrives later, it is added to the same alert, so nobody gets a second ping.
The signal already exists
Since May 2021, hospitals have been required to send electronic admit, discharge and transfer notifications for emergency and inpatient events (42 CFR 482.24(d)). Getting that signal to your liaison is not part of the rule, and it is the part Beacon is designed to handle.
Most transition alerts arrive after the fact, once a discharge summary exists. Beacon’s query signal is designed to fire before the admit does.
The alert
One sentence your liaison can act on
Each alert gives the patient, context, event, provider, owner and deadline in a sentence short enough to read on the move.
Beacon alert · launch format
“Resident X (discharged 12 days ago, dx CHF) just admitted to St. Mary's ED. Liaison to call by 4pm.”— Clarity Beacon, concept
Guardrails
The limits Beacon will run under
Monitoring will last only as long as the care relationship does. Clarity notifies; your clinicians decide.
Treatment and care coordination only
Beacon will cover only patients with an active care relationship to your organization, under BAA. It won’t be used for population surveillance, analytics or model training. We set these limits before we designed the feature.
Why the window is 31 days
Beacon will watch each patient for 31 days after discharge, then unsubscribe on its own. The window brackets Medicare’s 30-day return rule: a patient who returns to skilled care within 30 days needs no new qualifying hospital stay, and monitoring will end when that rule stops applying. A new discharge starts a new window.
- Day 0 · discharge
- Day 30 · Medicare return rule
- Day 31 · auto-unsubscribe
Declined referrals are never monitored
If you decline a referral, that patient will never be enrolled. Beacon will check every raw event against your active enrollments first, and when there is no match it will send nothing and keep nothing.
No patient details in the ping
Text and email nudges will say only that a time-sensitive alert is waiting. Patient details will appear only after sign-in, behind role-based access, or arrive through a webhook into the system you already run.
On Clarity’s production platform
Beacon will run on the platform Clarity operates under BAA today: encryption in transit and at rest, role-based access, hard tenant isolation verified in evaluation, and full audit logging on every view, alert and outcome.
Identity graph · in production today
One alert per patient, even with many record numbers
The identity graph resolves hospital MRNs, SNF MRNs and network identifiers to one canonical patient. Each real-world event will produce one alert, with no duplicates and no missed matches.
Clarity matches the records and will route the alert, and your clinicians decide what to do. Every alert will carry a named owner, an outcome and an audit trail.
By setting
What the heads-up is worth
The same alert pays off differently in each setting. Both figures are illustrative.
Skilled nursing
~$135k/yr
1 re-referral won per month × ~$11,250 per skilled stay
Win the re-referral
A former patient who lands in an ED may soon need a skilled bed again. Beacon will tell your team in time to reach out while the 30-day window is still open and be the first credible yes. Winning back one referral a month is worth ~$135,000 a year to a reference 120-bed facility, before counting any protection of your readmission rate or VBP withhold.
CCRCs and life plan communities
~$110k/yr
half of ~19 leaked skilled stays recaptured × ~$11,250
Bring the resident home
When a resident is admitted to another hospital or ED, your liaison will know in time to start the return-to-campus conversation before the packet goes out to outside SNFs. Recapturing half of a typical community’s leaked stays is worth ~$110,000 a year. It also keeps the promise residents moved in for: we will know, and we will come get you.
This is the same recapture the CCRC page counts, not an extra amount.
Illustrative economics for the reference models (120-bed SNF · 350-resident community). These are targets, not guarantees, and not audited customer results. The pilot replaces every line with your baseline.
FAQ
Questions about Beacon
What compliance officers, DONs and CFOs tend to ask first.
Not yet. Beacon is in development and launching soon, and the early-access cohort is forming now. What it runs on is already in production: nationwide record connectivity, the patient identity graph and the cited-AI document pipeline. Design partners get first access and help shape the launch.
What runs today vs. what’s launching
In production now: nationwide record connectivity, the patient identity graph, the cited-AI document pipeline, and the team and workflow platform.
Launching with Beacon: query-signal detection, the alert rules engine, and routed delivery. Design partners get first access and help shape the launch.
Join the Beacon early-access cohort
The early-access design-partner program is forming now. Partners shape the alert types, plays and delivery channels, start with a shadow-mode pilot on their own discharges, and are first in line at launch.