FDA Human Factors of Medical Devices

Slides:



Advertisements
Similar presentations
Introducing evaluation. The aims Discuss how developers cope with real-world constraints. Explain the concepts and terms used to discuss evaluation. Examine.
Advertisements

Building a Cradle-to-Grave Approach with Your Design Documentation and Data Denise D. Dion, EduQuest, Inc. and Gina To, Breathe Technologies, Inc.
Chapter 5 Development and Evolution of User Interface
Focus on Patients Manufacturer’s viewpoint The intended use/purpose of a medical device can be depicted using an idealized functional input/output diagram:
Testing Medical Devices A Brief Overview © 2005 Max Cortner. Copying and distribution of this document is permitted in any medium, provided this notice.
FT228/4 Knowledge Based Decision Support Systems Knowledge Engineering Ref: Artificial Intelligence A Guide to Intelligent Systems, Michael Negnevitsky.
References Prof. Saul Greenberg, University of Calgary, notes and articles INUSE 6.2 and RESPECT 5.3 Handbook Prof. , University of , Notes and articles.
CS 501: Software Engineering Fall 2000 Lecture 2 The Software Process.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
1 Human Factors/Usability for Medical Devices: An Historical Perspective Ron Kaye Human Factors Premarket Review, Team Leader Office of Device Evaluation,
Usable Security (Part 1 – Oct. 30/07) Dr. Kirstie Hawkey Content primarily from Teaching Usable Privacy and Security: A guide for instructors (
Developing safety critical systems
The Process of Interaction Design. Overview What is Interaction Design? —Four basic activities —Three key characteristics Some practical issues —Who are.
Usability presented by the OSU Libraries’ u-team.
Fundamentals of Information Systems, Second Edition
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
HFSD Methods Nov HFSD Methods Objectives –To consider types of systems –To characterise methods for HF input into SD –To identify HF contributions.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
External Defibrillators: Recalls, Inspections, and the Quality System Regulation Melissa Torres Office of Compliance December 15, 2010.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Chapter 3 Reference Slide 2 of Lecture 1.  Most products designed without adequate consideration for human factors  Focus is on technology and product.
Chapter 2 The process Process, Methods, and Tools
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Intent Specification Intent Specification is used in SpecTRM
Human Factors (HF) - Assessment Method Agenda What is Human Factors? Why do we need HF-Assessment Method ? What is the HF-Assessment Method ? Why.
Chapter 3: Managing Design Processes
INTRO TO USABILITY Lecture 12. What is Usability?  Usability addresses the relationship between tools and their users. In order for a tool to be effective,
Human Factors Issues Chapter 9. Human Factors = ergonomics WWII based – military significance… … a necessary part of medical device design…
Human Computer Interaction
Chapter 12: Introducing Evaluation. The aims To illustrate how observation, interviews and questionnaires that you encountered in Chapters 7 and 8 are.
Chapter 7 Interactive Design and Prototyping Human Performance Engineering Robert W. Bailey, Ph.D. Third Edition.
Software Engineering User Interface Design Slide 1 User Interface Design.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
SOFTWARE ENGINEERING MCS-2 LECTURE # 4. PROTOTYPING PROCESS MODEL  A prototype is an early sample, model or release of a product built to test a concept.
Evaluating a UI Design Expert inspection methods Cognitive Walkthrough
Prof. Moustafa M. Mohamed Vice dean Faculty of Allied Medical Science Pharos University in Alexandria Development and Regulation of Medical Products (MEDR-101)
Chapter 3 Managing Design Processes. 3.1 Introduction Design should be based on: –User observation Analysis of task frequency and sequences –Prototypes,
Software Prototyping Rapid software development to validate requirements.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Human Factors Issues Chapter 8. What is Human Factors? Application of the scientific knowledge of human capabilities and limitations to the design of.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
WHAT IF ANALYSIS USED TO IDENTIFY HAZARDS HAZARDOUS EVENTS
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Failure Modes and Effects Analysis (FMEA)
Alex Ezrakhovich Process Approach for an Integrated Management System Change driven.
The CDRH Software Message (October 19, 2002) John F Murray Jr.. Center for Devices & Radiological Health US Food and Drug Administration
의료용 S/W 기술문서 심사 방법 원 찬 요 유엘 코리아 발표자 소개 년 2 월 한양대 전자공 졸업 ~ : ㈜ 금성사 ( 현 LG 전자 ) 연구원 ~ : ㈜ 메디슨 규격팀 팀장
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
고려대학교 산업경영공학과 IMEN 315 인간공학 1. INTRODUCTION. 고려대학교 산업경영공학과 IMEN 315 인간공학.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
Information Systems Development
CASE Tools and Joint and Rapid Application Development
Digital media & interaction design
CIS 376 Bruce R. Maxim UM-Dearborn
Human Factors Issues Chapter 8 Paul King.
HSE Case: Risk Based Approach.
Chapter 9 Industrial Design
Engineering Processes
Usability Techniques Lecture 13.
1. INTRODUCTION.
Information Systems Development (ISD) Systems Development Life Cycle
Computer in Safety-Critical Systems
Human Factors in Digital Health
Presentation transcript:

FDA Human Factors of Medical Devices Ensuring a safe, user friendly device-user interface I will be speaking to you today about some of the opportunities and problems Plug-N-Play present us in dealing with dangerous use error and patient safety. I will tell what FDA is doing to try to see that medical devices more user friendly and safer. We see real promise in the Plug-N-Play scheme and we also see some possible problems. But the promise looks like it may far out weigh the problems.

Medical Errors in U.S. each Year Result In: Up to 98,000 deaths 5th leading case of death: exceeds auto accidents, breast cancer and AIDS $29 Billion added cost An Institute of Medicine report cites studies that show that as many as 98,000 people die every year from medical error. That’s equivalent to an overloaded jumbo jet falling out of the sky every other day of the year. In addition, thousands more are injured. Medical errors attributable to device use is not the major cause. Non-the-less, we have every reason to believe it’s a significant contributor.

FDA Medical Device Incident Reports: 100,000 reports per year More than 1/3 involve use error Tip of the Iceberg FDA receives about 100,000 medical device incident reports every year. More than than 1/3 of these reports can be attributed primarily to use error. This is a small fraction of all the incidents that actually occur. Really only a few percent of the total.

FDA Recall Study 44% of medical device recalls due to design problems. Use error often linked to design. An internal FDA study some years ago showed that 44% of medical device recalls were the result of design problems and more than 1/3 involved the device-user interface (device, it’s labeling or instructions for use).

More user friendly Design Operations - don’t exceed user capabilities Information - Sufficient, legible and intelligible Procedures - logical and intuitive Operations - consistent with conventions Dangerous error - designed out Conditions of use - considered and addressed Here’s some advice to help avoid these mistakes?

Key safety concepts in design make things visible simplify the operation avoid reliance on memory avoid reliance on vigilance use natural mappings use forcing functions make it easy to reverse an error

FDA’s authority Quality Systems Regulation/ CGMP - Design Controls (1996) The FDA Quality Systems Regulation is the basis for FDA authority to require proper attention to the design of the device user interface. FDA wants to make sure manufacturers know how to achieve good design and this authority provides us a means for educating slow learners. Nothing like the threat of a little jail time to get their attention.

Design Controls Regulatory Language: “… design requirements … intended use … needs of the user and patient.” “… testing production units under actual or simulated use conditions.” “… conduct risk analysis.” The Design Control provisions of the FDA regulation require manufacturers to address the user's needs and those needs certainly include a safe user interface. Design validation calls for testing under actual or simulated use conditions and for a risk analysis to be carried out.

Design Controls Preamble Language: “… conduct appropriate human factors studies, analyses, and tests …” “… human interface includes both the hardware and software characteristics…” The preamble to the FDA regulation speaks, in some detail, to the need for human factors studies, analysis and tests. Preambles to FDA regulations have legal standing and are used to clarify and provide the rationale for the regulation.

Design Controls - Human Factors Engineering (HFE) Process HFE applied from concept stage to final design Early Involvement of typical users is critical The process is iterative Incorporating HFE into the design process is the only way to reliably ensure that the needs of the user are adequately addressed in the final product.

Human Factors Engineering Process Concept Phase Design Input Design Output Verification Validation Perform Studies & Analyses Develop Require- ments Specs. Test Output Against Input Test Against Patient & User Needs * HF Elements Analyses Expert Evaluation Rapid Prototyping Literature Complaints Observation Interviews HFE is conducted throughout the design process from beginning to end. It's also a process that must be fully integrated into the overall design activities. HFE starts early, involves typical users, is iterative just like the rest of the design process. Safety Environment Users Performance Drawings Mockups Computer Prototypes Production Units Full Usability Test Risk Assessment *Design and Development Planning Important Here

Human Factors Engineering - Summary of Methodology Study the user population and use conditions Analyze function, tasks, and hazards Incorporate findings in requirements To summarize the HFE methodology. All this information has been provided to manufacturers via our FDA website and in a number of voluntary consensus standards that FDA has recognized.

Human Factors Engineering - Summary of Methodology Test and analyze prototypes against requirements Test production models in simulated environment Conduct a risk assessment Read screen

HFE Standards ANSI/AAMI HE74:2001 Human factors design process for medical devices IEC 60601-1-6, Ed1, Usability Here is one of those voluntary consensus standards that FDA has recognized to give guidance to manufacturers. We highly recommend it. FDA staff worked closely with the AAMI HFE Committee and medical device manufacturers to write this standard. A survey of manufacturers was carried out to determine what information they needed and what question they wanted answered. It’s a user friendly guidance document designed for the HFE novice as well as the HFE experts. It served as the basis for the new IEC 60601-1-6, Collateral Standard: Usability which is currently being balloted as an FDIS.

ANSI/AAMI HE74:2001 Overview of the HFE process Planning the HFE process HFE process: a systems approach Methods and techniques Risk & cost benefit analysis This is an overview of contents of that standard.

ANSI/AAMI HE74:2001 Need for user input Scaling the HFE work Documenting the HFE activities Design evaluation: verification & validation More content.

ANSI/AAMI HE74:2001 Relevant FDA regulations Practical tips Bibliography - General HFE references - Human error - Human computer interface - Usability testing More useful content. That is – useful according to the feed back from manufacturers.

FDA Web Site http://www. fda.gov/cdrh/humanfactors.html fda.gov/cdrh/usererror.html