HCI & Healthcare: Bridging the Gap Between Design and Lifesaving Technology
10889_Computer-human interaction and health care opportunities, roadblocks, tips, and tricks.
This article presents a tutorial and roadmap for applying Human-Computer Interaction (HCI) and Human Factors Engineering to healthcare information systems. Authored by John W. Gosbee, M.D., it outlines the methodologies for designing usable medical software and devices to reduce adverse events and improve clinical outcomes, notably aligning with emerging 1990s FDA requirements.
TL;DR
At the intersection of medicine and technology, usability is literally a matter of life and death. This seminal 1999 work by Dr. John Gosbee outlines how Human-Computer Interaction (HCI) and Human Factors Engineering are essential to modernizing healthcare information systems. It addresses the shift from clinician-only systems to patient-centric design, providing a blueprint for surviving the "roadblocks" of medical software development.
Problem & Motivation: The Danger of Poor Design
In the late 1990s, the medical community faced a crisis of complexity. Information systems were becoming pervasive, yet their design often ignored the high-stress, high-stakes environment of the hospital or clinic.
The motivation for this work was two-fold:
- Safety: Poorly designed software leads to "adverse events" (e.g., medication errors).
- Regulation: Agencies like the FDA and organizations like the American Medical Association began demanding that human factors be integrated into the design cycle to prevent user-induced failures.
The "Why" is clear: Medicine is a "strange environment," and generic software design principles often fail when applied to an information-intense rural clinic or a busy emergency ward.
Methodology: The HCI Toolkit for Healthcare
The methodology described isn't just about making interfaces "pretty"; it's about contextual grounding.
1. Contextual Inquiry
Designers are encouraged to perform deep dives into actual clinical settings (video tours, slide analysis) to understand the "information rich" nature of medicine.
Figure 1: Healthcare HCI involves mapping the complex interactions between professionals, patients, and devices.
2. Iterative Usability Testing
The paper advocates for a rigorous cycle of prototyping followed by usability testing specifically for computerized medical records. This ensures that the mental model of the physician matches the system's logic.
3. Training and Education
Dr. Gosbee identifies a specific "roadblock": the lack of HCI professionals who understand medicine. He proposes specialized coursework to help tech professionals interpret medical workflows accurately.
Experiments & Results: Evidence of Impact
The impact of this approach is evidenced by the industry's shift. Major healthcare IT players (like Cerner and SMS) began creating dedicated usability groups.
- Case Success: The Mayo Clinic's adoption of these methods led to the creation of two dedicated usability labs.
- Educational SOTA: Previous iterations of this tutorial at CHI '98 were sold out, proving the massive industry demand for these specific "tips and tricks" in a historically stagnant field.
Figure 2: The HCI/Human Factors discipline became crucial in decreasing adverse events with medical software.
Critical Analysis & Conclusion
Takeaway
Dr. Gosbee’s work served as a wake-up call: the transition from "clinician-only" users to home health care (where the elderly are the primary users) necessitates a radical shift in HCI paradigms. Design must account for physical limitations, cognitive load, and the extreme environment of medical practice.
Limitations
The paper focuses heavily on the organizational and educational roadblocks. While it provides "tips and tricks," it lacks 2020-era quantitative metrics (like millisecond-level interaction latency) because the field in 1999 was still fighting for a seat at the table.
Future Outlook
Today, as we move into AI-assisted surgery and LLM-driven diagnostics, the principles laid out here remain the foundation. We are still solving the same core problem: how do we ensure that the computer helps the healer rather than getting in their way?
