Training and staff adoption
Staff adoption
How the design tries to reduce friction and support learning.
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
C0259Will staff need a lot of training?
Training depends on scope. The design lists role-based user guides, quick-reference cards and a competency curriculum, but none has been produced. The pilot is small enough to learn from its own screens.
C0260Are there training materials?
Planned deliverables include clinical user guides by role tier, quick cards for tablets, alerts and downtime, and an administrator guide. They are not written yet.
C0261How does the design handle shared-login habits?
By preventing shared credentials technically, while keeping security friction low, since clinics have variable IT literacy and high turnover.
C0262Can staff with large text needs use it?
The pilot has large-text, high-contrast, light theme and reduce-motion preferences.
C0263Are alerts easy to recognise under stress?
Alerts use colour plus pattern plus plain text, so they do not rely on colour alone, and emergency alerts take over the full screen with a deliberate acknowledgement.
C0264Is the touch target large enough for gloved hands?
On touch screens the pilot sets buttons to 48 px, the specification's target, and with a mouse the minimum is 36 px. It has not been tested with gloves, and no usability study exists.
C0265Are there usability metrics?
Time to chart, tasks per session and usability score per release are planned measures. None has been collected.
C0266Can I set the screen language for each user?
Localization is a specification target. The pilot screens are English only.
C0267Can the front desk and nurses see different screens?
Yes: navigation and permissions follow the role tier and the tenant's manifest.
C0268How are nurses supported on handoff?
A nursing handoff feature is designed in the nursing module. It is not built in the pilot.
C0269How does the system reduce typing?
Type-ahead over coded lists, note templates and smart phrases, order sets and copy-forward exist in the pilot. Ambient documentation is not built, and AI would be off by default.
C0270Is there a patient-facing guide?
No patient education content is published. The patient portal exists, with in-person activation, but it carries no education material, and patient guides are part of the planned forms library.
C0271Who supports super-users?
Support for each tier is undecided; escalation paths and severity levels are designed.
C0272Can staff practice without real patients?
Yes. Everything in the pilot uses synthetic, clearly labelled records, which suits practice and demonstrations.
C0273How are drills supported?
Code alerts support drill sessions in the pilot, with timings and delivery and acknowledgement reports. Unit-level downtime drills are designed, and none has been run at a site.