의료용 S/W 기술문서 심사 방법 2007-03-30 원 찬 요 유엘 코리아 발표자 소개 -1998 년 2 월 한양대 전자공 졸업 -1987-11 ~ 1992-04: ㈜ 금성사 ( 현 LG 전자 ) 연구원 -1992-04 ~ 1999-06: ㈜ 메디슨 규격팀 팀장 -1999-07.

Slides:



Advertisements
Similar presentations
Medical Device Software Development
Advertisements

FDA Human Factors of Medical Devices
Testing Medical Devices A Brief Overview © 2005 Max Cortner. Copying and distribution of this document is permitted in any medium, provided this notice.
Requirements Specification and Management
System Integration Verification and Validation
Chapter 4 Quality Assurance in Context
Audit of IT Systems SARQA / DKG Scandinavian Conference, October 2002, Copenhagen Sue Gregory.
Agile and Medical Device Software
Prepared By: Certified Compliance Solutions, Inc. August 2012
CBER 1 Blood Establishment Computer Software (BECS) Michael Gorman, BA, MT(ASCP)SBB Consumer Safety Officer, CBER, OBRR, DBA September 15, 2009.
1 Systems V & V, Quality and Standards Dr Sita Ramakrishnan School CSSE Monash University.
User Documentation (no quiz) Tori Bowman CSSE 375 October 8 th, 2007.
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
The Waterfall Model A Case Study
Software Configuration Management (SCM)
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
1 Overview of Standards for External Defibrillators: Role of FDA Charles Ho, Ph.D. FDA/CDRH/ODE
CSE Senior Design II Test Planning Mike O’Dell Based on an earlier presentation by Mike O’Dell, UTA.
CDRH Software Regulation
Requirements for Premarket Submissions: In vitro Diagnostic Instrumentation and Software Related to Donor Screening and HIV Diagnostic Assay Systems Diane.
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Effective Methods for Software and Systems Integration
“Here’s why you need the new wheels, too…” Shawn and Steve Image from
Prof. Moustafa M. Mohamed Vice dean Faculty of Allied Medical Science Pharos University in Alexandria Development and Regulation of Medical Products (MEDR-101)
Software Configuration Management
S oftware Q uality A ssurance Part One Reviews and Inspections.
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
1 Configuration Management “The Cookbook Approach”
Asher Etkin DOE Accelerator Safety Workshop August , 2009 DRAFT DOE STANDARD APPLICATION OF SAFETY INSTRUMENTED SYSTEMS USED AT DOE NON-REACTOR.
Development and Regulation of Medical Products (MEDR-101)
Software Requirements Engineering CSE 305 Lecture-2.
Center for Devices and Radiological Health U. S. Department of Health and Human Services Surviving an FDA Audit Richard Chapman, FDA TwinSPIN University.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
BPA 1 Verification in the Development of Medical Device Software Per IEC Tim Stein, Ph.D. CEO and President of Business Performance Associates, Inc.
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.
11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.
Software Safety Case Why, what and how… Jon Arvid Børretzen.
Configuration Management for Digital Upgrades Configuration Management Benchmarking Group 2008 Conference Scott Patterson Program Manager for I&C Obsolescence.
Over View of CENELC Standards for Signalling Applications
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
The world leader in serving science Validation and Qualification Overview Mike Garry Software Product Manager Spectroscopy Software Platform Team.
Product development Engineering & Regulatory Raj Agrawal InnAccel.
Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…
T Project Review Muuntaja I1 Iteration
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
Workshop on Accreditation of Bodies Certifying Medical Devices Kiev, November 2014.
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
Digital Health Think Tank kick-off meeting June 14, 2016.
Medical Device Software Development
System Design, Implementation and Review
Software Specification and Configuration Management
Software Verification and Validation
Chapter 18 Maintaining Information Systems
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
Engineering Processes
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
Project Management Methodology Documentation Chart
יוסי שדמתי רק איכות מניהול סיכונים לאימות ותיקוף תהליכי הרכבה From Risk Management to Processes Validation יוסי.
PSS verification and validation
PSS0 Configuration Management,
Software Reviews.
Connected HealthCare.
Presentation transcript:

의료용 S/W 기술문서 심사 방법 원 찬 요 유엘 코리아

발표자 소개 년 2 월 한양대 전자공 졸업 ~ : ㈜ 금성사 ( 현 LG 전자 ) 연구원 ~ : ㈜ 메디슨 규격팀 팀장 ~ : 원텍시험소 안전규격실장 ~ : ㈜에이치엠티 프러덕트매니저 ~ 현재 : 유엘코리아, 의료기기사업부, 적합성평가부 * 현재업무 : FDA 510(k) 3 자기관, UL 마크 서비스 Reviewer, CE-Marking TCF Reviewer, CBTL Reviewer

개정안 – 의료기기 소프트웨어에 관한 자료 “ 당해 제품에 소프트웨어가 내장되어 있거나 단독으로 사용되는 소프트웨어인 경우, - 소프트웨어의 형명 또는 명칭, - 버전, - 알고리즘, - 구조, - 주요 기능 및 기능표시화면, - 개발 환경 및 사용환경, - 위험분석, - 검증 및 유효성확인 등의 내용이 포함된 자료 ”

FDA’s Guidance Documents  Guidance for the content of premarket submissions for software contained in medical devices  Guidance for industry, general principles of software validation  Guidance for off-the-shelf software use in medical devices  Design control guidance for medical device manufacturers

소프트웨어와 품질시스템  유럽  미국 IEC FDA’s Reviewers Guidance’s Quality System Regulation ISO SAFE MEDICAL DEVICES ACT MEDICAL DEVICES DIRECTIVE ONE SET OF DOCUMENTS ISO 13485

