This document summarizes key information from a seminar on getting medical devices approved by the FDA. It discusses common reasons why companies fail FDA approval, including inadequate software documentation. The document outlines FDA guidance and standards for software documentation, design, validation, and human factors. It also discusses FDA concerns about cybersecurity for networked devices and provides an overview of FDA guidance on managing cybersecurity risks.
9. Software‐related Documentation
Overview
Describe the design of your device
Document how your design was implemented
Demonstrate how the device produced by your design
implementation was tested
Show that you identified hazards appropriately and
managed risks effectively
Provide traceability to link together design,
implementation, testing, and risk management
8
14. Software Verification and Validation (V&V)
MINOR LOC:
System or device level testing, any integration testing
Pass/fail criteria
Summary of test results
MODERATE LOC:
V&V activities at the unit, integration, and system level
Summary list of V&V activities
Pass/fail criteria
Test results
MAJOR LOC:
V&V activities at the unit, integration, and system level
Unit, integration and system‐level test protocols
Pass/fail criteria
Test report, summary, test results
13
21. 2011 Draft Human Factors Guidance
FDA’s best thinking regarding:
Device Users, Use Environments and User Interfaces
Use‐Related Hazard Analytical Methods
Formative Evaluations
Mitigation and Control of Use‐Related Hazards
Design Verification Testing
Human Factors Validation
20
“Use error caused by designs that are either overly complex or contrary
to users' intuitive expectations for operation is one of the most
persistent and critical problems encountered by FDA.”
‐ General Principles of Software Validation, Final Guidance for Industry and FDA Staff (2002)
62. 2
mentor.com/embedded
2
Trends for Mixed Criticality
Needed to meet stringent non-functional requirements
— Cost
— Space
— Weight
— Heat generation
— Power consumption
Issues
— Partitioning for safety assurance
— Sharing for efficient resource usage
— Hard Tasks must be guaranteed
— Soft Tasks given best possible service
— Must ensure the behavior of low criticality components does not
adversely impact the behavior of higher criticality components
63. 3
mentor.com/embedded
3
Memory Protected
Memory
Protected
Memory
Protected
Memory
Protected
Nucleus Processes
Memory Protected Modules
— Prevents sub-systems
from bringing down the
system
— No Virtual Addressing
Multiple Types
— Applications
— Libraries
— Hybrids
Integrated with Sourcery
CodeBench
— Build projects via wizards
— Debug / load modules
— Profile module execution
File
Systems
Peripheral
Bus Drives
GUINetworking
Power Aware Kernel
StorageLCD
Ethernet/
Wireless
Devices
Memory
Protected
Application 1
Task 1
Task 2
…
Task n
Library 1
Function 1
Function 2
…
Function n
Hybrid 1
Task 1
Function 1
…
Task n
Function n
Application 2
Task 1
Task 2
…
Task n
67. 7
mentor.com/embedded
77
Mentor Embedded
United States
Canada
United Kingdom
Ireland
Netherlands
Germany
Denmark
Sweden
Finland
Poland
Armenia
Russia China
Japan
Korea
Taiwan
Australia
Singapore
India
Pakistan
Israel
Egypt
Hungary
ItalyAustria
Switzerland
Spain
France
Brazil
400+ engineers
50+ engineers in lead OSS community roles
10,000+ accepted OSS changes
Deployed in 3 Billion+ devices
20,000+ Sourcery CodeBench users
“Since 1996, Mentor Graphics has been the only EDA vendor with a broad product line of
embedded tools and software IP. Integrating our software and hardware expertise more
readily enables our customers to deal with the challenges of today’s multicore and power
management complexities.”
Walden Rhines, CEO