A workflow prototype for emergency-room queue visibility, patient-state tracking, and triage prioritization using structured forms, local data persistence, and dashboard views.
Emergency room workflows depend on clear shared visibility. Intake, vitals, priority, room assignment, and treatment progression can become fragmented if they are not represented in one system.
The prototype centralizes patient intake, vitals entry, priority scoring, queue monitoring, patient insight pages, and status history.
Stack: Python · NiceGUI · SQLite · Testing · Workflow Modeling
Tradeoff
A hospital queue screen can look useful even if it does not reflect patient states, priority changes, or staff handoff.
Outcome
Modeled queue visibility, triage priority, patient status, and dashboard state before treating the UI as the final artifact.
Tradeoff
A cloud backend would be more realistic, but it would slow early iteration for a workflow prototype.
Outcome
Used local data persistence so the prototype could demonstrate patient state changes, queue behavior, and dashboard updates quickly.
Tradeoff
Automated priority scoring can become unsafe or untrusted if users cannot understand why a patient moved in the queue.
Outcome
Kept triage logic structured so future versions can show the reason behind priority changes and attention flags.
