Safety

What is implemented, what is proposed, and what is blocked before real-patient use.

The safety center separates current controls from pending sign-offs, prototype scope, non-goals, privacy boundaries, and live-use gates.

Read resources
Patient reportNurse reviewUpdated summary

The triage workspace separates updates from nurse decisions.

Worklist state, patient report, vitals, draft support, nurse assessment, and reassessment stay separated.

Triage proof: currentData: synthetic

Queue

Source order plus nurse state

Draft boundary

Question prompts never set clinical decisions

Action pane

Nurse records assessment and patient-safe messages

Opened
Reviewed
Reassessed

Review sequence

01 / Report

Context is received.

02 / Review

Nurse decides.

03 / Update

Changes return.

Safety evidence
Clinical oversightReview stays explicit
Patient boundaryPrivate by design
Audit trailActions are reviewable
GovernancePilot checks first

Safety contract

Safety has to be visible in the workflow.

Hospitals need to see who owns the work, what patients can see, and how changes are audited.

Read resources
01Clinical oversight

Draft context remains separate until a responsible clinician records the decision.

Nursing
02Patient boundary

Patient guidance stays limited to receipt, update, and escalation language.

Privacy
03Audit trail

Validation status, assessment changes, review notes, and handoff events stay visible.

Governance
04Delivery boundary

Access, handoff destination, support owner, and delivery evidence are mapped before pilot launch.

Clinical IT

Review checklist

The pilot should answer these questions early.

Current capability labeledPrototype labeledNurse authority visibleSynthetic data markedDestination receipt required