Sensus · Executive program review

Hospital reliability

The master review for the owner and CNO: house supervisor program, charge nurse reporting center, reliability patterns, and the 100 Healings relay — the working document for hospital huddles.

Review period

Pulse · 15 step-ins · UAR 80.0% Executive operations workspace Read-only oversight Program connected
SYNTHETIC DEMO DATA

Descriptive measures for the period. This view does not produce a composite enterprise score — distributions, trends, and denominators stand on their own.

01 · Reliability patterns

Where the operation is stable, and where it is moving

Shift-level Unit Reliability Index (URI), event load, and resolution patterns across units and shift types. Units are grouped by unit only — never ranked, and never labeled by a band.

Unit reliability over the period

Median URI per window with the interquartile spread of qualifying shifts. Each unit reads on its own; charts share a scale so shapes stay comparable. Unit order below is fixed and does not rank performance.

Hospital-wide URI distribution over time

Median across all qualifying shifts per window, with the middle 50% of shifts shaded. A wide band means units and shifts disagree; a falling band means reliability is moving together.

Shift-type contrast

Day, Evening, and Night shift patterns for the period. A contrast is a description, not a verdict on any shift team.

Response flow: re-escalation & carryover

Re-escalation share (first response didn't hold) and carryover share (instability crossing the shift boundary), by window. Line rates are computed on events recorded in each window.

Event classes over time

How the instability mix is shifting — which operational problems the hospital is absorbing more of, window by window. Classes use the frozen LWS taxonomy.

Resolution mix for the period

How events ended across the period. Resolution statuses use the frozen LWS data dictionary.

02 · House supervisor program

How the response system is holding up

Role-level view of the house supervisor function: response timing across the frozen Identify → Escalate → Acknowledge → Act → Resolve chain, acknowledgment within the frozen 15-minute target, and shift coverage. This program never scores individual supervisors.

Response-chain timing by shift type

Median minutes for each step of the chain, per shift type, for the period. Reference lines are frozen LWS dictionary targets, not new thresholds.

Acknowledged within 15 minutes

Share of escalated events acknowledged inside the frozen dictionary target, by shift type. Weighted by events per shift.

House supervisor coverage

Shifts with house supervisor coverage, for the period.

Program detail by unit

Unit-level view of the response chain for the period — the unit, not the person, is the operational object.

03 · Charge nurse reporting center

The capture layer is the measurement

Program-level view of shift-reliability capture: recording volume, field completeness, and how quickly events land in the log after they start. Reported only by unit — never by person.

Log records per shift, by unit

Average records captured per shift across the period. Recording volume describes workload and capture, not quality.

Record completeness & timeliness

Share of records with all frozen required fields, and median minutes from event start to log entry — two dot plots, each with its own scale.

“Other” event entries

Share of entries classified “Other” against the dictionary rule: if Other exceeds 10% of entries, the taxonomy needs review.

Reporting center, by unit

Program metrics per unit for the period.

04 · Where reliability can improve

Patterns worth the huddle's time

Observed patterns computed from this period's capture — each with its windows, counts, and a discussion question. These describe what happened; intervention is the executive's decision.

Pre-specified detection rules, descriptive only: change checks compare the first 3 windows against the last 3 (reliability slide ≤ −6 points, lift ≥ +5, carryover ≥ +4pp, re-escalation ≥ +3pp, coverage-gap events ≥ +8pp, shift-level acknowledgment median ≥ 1.25×); a unit is noted as sustained low when its window median sits below 68 in ≥60% of windows; day view shows within-day contrasts. Computed entirely from the synthetic capture above — they prescribe no action and label no unit.

05 · Huddle brief

One page to open the huddle

Generated from this view's period, measures, and detected patterns. Download reads the same as the screen — markdown, for notes or the shared drive.

Huddle brief

    06 · 100 Healings · Pulse

    Pulse performance

    The 100 Healings relay is threshold-activated: powered by LWS data, dormant until validated thresholds fire. This review reads its performance for the period — how often it stepped in, by which relay action, and how the supervisors judged each step-in. It is judged by its interruptions, not its volume: every activation had to earn the supervisor's attention.

    Activations over the period

    Each bar stacks the window's activations by relay action. Days the relay stood down — no thresholds firing — are design, not missing data.

    By relay action, with supervisor judgment

    Activations per frozen relay action, split by the supervisor's disposition on that activation. The relay prepares, never sends.

    Useful Activation Rate over time

    Supervisor-deemed useful ÷ activations, per window. Windows with no activations carry no rate — silence is not scored.

    The relay earns its interruptions one disposition at a time. Supervisors disposition every activation — useful or not useful — and those dispositions feed the Relay Learning & Governance Loop. Thresholds change only through validated governance, never autonomously. The supervisor-controlled escalation brief stays supervisor-sent: the relay may prepare it, but it can never send it.
    • Powered by LWS data — the review below exists only because the capture layer exists. No LWS data, no relay, no report.
    • Deferred, by design — direct escalation is decided by the house supervisor, not by a threshold.
    Governance & implementation appendixEvidence, architecture gates, and role contract

    07 · Pressure test & executive spec

    The spec the Admin app is held to

    Finished pressure-test research for the Sensus Admin app: every proposed element tested against seven gates, the literature-grounded executive metric set with its values, sources, and hedges, the three-app role contract, and the open items awaiting Jordan — carried in whole as the 2026-10-01 draft.

    StatusDraft — for review Dated 2026-10-01 · no build authorized yet

    BasisTwo literature surveys: (1) the Sigma concept-gap check, 2026-10-01 (27 constructs); (2) the executive nurse leadership dashboard metrics survey, 2026-10-01.

    ScopeLocked: the Admin app stays as a deliverable — the executive layer for directors, CNOs, and presidents. It merges with the Linked Demo's existing CNO view into one executive surface. No duplicate CNO views.

    The importance test

    The Admin app earns its existence by answering the three questions only an executive can ask. Every feature must serve one of these three — anything that doesn't is cut.

    Is our workforce stable?

    Panel A answers it: turnover, vacancy, premium labor, span of control.

    Is the operation reliable?

    Panel B answers it: URI trends, event patterns, response timing — aggregate, never real-time.

    Are we governed?

    Panel C answers it: change control, training completion, validation status, evidence base.

    §1 — The seven gates

    Every proposed Admin element was tested against these gates. Any element fails one gate is removed or reframed.

    1. G1

      Frozen architecture

      URI / HORI / SRBI terminology intact; house-supervisor-led operating model; non-punitive design.

    2. G2

      Evidence tiers

      No causal or outcome claims without live data; synthetic/demo data labeled as such, never presented as findings.

    3. G3

      DNP firewall

      Nothing in the Admin app activates, previews, or implies 100 Healings during the DNP period.

    4. G4

      Role separation

      The Admin app is oversight, not command. Executives never acknowledge events, reassign staff, or override supervisor decisions from this view. Real-time operational control stays with the house supervisor.

    5. G5

      Non-punitive display

      No unit letter grades, no public unit rankings.

      Boundary note carried with the gate: the literature does not peer-review-ban rankings — this is a design choice grounded in just-culture research (blame/shame reduces reporting) plus the frozen non-punitive principle. Stated as our standard, not as a literature mandate.

    6. G6

      The adequacy fence

      Patients-per-RN and perceived adequacy are display-only context (“Context, not a score”), fenced off from URI scoring. Already decided 2026-10-01 — the Admin app must preserve the fence, not erode it.

    7. G7

      URI–outcome separation

      URI is a process-reliability measure, never presented alongside clinical outcomes in a way that implies causation (frozen concept-paper principle).

    §2 — Verdicts on current Admin app elements

    Draft verdicts from the pressure test — part of the spec awaiting Jordan's review, not build directions.

    • Dark-space/atom welcome, star-glow SENSUS entry, dissolving letters

      Cinematic theater. Executive trust reads as restraint — replace with a quiet, dense executive entry.

      Remove
    • Drill-downs (aggregate → operational indicators)

      Standard executive dashboard pattern (Karami & Safdari): aggregate first, drill to operational detail on demand.

      Keep
    • Plain-language tooltips

      AONL 2026: informatics/AI leadership and improvement science are executive competencies — tooltips teach the metric, not just show it.

      Keep
    • Day / Week / Month / Year time controls

      Executives need trends over weeks/months (umbrella review 2026); this is the correct executive time grain.

      Keep
    • R/Y/G status coding

      Literature endorses traffic lights; frame red as “needs system support” with drill-down to root causes — never as unit shaming.

      Keep, reframed
    • Any real-time unit command surface

      Fails gate 4. Live boards invite executive override of supervisor decisions. Trends only.

      Remove
    • Any unit grading/ranking display

      Fails gate 5. Distributions and trends, never grades.

      Remove

    §3 — Panel A: workforce stability

    “Is our workforce stable?” — every metric with its definition, values with sources, chart form, data source, and the caveat the research attaches.

    A1

    RN turnover: overall, voluntary, first-year

    % of RNs separated in the period. First-year = 12 months tenure or less.

    • Values

      17.6% national (n = 527 hospitals); ~$60k cost per RN turnover — NSI 2025 data.

    • Source

      NSI National Health Care Retention & RN Staffing Report (annual survey).

    • Chart

      Trend line + NSI benchmark line; split voluntary / involuntary / first-year.

    • Data source

      Hospital HR.

    • Caveat

      Benchmarks are vendor survey data, not peer-reviewed — label them as such.

    A2

    RN vacancy rate + time-to-fill

    % of budgeted FTEs unfilled; mean days to fill experienced-RN requisitions.

    • Values

      9.6% vacancy; 83-day average fill — NSI 2025 data.

    • Source

      NSI National Health Care Retention & RN Staffing Report (annual survey).

    • Chart

      Trend + benchmark; vacancy by unit shown as a distribution.

    • Data source

      Hospital HR.

    • Caveat

      Same labeling condition as A1: vendor survey data, not peer-reviewed.

    A3

    Agency/traveler utilization + premium-labor spend

    % of hours from agency/travelers; premium spend trend.

    • Values

      Travel RN ≈ $190k/yr vs. ~$124k staff RN; 80% of hospitals planned decreases — NSI.

    • Source

      NSI National Health Care Retention & RN Staffing Report (annual survey).

    • Chart

      Stacked trend: staff vs. premium hours; spend line.

    • Data source

      Hospital finance / HR.

    A4

    Nurse-manager span of control

    Mean direct reports per manager; % of managers above threshold.

    • Values

      Turnover inflections ≈15 and ≈40 reports (Cathcart); +1.6% unit turnover per 10 added reports (Doran); wider span → more med errors/infections (Boned-Galán); 1 in 4 managers with >75 reports (Vizient 2026).

    • Source

      Cathcart et al. 2004 (J Nurs Adm); Doran et al. 2004; Boned-Galán et al. 2023 (integrative review); Vizient 2026.

    • Chart

      Distribution + threshold flag; trend.

    • Data source

      Hospital HR.

    • Caveat

      No optimal number exists in the literature — flag thresholds as organizational policy, not evidence-based cutoffs.

    A5

    HPPD actual vs. budgeted + skill mix

    Nursing hours per patient day vs. budget; % RN hours.

    • Source

      NDNQI / NQF #0205 (definitions); CDC NHSN staffing protocol.

    • Chart

      Variance trend by unit (actual − budget); skill-mix bar.

    • Data source

      Hospital finance + staffing.

    • Caveat

      “Budgeted HPPD” has no published benchmark — internal comparison only.

    Panel B — Reliability posture

    “Is the operation reliable?” Aggregate and trended only — never the live board. This is the URI the executive is allowed to see.

    B1

    URI trend by unit and shift

    Weekly/monthly URI distributions — box/distribution plots, never single numbers, never grades.

    • Chart

      Trend + distribution.

    • Condition

      Honors HRO “reluctance to simplify”: the distribution is the signal, not a score.

    B2

    Event volume by category

    Counts by event type over time.

    • Chart

      Stacked bars.

    • Condition

      Operational pattern recognition.

    B3

    Response-timing distributions

    Ack and action time distributions (median, spread).

    • Chart

      Histograms / trend of medians.

    • Condition

      Process reliability, not individual performance.

    B4

    Carryover and re-escalation rates

    % events carried over; % re-escalated, trended.

    • Chart

      Trend lines.

    • Condition

      Continuity-burden signal for executives.

    B5

    Adequacy context (display-only)

    Patients-per-RN by unit/shift; end-of-shift perceived-adequacy item.

    • Chart

      Small multiples, labeled “Context, not a score”.

    • Condition

      Gate 6: fenced from URI scoring — visually fenced in the UI.

    B6

    Missed/unfinished care (when instrumented)

    Per-shift “care left undone” count (RN4CAST items).

    • Chart

      Trend.

    • Condition

      Gap #2 closure; routed through change control + DNP chair first — NOT built until approved.

    Panel C — Governance and culture

    “Are we governed?”

    C1

    Reporting-rate trends by unit

    Event-report volume per unit over time.

    • Source

      Edmondson 1990s psychological-safety literature: reporting behavior is a proxy for experienced safety.

    • Condition

      Framed as a culture signal, never as a data-quality complaint.

    C2

    Safety-culture pulse

    Periodic HSOPS items (especially nonpunitive response, handoffs & transitions).

    • Source

      AHRQ HSOPS v2.0; Lee et al. 2020 (J Nurs Scholarship, Sigma): perceived culture predicts outcomes.

    • Condition

      Tests whether non-punitiveness is experienced, not just designed.

    C3

    Governance record

    Change-control log, training completion by unit, validation status, pre-registration record.

    • Condition

      Unique to the Admin app — supervisors don't need it, executives do. Directly evidences the Governance Transfer Control.

    C4

    Evidence base

    The Sigma concept-gap verdicts (covered / partial / gap), with linked sources.

    • Source

      The sensus-concept-gap-check artifact.

    • Condition

      Already exists as the Evidence tab — keep the content, demote from primary navigation.

    Deliberately excluded from the Admin app

    Excluded with reasons, per the spec.

    • Clinical outcome metrics computed by Sensus (falls, HAPU, CAUTI/CLABSI, FTR)

      NDNQI indicators are executive-relevant, but Sensus does not compute them. They may appear ONLY as clearly-labeled external context imported from hospital quality reporting — in a separate panel, with explicit “association is not causation” framing — never adjacent to URI trends in a way that implies Sensus drives outcomes. Gate 7.

      Excluded
    • Real-time unit status / live event feed

      Fails gate 4 (role separation).

      Excluded
    • Unit grades, rankings, red-list

      Fails gate 5.

      Excluded
    • NEWS2 / physiological scores

      Out of scope (gap-check “deliberately not adopt”).

      Excluded
    • 100 Healings activation or threshold preview

      Fails gate 3 (DNP firewall).

      Excluded

    §4 — Role-differentiation contract (three-app sync)

    One shared database. Three role-gated views. The Linked Demo already proved this pattern — extend it, don't build parallel.

    Data flow · On-Unit (intake) → shared DB → House Sup (measurement + command) → shared DB → Admin (aggregation + governance)

    On-Unit App

    Role
    Bedside / charge capture
    Time grain
    This moment
    Sees
    Blank frozen-field form; own submissions
    Does
    Logs events (intake only)
    Never
    Scores, interprets, or sees URI
    Write permissions
    Event records

    House Supervisor App

    Role
    Operational command
    Time grain
    This shift, real-time
    Sees
    Live unit status, active events, timelines, shift URI, handoff
    Does
    Acknowledges, acts, reassigns, hands off; sole measurement authority (URI scoring)
    Never
    Sees executive cost/HR data
    Write permissions
    Event records + decisions + scores

    Admin App

    Role
    Executive oversight
    Time grain
    Weeks / months, trends
    Sees
    Aggregate trends, benchmarks, costs, culture, governance
    Does
    Reviews trends; approves change-control items; reviews evidence
    Never
    Acknowledges events, reassigns staff, overrides supervisors, sees real-time ops
    Write permissions
    Governance records only

    The Admin app is read-only on operations and write-only on governance. That asymmetry is the entire role contract — it is what keeps the house-supervisor-led model intact while giving executives real oversight.

    §5 — Build instructions: add / remove / change

    Draft instructions from the spec — none are build directions until Jordan's review.

    Remove

    1. Cinematic entry (dark-space/atom world, star-glow SENSUS, dissolving letters) → replace with a restrained executive entry.
    2. Any real-time operational mirror (live unit status, active event feed).
    3. Any unit grading/ranking display.
    4. Seasonal/decorative dressing carried over from the supervisor app.

    Add — in priority order

    1. Panel A (workforce stability): A1–A5 with NSI benchmark lines where published.
    2. Panel B (reliability posture): B1–B5 as distributions and trends; B6 only after change-control + DNP chair approval.
    3. Panel C (governance and culture): C1–C4; C3 is the highest-value unique executive feature.
    4. Drill-down paths: every aggregate → operational indicators (not to individual events or people).
    5. Tooltips with metric definitions + source citations on every panel — executives should learn the metric, not just see it (AONL informatics competency).

    Change

    1. Merge the Linked Demo's CNO view into this app — one executive surface.
    2. Reframe all R/Y/G as system-support signals with root-cause drill-down.
    3. Entry experience: quiet, dense, serious. No theater.

    §6 — Non-negotiables in the build

    • Synthetic/demo data is labeled on every panel until live pilot data exists. No exceptions.
    • No causal language anywhere near URI + outcome displays. Ever.
    • The adequacy fence is visual as well as logical: “Context, not a score” labeling, separate panel, no blending into reliability scoring.
    • Reporting-rate displays never become compliance shaming (“Unit X under-reports”).
    • Nothing in this app may be screenshotted into a claim the evidence tiers can't support — the export/share surface, if any, carries the same labels.

    §7 — Open questions · need Jordan

    Four items are awaiting Jordan's answers. None are assumed, none are resolved — marked plainly Open until she answers them.

    • OpenQ1

      Confirm the metric set (§3) — especially whether hospital HR/finance data feeds are realistic for the pilot site, or whether Panels A1–A5 start as labeled demo content.

    • OpenQ2

      Confirm NDNQI-outcome-as-external-context (currently conditional) vs. excluding outcomes entirely until post-pilot.

    • OpenQ3

      B6 (missed-care capture) and any adequacy instrumentation changes: already routed to change control + DNP chair — not built until approved.

    • OpenQ4

      Merge decision: fold the Linked Demo CNO view in now, or keep both during transition?

    Source citations are the literature names as the research names them; the research carried no links, so none are added.