Beacon targets minutes-scale delivery, and the query rail is designed to fire before an admit is even recorded. We characterize latency honestly by rail, and we won’t put the phrase “real-time” in a contract until network partner latencies are contractually confirmed.

How do you know it’s my patient?

Clarity’s identity graph resolves every event to one canonical patient across MRNs and systems. It is the same production graph that already resolves inbound network documents in Clarity’s pipeline today. One patient, many identifiers, one alert.

Does this work for Medicare Advantage patients?

Beacon will monitor and alert regardless of payer; the signal doesn’t care who’s paying. The recapture economics differ. The no-new-qualifying-stay math is Medicare fee-for-service, and MA plans may require reauthorization on readmission, so Beacon will flag payer context on each alert at launch and your team will know which play applies.

Do we need Clarity Admit to use Beacon?

No. Beacon will deliver standalone through text and email nudges with no patient details, and through webhooks, with EHR inbox delivery on the roadmap. It is simply better with Clarity Admit, where alerts become workflow items with the patient’s five-gate context and a readmission path attached.

Clarity Beacon · care-transition alerts

Know the moment your patient moves

The day a patient leaves your building, you stop hearing about them. Medicare keeps scoring you for another 30 days anyway. Beacon will close that gap: one clean alert when your patient shows up at another hospital or ED, with a named owner and a deadline, watched only as long as your care relationship lasts. A hard 31-day window after discharge, with auto-unsubscribe.

Request early access See how it works

31-day window, hard auto-unsubscribeTreatment purposes onlyOne alert per real-world event

For: SNF, CCRC and ACO leadership
Status: Early-access cohort forming · built on rails Clarity operates in production

Beacon alertConcept

EDOut of network

Resident X (discharged 12 days ago, dx CHF) just admitted to St. Mary's ED. Liaison to call by 4pm.

Day 12 of 31

Window open · 19d left · auto-unsubscribes at day 31

Owner: Liaison
Deadline: 4:00 pm today
Signal: Record query
Identity: 3 MRNs → 1 patient

Direct-return eligible · no new 3-day qualifying stay

The playNext best actions, in order

01Call the ED
02Initiate direct return
03Loop a clinician

How Beacon will work

Catch, resolve, route

Three moves, from a raw signal to one alert with an owner.

01
Catch the signal
Three rails, in order of lead time. First, record-query detection on the nationwide networks Clarity operates on. When another organization asks the network about your patient, that question is itself the earliest signal, and it is the launch centerpiece. Second, the hospital event feeds federal rules already require, wired per market during your pilot. Third, events from Clarity’s own referral network.
02
Resolve the identity
Every raw event will hit the identity graph. One patient, many medical record numbers, one match, duplicates collapsed. Then the guardrail check: no active enrollment, no alert, and nothing is kept. An enrollment is the 31-day window after a SNF or CCRC discharge, or a roster seat for an ACO’s attributed members.
03
Route with a deadline
The rules engine will match team, population, event type and provider type, then deliver one alert with an owner and a clock. It arrives in the Clarity app, or as a text or email nudge that carries no patient details, or through a webhook.

Why it’s different

The alert that arrives before the admit

Think of it like a smoke detector versus a fire report. Traditional notification begins when an admit message exists, which means at or after the admission. Beacon’s query rail is designed to begin earlier, when another organization asks the network about your patient, while the disposition is still shapeable.

Awareness rail
Claims data
Typical time until the team knows
~90 days
What’s still possible when you find out
Nothing. 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. The admit 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 itself: treat and return, in-network redirect, step up in place.

Awareness rail	Typical time until the team knows	What’s still possible when you find out
Claims data	~90 days	Nothing. Retrospective reporting only.
Hospital admit notifications	hours after admit sometimes next-day batch	Discharge planning. The admit already happened.
Beacon query signal launch capability	minutes-scale target often before an admit exists	Shape the disposition itself: treat and return, in-network redirect, step up in place.

Awareness rail

Typical time until the team knows

What’s still possible when you find out

Claims data

~90 days

Nothing. Retrospective reporting only.

Hospital admit notifications

hours after admit

sometimes next-day batch

Discharge planning. The admit already happened.

Beacon query signal

launch capability

minutes-scale target

often before an admit exists

Shape the disposition itself: treat and return, in-network redirect, step up in place.

Latencies are directional characterizations of each rail, not contractual commitments.

The moment to picture

Illustrative scenario · synthetic patient

01Day 9 after discharge. Your patient walks into an out-of-network ED in the evening.
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.
05Outreach within the hour: care context, med list, disposition options. When the admit message arrives later, it folds into the same alert. No second ping.

“Within the hour” describes your team’s outreach, not Beacon’s latency. Each rail’s latency is characterized in the table above, not promised.

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)). The rule mandates the signal. It does not deliver it to your liaison. Beacon is designed to close that last mile.

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 line your liaison can act on

Patient, context, event, provider, owner, deadline. Specific enough to run the play, 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

Patient · context · event · provider · owner · deadlineone sentence, one job · synthetic patient

