Design a pilot

Triage workflow

The story is ready before triage and updated through nurse review.

The triage workspace brings worklist state, patient report, questions, vitals, draft support, nurse assessment, and reassessment into one accountable surface.

Design an intake pilot
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.

Triage workflow evidence
Report contextPatient state visible
Review contextOwner visible
Changed symptomsReturns to review
Handoff fileHistory travels forward

Inside triage

Start with the next action, not another surface beside the work.

Nurses need the selected patient, updates, review context, owner, and handoff action in one place.

Report stateVitals and patient context sit together.Patient concerns, symptom history, and captured observations stay in one review surface.
Review stateReview context stays attributable.The care team sees patient context, changed symptoms, and source notes before recording the next owned action.
Handoff stateThe physician sees what changed.Validation history travels with the file, so handoff quality does not depend on memory.

Reassessment path

Reassessment should make changed symptoms visible.

Any triage surface has to clarify what changed, who reviewed it, and when the current assessment version was recorded.

1

Patient tablet

Guided questions and status cues collect context while clinical review details stay with the care team.

2

Nurse station

Vitals, changes, review notes, and assessment controls remain in one workflow.

3

Room signal

New symptom updates can return to the validation queue instead of being lost.

4

Physician handoff

The final file includes context, review notes, and validation history.

Triage contract

Four views, one reviewed summary.

Every view has a different user, but the owner, status, and audit trail stay connected.

Design a pilot
01Patient tablet

Guided questions and status cues collect context while clinical review details stay with the care team.

Patient
02Nurse station

Vitals, changes, review notes, and assessment controls remain in one workflow.

Nurse
03Room signal

New symptom updates can return to the validation queue instead of being lost.

Care team
04Physician handoff

The final file includes context, review notes, and validation history.

Physician