Facility Workflow Memo
Status: Phase-1 build plus regulated expansion roadmap
Updated: 2026-05-17
Investor read: Product depth, human-control boundary, and hospital workflow scope
TL;DR
Rōvn is the operating network for the healthcare workforce, verify once and reuse everywhere. The OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator is how a facility experiences the network: the facility workflow layer turns one evidence-backed worker record into intake, credentialing, privileging, monitoring, payer readiness, and audit-ready proof. It does not replace a medical staff office, Credentials Committee, MEC, Board, hiring manager, payer enrollment team, or clinical leader.
Doctrine: AI operates the workflow. Source systems prove the facts. Humans make every regulated decision.
Sequencing
The facility workflow memo sits inside a five-stage expansion arc. The facility workflow layer (OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator) is the currently-shipping product. Readiness is the Pilot-tier wedge; Worker PassportProduct surface04.2 Worker Profile / Passport Memo · worker-owned credential evidence, Network, and Workforce OS are the post-OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator expansion stages.
Five-stage expansionSequencing01-pitch intro strap · Readiness wedge → Operator → Worker Passport → Network → Workforce OS (Workforce OS for healthcare): 1. Readiness, JC/CMS survey-prep packets. Shipping now. Pilot-tier entry point ($12K, 90-day, one-time). 2. OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator, full credentialing + privileging cockpit for facilities. In design-partner conversations. Core ($10,000/mo · $120K ACV) and OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator ($20,000/mo · $240K ACV) tiers. 3. Worker PassportProduct surface04.2 Worker Profile / Passport Memo · worker-owned credential evidence, portable, primary-source-verified record owned by the clinician. Phase 2. 4. Network, verified clinicians meeting verified facilities. Phase 3. 5. Workforce OS, the operating network the healthcare workforce runs on, owned by Rōvn. The endgame.
The buyer journey: a facility enters at Readiness as a $12K 90-day Pilot (one-time, pilot-to-production). At day 90 they convert to Core or OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator (annual, monthly-billed). OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator buyers later pull Passport and Network as they expand across hiring, recredentialing, and continuous monitoring. Workforce OS is the long arc.
What the workflow does
The facility workflow layer coordinates the work that currently lives in inboxes, spreadsheets, shared drives, and point systems:
- Intake from CSV, manual entry, email-forwarded submissions, and Rōvn-hosted application forms.
- Evidence extraction from uploaded documents and facility-held files.
- Source checks where API or source-receipted access is live.
- Manual PSV routing where automation is not live.
- Missing-item tasks, reminders, and worker Passport prompts.
- Stage 1 / Stage 2 screening summaries.
- Interview and offer gates with persistent human decisions.
- Credentialing, privileging, reappointment, monitoring, payer-readiness, and audit packets as the regulated expansion deepens.
The layer is workflow infrastructure. It can draft, route, summarize, compare, nudge, forecast, and assemble proof. It cannot approve, deny, discipline, privilege, enroll, report, or clinically judge without a named human decision-maker.
Human decision gates
Every regulated or employment-adjacent decision must carry:
| Gate | Human control required |
|---|---|
| Interview | Named reviewer, date, recommendation context, typed reason when advancing or declining |
| Offer | Named reviewer, offer/no-offer decision, typed reason, audit receipt |
| Credentialing | Committee or delegated credentialing reviewer, packet receipt, approval or deferral reason |
| Privileging | Privilege-specific reviewer or committee, privilege-to-competency evidence, approval/limitation reason |
| Adverse action | Named decision-maker, due-process path, fair-hearing status where applicable, NPDB reporting review |
No AI-only adverse action. No AI-only hiring decision. No AI-only credentialing or privileging decision.
Evidence model
Every imported fact must carry provenance:
importedattestedprocessedsource-verifiedapproved
Rōvn treats source systems as fact authorities. AI can extract, normalize, compare, and summarize. A fact is not source-verified unless a source receipt supports it.
May 17 verification coverage
The current coverage proof shows:
- 43 rolesRole coverage43 healthcare roles in the Rōvn workforce catalog · 07.7 + 11.3 coverage grid.
- 51 jurisdictionsJurisdictional coverage50 US states + DC = 51 jurisdictions · 11.3 coverage grid · 07.7 Source Authority Rail.
- 2,193 role/state coverage cells.
- 0 unsupported catalog cells.
Claim boundary: API/source-receipted where live; manual PSV where automation is not live. This is a coverage and workflow claim, not a claim that every role has full automated primary-source verification today.
What is live, partial, and planned
| Area | Status | Investor-safe wording |
|---|---|---|
| Worker PassportProduct surface04.2 Worker Profile / Passport Memo · worker-owned credential evidence | LIVE | Worker-owned record and document intake rails are live. |
| Source receipts | LIVE/PARTIAL | Receipt-bound trust states are enforced where wired; full population continues across all verification paths. |
| 43-role coverage map | LIVE | 50 states plus DC mapped with API/manual-review labels. |
| Stage screening | PHASE-1 | Screening workflow and evidence-bound readiness are being hardened for pilot use. |
| Interview / offer gates | PHASE-1 | Human gates with persistent decisions and audit receipts. |
| Medical staff privileging | SCAFFOLD -> BUILD | Schema and workflow plan; hospital-grade committee workflow is an expansion deliverable. |
| OPPE / FPPE | SCAFFOLD -> BUILD | Data model exists; real-world workflows require pilot design partners. |
| Reappointment | SCAFFOLD -> BUILD | Recurring credentialing cycle needs build-out for 2-3 year renewal revenue. |
| Payer/provider enrollment | SCAFFOLD -> BUILD | CAQH, PECOS, Medicaid, and commercial payer tracking are roadmap/build items, not live submission automation. |
| Survey/audit export | SCAFFOLD -> BUILD | Proof packet and report assembly are core expansion scope. |
Why facilities care
Credentialing is not enough. A provider who is credentialed but not privileged cannot safely practice. A provider who is credentialed but not enrolled cannot bill. A file that cannot be exported for a survey still creates operational risk. Rōvn's workflow layer is built around that reality: readiness means compliant, billable, monitored, and defensible.
Competitive frame
Large incumbents sell facility-owned systems of record. Rōvn's wedge is a worker-owned evidence record plus a facility workflow layer that reads the same proof repeatedly. The compounding asset is not a dashboard. It is the growing body of receipts, decisions, exceptions, renewals, and rule mappings that makes the next facility workflow cheaper and more defensible.
Procurement-safe line
Rōvn helps healthcare facilities get workers from application to compliant, billable work faster, with source-backed proof and named human decisions at every regulated gate.