Platform, configuration and devices
Terminal and tablet user experience
Thin-client UX.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0874Is the terminal interface designed for gloved hands and quick touches?
The terminal and tablet user experience part of the specification (REQ-4901) says Terminal UI must be usable with gloves and quick-touch: min 48 px targets, high contrast, large-text mode, and no PHI cached in the browser. The pilot covers part of this. The rest is designed, not built. Pilot detail: Large-text/high-contrast/reduce-motion prefs and role home exist; buttons min-height 36 px (spec 48 px). Acceptance check: accessibility audit and cache inspection pass.
C0875What does the tablet home screen show for each role?
How would it be tested? The specification says alert appears while any workflow open. That is the check for REQ-4902: the tablet UI must provide role-based home, patient list, alert tray, messaging and Memo Desk access with an always-visible alert banner area. The pilot covers part of this. The rest is designed, not built. Where the code stands: Large-text/high-contrast/reduce-motion prefs and role home exist; buttons min-height 36 px (spec 48 px).
C0876Would terminal screens show a watermark and lock when idle?
Designed, not built: there is no code for this in the pilot. For reference, REQ-4903 (a top-priority requirement, all three tiers) says the terminal must show a live on-screen watermark (user, terminal, time) and lock on idle timers (2, 5, 10 min by area, proposed). Check: timer values configurable by area.
C0877Can staff tap a proximity badge to sign in and switch users quickly?
The terminal UI must support proximity badge tap-in/out and fast user switching within the session policy. That is REQ-4904, a high-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: tap-out locks within 1 s.
C0878Will the interface support Spanish and Portuguese, and how will clinical content be translated?
No. The specification describes it, but the pilot does not include it. REQ-4905 says the UI must support Spanish, Portuguese (BR) and English, with locale-specific date/number/units, and must not machine-translate clinical content silently. Its acceptance check: locale switch retains data; translation flagged.