The CDRH Software Message (October 19, 2002) John F Murray Jr.. Center for Devices & Radiological Health US Food and Drug Administration

Slides:



Advertisements
Similar presentations
The Role of the IRB An Institutional Review Board (IRB) is a review committee established to help protect the rights and welfare of human research subjects.
Advertisements

VALIDATION OF COMPUTERISED SYSTEMS IN THE PHARMACEUTICAL INDUSTRY Matt Safi Product manager.
"Determining the Regulatory Pathway to Market" Classification Heather S. Rosecrans Director, 510(k) Staff Office of Device Evaluation Center for Devices.
Subpart S - SEMS September 11, 2012 Prepared by: BSEE, Office of Safety Management Author: Jason Mathews.
Regulatory Compliant Performance Improvement for Pharmaceutical Plants AIChE New Jersey Section 01/13/2004 Murugan Govindasamy Pfizer Inc.
Introduction to Regulation
Becker Grand Rounds: Wally Pellerite June 30, 2011.
Columbia University IRB IRB 101 September 21, 2005 George Gasparis, Executive Director, CU IRB Asst. V.P. and Sr. Asst. Dean for Research Ethics.
Telemedicine Credentialing and Privileging October 16, 2014.
1. 2 This tool focuses on the CSBG requirements relating to tripartite board composition and selection and is divided into the following four parts: 1.General.
FDA’s Pharmaceutical Inspectorate Robert Coleman National Expert Drug Investigator Food and Drug Administration.
CDRH Software Regulation
Session 6: Data Integrity and Inspection of e-Clinical Computerized Systems May 15, 2011 | Beijing, China Kim Nitahara Principal Consultant and CEO META.
Animal Feed GRAS Notifications Geoffrey K. Wong, M.S. Division of Animal Feeds Center for Veterinary Medicine Pet Food Institute Pet Food Institute October.
Center for Devices and Radiological Health U. S. Department of Health and Human Services Al Taylor Acting Chief, Medical Electronics Branch Office of Science.
FDA Resources and Meetings FDA/EMA Orphan Designation and Grant Workshop Silver Spring, Maryland FDA Campus (White Oak) October 12, 2012 Bill Sutton Deputy.
21 CFR Part 11 A Food Industry Perspective FDA Public Meeting June 11, 2004 Sia Economides Center Director Center for Development of Research Policy and.
FDA Regulatory review in Minutes: What Product Development Executives Need-to-Know. Specifically, frequent causes of recalls and related areas that investigators.
Prof. Moustafa M. Mohamed Vice dean Faculty of Allied Medical Science Pharos University in Alexandria Development and Regulation of Medical Products (MEDR-101)
Physiologists & the FDA Kevin J. Greenlees, Ph.D., DABT Senior Advisor for Science & Policy Office of New Animal Drug Evaluation FDA Center for Veterinary.
The Medical Device Pathway as a Legal Onramp for Futuristic Persons THE FUTURE T HE M EDICAL D EVICE P ATHWAY AS A L EGAL.
Industry Perspective on Challenges for Product Developers - Drugs Christine Allison, M.S., RAC Associate Regulatory Consultant, Global Regulatory Affairs.
Top 10 Medical Device Citations
University of Miami Office of Research Compliance Assessment Lynn E. Smith, JD, CIM, CIP Johanna Stamates, RN, BA, CCRC With assistance from Elizabeth.
Compliance with FDA Regulations: Collecting, Transmitting and Managing Clinical Information Dan C Pettus Senior Vice President iMetrikus, Inc.
UNCLASSIFIED10/12/ :41 AM Slide 1 Division of Regulated Activities and Compliance.
March 28, 2006 Combination Products: Preparing for the Journey March 28, 2006 Pamela J. Weagraff Principal Consultant.
1 CONSENSUS STANDARDS OIVD WORKSHOP April 22-23, 2003 Rockville MD Ginette Y. Michaud, M.D. OIVD.
FDA Recommendations: Sampling Plans for Blood Establishments Lore Fields MT(ASCP)SBB Consumer Safety Officer OBRR/CBER/FDA October 19, 2012.
10/16/2015 Roles and Responsibilities of Principal Investigators/ Program Directors/ Project Directors.
1 PAT and Biological Products Tom Layloff FDA-SGE Management Sciences for Health The views expressed here are those of the author and not necessarily.
PATRICIA KERBY, MPA HUMAN SUBJECTIONS PROTECTION COMPLIANCE OFFICER OFFICE OF RESEARCH COMPLIANCE What are the FDA’s expectations in 2010?
Legal & Ethical Issues. Objectives At the completion of this session the participant will be able to: ◦ Describe the ethical principles associated with.
1 Regulatory Aspects of Pharmaceutical Excipients PQRI Workshop Nick Buhay Acting Director Division of Manufacturing and Product Quality Office of Compliance.
UC DAVIS OFFICE OF RESEARCH Overview of Good Clinical Practices (GCP) Investigator and Study Team Responsibilities Miles McFann IRB Administration Training.
FDA Public Meeting on Electronic Records and Signatures June 11, 2004 Presentation of the Industry Coalition on 21CFR Part 11 Alan Goldhammer, PhD Chair.
Part 11, Electronic Records; Electronic Signatures
Prof. Moustafa M. Mohamed Vice dean Faculty of Allied Medical Science Pharos University in Alexandria Development and Regulation of Medical Products (MEDR-101)
Rules for Supporting Part 803 and Part 806 Decision Making Page 1 Establishing Rules for: Medical Device Reports (803) & Correction and Removal Reports.
Expectations for Facilities & cGMPs Biological Response Modifiers Advisory Committee Meeting October 9, 2003 Nicholas Obiri, Ph.D. CBER.
FDA’s Policies, Procedures, and Systems: Effects on Provider and Information Technology Sectors Karen M. Becker, Ph.D. and Philip J. Phillips, MBA Becker.
Copyright FDA Inspections: Where Do Things Go Wrong? Diana Naser RN, MS, CCRP Executive Director Clinical Research Administration Clinical Research.
Module C FDA Regulations Regulatory Documents Patricia E. Koziol 1Module C Final Version 10-apr-2010.
REGULATION OF COMBINATION PRODUCTS Mark A. Heller Wilmer Cutler Pickering Hale and Dorr LLP MassMEDIC Combination Product Program, March 28, 2006.
Joel Gerber Zachary Reaver Kurt Schilling.  Provides physical proof of development  Maintains product design knowledge base  Meets government and corporate.
Center for Devices and Radiological Health U. S. Department of Health and Human Services Al Taylor Acting Chief, Medical Electronics Branch Office of Science.
1 Quality Initiatives in the Convenient Care Setting Sandra F. Ryan, MSN, CPNP Co-Chair, Convenient Care Association Clinical Advisory Board Chief Nurse.
1 Drug Safety Oversight Board: Recent Activities FDA Science Board Advisory Committee Meeting March 31 st, 2006 Douglas C. Throckmorton, MD Deputy Director.
INVESTIGATOR RESPONSIBILITIES C. Karen Jeans, MSN COACH Project Analyst.
Legal Responsibilities for Studies Conducted or Supported by HHS Michael A. Carome, M.D. Associate Director for Regulatory Affairs Office for Human Research.
Workshop on Accreditation of Bodies Certifying Medical Devices Kiev, November 2014.
Complaint Handling Medical Device Reporting May 19, 2016 Rita Harden, Director Customer Relations & Regulatory Reporting.
The Regulation on Cell Therapy Products in Japan
Clinical Trials Validation, 21 CFR Part 11 Compliance
Division of Cardiovascular Devices
Recent Evolution of New Drug Review and Approval System in Korea
נמטוציטים משושנת ים Eli. S Lec. No.2.
Beverley Alberola, CIP Associate Director, Research Protections
FDA’s IDE Decisions and Communications
How to Put Together an IDE Application
Reasonable Assurance of Safety and Effectiveness: An FDA Division of Cardiovascular Devices Perspective Bram Zuckerman, MD, FACC Director, FDA Division.
Clinical Engineering Lecture (3).
Medical Device Regulatory Essentials: An FDA Division of Cardiovascular Devices Perspective Bram Zuckerman, MD, FACC Director, FDA Division of Cardiovascular.
FDA-CDRH in the Next Decade A Vision for Change
To start the presentation, click on this button in the lower right corner of your screen. The presentation will begin after the screen changes and you.
General tripartite board composition and selection information
FDA 21 CFR Part 11 Overview June 10, 2006.
FDA Resources and Meetings
Making Your IRBs and Clinical Investigators HIPAA-Ready
Regulatory Perspective of the Use of EHRs in RCTs
Presentation transcript:

