Question 21 of 28: Usability Goals for a Hospital Patient Registration System

Question 21: Usability Goals for a Hospital Patient Registration System (Part IV)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

A hospital registration system is used by staff under time pressure, at shift changeovers with variable training levels, and by clerks who must not let an avoidable data-entry mistake reach a patient's medical record — making all three usability goals directly safety-relevant, not merely a convenience concern.

1. Easy to learn. Design strategy: follow the SAME screen layout and interaction pattern (search → select → confirm) across every registration workflow (new patient, returning patient, transfer), so a clerk who has learned one workflow can transfer that knowledge directly to the others; supply inline field-level hints (e.g., expected date format shown directly in the field) rather than requiring a separate manual; and provide a guided, step-by-step wizard for the least frequent, highest-risk workflow (new-patient registration with insurance verification) where an infrequent user most needs structure.
2. Easy to use. Design strategy: minimize the number of fields and screens needed for the most common task (checking in a RETURNING patient) by pre-populating known data from the patient's existing record and requiring only a confirmation, not re-entry; support the health card / barcode scanner as the primary input path so frequent users almost never touch a keyboard for a routine check-in; and keep the most time-critical action (register an EMERGENCY/urgent-triage patient with minimal information) reachable in as few clicks as possible, deferring non-critical fields to be completed later.
3. Help prevent and/or fix user errors. Design strategy: PREVENT errors with real-time field validation (an invalid health-card-number format is flagged immediately, before submission, not after) and constrained input widgets (a date picker instead of free-text date entry) so a whole class of format errors cannot occur at all; and help FIX errors by showing a clear confirmation summary before final submission (so a clerk catches a wrong date of birth before it is saved) and by making every registration action explicitly reversible/correctable afterward (an "amend registration" action, rather than requiring a new record or an administrator's manual database fix) so a caught mistake costs one corrective action, not an escalation.

These three goals interact directly with a hospital's actual risk profile: an easy-to-learn system reduces training burden across frequent staff turnover and shift rotation; an easy-to-use system keeps routine check-in fast during high patient volume; and error prevention/correction protects against exactly the kind of misregistration (wrong patient record updated) that has direct clinical consequences.