November 17, 2004Planning Meeting for HCMDSS Workshop Breakout Session 2(II): Development Summary W. Rance Cleaveland II, PhD CEO, Reactive Systems Inc. -and- Dept. of Comp. Sci., SUNY at Stony Brook

Breakout Session Participants Facilitator:Doug Schmidt Recorder:Rance Cleaveland Group members:Lutz Andersohn Mike Blomquist Kevin Cleary David Forslund Edmond Israelski Mark Jones Peter Kazanzides Sohan Ranjan Steve Van Albert John Zaleski

Session Remit “We ask this breakout to discuss current practice and improvements in available technologies and approaches needed for high-confidence system and software development. What are the challenges in developing highly reliable software for medical devices and systems, yet achieving reasonable time-to-market and profitability? For the spring meeting, what questions should we be asking, and who should be participating in the discussion? For example: How might end products of development steps need to include information for certification or V&V that can enable this? How solid is the current technology base upon which medical devices and systems are built (e.g., real-time operating systems and networking technologies)? What are the security issues? Are reusable IT technologies (e.g., middleware, frameworks) in use? Is system code generated from mathematical control design frameworks such as MatLab and Simulink? How do critical decision support and highly-automated systems become trusted?”

Challenges and Opportunities  Validation / testing costs  Certification costs  Distribution and data sharing  Design technology  Automated process support  Open source

Existing Solutions  V&V costs: use-cases, manual testing  Certification: certification-centered processes, attention to certification issues up-front  Distribution: Syngo, reference architectures  Design technology: simulation (for GUIs), user-centered design, rapid iteration  Automated process support: Rational  Open source: Linux, ACE/TAO

Research and Development Needs (I)  Testing costs Automated test generation from use cases Better patient models (for high-fidelity simulation on the bench rather than in the lab)  Certification Classification of medical-device software according to verification needs (assessment / alerting / treatment) Reference models for device architectures

Research and Development Needs (II)  Distribution and data sharing Network QoS Patient / device authentication protocols Network trouble-shooting tools Secure data sharing for remote devices Side-effect reasoning  Design technology Techniques for mathematical analysis of specification completeness, consistency High-fidelity simulation support Standardized modeling languages (cf. VHDL for hardware design)

Research and Development Needs (III)  Automated process support Knowledge bases (remembering what we used to know, “software paperclip”) Cost estimation models for requirements changes Reference standard processes  Open source Open-source modeling tools Role of open-source tools in software development Third-party certification for FDA compliance

Logistics To Meet Needs  Consortia for standards  Tech-transfer vehicles for software technology  Funding!

Roadmap  Processes vis a vis tools (both important)  Standards issues addressable by govt., industrial consortia  “Co-operate on platforms, compete on devices”

Recommendations for Full Workshop  Invite representation from Professional organizations INCOSE, IEEE, AdviMed, AAMI, OMG Tool vendors IBM, National Instruments, MathWorks Other device makers (implantable, etc.) Medtronic, Guidant, GE Other industries Auto, aero, telecom  Experience reports on Current practices in device software Certification  Overview of FDA certification processes (maybe from FDA compliance side?)