The CDRH Software Message (October 19, 2002) John F Murray Jr.. Center for Devices & Radiological Health US Food and Drug Administration

Mr. John F Murray Jr. Mr. Murray currently serves as the: –Software and Part 11 Compliance Expert –Office of Compliance –Center for Devices and Radiological Health (CDRH) –US Food and Drug Administration.

Mr. John F Murray Jr. In this position Mr. Murray is the primary advisor to the Director of the Office of Compliance in the areas of: –Software validation –Software policy –Software classification and –Part 11 compliance issues. He is also responsible for: –the software standards program and –the software engineering training program at CDRH.

Mr. John F Murray Jr. Mr. John F Murray Jr. joined the FDA in March Prior to becoming an FDA staffer, he was: –A qualified Reactor Operator with United States Navy Submarine Fleet –A Computer Field Engineer with Telex Computer Products –An Electronics and Software Engineer with The General Dynamics Corporation and a –Systems Engineer at Technology Management & Analysis

Mr. John F Murray Jr. Prior to joining the Office of Compliance in June 2001, Mr. Murray served as the Team Leader for Software and Intelligent Medical Devices with the United States Food and Drug Administration, Rockville, MD. Mr. Murray is the primary Advisor to the Chief of the Medical Electronics Branch in the areas of software engineering, software safety and software standards.

