US & CANADA: REGULATION AND GUIDELINES ON MEDICAL SOFTWARE AND APPS OR



Similar documents
Final Document. Software as a Medical Device (SaMD): Key Definitions. Date: 9 December Despina Spanou, IMDRF Chair. IMDRF/SaMD WG/N10FINAL:2013

Medical Software Development. International standards requirements and practice

How To Know If A Mobile App Is A Medical Device

CDRH Regulated Software Looking back, looking forward

The Shifting Sands of Medical Software Regulation

CDRH Regulated Software

Regulatory Considerations for Medical Device Software. Medical Device Software

MEDICAL DEVICES INTERIM REGULATION

Medical Device Software: Establishing FDA Authority and Mobile Medical Apps

Medical Device Software

Mobile Medical Application Development: FDA Regulation

CENTER FOR CONNECTED HEALTH POLICY

Regulation of Mobile Medical Apps

An introduction to the regulation of apps and wearables as medical devices

Medical Device Data Systems, Medical Image Storage Devices, and Medical Image Communications Devices

Mobile Medical Applications: FDA s Final Guidance. M. Elizabeth Bierman Anthony T. Pavel Morgan, Lewis & Bockius, LLP

Safeguarding public health The Regulation of Software as a Medical Device

International Medical Device Regulators Forum (IMDRF) US FDA Center for Devices and Radiological Health - Update

Considerations for using the Web for Medical Device Applications

Developing a Mobile Medical App? How to determine if it is a medical device and get it cleared by the US FDA

Rethinking the FDA s Regulation of. By Scott D. Danzis and Christopher Pruitt

Medical Certification: Bringing genomic microcores to clinical use OI- VF- WP- 011

REFERENCE DOCUMENT. (DRAFT for Public Comments) Title: White Paper on Medical Device Software Regulation Software Qualification and Classification

FDA Issues Final Guidance on Mobile Medical Apps

EU Law and Life Sciences Mobile Health Apps. Webinar - Brussels, 9 July 2014

What is a medical device? Medical Devices: Roadmap to Market. Kathryn Klaus, Esq.

The U.S. FDA s Regulation and Oversight of Mobile Medical Applications

Correspondence between ISO 13485:2003 and the US Quality System Regulation

CE Marking: Your Key to Entering the European Market

Section 5: Quality Systems Regulation (QSR) and Good Manufacturing Practice (GMP)

Medical Product Software Development and FDA Regulations Software Development Practices and FDA Compliance

Mobile Medical Applications

Breakout Sessions: FDA s Regulation of Mobile Health and Medical Applications

Use of Mobile Medical Applications in Clinical Research

Combination Products Regulation in the United States

FDA Regulation of Whole Slide Imaging (WSI) Devices: Current Thoughts

Mobile Medical Applications: An Overview of FDA Regulation

Health Informatics Application of clinical risk management to the manufacture of health software Formerly ISO/TS 29321:2008(E) DSCN14/2009

Development and Validation of In Vitro Diagnostic Tests. YC Lee, Ph.D. CEO

GUIDANCE NOTE FOR MANUFACTURERS OF CUSTOM-MADE MEDICAL DEVICES

Risk based 12/1/2015. Digital Health Bakul Patel Associate Director for Digital Health Office of Center Director.

GUIDANCE NOTES FOR MANUFACTURERS OF CLASS I MEDICAL DEVICES

Med-Info. Council Directive 93/42/EEC on Medical Devices. TÜV SÜD Product Service GmbH

Quality Management Systems Manual

Navigating the New EU Rules for Medical Device Software

Guide for Custom-Made Dental Device Manufacturers on Compliance with European Communities (Medical Devices) Regulations, 1994

Medical Device Regulatory Requirements for Taiwan

UNDERSTANDING THE EC DIRECTIVE 98/79/EC ON IN VITRO DIAGNOSTIC MEDICAL DEVICES

Implementation of ANSI/AAMI/IEC Medical Device Software Lifecycle Processes.

How To Regulate A Medical Device From A Cell Phone

Understanding Medical Device Regulation for mhealth A Guide for Mobile Operators

Information Sheet Guidance For IRBs, Clinical Investigators, and Sponsors

