With new technologies come many innovative medical devices and tools to help treat patients and to improve their quality of life thru diagnosis, monitoring and therapy. New fields of study within Engineering are emerging throughout the academic community to better understand and improve these devices and tools. As a Systems Engineer what are we doing in this application that’s different from others? What are the challenges? What do we need to improve on? And Why?
This presentation provides an overview of the different types of Medical Devices and addresses the associated implications that affect the system under design. An example of a specific Medical Device will be presented along with a description of how the system integrates with Biological component. Systems Engineering Process comparison between Medical Device industry and Defense industry where Systems Engineering was conceived has been integrated throughout this presentation. You will learn more about some of the challenges that Medical Devices industry is facing and potential Systems Engineering solutions with specific approach and methodology.
11. Compare & Contrast
Defense Medical Device
1962 - Publication of “A Methodology for 1978 - 21 CFR part 820 became
Maturity Systems Engineering” effective; required Current Good
1969 - MIL-STD-499; began to mandate SE Manufacturing Practices (CGMP)
practices 1996 - 21 CFR part 820 added
1990 - NCOSE Design Control and ISO 9001
1995 - INCOSE concepts; including requirements
and verification/validation but not
1998 - EIA 632 released (based on MIL- a complete SE process
STD-499B which was never released)
1996 - ISO 13485 Quality
1999 - IEEE-1220 Management Systems for
2002 - ISO/IEC 15288 Designing and Manufacturing
SE viewed as Medical Devices
* The architect
* The requirements engineer SE viewed as
* Interface engineer * Requirements engineer
* System Integrator * Ad-hoc troubleshooting
* The system verification & qualification * Verification & Validation
planner and tester … * Facilitator
11
11
12. Compare & Contrast
Defense Medical Device
SoS with capabilities based on Systems focus on the intra-
Complexity interoperability between operability
Satellites, Aircrafts, Land
Vehicles, Ships, C4ISR
- DoD - Regulatory Affairs (worldwide)
Stakeholders - External systems - Medical Core Team member
- User with formal training - User (IVD, RUO, Expert,
Novices) with preferences (Lab
Workflow, Individual, Local)
- Biologists
12
13. Compare & Contrast
Defense Medical Device
- Normal Operation - Research Use Only (RUO)
Operation - Training - In-Vitro Diagnostics (IVD)
Modes - Diagnostics - Training
- Diagnostics
- System to System I/F (ICD) - Limited control of end user
Intended Use - User workflow SOP - For Invasive Device (i.e.
pacemaker) the intended use
is specific
- ConOps - Meetings with SME
Requirement - Formal analysis (UC, Causal - No abstraction control
analysis) - Ad-Hoc approach
- Interfaces - Requirement is complete
- Clear levels of abstraction when time is up
- ilities
13
14. Compare & Contrast
Defense Medical Device
- System level - Functional organization at system
Architecture - Subsystem level level
- Architecture at a subsystem level is
more formal
- BIT (SBIT, PBIT, IBIT) - Manual Troubleshooting notes
Standard - Self diagnostics & Recovery - Manual Replaceable parts
functions - Redundancy capabilities
- Component shelf life tracking
- Field Service Engineering
- Status log - For invasive devices such as
pacemaker there would be more
built-in capabilities such as
redundancy, PBIT, …
- Budget - Hazard to user & patient
Risk - Technical
- Schedule
14
15. Compare & Contrast
Defense Medical Device
- Integration Plan/Strategy - Exploratory Testing
Integration - Independent integration platform - Manage system test configurations
- IRS, ICD, N2 diagram - Coordinate daily standup meeting
between subsystems
- Incremental integration leads to - System performance verification
Verification final test and verification focuses more on application
- Design for verification protocols
- Verification Platform (test set) - Device level of verification is
- First Article Inspection mostly done by subsystem test
- System qualification/validation - Validation Plan
Validation - Simulating customer scenarios -
Determine a go or no-go of the
product release
- Validation reports
15
17. Challenges
Intensive Care Unit
Bed Side Monitoring IV Pumps
Ventilator Brain Monitoring
17
18. What To Do?
• Improve Systems Engineering process
(INCOSE Systems Engineering Handbook)
• System of Systems approach
• MBSE (Model Based Systems Engineering)
18
19. Conclusions
• SE in Medical Device Industry is not as
elaborate as in Defense Industry, however,
focus is on product safety
• Different types of Medical Devices demand
different levels of SE practices
• Improving SE process in the Medical Device
industry will optimize the following
– Efficiency of product development
– Usability
– Flexibility
19