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.
- G1
Frozen architecture
URI / HORI / SRBI terminology intact; house-supervisor-led operating model; non-punitive design.
- G2
Evidence tiers
No causal or outcome claims without live data; synthetic/demo data labeled as such, never presented as findings.
- G3
DNP firewall
Nothing in the Admin app activates, previews, or implies 100 Healings during the DNP period.
- 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.
- 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.
- 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.
- 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.
B2
Event volume by category
Counts by event type over time.
B3
Response-timing distributions
Ack and action time distributions (median, spread).
B4
Carryover and re-escalation rates
% events carried over; % re-escalated, trended.
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).
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.
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
- Cinematic entry (dark-space/atom world, star-glow SENSUS, dissolving letters) → replace with a restrained executive entry.
- Any real-time operational mirror (live unit status, active event feed).
- Any unit grading/ranking display.
- Seasonal/decorative dressing carried over from the supervisor app.
Add — in priority order
- Panel A (workforce stability): A1–A5 with NSI benchmark lines where published.
- Panel B (reliability posture): B1–B5 as distributions and trends; B6 only after change-control + DNP chair approval.
- Panel C (governance and culture): C1–C4; C3 is the highest-value unique executive feature.
- Drill-down paths: every aggregate → operational indicators (not to individual events or people).
- Tooltips with metric definitions + source citations on every panel — executives should learn the metric, not just see it (AONL informatics competency).
Change
- Merge the Linked Demo's CNO view into this app — one executive surface.
- Reframe all R/Y/G as system-support signals with root-cause drill-down.
- 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.