Medical Devices: CE Marking Step-by Step

Medical Software Quality: Ensuring Correctness in the Clinical Environment

QMS for Software as a Medical Device [SaMD] Lessons Learned from a Quality Perspective

Thomas Conroy, RPh., J.D. Director, Promotion Compliance Global Regulatory Affairs MARCH 11, 2015

2002 No. 618 CONSUMER PROTECTION. The Medical Devices Regulations 2002

[DOCKET NO.96N-0002] DRAFT

2.0 Rationale, Purpose and Scope Definitions General Principles... 7

a Medical Device Privacy Consortium White Paper

WHITEPAPER: SOFTWARE APPS AS MEDICAL DEVICES THE REGULATORY LANDSCAPE

Security of Medical Device Applications

Sarah Chandler A/Head, Regulatory and Scientific Section Medical Devices Bureau

PMAs, 510(k)s, and Advanced IDE Topics

Medical Technologies Evaluation Programme Methods guide

General Wellness: Policy for Low Risk Devices. Draft Guidance for Industry and Food and Drug Administration Staff

Topic Priority Setting for research on patient safety Operational Definitions

GOOD DISTRIBUTION PRACTICE FOR MEDICAL DEVICES (GDPMD)

Draft Guidance for Industry, Food and Drug Administration Staff, and Clinical Laboratories

AUSTRALIAN REGULATORY GUIDELINES FOR MEDICAL DEVICES

EU and US regulation of health information technology, software and mobile apps

How To Write Software

Unit/Standard Number. Proficiency Level Achieved: (X) Indicates Competency Achieved to Industry Proficiency Level

PROPOSED DOCUMENT. Global Harmonization Task Force. Title: Principles of In Vitro Diagnostic (IVD) Medical Devices Classification

Glossary of terms used in our standards. June Upholding standards and public trust in pharmacy

The New Paradigm for Medical Device Safety. Addressing the Requirements of IEC Edition 3.1

The Medical Device Industry in Korea: Strategies for Market Entry

MOBILE MEDICAL APPLICATIONS

Unique Device Identification Update FDA and GHTF

2014 Annual Report on Inspections of Establishments

Templates. FDA Mobile Medical App Regulations. Your own sub headline This is an example text. Your Logo

Medical Device Software Do You Understand How Software is Regulated?

Regulatory Strategy for Drug-Device Combinations By John Worroll

Mobile Medical Applications. Guidance for Industry and Food and Drug Administration Staff

Guidance on the In Vitro Diagnostic Medical Devices Directive 98/79/EC

AND. CE IT Community Town Hall Meeting Feb. 8, 2012

EVALUATION OF AUTOMATIC CLASS III DESIGNATION FOR STUDIO on the Cloud Data Management Software DECISION SUMMARY

Medical Device Directive 2007/47/EC What is New? Are we moving towards Drug Rules?

Transcription:

US & CANADA: REGULATION AND GUIDELINES ON MEDICAL SOFTWARE AND APPS OR A MEDICAL DEVICE IS A MEDICAL DEVICE IS A MEDICAL DEVICE AHWP Medical SW Workshop Taipei, Taiwan November 3, 2012 John G. Abbott, Ph.D. Presented by Peter Linders

Overview 2

WHERE IS SW USED WITH MEDICAL DEVICES? 3

Software can be a component, part or accessory of a medical device; itself a medical device; used in the production or development of a medical device; used in a manufacturer s Quality System (QS).

WHAT MAKES SOMETHING A MEDICAL DEVICE? 5

What makes an item a medical device? There are many definitions of a medical device around the world. They are all very similar They all have common attributes In some jurisdictions, there are kinds of medical devices, each with their own law or regulation Active Implantable Medical Device In Vitro Diagnostic Medical Device (other) Medical Device The GHTF has created a consensus definition of a medical device (Global Harmonization Task Force) http://www.ghtf.org/

