Rōvn · Investor Room
AI agent: checking…
All sections
Live Proof

Healthcare Glossary

Diligence noticeWorking state of Rōvn as of 2026-06-24 · Pre-launch by designSee 09 for receipts →
AI Diligence Console

Most VCs are software investors first, healthcare investors second. This glossary is the shortest possible mental model of the operating network for the healthcare workforce, every term used in this room, defined.

Credentialing
The process by which a facility verifies a clinician's identity, licenses, education, sanctions history, and work history before letting them practice. Initial credentialing is typically 60-120 days; recredentialing happens every 24-36 months.
Privileging
Separate from credentialing. A facility's medical staff committee decides what specific procedures or services a verified clinician is allowed to perform at that facility, based on training, case logs, and outcomes. A clinician can be credentialed without being privileged for a given procedure.
Primary Source Verification (PSV)
Verification of a credential by querying the authoritative issuer directly, a state Board of Nursing, the FSMB, ABMS, etc. PSV is what Joint Commission / CMS surveyor surveyors look for. Secondary-source verification (vendor aggregators returning unsourced answers) does not satisfy the standard.
Truth ladder
Rōvn's internal taxonomy for the depth of any fact: ATTESTED → PROCESSED → VERIFIED → APPROVED. Labels move up the ladder over time, never down. Receipts attach from PROCESSED upward. See 04.4 AI Doctrine.
Passport
The worker-owned verified credential record. Travels with the worker across facilities. Foundation of the network flywheel: one verification reusable everywhere.
Connect (internal codename)
Internal engineering codename for the facility operator cockpit. Public name: facility operator (also "OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator"). Not used in customer-facing copy, appears here only because investors hear it in technical conversations and may encounter it in code/repos. Orchestrates the hiring pipeline and reads verified Passports. Does not run credentialing itself; that's the Rōvn network engine.
NPDB
National Practitioner Data Bank. Federal repository of malpractice payments, adverse licensure actions, clinical privilege actions, and professional society actions. Queried via QRXS. Mandatory before initial appointment and biennially for renewal at most accredited facilities.
Nursys
NCSBN-operated national nurse-license database. Rōvn integrates the e-Notify API (v3.1.5) for active license lookup and continuous monitoring across all 50 states + DC.
OIG LEIE
HHS Office of Inspector General, List of Excluded Individuals/Entities. Federal sanctions list. Anyone on it cannot receive payment from any federal healthcare program. Sweep is monthly minimum.
SAM.gov
System for Award Management. Federal entity registration and exclusions list. The Rōvn entity is validated with an assigned UEI.
FSMB / PDC API
Federation of State Medical Boards. The PDC API is the commercial physician primary-data rail (MED API is board-only). Provides licensure, public board orders, and discipline records.
ABMS
American Board of Medical Specialties. Confirms physician board certification. On Rōvn's adapter roadmap, Q3 2026.
Verifiable
Commercial coverage-acceleration vendor that federates state board lookups. Used by Rōvn as a supplemental rail, not source-of-truth. Receipts must include source authority evidence (name+timestamp, URL, or artifact) before any cell flips to VERIFIED.
OPPE / FPPE
Joint Commission requirements for ongoing physician evaluation. OPPE = Ongoing Professional Practice Evaluation (continuous). FPPE = Focused Professional Practice Evaluation (triggered, e.g. new privilege). Both are workflow targets on the Rōvn roadmap.
CVO
Credentials Verification Organization. NCQA certifies CVOs across 11 verification elements. Rōvn's NCQA CVO trajectory is in progress, not certified. See 06.8.
NCQA ongoing monitoring (eff. July 1, 2025)
NCQA's updated standards, effective July 1, 2025, require ongoing monitoring of each provider's license, sanctions, and exclusions at least every 30 days, shortened primary-source verification windows (120 days accreditation / 90 days certification), and escalation of adverse findings to a peer-review body. The quarterly, manual, batch approach now fails survey. The lead regulatory why-now driver, see 10.4.
HIPAA-alignedHIPAA posture06.2 HIPAA Posture Memo · canonical procurement-safe phrasing (not 'compliant' / not 'certified') · BAA availableBAA posture06.4 Vendor BAA Matrix · customer BAA template at 08.9
The procurement-safe phrasing Rōvn uses. There is no HIPAA certification issued by any authority. "Aligned" means built to satisfy HIPAA Privacy and Security Rules; "BAA availableBAA posture06.4 Vendor BAA Matrix · customer BAA template at 08.9" means Rōvn will execute a Business Associate Agreement with the customer.
IAL2
Identity Assurance Level 2, per NIST SP 800-63A. Remote identity proofing with document + biometric checks. Rōvn uses Persona for IAL2-equivalent verification (currently sandbox-configured pending production key).
CAH / ASC / LTC
Critical Access Hospital (rural) · Ambulatory Surgical Center · Long-Term Care. Rōvn's initial ICP wedge, small to mid-sized facilities that feel the credentialing cost most acutely and have the shortest decision cycles.
CMS recoupment
When CMS retroactively claws back Medicare/Medicaid payments for services that turn out to have been ineligible, including services rendered by an unprivileged or improperly credentialed provider. Billing for an improperly-credentialed provider remains exposed to False Claims Act liability under Medicare's 60-Day Rule. A driver of the regulatory tailwind in 10.4.
SAFE
Simple Agreement for Future Equity. Y Combinator-originated instrument. Rōvn's current raise is $2.25MRound sizeRōvn SAFE term sheet · 2026-05 · canonical raise (see 02.1 Use of Funds) on a $15M post-money SAFERound structureRōvn SAFE term sheet · 2026-05 · $2.25M / $15M post-money cap.
Ask the AI agent about this section, the raise, compliance posture, or any cross-document question. Grounded in Rōvn's deep context, with on-page source citations.

AI queries route through AWS BedrockAI provider chain07.3 AI Architecture · AWS Bedrock under BAA → Anthropic Claude Haiku 4.5 under BAA → Rōvn ECS under BAA · Anthropic Claude (Haiku 4.5)Model identity07.3 AI Architecture · Haiku 4.5 chosen for cost + latency + BAA chain under BAA · zero-data-retention posture · no PHI in prompts.