적용범위  “ 당해 제품에 소프트웨어가 내장되어 있는 의료기기 ”  “ 단독으로 사용되는 소프트웨어 ”

Scope – “Software Device”  Firmware 및 의료기기의 소프트웨어 기반의 control 를 위한 기타 수단  독립적 (Stand-alone) 으로 사용되는 소프트웨어  일반 컴퓨터에 설치 (installation) 하여 사용할 수 있도록 설계된 소프트웨어  의료용 하드웨어 / 소프트웨어 기기  의료기기의 부속품 (accessory). 단, 부속품이 소프트웨어를 포함하거나 소프트웨어로 구성되어 있는 경우. “factory-installed”, installed by a third party vendor, or “field installed (by user)” Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Scope – Exclusion  제조 혹은 공정 관리 기능을 위해 설계된 소프트웨어  GMP – “ 설계에서의 밸리데이션 (validation)” – “ 공정에서의 밸리데이션 (validation)” Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

FDA Consensus Standard  ISO ; Medical devices – Risk Management – Part 1: Application of risk analysis  AAMI SW68:2001; Medical device software – Software life cycle processes (Ref. IEC 62304) Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

소프트웨어에 관한 자료 소소프트웨어의 형명 또는 명칭, 버버전 (Version, Revision History), 알알고리즘 (Algorithm in SRS), 구구조 (Architecture), 주주요 기능 및 기능표시화면 (SRS), 개개발 환경 및 사용환경 (Software Development Environment), 위위험분석 ( 위험요인분석 – Device Hazard Analysis), 검검증 및 유효성확인 (Verification & Validation)

FDA Software Documentation LL evel of Concern SS oftware Description DD evice Hazard Analysis SS oftware Requirement Specification (SRS) AA rchitecture Design – Software Architecture Specification (SAS) SS oftware Design Specification (SDS) TT raceability Analysis SS oftware Development Life-Cycle VV erification and Validation (V & V) Documentation RR evision History UU nresolved Anomalies (Bugs or Defects) Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Level of Concern - Severity  Minor / Moderate / Major  Questionnaires - Rationale – Blood Establishment Computer Software – With Drug or Biologic – Accessory to Medical Device of (Major / Moderate) Level of Concern – Death or Serious Injury / Minor Injury Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Software Description  Summary Overview of the features ( 개요 )  Software Operating Environment ( 운영환경 ) – Programming Language – Hardware Platform – Operating System (if applicable) – Use of Off-the-Self Software (if applicable) Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Device Hazard Analysis  ISO , Risk Management Summary  Hazards associated with device’s intended use, hardware & software. – Identification of Hazards ( 위험요인식별 ) – Severity of Hazards ( 심각도분석 ) – Cause of Hazards ( 원인분석 ) – Method of Control ( 통제방법 ) – Corrective Measures ( 위험경감 조치사항 ) – Validation ( 최종 확인 ) Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

SRS – Requirement Spec.  Hardware Requirements  Programming Language Requirements  Interface Requirements  Software Performance & Functional Requirements Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

SRS - Hardware  Microprocessor  Memory device  Sensor  Energy Source  Safety Feature  Communication Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

SRS – Programming Language  Program Size  Information on management of memory leaks Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

SRS - Interface  Printer  Monitor  Keyboard  Mouse Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

SRS – Performance & Function  Algorithm or Characteristics  Performance and Functional Requirements – Device limitation due to software – Internal software tests and checks – Error and Interrupt handling – Fault detection, tolerance, and recovery characteristics – Safety requirements – Timing and memory requirements – Identification of off-the-shelf software (if applicable) Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Architecture  Flow chart or similar, showing: – Relationships among the major functional units in the “Software Device” – Relationships to hardware and to data flows such as networking  Maybe included in the SRS. Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

SDS – Design Spec.  Implementation & Details of SRS – Software Design Description (SDD), Functional Specification – SRS: What the Software Device will do – SDS: How the SRS are implemented Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Traceability  Matrix showing: – Requirements – Specifications – Tests – Hazard Mitigation Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Development Life-Cycle  Summary of Development Life-Cycle Plan – Defined Development Life-Cycle – Processes and Activities – Document List – Software Coding Standard (for Code Review)  Configuration (or Change) Management & Maintenance Plan – Definitive specifications – Life-Cycle – Test Plan Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

V & V Documents  V & V activities (lists) during Development Life-Cycle  System (Functional) Test (for minor/moderate level) Plan & Results  Unit / Integration / System Test (for major level) Plan & Results Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Revision Level History  Revision History – Date – Version No. – Brief Description  Version No. System Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Unsolved Bugs  For each anomaly: – Problem – Impact on device performance – Corrective Action Plan or Timeframe Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

Required Documents vs. Level of Concern  Documentation Based on Level of Concern DocumentationMinorModerateMajor Level of ConcernStatement & Rationale Software DescriptionOverview & Operating Environment Hazard AnalysisRisk Management Summary SRSSummary of Functions Complete SRS ArchitectureNoFunctional Units & Software Modules SDSNoSDS TraceabilityTraceability Analysis / Relationship Software Development Life-Cycle NoLife-Cycle (Summary of Configuration Management / Maintenance) Life-Cycle (Document list for each process, Coding Standard) (Plan of Configuration Management / Maintenance) V & V Function test V & V activities. System Level test V & V activities. Unit/Integration/System Level test Revision HistoryRevision Log & Release Version No. Unsolved BugsNoBugs or Defects / Explanation

Turn out the Lights The party’s over