Clinical intelligence
Data sources and limitations behind clinical signals
- Input classes
- Nine, each with a stated limitation
- Observation cadence
- Shift-based, not continuous
- Published performance figures
- None
- Last reviewed
- October 16, 2026
Author and clinical review
Written by the SeniorCRE Clinical Intelligence Group. Clinically reviewed by the SeniorCRE Clinical Review Panel.
Registered-nurse clinical operations review (director-of-nursing and chief-nursing-officer practice background in skilled nursing and assisted living), paired with a regulatory-compliance reviewer and a data-governance owner. Every clinical page in this cluster requires all three sign-offs before publication.
SeniorCRE publishes the review structure rather than an individual byline: the dedicated Clinical Safety Officer seat is open and under active recruitment, and no individual clinician is named as a public sponsor of this content until that seat is filled and the person consents to attribution. Nothing on these pages is medical advice, and none of it establishes a clinician–patient relationship.
Reviewed at publication and re-reviewed at least quarterly, or on any change to cited guidance. Last reviewed October 16, 2026. The Clinical Safety Officer role is open.
Scope and evidence posture. SeniorCRE clinical intelligence is decision support: it surfaces deterioration signals and reconciles them with staffing, documentation, and operating context so a licensed clinician can act sooner. It does not diagnose, does not assign a clinical severity score of record, and does not initiate treatment or transfer. Capabilities described here are built; there is no published operator-production outcome data, and SeniorCRE makes no claim about mortality, transfers, length of stay, survey results, or cost avoided.
Capability · Validated · Production
Capability
Does it exist in the product?
Built
The signal framework, the acknowledgment and escalation ladder, dismiss-with-reason, provenance capture, and the per-signal-class kill switch are implemented in the platform.
Validated
Has it been exercised, and against what?
Built; not validated
Exercised against synthetic resident fixtures and vendor-documented interface contracts, with clinical review of wording, ranking, and dismissal flow. No external clinical validation study has been published, and no performance figure is claimed.
Production
Is it running on real residents today?
Not in operator production
There is no completed operator-production clinical deployment and no operator-production outcome data. Live clinical exposure is gated on an executed BAA, a named clinical owner, the operator’s own written change-in-condition protocol, a silent-run period, and written DON acceptance.
Every input class, its source system, and the limitation it imposes
A clinical signal is only as good as the observation behind it. Each row states how reliably that observation is captured in real senior housing & care operations, and what it therefore cannot support.
| Input class | Source system | Capture reliability | Limitation it imposes |
|---|---|---|---|
| Structured vital signs (temperature, heart rate, respiratory rate, blood pressure, SpO₂) | EHR vitals capture or point-of-care device integration | Reliable when captured as structured fields on a stated cadence; respiratory rate is the most frequently missing or estimated value in practice. | Signal sensitivity is bounded by capture frequency. A once-per-shift cadence cannot support the lead time reported in acute-care studies with continuous monitoring. |
| Mental-status and behavior documentation | Nursing progress notes, behavior tracking | Often free text, and the resident’s own baseline is frequently implicit rather than recorded. | Without a structured baseline, a change from baseline can only be inferred weakly. Free-text extraction is not treated as equivalent to a structured observation. |
| Medication administration and orders | eMAR and orders — the incumbent system, or SeniorCRE’s own eMAR where the operator elects it | High for administration events; timing granularity varies by workflow. | Exactly one authoritative MAR at all times. In a parallel configuration SeniorCRE reads one direction only and writes nothing back unless a clinician initiates it. |
| Care-task and ADL completion | Care delivery / point-of-care task records | Good coverage where documentation is enforced at the point of care; batch documentation at end of shift distorts timing. | Task records reflect what was documented, not necessarily what was delivered. Absence of a record is treated as a documentation gap, never as a clinical finding. |
| Dietary intake, hydration, and weights | Dietary and nutrition records, weight log | Intake is often estimated in bands rather than measured; weights vary with time of day, scale, and technique. | Useful as trend evidence only. A single reading is never treated as a deterioration signal on its own. |
| Incidents, falls, and change-in-condition reports | Incident reporting and risk-management systems | Reported reliably for reportable categories; near-misses are systematically under-reported. | Under-reporting is not randomly distributed, so incident data must never be used to compare communities or staff without acknowledging reporting-culture differences. |
| Staffing, scheduling, and worked hours | Scheduling and payroll or time systems | Payroll is authoritative for hours paid; the schedule reflects intent, not delivery. | Staffing context explains an observation gap; it is never used as a clinical input about a resident. |
| Laboratory and culture results | Lab interfaces where they exist | Sparse and delayed in assisted living relative to acute care; frequently absent altogether. | Any method that depends on frequent labs does not transfer to this setting. Culture and antibiotic events are read as clinician-suspicion markers, not as inputs to a severity score. |
| Goals of care, hospice and comfort-care status | Clinical record, advance-directive documentation | Present but often unstructured or stale. | Required as a structured, current field. Where it is missing or out of date, deterioration signalling for that resident is suppressed rather than guessed. |
Where the data runs out
- Sparse observation, not continuous monitoring. Senior housing and care documents vitals on a shift cadence with few labs; the acute-care literature that dominates published sepsis-prediction performance assumes neither of those constraints.
- Baseline-relative signalling is a trade, not a free improvement. It catches atypical presentations that absolute thresholds miss and it raises more signals in residents with unstable baselines, advanced dementia, or an end-of-life trajectory.
- Documentation timing distorts every derived trend. Batch documentation at end of shift compresses hours of change into one timestamp, so timing conclusions are stated with that caveat rather than to the minute.
- Missing data is informative but ambiguous. A skipped vitals round on a changing resident is an operational signal about observation, not a clinical statement about the resident.
- Identity resolution bounds everything. If a resident is not reconciled to one identity across the clinical, dietary, incident, and staffing systems, no cross-system signal about that resident is trustworthy, and unmatched records go to an exception queue rather than into a signal.
- Free text is not a structured observation. Where a signal depends on a value that exists only in prose, the honest answer is a narrower signal set until the value is captured as a field.
- No SeniorCRE performance figure is published. There is no sensitivity, specificity, lead-time, transfer, mortality, survey, or cost figure of our own, because there is no completed operator-production clinical deployment to derive one from.
- External validation is the standard we ask to be held to. Independent validation of a widely deployed proprietary sepsis model found materially poorer discrimination than the vendor reported; operators should demand external validation from every vendor, including SeniorCRE.
Implementation prerequisites
Ten prerequisites gate clinical exposure. An operator that cannot meet them yet does not get a weaker version of the signal set; it gets the readiness work first.
- Executed BAA and documented lawful basis
- An operator BAA is a pilot-readiness gate. No PHI moves before it is signed, and the data categories in scope are enumerated in writing.
- Named clinical owner with authority to stop
- A DON or CNO is accountable for the signal set and holds an unconditional kill switch per signal class and per community.
- The operator’s own change-in-condition protocol, in writing
- SeniorCRE reproduces the operator’s protocol. If a written protocol does not exist, writing one is the first deliverable — before any signal is enabled.
- Structured vitals with a stated capture cadence
- Respiratory rate and mental status must be captured as structured fields, not free text, with a documented expected frequency per resident acuity tier.
- A per-resident baseline window
- Baseline-relative signals need a defined trailing window per resident and an explicit rule for new admissions who have no baseline yet.
- Resident-identity reconciliation across systems
- One resident identity across EHR, eMAR, dietary, incident, and staffing systems, with a documented match rate and an exception queue for unmatched records.
- Goals-of-care and hospice status available as a field
- Comfort-focused residents must be excludable by data, not by memory.
- Agreed alert-burden budget and acknowledgment windows
- Alerts per nurse per shift, acknowledgment window, and escalation ladder are agreed and documented before clinicians see a single signal.
- Silent-run and acceptance gate
- A shadow period against the operator’s own data, reviewed by the clinical review panel and the operator’s DON, with written acceptance before clinical exposure.
- QAPI integration
- Signal performance, response times, dismissal reasons, and missed-signal review are standing items in the operator’s existing QAPI cadence, not a vendor dashboard nobody opens.
Where this connects
- AI-assisted early sepsis risk workflows — the signal set these inputs support.
- Human review and escalation — the clinician who acts on the signal, on a clock.
- QAPI and survey readiness — documentation gaps as a record-integrity finding.
Clinical and regulatory sources
These sources describe the clinical problem, the consensus definitions, the published limits of sepsis prediction models, and the transparency expectations for decision-support software. None of them reports SeniorCRE performance, and none should be read as doing so.
Source 1 · Singer et al., JAMA · 2016
The Third International Consensus Definitions for Sepsis and Septic Shock (Sepsis-3)
Defines sepsis as life-threatening organ dysfunction caused by a dysregulated host response to infection, and introduces qSOFA (altered mentation, systolic BP ≤100 mmHg, respiratory rate ≥22/min).
Source 2 · Evans et al., Critical Care Medicine / Intensive Care Medicine · 2021
Surviving Sepsis Campaign: International Guidelines for Management of Sepsis and Septic Shock 2021
Recommends against qSOFA as a single screening tool and supports systematic screening of acutely ill, high-risk patients — the basis for treating any signal as screening support rather than a decision.
Source 3 · U.S. Centers for Disease Control and Prevention · 2023
Hospital Sepsis Program Core Elements
Establishes leadership accountability, action, tracking, reporting, and education as the structural elements of a sepsis program — the model our governance section follows.
Source 4 · Wong et al., JAMA Internal Medicine · 2021
Independent validation found substantially poorer discrimination than the vendor reported, with a high alert burden. Cited here as the reason to demand external validation from any vendor — including SeniorCRE.
Source 5 · Royal College of Physicians · 2017
National Early Warning Score (NEWS2)
The reference standardized deterioration score. SeniorCRE does not reproduce or substitute for NEWS2; signals are explicitly labelled as not a validated severity score.
Source 6 · U.S. Food and Drug Administration · 2022
Clinical Decision Support Software — Guidance for Industry and FDA Staff
Describes the criteria that separate non-device clinical decision support from regulated device software, including whether the clinician can independently review the basis for the recommendation.
Source 7 · U.S. Assistant Secretary for Technology Policy / ONC · 2024
HTI-1 Final Rule: Decision Support Interventions and Predictive DSI transparency (source attributes)
Sets the transparency expectations — intended use, inputs, validation, fairness, and maintenance — that the buyer’s checklist on this site mirrors question for question.
Source 8 · U.S. Centers for Disease Control and Prevention · 2024
Sepsis: Clinical Information and Data
Background on sepsis burden and the role of early recognition. Used for problem framing only; no SeniorCRE outcome is derived from it.
Frequently asked questions
What data does clinical AI use in senior housing & care?
Structured vital signs, mental-status and behavior documentation, medication administration, care-task and ADL completion, dietary intake and weights, incidents and change-in-condition reports, staffing and worked hours, any available laboratory results, and a current structured goals-of-care field. Each input arrives from a named source system, with its capture time retained.
Why do acute-care AI results not transfer to assisted living?
Because the data does not. Published sepsis-prediction performance largely comes from hospital settings with frequent vitals, continuous monitoring, and routine laboratory draws. Senior housing and care typically documents vitals on a shift cadence with few labs, so any method that depends on that density does not carry over, and neither does its reported performance.
What happens when data is missing?
It is treated as a documentation gap, never as a clinical finding. A skipped observation round on a changing resident is an operational signal about observation, not a statement about the resident. Where a required field such as goals of care is missing or stale, deterioration signalling for that resident is suppressed rather than guessed.
Does SeniorCRE publish sensitivity or lead-time figures?
No. There is no completed operator-production clinical deployment and therefore no sensitivity, specificity, lead-time, transfer, mortality, or cost figure of our own. Capability is built against synthetic fixtures and vendor-documented interface contracts.
How should an operator judge a vendor’s clinical AI evidence?
Ask for independent external validation on data resembling your own population and documentation cadence. Independent validation of a widely deployed proprietary sepsis model found materially poorer discrimination than the vendor reported. Hold every vendor to that standard, including SeniorCRE.
Which system stays authoritative for medications?
Exactly one MAR is authoritative at all times. SeniorCRE clinical record surfaces are built; medication administration and eMAR remain roadmap — not built. It can run alongside an incumbent eMAR reading one direction only, with the incumbent MAR authoritative. That is a configuration choice the operator makes.
Continue in this cluster
Is SeniorCRE your clinical system of record? Capability vs. configuration
The platform carries its own EHR and eMAR and can be the clinical system of record — or it can run alongside an existing eMAR, reading one direction only, so one medication record stays authoritative. Both configurations, side by side.
Answers: Is this replacing my eMAR?
How AI supports earlier sepsis detection in senior residents
A clinician-reviewed guide to the signals, the escalation workflow, the published limits of sepsis prediction models, and the safeguards that keep detection support out of diagnosis.
Answers: How does AI support earlier sepsis detection in older adults in senior housing & care?
Clinical and financial intelligence in assisted living
How acuity, care minutes, staffing, documentation, census, and revenue are reconciled with operator-controlled authority — and where the clinical record still governs.
Answers: What is clinical and financial intelligence in assisted living, and how are the two reconciled?
Buyer’s checklist for AI clinical tools
A 30-question evaluation checklist across intended use, evidence, safety workflow, bias and drift, regulatory posture, data rights, and contract terms.
Answers: What should operators ask before buying an AI clinical tool?
Human review and escalation: who acknowledges, who decides, who is accountable
The acknowledgment clock, the role-by-role escalation ladder, dismiss-with-reason, the kill switch, and what the record retains about every human step.
Answers: Who reviews an AI clinical alert, and what happens if nobody does?
QAPI and survey-readiness use cases
Six governed QAPI and survey-readiness use cases, each with the question it answers, the evidence it produces, and the limit on what it can claim.
Answers: How is clinical intelligence used for QAPI and survey readiness?
- Pillar: Clinical intelligence for senior housing & care
- Product: Clinical platform · Clinical workflows
- Vendor comparison: Clinical and financial analytics platforms for assisted living
- Security and compliance posture: Trust Center
Evaluate this the way you would evaluate a clinical protocol
The honest version of this conversation is a readiness review against your own documentation, vitals cadence, and change-in-condition protocol — followed by a silent run on your own data before any clinician sees a signal.