How it works
Who controls the work and the record?
Two principals, explicit authority and dependable handoffs: follow the proposed loop from a situation to requirements, decisions, actions, exceptions and an accepted outcome.
Inspect the demonstrationsInside this chapter
Two principals · proposed model
An agent for each side. A clear mandate for each.
A workforce workflow only works if each party can see what it controls. The proposed model gives the clinician an agent operating within the clinician’s goals and consent, and gives the facility agents operating within the facility’s permissions, department rules and named authority.
Clinician platform ↔ facility workforce OS
Two sides of the market, coordinated through a permissioned record.
Clinician platform
Career, permissions, evidence
- Identity and credentials
- Approved sharing
- Readiness and history
Rōvn operating record
Worker · role · facility · evidence · workflow stateConsent, provenance and receipts travel with each permitted handoff.Facility workforce OS
Requirements, decisions, operations
- Local policy and rulebooks
- Named decision authority
- Facility workflow state
- The clinician’s career home
- A reusable record, source-backed evidence, career history, renewals, opportunities and communication. The clinician sets sharing scope, can correct or export the record, and can revoke permission. Core career utility is part of the initial plan; broader community features must earn participation and moderation evidence.
- The facility’s operating view
- Requirements, people, dependencies, deadlines and the facility’s own acceptance decisions around an agreed outcome. HR, credentialing, nursing leadership and operations retain their roles while authorized work moves between them.
- What never crosses the boundary
- A clinician’s agent cannot commit the facility; a facility agent cannot override the clinician’s sharing choice. A facility’s private policy, pipeline, decision and background report do not travel to another facility or train a cross-facility system.
Designed and planned scope. Inspect the current demonstrations and capability state.
The operating loop · planned
Connect a commitment to an accepted outcome.
Start with a concrete commitment: a qualified person at a first worked shift. The loop holds the facts needed to move work forward and shows where human authority or a recovery path is required.
| Participant | Working responsibility | Decision or receipt that closes their part |
|---|---|---|
| Clinician | Shares eligible evidence, answers a clarification or changes consent. | Visible consent scope, correction or revocation receipt. |
| Coordinator / credentialing | Works the requirements, routes exceptions and prepares the next handoff. | Requirement state and a clear named next owner. |
| Facility approver | Makes the facility’s hire, offer or start decision. | Authorized decision record; it is never inferred from workflow progress. |
| Receiving system or operating team | Accepts an authorized change and confirms the actual operating state. | Destination acknowledgement and, separately, first-shift confirmation. |
Dependable handoffs
The next person should know what they are accepting.
A handoff is more than a task assignment. The proposed handoff carries the request, permitted evidence, remaining prerequisites, accountable owner, deadline and completion criteria. Acceptance of responsibility, an external acknowledgement and an actual outcome are separate states.
Illustrative case: a nurse’s intended start depends on a health-screening status. The vendor retains the underlying results; Rōvn carries the permitted pass or pending status. The responsible facility team resolves the pending item, the authorized person makes the start decision and the actual first worked shift is confirmed separately.
What a dependable handoff needs to preserve
- Scope and authority
- Which requirement or action is in scope, for which purpose, under whose mandate, and what is explicitly out of scope.
- Evidence and state
- Source, version, time checked, acceptance state, unresolved prerequisites and the policy that applies to this site and role.
- Clock and owner
- Who currently owns the next move, when the commitment is affected and where conflict or delay escalates.
- Receipt and recovery
- What the receiving system or responsible person acknowledged, whether the action actually completed, and how to reconcile if that cannot be determined.
When the handoff cannot safely proceed
If a source changes after a decision was prepared, the affected decision becomes stale and its dependencies reopen. If permission is revoked, downstream views and actions lose access. If departments have conflicting rules, each rule stays visible and the named resolver owns the escalation.
If no feasible staffing option exists, the system must show the uncovered demand and violated constraints; it cannot invent qualification or quietly weaken policy. If an external write is uncertain, the team reconciles the destination before retrying. An outage leaves state visibly stale, queues only permitted work and hands urgent work to the agreed manual procedure.
These are required release and recovery exercises for a relevant capability, not a claim of deployed integrations or live agent automation.
Human decision boundary
Agents prepare authorized work. Named people retain consequential decisions.
Agent work
- Assemble evidence
- Check permitted requirements
- Prepare a task and receipt
- Route an exception
Named authority
Review the evidenceand decideHire · offer · start and facility policy decisions remain with accountable people.
Operating record
- Permission and scope
- Source and freshness
- Decision and rationale
- Receiving acknowledgement
The visual describes a control boundary: agents prepare authorized work and named people retain consequential decisions.
A clinician’s permission opens access to eligible evidence. It does not transfer one employer’s policy, private pipeline, decision or background report. Each facility orders its own background report.
A usable record lifecycle
Reuse begins with provenance and ends with receiving acceptance.
The planned handoff carries eligible evidence with its source, date and purpose. The clinician grants access to a named facility; that facility decides what it can accept under its own current requirements. If a record is corrected, expires, is disputed or is withdrawn, affected work must become visible for review rather than leaving an old representation in place.
- Capture
- Retain the permitted source assertion, its version and how it was obtained. Do not label an upload, OCR output or model interpretation as source-checked.
- Use
- Apply it only to the authorized recipient, purpose and role/site requirement. Preserve the facility’s acceptance or rejection reason where it is permitted to do so.
- Correction and revocation
- Give the clinician a route to correct or dispute information and to revoke future sharing. Maintain the necessary receipt and propagate correction to permitted relying views.
- Reuse
- Measure whether a second facility accepts eligible evidence, how much repeated collection is avoided and whether the experience is actually faster for both sides.
Our goal is one clinician moving between two facilities, with the second recording an accepted check, by December 31, 2026.
Goal set October 1, 2026. Accepted reuse remains subject to consent, source terms, freshness and the receiving facility’s requirements.