Questions from specific roles
Workflows in a small clinic
Everyday workflows and how far the pilot gets with them.
How to read status labels: In the pilot (v0.5.0, synthetic data) Simulated in the pilot (no real external system) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0453How does a front desk check in a new patient?
The registration form collects demographics, creates a clinic-prefixed record number with a check digit, warns on possible duplicates and can admit a visit. Scheduling, check-in and rooming are separate modules, and coverage checks run against a simulator.
C0454What if the patient is unknown or unconscious?
Unknown-patient registration lets staff start a record and later merge it with a two-person approval.
C0455How does a nurse take vitals?
She opens the patient's chart and adds structured vitals with range flags, notes and intake and output that appear live to the doctor's open view. A high NEWS2 score can raise an alert.
C0456How does a doctor see a critical lab?
The result files to the chart and a sticky banner demands acknowledgement with a read-back note. The lab feed is synthetic in the pilot.
C0457How are allergies recorded?
As coded entries with reaction and severity, with an explicit allergy status so an empty list never reads as none.
C0458How are medications reconciled?
Every active medication needs a continue, stop or change decision before the list can be saved.
C0459How does a code get called?
A code button for the facility catalog raises an alert to its audience by role, responders must acknowledge and the history is kept. Colour, pattern and plain text all show the meaning.
C0460How are messages and memos different?
Messages are short, quick and conversational. A memo is a formal inbox item with priority, read receipts and acknowledgement. Urgent-sounding memo text is redirected to the alert path.
C0461How does a supervisor change an alert policy?
By proposing it; a different authorized person approves it, and the change is versioned with history.
C0462How does a clinic add a new staff member?
An administrator creates the user, who receives a one-time password and must change it at first login. Privileged roles need a second approver.
C0463How does a clinic remove a leaver?
An administrator disables the user, and the session is revoked. Role expiry and recertification are designed.
C0464How does a clinic book appointments?
Through the scheduling module (since v0.4.0): staff pick a resource and appointment type, book into a template slot with conflict checks, and can reschedule, cancel, record a no-show, use the waitlist and check the patient in. Patient self-booking and reminders are not built.
C0465How does a clinic print a chart?
Through a logged print queue to a wired printer (since v0.4.0): every job is audited and watermarked, a per-user daily limit applies, and protected compartments need a purpose and a password step-up. No real printer driver exists, so this is the queue and its controls, not tested printing hardware.
C0466How does a clinic send a referral?
Referral and care-coordination loops are designed and not built.
C0467How does a clinic order a lab test?
By a structured order from the catalog or an order set, signed per the permission matrix. The order goes to a simulated lab connector as an HL7 v2 message and the result comes back to the inbox. No real laboratory is connected.
C0468How are results communicated to the patient?
Through the patient portal, once staff release a result, or by the clinician. The portal exists with in-person activation and no real patient uses it.
C0469How do small clinics handle immunizations?
The pilot has coded immunization entries. Registry reporting is designed, not built.
C0470How are prescriptions printed?
Not supported. E-prescribing runs through a simulated pharmacy network; prescription paper and printing are not built.