Owl
Owl lines up the evidence before a surveyor asks for it. It is the first app on Nightingale OS, the operating system for the whole hospital, and it lands with compliance: continuous survey readiness across the 150 accreditation, certification, designation and regulatory programs a hospital answers to, 50 of them modeled end to end. Owl is designed to run on site, on Grace, the on-premise server we lease to the hospital, and every later app runs on the same install.
Owl is built and testable on synthetic data; Grace is in design. Live demo on request.

The work a quality team does by hand
before a survey.
Every department in a hospital is surveyed, and every role is accountable. Owl starts where that work is heaviest: keeping the evidence current, for every program, every day of the year, not only the week the surveyors arrive.
① Standards, evidence, owner
Owl maps each standard to its evidence and names the person who owns it, so “who has that?” has an answer before anyone asks.
② What is still open
Owl surfaces open findings and corrective actions, and what a lapse would put at risk, while there is still time to fix it.
③ The whole portfolio
150 accreditation and designation programs tracked; 50 modeled end to end, down to each cited criterion.
Your hospital is already doing the work.
The paperwork is the barrier.
Charlie Owl is built on an assumption of good faith: hospitals want to do the right thing, and mostly they already are — what lapses is the proof, not the care. So the product’s job is not surveillance. It is to make the evidence exist the moment the work does, so “produce the record” stops being a threat and becomes a two-tap answer.
Compliance is a documentation problem first
The standard was met at the bedside; the binder just doesn’t know it yet. The gap between doing the work and proving the work is where findings, lapsed designations, and survey-week weekends come from — and it is a gap software can close without asking clinicians to do more.
Receipts as a byproduct, not a second job
Every attestation, decision, and refusal lands in the hash-chained ledger as the work happens — a receipt for everything, printed automatically, without being asked. Proof stops being a reconstruction project and becomes exhaust the system keeps for you.
Not just Joint Commission.
The spine 150 programs share.
A hospital answers to far more than one accreditor, and its portfolio usually lives across several tools, in-house workflows and binders. Owl holds it in one place. The Joint Commission gets the deepest treatment — a tracer engine and mock-survey mode — but the same continuous-readiness spine carries every body below. Each of these is in the product and testable on synthetic data, at the depth stated below, in honest tiers — 50 programs modeled end-to-end with 583 individually-cited survey criteria behind a live readiness score, 60 pre-cited certifier packs — 13 curated plus 47 derived from the modeled programs’ own cited criteria, 631 criteria with every one carrying a standards citation, and a 150-program designation roster — 44 regulatory, 39 certification, 35 accreditation, and 32 voluntary-excellence, each entry with a validated designating authority and honest tier — that a facility can register, attest, and revenue-model against. Breadth is never dressed up as depth.
The market research behind this roster, every figure sourced, is in Owl market research →
Deemed-status accreditors
The Joint Commission (tracer engine + mock-survey), DNV / NIAHO, HFAP, CIHQ, and ACHC as alternative accreditor tracks, and CARF for behavioral-health and rehab programs.
CMS & federal
Conditions of Participation (42 CFR 482), the CMS-2567 Statement of Deficiencies and Plan of Correction, EMTALA, NHSN / CDC infection surveillance, MQSA mammography, and Section 1557 language access.
Pharmacy, lab & safety
DEA controlled-substance and diversion, SAMHSA OTP/MAT, 340B, USP 797/800 compounding, CLIA / CAP lab, and OSHA workplace safety.
Nursing, privacy & state scope
ANCC Magnet and shared governance, HIPAA / OCR privacy and Safe-Harbor de-identification, and a 52-jurisdiction scope-of-practice matrix (50 states, DC and Puerto Rico).
Responsible use of AI, as one program
The Joint Commission and CHAI guidance on responsible use of AI is one more program on the roster. Owl’s RUAIH readiness pack maps the hospital’s AI evidence onto all 5 standard areas of the Joint Commission’s RUAIH certification (launched June 1, 2026) and the 7 guidance elements. Owl inventories the algorithms in use and keeps the human-review evidence for each, the same way it keeps the evidence for every other program. RUAIH certifies hospitals, not software. Source: server/src/services/owlRuaihReadinessPack.js, verified 2026-11-10.
Coverage depth varies by body: the Joint Commission carries the full tracer and mock-survey engine, while several accreditors are catalog-level reference tracks today. A handful of compliance surfaces are not yet wired to a citation chain and are not claimed as citation-grade until they are.
A designation is a promise,
not a billing code.
Trauma verification, stroke certification, cancer accreditation — each is an outside body's promise that a high-acuity service line actually works, and the license to bill for it. Losing one is a patient-safety event, a loss of community access to specialty care, and a multi-million-dollar, press-release event — in that order. Charlie Owl tracks every criterion, its evidence status, and what a lapse puts at risk, cited to the actual standards.
Continuous Readiness
A living readiness score per designation — every criterion green, amber, or red, with the evidence (or the gap) attached. Survey day becomes a walk-through instead of a scramble, because readiness was never allowed to decay in the dark.
Survey-Day Tooling
Live tracer management, Immediate Jeopardy assessment, and plan-of-correction workflows that gate a finding until the correction is evidenced. Drill mode runs the same walk before the real one. Document requests get a section of their own below.
Survey Mode, in Your Pocket
Walk the halls with the surveyor: tracer prompts, two-tap evidence pull, findings logged in real time — offline-capable, because surveys don't wait for hospital wifi.
Regulatory Change-Watch
When a standard changes, the criteria that depend on it flag themselves for review. Charlie Owl never silently fabricates a readiness score or a regulatory update — when it doesn't know, it says so, with a citation.
A surveyor asks for the QAPI minutes.
The hospital’s rules decide.
QAPI committee minutes are privilege-sensitive. When a surveyor asks for them, Owl flags the request, holds the release, says why, and logs it. A privileged request cannot be marked released without a defense-locker reference, because privilege waived in a hurry is privilege lost. The hospital decides what the surveyor gets. That is the design rule of the whole operating system at work: nothing acts unless it passes the hospital’s own rules.
① Every request captured
The surveyor request queue captures every ask as it lands. Release is confirm-gated against the hospital’s policy registry, stamped with version and content hash, and delivered as an expiring, revocable, access-audited link, never as loose files.
② A named person confirms
A named person on the hospital’s team confirms every release. Every render is scanned for patient identifiers, and a hit refuses the release outright.
③ Ready for the unannounced
A complaint investigation does not call ahead. The readiness score, the evidence chain and the release path are the same ones running every other day of the year.
The release mechanics — request queue, policy-registry document production, expiring-link delivery and their cited refusal codes — are built and testable on synthetic data, with no EHR integration in phase one.
Each covers part of survey readiness.
Survey readiness today is split across tools, in-house workflows and binders. Joint Commission Resources’ Tracers with AMP, Vastian, Ideagen’s Healthcare Guardian and RLDatix each support the major accreditors and CMS; the rest lives in in-house Epic workflows and binders. Owl tracks 150 programs, 50 modeled end to end, and is designed to run on site, on Grace.
How we compare, honestly
Vendor pages name the accreditors they support, not the programs they cover, so we do not print program counts for them and do not compare their numbers with Owl’s. Each of these tools does real work for the bodies it supports.
One app first.
Every later app on the same install.
Owl is how a hospital starts with Nightingale OS. Comprehensive compliance is vertical integration: hardware, compiler and apps built together, for every department. Owl lands it with survey readiness; the same install then carries every app after it.
Phase one: no EHR integration
There is no EHR integration in phase one.
On site, on Grace
Owl is designed to run on Grace, the on-premise server Nightingale leases to the hospital, whose clinical compiler checks every action against the hospital’s own rules. Grace is in design; the prototype is built with this round. Security by design →
Measured from day one
Owl is measured on what it can move in a few months: survey readiness, complete evidence, time to evidence, and open items closed.
Administrative work first
Owl starts with administrative compliance work. Every recommendation shows its basis, so people review it and decide. The clinical decision tools we have scoped will seek FDA clearance.
A readiness score with four inputs,
on a spine you can verify.
“Living green/amber/red” is the outcome. Here is the machinery under it. Each accreditation domain carries a running 0–100 readiness score that moves on four measurable inputs, with the weakest domains flagged. Bands: ready ≥ 90 · watch 75–89 · at-risk < 75. The score is a prioritization aid — the product labels it exactly that, never as compliance evidence or a guarantee of survey outcome.
① Open findings
Unresolved findings from tracers, drills, and prior surveys weigh the domain down until each is closed with evidence attached.
② Criterion gaps
Every criterion a designation requires that has no evidence behind it yet — the standard's own checklist, scored against what you can show.
③ Stale & expiring evidence
Evidence carries a freshness clock. Competencies, policies, and attestations decay toward their review date — and the score decays with them, before they lapse.
④ Mock-survey pass rate
Your team's scored performance on the sandboxed drill walk feeds back in — practice that never touches the real evidence chain, but that the score can see.
The spine underneath the number
Hash-chained Decision log
Every mutation, attestation, and refusal is a row in an append-only, hash-chained ledger — each row referencing the last, completeness-checked on a schedule. A surveyor can verify the chain end-to-end.
Tracer engine
A Joint Commission patient tracer walks one patient backward through every standard touchpoint; a system tracer walks one process end-to-end. Each touchpoint maps to the standard chapter it tests, with a finding slot attached.
Sandboxed mock-survey mode
Simulates an accreditor's questions and emits a readiness scorecard with per-element gaps and actions. By construction it refuses to turn practice into real evidence, to pool across facilities, or to auto-fire remediation.
Citation & deficiency tooling
Structured CMS-2567 Plan-of-Correction composition and SAFER-matrix placement — the deficiency response drafted against the actual standard, not a blank template.
Evidence-loop refusals
A surface cannot publish a readiness claim without a verified citation chain. When the audit trail would auto-modify a surface's own citation, the evidence loop refuses — a machine-readable code, naming the policy.
Honest empty states
Boards render live evidence only where a facility has loaded it. Where nothing is seeded, Owl shows the empty state — it never fabricates a screenshot, a score, or a survey finding to fill the gap.
The stakes are measured in outcomes,
not only dollars.
A service line runs on its designation, and a community's access to specialty care runs on both. When one lapses, the public evidence on what a community loses is peer-reviewed and — kept honest — associational, not causal. We cite it the way we cite everything else.
How to read these
These are the honest stakes, honestly labeled. The stroke figure is a modeled estimate for a typical large-vessel stroke, not a measurement. The trauma and obstetric figures are observational associations, adjusted for the confounders their authors could measure, and drawn from datasets a decade old. They do not prove that any one closure caused any one death, and Charlie Owl never claims they do. They establish the stakes of the promise a designation makes — which is exactly why keeping it provable, continuously, is worth doing.
Abstract once. Submit everywhere.
Registry abstraction still means a human hunting through charts — about 39 minutes per case before acuity, by peer-reviewed stopwatch study. The same hospitals abstract again for cardiology, surgery, stroke, and cancer registries. Charlie Owl proposes; a named registrar attests; the hash chain keeps the receipt.
Amplification, Never Replacement
The registry standards require human registrars — so amplification is the only compliant architecture, and it's ours by design. The registrar's judgment is the product; Charlie Owl removes the chart-hunting around it.
Your File Will Not Bounce
National registry submissions are rejected whole-file on a single critical flag. Charlie Owl validates locally, before submission, against the same rules — so the deadline week isn't spent discovering what the registry would have told you.
Continuous survey readiness is the bar
this category should be judged by.
The readiness market judges itself by two things: surviving survey day, and a mock-survey quote every cycle. Charlie Owl's position is that always-ready is the only honest bar — the standard held 365 days a year, not just the week the surveyors are in the building — because the patients, the community, and the revenue do not wait for survey week. This is a path to continuous survey readiness. That is the goal, and that is the standard.
The accreditor already agrees
The Joint Commission itself sells a “Continuous Survey Readiness Program” — one federal purchase order obligated $9.71M over roughly six years (USAspending.gov, VA, 2010–2016). Continuous readiness is not our marketing idea; it is the thing the incumbent already charges seven figures for. We think it should be the product, not the premium tier.
Don't rent your evidence file from the accreditor
The evidence a hospital uses to prove readiness — and to contest a finding, defend an Immediate Jeopardy, or switch accreditors — should not live inside the accreditor's own tool. The conflict of interest is the same one that keeps an EHR from auditing itself. Your receipts should be yours, portable across every certifier your portfolio spans.
How we build it: Nuthatch
The software behind Owl is built under Nuthatch, our harness that checks each AI coding agent’s write at the tool call, before it lands, and receipts every check to a hash-chained ledger. Bypass is possible and we say so: break-glass demands a written reason of at least 40 characters and burns the grant before the bypass applies, so a bypass is witnessed, not prevented. Nuthatch is a developer tool, not part of Owl. The developer page →
See Owl on synthetic data.
Owl is built and testable on synthetic data today. Live demo on request.