The GHTF definition: any instrument, apparatus, implement, machine, appliance, implant, in vitro reagent or calibrator, software, material or other similar or related article, intended by the MANUFACTURER to be used, alone or in combination, for human beings for one or more of the specific purpose(s) of diagnosis, prevention, monitoring, treatment or alleviation of disease, diagnosis, treatment, alleviation of or compensation for an injury, investigation, replacement, modification, or support of the anatomy or of a physiological process, supporting or sustaining life, control of conception, disinfection of medical devices, providing information for medical purposes by means of in vitro examination of specimens derived from the human body, and which does not achieve its primary intended action in or on the human body by pharmacological, immunological or metabolic means, but which may be assisted in its function by such means.

Key elements Intended by the MANUFACTURER The objective intent of the manufacturer as indicated in the labelling Labelling includes advertising and oral presentations by sales people as well IFU or Technical Data sheets. Example: hammer The intent of the manufacturer (as labelled) can turn a general purpose device into a medical device

Key elements: for one or more of the specific purpose(s) of diagnosis or monitoring of disease or injury What is the labelled purpose of the item? Is it intended to be used to diagnose or monitor patient(s) regarding disease or injury? Examples: hose adaptor HL7 protocol converter versus network switch clinical information software clinical decision support software electronic health record software

A quick summary: Software intended by the MANUFACTURER for one or more of the specific purpose(s) of diagnosis or monitoring of disease or injury What is the labelled purpose of the software? Is the software intended to be used to diagnose or monitor? patient(s) regarding disease or injury? Is the software an accessory to a medical device? Accessories can be treated as part of medical device, or Accessories can be treated as medical devices in their own right Is the software transforming existing information or creating new information about a patient?

HEALTH CANADA 11

Health Canada Canada explicitly recognizes that software can be a medical device http://www.hc-sc.gc.ca/dhp-mps/md-im/activit/announceannonce/md_notice_software_im_avis_logicels-eng.php Canada has released and is enforcing their new guidance document It clearly indicates that they consider it possible for software to be a medical device It classifies these devices based on their classification rules Class II Software required a license by 2011-09 and Class I software by 2011-02

Health Canada Any patient management software used only for storing, acquiring, transferring or viewing data, or images is considered a Class I medical device Any patient management software with capabilities beyond basic data visualization, acquisition, transfer and storage is considered a Class II medical device includes any patient management software involved in data manipulation, data analysis, data editing, image generation, determination of measurements, graphing, flagging of results, identifying a region of interest or performing calculations (if the software performing calculations directly impacts diagnosis and/or treatment of a patient) Free and Open-Source Software (FOSS) that is used for patient management is subject to the same regulatory requirements

UNITED STATES (FDA) 14

US FDA Standalone software can be not a medical device (not within the FDA s jurisdiction) a device for which FDA exercises enforcement discretion classified as class I (general controls), i.e. typically no 510(k) classified as class II (special controls in addition to general controls ), i.e. typically 510(k) classified as class III (premarket approval), i.e. PMA Examples include: central stations, PACS, clinical information, electronic health record, decision support, various protocol converters e.g. HL7 translators

US FDA Guidances Software guidances 0938 (2005) - General Principles of Software Validation; Final Guidance for Industry and FDA Staff Replacement expected soon FDA recently Recognized the IEC 62304 lifecycle process standard 0585 (1999) - Off-The-Shelf Software Use in Medical Devices Replacement expected soon 1741 (2011) - draft Mobile Medical Applications 0337 (2005) - Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices product classifications that apply to software medical devices LIS (lab information systems) PACS (picture archiving systems) MDDS (medical device data systems)

US FDA: MDDS The new MDDS final classification regulation: Class I, 510(k) exempt Many such devices were previous Class III (needed PMA) Not just limited to software, but most MDDS are software devices Is a device that is intended to provide one or more of the following uses and function, without controlling or altering the functions or parameters of any connected medical device An MDDS is not intended to be used in connection with active patient monitoring

SUMMARY 18

Summary No special regulatory process for Software as a Medical Device A Medical Device is a Medical Device Guidances are available Standalone software can be a medical device in Canada & the US and can have any classification Software can be a component of a medical device To be a medical device, software must do something as intended by its manufacturer be for the purpose of diagnosis or monitoring of disease or injury

One last note To new developers of software that is a medical device: Welcome to the wonderful world of medical device regulation

Thank you 21