Medical Product Software Development and FDA Regulations4008
Medical Product Software Development and FDA Regulations4008
IEEE Orange County Computer Society March 27, 2006 Carl R. Wyrwa
Patients
Environment
Operators
Bystanders
Service Personnel
Medical Practitioners
Reviewers
Internal Auditors External Reviewers
Medical Practitioners
Reviewers
Internal Auditors External Reviewers
FDA Overview
FDA is a public health agency, charged with:
z
protecting American consumers by enforcing the Federal Food, Drug, and Cosmetic Act and several related public health laws.
the food we eat is safe and wholesome, the cosmetics we use won't hurt us, the medicines and medical devices we use are safe and effective, and that radiation-emitting products, such as microwave ovens, won't do us harm
z z
One of our nation's oldest consumer protection agencies. Located in district and local offices in 157 cities across the country
10
11
FDA Overview
z
Unannounced and Announced Inspections Inspectional Observations - 483 Warning Letters Adverse Publicity FDA-Initiated Recalls and Monitoring Company-Initiated Recalls Delay, Suspension, or Withdrawal of Product Approvals Preclusion of Government contracts Detention and Refusal of Entry into U.S. Commerce of Imported Products
12
13
Simple Devices
z
Complex Devices
z z
Class I devices include those with the lowest risk Class III devices includes those with the greatest risk.
14
"an instrument, apparatus, implement, machine, contrivance, implant, in vitro reagent, or other similar or related article, including a component part, or accessory which is:
recognized in the official National Formulary, or the United States Pharmacopoeia, or any supplement to them, intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease, in man or other animals, or intended to affect the structure or any function of the body of man or other animals, and which does not achieve any of it's primary intended purposes through chemical action within or on the body of man or other animals and which is not dependent upon being metabolized for the achievement of any of its primary intended purposes."
15
16
(1) Each manufacturer of any class III or class II device, and the class I devices listed in paragraph (a)(2) of this section, shall:
z
establish and maintain procedures to control the design of the device in order to ensure that specified design requirements are met.
z
17
Because of its complexity, the development process for software should be even more tightly controlled than for hardware, in order to prevent problems that cannot be easily detected later in the development process. . software engineering needs an even greater level of managerial scrutiny and control than does hardware engineering.
[1]
18
19
Regulation of Software
Basic Regulatory Requirements Quality System Regulation
A - General Provisions B - Quality System Requirements C Design Controls D Document Controls E Purchasing Controls F Identification and Traceability G Production & Process Controls H Acceptance Activities I Nonconforming Product J Corrective & Preventive Action (CAPA) K Labeling & Packaging Control L Handling, Storage, Distribution & Installation M - Records N - Servicing O Statistical Techniques Design Controls
820.30(a)
General
Establishment Registration
820.30(b)
Design Input
820.30(d)
Design Output
820.30(e)
Design Review
820.30(f)
Design Verification
820.30(g)
Design Validation
820.30(h)
Design Transfer
820.30(i)
Design Changes
820.30 (j)
21 CFR 803
Regulation of Software
Basic Regulatory Requirements Quality System Regulation
A - General Provisions B - Quality System Requirements C Design Controls D Document Controls E Purchasing Controls F Identification and Traceability G Production & Process Controls H Acceptance Activities I Nonconforming Product J Corrective & Preventive Action (CAPA) K Labeling & Packaging Control L Handling, Storage, Distribution & Installation M - Records N - Servicing O Statistical Techniques 21 Production & Process Controls
820.70(a)
General
Establishment Registration
820.70(b)
Environmental Control
820.70(d)
Personnel
820.70(e)
Contamination Control
820.70(f)
Buildings
820.70(g)
Equipment
820.70(h)
Manufacturing Material
820.70(i)
Automated Processes
21 CFR 803
Regulation of Software
Basic Regulatory Requirements Quality System Regulation
A - General Provisions B - Quality System Requirements C Design Controls D Document Controls E Purchasing Controls F Identification and Traceability G Production & Process Controls H Acceptance Activities I Nonconforming Product J Corrective & Preventive Action Action(CAPA) (CAPA) K Labeling & Packaging Control L Handling, Storage, Distribution & Installation M - Records N - Servicing O Statistical Techniques 22 Corrective & Preventive Action
820.100
Establishment Registration
21 CFR 803
Regulation of Software
Basic Regulatory Requirements Quality System Regulation
A - General Provisions B - Quality System Requirements C Design Controls D Document Controls E Purchasing Controls F Identification and Traceability G Production & Process Controls H Acceptance Activities I Nonconforming Product J Corrective & Preventive Action (CAPA) K Labeling & Packaging Control L Handling, Storage, Distribution & Installation M - Records N - Servicing O Statistical Techniques 23
Establishment Registration
General
820.25(b)
Training
820.22
Quality Audit
21 CFR 803
Procedures Medical Product Software Development and FDA Regulations Plans SW Life-Cycle Model SW Requirements Analysis SW Requirements Verification SW Architectural Design SW Architecture Verification SW Detailed Design SW Detailed Design Verification SW Coding SW Code Verification Unit Test Integration Test SW System Test Beta Testing SW Verification SW Validation COTS Software Components SW Risk/Hazard Analysis SW Human Factors (Use Errors) SW Change Control SW Configuration Management SW Problem Tracking & Resolution SW Traceability Non-Product Software Validation Corrective & Preventive Action (CAPA) Design Transfer Design History File Training Software Quality Audits 24
25
Plans
Software Development
SW Life-Cycle Model SW Requirements Analysis SW Requirements Verification SW Architectural Design SW Architecture Verification SW Detailed Design SW Detailed Design Verification SW Coding SW Code Verification
27
Testing
Unit Test Integration Test SW System Test Beta Testing
28
SW Validation
29
Supporting Processes
COTS Software Components SW Risk/Hazard Analysis SW Human Factors (Use Errors)
SW Change Control SW Configuration Management SW Problem Tracking & Resolution SW Traceability Non-Product Software Validation Corrective and Preventive Action (CAPA)
30
Release
Design Transfer Design History File
31
Personnel
Training Software Quality Audits
32
33
The Reason
WHY
we need to have a comprehensive and effective Software Development Life Cycle
34
Patients
Environment
Operators
Bystanders
Service Personnel
35
Understanding Defects
Defects
Start
Development Process
Ship
[2]
36
Understanding Defects
Defects
Defects Injected
Start
Development Process
Ship
[2]
37
Understanding Defects
Defects
Defects Injected Defects Detected And Corrected
Defects Shipped
Start
Development Process
Ship
[2]
38
Inject Fewer
Defects
Start
Development Process
Ship
[2]
39
Software Requirements
Software Coding
Software Requirements
Software Coding
Software Requirements
Software Coding
Defect Injection Rates are directly related to the completeness and the effectiveness of each of these activities
42
100 90 80
Cumulative Defects
70 60 50 40 30 20 10 0
S R ys s eq SW qs Re
Defects Injected
ig n i gn es es D D t HL De
g din Co
st Te t i Un
t In
st Te SW
st l id Te Va s s Sy Sy
ta Be
st Te
m sto Cu
er
43
Inject Fewer
Defects
Detect Earlier
Start
Development Process
Ship
[2]
44
Software Requirements
Software Coding
Verification
Verification
Verification
Verification
Unit Test
Integration Test
System Validation
Customer
45
Inject Fewer
Defects
}
Detect More Effectively
Fewer Defects
Zero?
Detect Earlier
Start
Development Process
Ship
[2]
46
47
Software Requirements
High-Level Design
Verification
Software Coding
Verification
Unit Test
Integration Test
System Validation
Customer
48
Software Requirements
Verification
Basic Functionality Software Defects Use Errors Verification Verification Environment Interfaces
High-Level Design
Software Coding
Verification
Unit Test
Integration Test
System Validation
Customer
49
Software Requirements
Software Coding
Verification
Verification
Verification
Verification
Unit Test
Integration Test
System Validation
Customer
50
Software Requirements
Software Coding
Verification
Verification
Verification
Verification
Unit Test
Integration Test
System Validation
Customer
51
Software Requirements
Software Coding
Verification
Verification
Verification
Verification
Unit Test
Integration Test
System Validation
Customer
52
Software Requirements
Software Coding
Verification
Verification
Verification
Verification
Unit Test
Integration Test
System Validation
Customer
53
Software Requirements
Software Coding
Verification
Verification
Verification
Verification
Unit Test
Integration Test
System Validation
Customer
54
User X Error
User Error Blames The User For Doing Something Wrong Use Error Developer takes accountability for developing software that allowed the user to make an error And..the developer incorporates Use Error Analysis into the risk management process resulting in the implementation of built-in safeguards to protect against Use Error
55
Skill Level Variation Environmental Variation Compromising Factors Physical and Sensory Characteristics Perception Cognition Expectancies Mental Models Home Use
56
Potential Harm To
Potential Harm To
Potential Harm To
Potential Harm To
Potential Harm To
Patients
Operators
Bystanders
Service Personnel
Environment
Use Errors
YES
You are developing a function where the user will be asked to manually enter a patients age You realize that if the age is entered incorrectly that an incorrect diagnosis might be made
57
Environment
Interfaces
Severity Major
59
60
Recall Statistics
Software Related Recalls
Initial (21%) Due To Changes (79%)
FDA Analysis 3140 Recalls (1992 1998) Software-related recalls 242 Software recalls due to changes 192 (79%)
Of those software related recalls, 192 (or 79%) were caused by software defects that were introduced when changes were made to the software after its initial production and distribution FDA Guidance (2002) General Principles of Software Validation
61
Maintenance Challenges
Oversimplification of the task Customer and Patient expectations Increased requirements on system Changes Design additions and/or modifications State of the documentation Knowledge level Personnel changes Software components (COTS) Hardware components Interfaces Cybersecurity issues Maintenance Challenges
62
Creating A Balance
Processes Requirements management Anomaly management Technology transition management Risk management Training Change control Software development life cycle Technical reviews Validation planning Testing Configuration management Documentation updates
63
Challenges Oversimplification of the task Customer and Patient expectations Increased requirements on system Changes Design additions and/or modifications State of the documentation Knowledge level Personnel changes Software components (COTS) Hardware components Interfaces Cybersecurity issues
64
Same Product Similar Problems? Investigate Find Root Cause Problem Encountered Correct The Problem Investigate Find Root Cause Correct The Problem
Other Products Similar Problems? Investigate Find Root Cause Correct The Problem
65
66
Do It By Design
ISO 62304
ISO 13485
67
ISO 62304
68
69
70
71
72
FDA Website
www.fda.gov
73
FDA Website
74
FDA Website
75
FDA Website
76
FDA Website
77
FDA Website
http://www.fda.gov/cdrh/humanfactors/
78
AAMI Website
www.aami.org
79
Procedures Medical Product Software Development and FDA Regulations Plans SW Life-Cycle Model SW Requirements Analysis SW Requirements Verification SW Architectural Design SW Architecture Verification SW Detailed Design
Medical Device Quality System Manual Design Control Guidance General Principles of Software Validation Software Pre-Market Submission Guidance Off-The-Shelf Software Guidance
Integration Test SW System Test Beta Testing SW Verification SW Validation COTS Software Components SW Risk/Hazard Analysis SW Human Factors (Use Errors) SW Change Control SW Configuration Management SW Problem Tracking & Resolution SW Traceability Non-Product Software Validation Corrective & Preventive Action (CAPA) Design Transfer Design History File Training Software Quality Audits 80
81
Software Requirements
Software Coding
Verification
Verification
Verification
Verification
Unit Test
Integration Test
System Validation
Customer
82
Its All About Making It Safe Your Families! - Your Loved Ones! - Your Friends! Each and Every One Of YOU!
Patients Environment
Operators
Bystanders
Service Personnel
83
References
[1] FDA (2002). General Principles of Software Validation; Final Guidance for Industry and FDA Staff. FDA website: http://www.fda.gov/cdrh/comp/guidance/938.pdf [2] Pietrasanta, Alfred M. (1990). Defect Prevention. Software Quality Improvement Module 9: Software Engineering Institute, Carnegie Mellon University.
85