I have finalised the demo for the ICH-GCP E6 R3 refresher course. Overall, I liked the content and the interface. I also want to thank Whitehall Train...
About
Human Factors and Usability Engineering is a critical discipline that ensures medical devices are designed to be safe, effective, and easy to use by their intended users in real-world environments. By applying a systematic usability engineering process, manufacturers can identify and reduce use-related risks, improve user performance, and support regulatory compliance throughout the product lifecycle.
This Human Factors and Usability Engineering for Medical Devices Training Course & Certification provides comprehensive knowledge of human factors principles, usability engineering processes, user and use environment analysis, task analysis, use-related risk management, formative evaluations, user interface design, human factors validation studies, the Usability Engineering File, regulatory expectations, and post-market usability activities. Upon successful completion, learners receive a certification demonstrating their understanding of human factors engineering and medical device usability best practices.
- Medical Device Design and Development Engineers
- Human Factors and Usability Engineering Professionals
- Quality Assurance and Quality Management Professionals
- Regulatory Affairs and Compliance Professionals
- Risk Management Specialists
- Verification, Validation, and Testing Engineers
- Medical Device Product Managers and Project Managers
- Anyone involved in the design, development, evaluation, or regulatory compliance of medical devices
What you will learn
Understand the principles of human factors and usability engineering, applicable regulatory requirements, and the role of usability in ensuring the safety and effectiveness of medical devices.
Learn how to identify users, use environments, intended use, use scenarios, critical tasks, and use-related hazards throughout the medical device lifecycle.
Develop knowledge of task analysis, use-related risk analysis, formative evaluations, user interface design, and human factors validation studies in accordance with industry standards.
Gain practical understanding of usability engineering documentation, the Usability Engineering File, regulatory submissions, post-market feedback, and lifecycle management best practices.
Course Syllabus
- What human factors engineering is
- Use error is a leading safety concern
- Human capabilities and limitations — the map
- Perception and its limits
- Cognition and mental models
- Memory — working versus long-term
- Attention — selective, divided and vigilance
- Physical capability and anthropometry
- Fatigue and stress
- Usability, defined
- User experience (UX), defined
- Use-related safety, defined
- Usability vs UX vs use-related safety
- How the three concepts nest
- Why the terminology must be exact
- Use error
- Abnormal use
- Reasonably foreseeable misuse
- Close call
- Operational difficulty
- The five terms at a glance
- Design controls — the framework
- Design inputs and outputs
- Verification versus validation
- Where usability engineering sits
- Design review and the design file
- FDA QMSR — design controls, updated
- IEC 62366-1:2015 (+A1:2020) — overview
- The usability engineering process
- The use specification
- User interface and known use
- Hazard-related use scenarios
- Formative versus summative evaluation
- IEC/TR 62366-2:2016 — guidance
- ISO 14971:2019 and use-related risk
- ISO/TR 24971:2020 — guidance
- IEC 60601-1-6 — the usability collateral
- How the standards fit together
- FDA 2016 human factors guidance
- Critical tasks — a first look
- FDA submissions guidance — final 2026
- The three HF submission categories
- EU MDR — Regulation (EU) 2017/745
- MDR Annex I — usability and information for safety
- MDR technical documentation
- IEC 62366-1 in the EU — a nuance
- Human factors across the lifecycle
- Misconception — 'training fixes the interface'
- Misconception — 'labels eliminate risk'
- Misconception — 'one validation proves it forever'
- Why users, environments and the Use Specification come first
- Three terms people blur: indication, purpose, use
- Intended medical indication, defined
- Intended purpose, defined
- Intended use and the instructions for use
- Who counts as a user?
- User groups and subgroups
- Healthcare professionals as users
- Patients and lay users
- Lay caregivers
- Maintenance, service and reprocessing personnel
- Template T002 — the User Group Profile
- Why user characteristics matter
- Knowledge, experience and training level
- Language, literacy and numeracy
- Sensory ability, including low vision
- Physical ability, including limited dexterity
- Cognitive ability, health and emotional state
- Design for the range, not the average user
- Why the use environment matters
- Hospital and clinic environments
- The home use environment
- Ambulance, transport and emergency settings
- Laboratory and public settings
- Environmental factors — lighting, noise, space
- Environmental factors — stress, interruptions, PPE
- Environmental factors — connectivity and cleaning
- Template T003 — the Use Environment Profile
- The operating principle
- User-interface elements
- Accessories
- Connected systems and interoperability
- Use scenarios in the Use Specification
- Frequency, duration and sequence of use
- Normal use and reasonably foreseeable scenarios
- Training assumptions in the Use Specification
- The risk of excessive reliance on training
- What is a Use Specification?
- Structure of a Use Specification (template T001)
- Traceability to design inputs
- The Use Specification as the foundation
- What a good Use Specification contains
- Where the Use Specification sits — IEC 62366-1
- Worked example — infusion device
- Worked example — auto-injector
- Worked example — diagnostic system (IVD)
- Worked example — Software as a Medical Device (SaMD)
- Worked example — home-use monitoring device
- A peer-review checklist for the Use Specification
- Why known use problems come before new risk analysis
- The sources landscape for known use problems
- Source 1 — complaints and CAPA records
- Source 2 — recalls and field safety corrective actions
- Source 3 — adverse-event databases
- Source 4 — published and grey literature
- Source 5 — analogous and predicate devices
- Source 6 — service, maintenance and post-market signals
- Building a search strategy
- Appraising relevance and reliability
- The Known Use Problems Search Log — template T004
- Logging discipline and traceability
- What task analysis is, and why it matters
- Hierarchical task analysis (HTA)
- Cognitive task analysis (CTA)
- Choosing and combining HTA and CTA
- Decomposing a task: subtasks, decisions, feedback, error opportunities
- The perception-action cycle
- Information flow: displays, controls and the user
- Do not analyse only normal use
- Normal-use and emergency-use tasks
- Maintenance, cleaning, installation and disposal tasks
- Reasonably foreseeable use scenarios
- Edge cases and the worst credible scenario
- The Use Scenario Catalogue — template T006
- Sequence diagrams: showing the interaction over time
- Journey maps: the user's experience end to end
- User-interface flow models
- From task failure to hazardous situation
- Task failures caused by labels and instructions
- Task failures caused by controls
- Task failures caused by displays and alarms
- Task failures caused by software navigation and physical layout
- Common failures in known-problem gathering and task analysis
- From task analysis into use-related risk
- Slips, lapses and mistakes
- Use error, close call and operational difficulty
- Harvesting close calls and operational difficulties
- Mental models and user expectation
- Interruptions, workload and attention
- Methods for eliciting task information
- Mode confusion in connected devices
- Linking known problems to user groups and environments
- Prioritising which tasks to analyse in depth
- What use-related risk analysis is
- Integrating with ISO 14971 hazard analysis
- The use-related risk chain
- Sharpening the terminology of use
- Potential use errors: where to look
- Contributing design factors
- User-interface characteristics related to safety
- Primary operating functions
- What makes a task critical
- Determining critical tasks — a risk-based decision
- The Critical Task Register — template T008
- Why probability of a use error cannot be meaningfully estimated
- Prioritise on severity
- The software-risk parallel
- Risk controls: the order of precedence
- Tier 1 — inherent safety by design
- Tier 2 — protective measures
- Tier 3 — information for safety is the weakest control
- Strong versus weak controls, compared
- From risk control to user-interface requirement
- The User-Interface Requirements template — T009
- Residual risk and overall residual risk
- Benefit-risk considerations
- The traceability thread
- The Use-Related Risk Analysis template — T007
- Common failures in use-related risk analysis
- Use-related hazard versus its cause
- Reasonably foreseeable misuse in the risk analysis
- Categories of use error
- Error-producing conditions
- Mapping errors to perception, cognition and action
- Primary operating function versus critical task
- Grouping and documenting critical tasks
- Severity scales and harm categories
- Judge on worst credible harm
- Detectability does not rescue a use-related risk
- Defence in depth: combining controls
- New risks introduced by risk controls
- Verifying that a control is effective
- Using information for safety well
- Writing verifiable user-interface requirements
- Linking requirements to design controls
- Production and post-production information
- The risk-management report and human factors
- Connected, combination and home-use considerations
- What formative evaluation is
- When to run formative evaluation: early and often
- Formative evaluation across the development lifecycle
- The value of finding problems early
- Formative versus summative — the central distinction
- Danger — never present formative work as validation
- What each evaluation can and cannot tell you
- The formative methods toolkit
- Heuristic review and expert review
- Cognitive walkthrough
- Interviews and contextual inquiry
- Simulated-use formative testing
- Choosing a method to fit the stage and question
- Representative participants — why it matters
- Defining participant characteristics
- How many participants for a formative study?
- Prototype fidelity — low, medium and high
- Low- and medium-fidelity prototypes
- High-fidelity prototypes and matching fidelity to the question
- The formative evaluation plan (template T010)
- Writing formative scenarios and tasks
- Designing data collection
- Moderator behaviour — do not lead or coach
- Think-aloud and probing without steering
- Three kinds of formative data
- Observational data
- Performance and subjective data
- Root-cause analysis of use errors and close calls
- Distinguishing use error, close call and difficulty
- The root-cause interview (template T015)
- Design iteration on the evidence
- Documenting design decisions — why a change was made
- Knowing when not to change
- Re-testing after a change
- Formative evidence and risk controls
- What formative evidence can and cannot support
- Remote and unmoderated formative studies
- Software and app prototype testing
- Accessibility in formative studies
- Formative Evaluation Plan — template T010 in full
- Formative Evaluation Report — template T011
- Common failures in formative evaluation
- From formative to a stable, validatable design
- Setting clear formative objectives
- Simulating the use environment in formative work
- Recruiting and screening participants
- Consent and ethics in formative studies
- Piloting the session before you run it
- Triangulating the three data types
- Prioritising findings for iteration
- Comparative formative testing of design options
- Formative testing of connectivity and stale data (KUP-05)
- Turning formative findings into UI requirements
- How many rounds, and when to stop
- Team roles in a formative study
- Formative work for connected, combination and home-use devices
- What human factors validation is
- Validation is part of design validation
- Validation versus verification
- Formative and summative — the boundary restated
- What validation must demonstrate
- Validation readiness — are you ready to validate?
- The stable, frozen user interface
- Danger — do not validate a moving target
- Validation focuses on the critical tasks
- Selecting validation scenarios
- Developing realistic use scenarios
- Including reasonably foreseeable misuse
- Combining tasks into realistic sequences
- Representative users for validation
- Distinct user groups and subgroup coverage
- Sample size is a risk-based rationale, not a universal number
- On FDA's '15 per group' convention
- Building the sample-size rationale
- Use environments in validation
- Simulated-use fidelity
- Actual-use considerations
- Training conditions in validation
- Realistic training, not over-training
- Training decay periods
- The moderator script
- Preventing coaching in validation
- Data-collection forms (template T014)
- Predefine the definitions before the study
- Capturing data for later root-cause analysis
- Study controls and avoiding confounds
- Safety controls during the study
- Study stopping rules
- Ethics and oversight
- Pilot study and protocol refinement
- Acceptance rests on analysis of use-related risk
- Why a pass percentage is the wrong criterion
- A residual use error is analysed, not an automatic fail
- A clean run is not an automatic pass
- The acceptance reasoning
- Residual risk and benefit-risk in the conclusion
- The human factors validation protocol (template T012)
- What the protocol fixes in detail
- Defining task success and assists precisely
- Predefining the analysis approach
- Protocol review and roles
- Mapping scenarios to critical tasks
- FDA submission expectations
- Preview — the three HF Submission Categories
- Organising the study documentation
- A note on EU technical documentation
- Common failures in validation planning
- What good validation planning delivers
- Think-aloud in validation — retrospective only
- Recording and observation logistics
- Counterbalancing scenario order
- Non-critical tasks and overall realism
- Using formative results to inform the plan
- Test sites and environment set-up
- From plan to execution
- The execution mindset
- The execution-to-report workflow
- Setting up and controlling the test site
- Equipment control and configuration management
- Confirming the exact UI version under test
- Recording and observation set-up
- Recruitment and screening confirmation
- Informed consent
- Confidentiality and data protection
- The moderator role during execution
- Observational discipline - no coaching, no leading
- Standardised task instructions and prompts
- When a participant asks for help
- Handling deviations from the protocol
- Unexpected events during a session
- Equipment failure mid-session
- Documenting deviations and their impact
- What to capture in each session
- Recording task outcomes precisely
- Identifying use errors in the moment
- Close calls and operational difficulties
- Capturing participant comments
- Comprehension methods
- The purpose of root-cause interviews
- Interview without leading - ask why, do not suggest
- Good and poor interview questions
- Probing perception, cognition and action
- Coding and categorising the data
- Inter-rater consistency
- Traceability of every observation
- Managing the raw dataset
- The analysis approach
- Analysis by task
- Analysis by user group
- Analysis by scenario
- Analysis by potential harm
- Aggregating and finding patterns
- Determining whether a design change is needed
- The risk-control hierarchy revisited
- Additional controls versus redesign
- Residual use-related risk conclusions
- Benefit-risk in the conclusion
- Updating the risk-management file
- The Human Factors Validation Report (T016)
- The report contents in detail
- Writing the conclusion honestly
- Inadequate conclusions and unsupported claims
- 'No use errors, therefore safe' - why it is wrong
- More unsupported claims to avoid
- Common failures in execution, analysis and reporting
- What good execution and reporting delivers
- Handover to the file and submission
- From the validation report to the file
- The usability engineering process at a glance
- The Usability Engineering File structure (T017)
- What goes in the file - and what does not
- Traceability across the file
- Traceability to design inputs
- Traceability to risk management
- Traceability to verification and validation
- EU technical documentation under the MDR
- Design-history evidence under the MDR
- FDA marketing submissions and human factors
- The final submissions guidance (29 May 2026)
- The risk-based framework - overview
- The three HF Submission Categories
- Choosing the category - a decision tree
- From 1 August 2026 - templates prompt the category
- Summarising the evidence (checklist T018)
- Summarising users, environments and known problems
- Summarising critical tasks, formative and validation
- Legacy user-interface evaluation
- How to evaluate a legacy interface
- Changes to user interfaces and software
- Changes to labels, accessories and training
- When a change re-opens usability work
- Assessing the impact of a change
- Post-market surveillance and usability
- Use-related signal detection (T019)
- Distinguishing use error from device malfunction
- CAPA and usability
- Field-action implications
- Home-use device considerations
- Connected and software-driven devices
- AI-enabled device considerations
- Combination-product considerations
- Maintaining usability evidence over the lifecycle
- Audit and inspection readiness
- What auditors and reviewers look for
- Common failures in files and submissions
- What good file and submission management delivers
- The traceability matrix in practice
- FDA and EU - two homes for the same evidence
- Marketing submission types and where HF fits
- Complaints handling and use-related coding
- Keeping the file and the submission consistent
- Human factors across the total product lifecycle
- 📘 Bonus: Human Factors and Usability Engineering eBook (Free with purchase)