Stated up front

Guardrails are the feature

Monitoring will last exactly as long as the care relationship does, and not a day longer. Clarity notifies; your clinicians decide.

Treatment and care coordination only

Beacon will operate for patients with an active care relationship to your organization, under BAA. Never population surveillance, analytics or model training. We designed the guardrails before the feature.

A hard 31-day window, for a reason

Beacon will watch for 31 days after discharge, then unsubscribe on its own. That window brackets Medicare’s 30-day return rule exactly. A patient who returns to skilled care within 30 days needs no new qualifying hospital stay. Monitoring will end the day that logic does. A new discharge starts a new window. For an ACO, the relationship is the attribution year, reconciled quarterly.

Day 31 of 31Day 31 · auto-unsubscribe

Medicare 30-day return rule

Day 0 · discharge
Day 30 · Medicare return rule
Day 31 · auto-unsubscribe

Declined referrals are never monitored

Decline a referral and that patient will never be enrolled. Every raw event will be checked against your active enrollments first: no active enrollment, no alert, nothing kept.

No patient details in the ping

Text and email nudges will say only that a time-sensitive alert is waiting. Patient details will render 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

Machine resolution, human action

The identity graph resolves hospital MRNs, SNF MRNs and network identifiers to one canonical patient. One real-world event will become one alert, not four duplicates or a missed match.

The machine resolves and will route. It never acts. Clarity notifies; your clinicians decide. Every alert will carry a named owner, an outcome and an audit trail.

Concept · synthetic patient · three identifiers resolved to one patient, one alert

Three audiences

What the heads-up is worth

The same alert, three different paydays. Each is an illustrative model a pilot replaces with your own baseline.

Skilled nursing

~$135k/yr

1 re-referral won per month × ~$11,250 per skilled stay

Win the re-referral

Readmits are referrals about to happen. When a patient you discharged lands in an ED, your team will hear in time to reach out, protect the 30-day window, and be the first credible yes. Winning one re-referral a month is ~$135,000 a year for a reference 120-bed facility, before counting readmission-rate and VBP-withhold protection.

CCRCs and life plan communities

~$110k/yr

half of ~19 leaked skilled stays recaptured × ~$11,250

Bring the resident home

When a resident admits to another hospital or ED, your liaison will know in time to start the return-to-campus conversation, before the packet ever broadcasts to outside SNFs. Recapturing half of a typical community’s leaked stays is ~$110,000 a year, and every stay kept on campus keeps the continuum promise behind it: we will know, and we will come get you.

The same recapture lever the CCRC page counts, seen from the alert.

ACOs and risk-bearing groups

~$11,600

per caught event · ~$400 visit vs ~$12,000 ED episode

Intervene in place

An attributed patient shows up in an out-of-network ED and your team will learn while the disposition is still shapeable, not 90 days later from claims. An intervene-in-place visit instead of the reflexive ED-and-admit path avoids ~$11,600 per caught event, with readmissions tracked as a first-class counter-metric.

Illustrative economics for the reference models (120-bed SNF · 350-resident community · 20,000-life ACO). Targets, not guarantees, and not audited customer results. The pilot replaces every line with your baseline.

Common questions

Asked first, answered first

The questions a compliance officer, a DON and a CFO ask before anyone asks for a demo.

Not yet. Beacon is in development and launching soon, and the early-access cohort is forming now. The infrastructure underneath it runs in production today: nationwide record connectivity, the patient identity graph, and the cited-AI document pipeline. Design partners get first access and shape the launch.

Yes, and the limits are the point. Beacon will run on the nationwide record networks Clarity already uses, under BAA. It will work for treatment and care coordination only, and only for patients with an active care relationship to your organization. Monitoring will last exactly as long as that relationship does. For a SNF or CCRC discharge, that is a 31-day window that shuts off automatically, and a new discharge starts a new window. For an ACO, attributed members stay covered for the attribution year and drop off the day attribution ends. No population surveillance, no monitoring of declined referrals, and no patient details in the notification itself.

No. The design goal is fewer, better alerts: deduplicated at the identity graph, filtered by your team’s population, event type and provider subscriptions, and routed to a named owner with a deadline. An alert with an owner and a deadline is a task, not noise, and the pilot tunes volume until your team says it’s right. At a reference 120-bed SNF that works out to roughly two alerts a week, about 96 alertable events a year, each with one owner. That figure is illustrative, and it is the first thing the pilot measures against your own discharges.

Days 1 through 30 run in shadow mode: Beacon will generate alerts while your team logs what it would otherwise have known, and when. That produces your baseline. Days 31 through 90 run live with SLA tracking. Success is defined up front: a documented lead-time gain, at least one recaptured admission or documented interception, and an alert-acknowledgement rate inside SLA that you set with us before day one. You renew on your numbers, not our illustrations.

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. Beacon is in development and launching soon. The early-access cohort is forming now, and design partners get first access and shape the launch.

See your own baseline, not our slide

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.

Request early access See Clarity Admit