Mr. John F Murray Jr. The software team is responsible for: –Maintaining the technical foundations that are required for the regulation of medical device software. –Regulatory decisions regarding the safety and effectiveness of medical device software are based on engineering and scientific foundations. –Software Standards is one example of these engineering foundations.

Mr. John F Murray Jr. Mr. Murray is chairperson for the FDA Software Standards Technical Group (STG). –The Software STG is responsible for review and recognition of software engineering standards for use in the regulatory process. Mr. Murray also serves as Co-Chair of the AAMI Software Committee.

Mr. John F Murray Jr. Mr. Murray earned a: –BS Degree in Electrical Engineering from George Mason University –MS Degree in Computer Science from Rensselaer Polytechnic University (RPI).

The CDRH Software Message John F Murray Jr.. Center for Devices & Radiological Health US Food and Drug Administration

Public Health and Software The Quality of Pubic Health is highly dependent on the Quality of Medical Software i.e. Medical Device Software, Clinical Information Systems, Hospital Information Systems, Manufacturing Systems etc

What type of Quality do we Want? To get some perspective lets try what I call the YB scale. [yugo vs. bmw] I ask the following questions: Where would Microsoft be on this scale? Where do we want our software quality to be? Where do you want your software to be?

Do the regulations recognize this need Yes they do: 21 CFR CFR (a) (2) (i) 21 CFR (g) 21 CFR (i)

21 CFR Design Controls Each manufacturer of any Class II or Class III device, and the Class I devices listed in paragraph (a)(2) of this section, shall establish and maintain procedures to control the design of the device in order to ensure that the specified design requirements are meet.

21 CFR (a)(2)(i) Class I –The following Class I devices are subject to design controls: Devices automated with computer software

21 CFR (g) Design validation shall include software validation and risk analysis where appropriate

21 CFR (i) Automated processes –When computers or automated data processing systems are used as part of production or the quality system, the manufacturer shall validate computer software for its intended use according to an established protocol. All software changes shall be validated before approval and issuance. These validation activities shall be documented.

Software is Different Traditionally not engineered, but crafted Not physics based Easy to change or is it? Does not fail the hardware way. etc

What is the goal? By Law: Medical Devices must be reasonably safe and effective By default: Software must be safe and effective

Safe and Effective It depends! Cannot be easily defined What is safe and effective software –Software Engineering –Risk Management –Quality System

Conclusion The law and regulations are written in broad terms Software should be engineered using: –Software Engineering –Risk Management –Quality System This is the CDRH Software Message

Keys to Success Avoid denial Make a plan Document your activities Remember the three A’s of meeting the regulatory requirement –Activities –Attributes –Artifacts