Corey Beth Monarch Lindsey Novak Michael Seikel Whitney Young

Slides:



Advertisements
Similar presentations
Building a Cradle-to-Grave Approach with Your Design Documentation and Data Denise D. Dion, EduQuest, Inc. and Gina To, Breathe Technologies, Inc.
Advertisements

PRINCIPLES OF A CALIBRATION MANAGEMENT SYSTEM
Medical Device Software Development
Radiopharmaceutical Production
Regulatory Auditing. Audit Areas Management Responsibility Auditing (internal and external) Design Control Document Control Purchasing Control Identification.
Product Documentation Chapter 5. Title 21 of the Code of Federal Regulations  Volume 1: Parts 1-99 (FDA, General)  Volume 2: Parts (FDA, Food.
ISO 9001:2000 Documentation Requirements
Validation, Verification, Qualification : Which is right and does it really matter?
Corrective & Preventive Action Programme l Corrective and preventive action managed by one programme l Closely linked to the internal audit programme l.
Combining Product Risk Management & Design Controls
Quality Management System
Pre-Market and the QSR Presented by: Dawn Fernandes.
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
External Defibrillators: Recalls, Inspections, and the Quality System Regulation Melissa Torres Office of Compliance December 15, 2010.
ISO 9000 Certification ISO 9001 and ISO
Huzairy Hassan School of Bioprocess Engineering UniMAP.
BRC Food Safety Quality Management System Training Guide
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Regulatory Overview.
MethodGXP The Solution for the Confusion.
Introduction to ISO New and modified requirements.
Rocky Mountain RAPS Process Validation Presentation 6/7/06 By Clay Anselmo.
FDA Regulatory review in Minutes: What Product Development Executives Need-to-Know. Specifically, frequent causes of recalls and related areas that investigators.
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
Software Configuration Management (SCM)
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Important informations
Paul Hardiman and Rob Brown SMMT IF Planning and organising an audit.
This class cannot be shared or copied without the written permission of PracticeWorks Systems, LLC.
Prof. Moustafa M. Mohamed Vice dean Faculty of Allied Medical Science Pharos University in Alexandria Development and Regulation of Medical Products (MEDR-101)
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Design Documentation Clint Kehres, Brian Krouse, Jenn Shafner.
Joel Gerber Zachary Reaver Kurt Schilling.  Provides physical proof of development  Maintains product design knowledge base  Meets government and corporate.
Implementation & Maintenance of a LM Control Program.
The Second Annual Medical Device Regulatory, Reimbursement and Compliance Congress Presented by J. Glenn George Thursday, March 29, 2007 Day II – Track.
Joe Selva Rohan Thakkar Jean Valderrama.  “Documentation” is what’s written on paper  Provides written details, events, and information about a particular.
WORKSHOP ON ACCREDITATION OF BODIES CERTIFYING MEDICAL DEVICES INT MARKET TOPIC 9 CH 8 ISO MEASUREMENT, ANALYSIS AND IMPROVEMENT INTERNAL AUDITS.
Workshop on Accreditation of Bodies Certifying Medical Devices Kiev, November 2014.
MANAGEMENT INFORMATION SYSTEM
Process engineering Quality controls.
Medical Device Software Development
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
BSB Biomanufacturing CHAPTER 4 GMP – Documentation Part I (SOP)
GOOD MANUFACTURING PRACTICE FOR BIOPROCESS ENGINEERING (ERT 425)
World Health Organization
Software Quality Control and Quality Assurance: Introduction
Raechel Huebner Ruthanne Sherer
Prepared by Rand E Winters, Jr. ASR Senior Auditor October 2014
FMEA.
Fundamentals of ISO.
Software Requirements
DSQR Training Control Plans
Air Carrier Continuing Analysis and Surveillance System (CASS)
Quality Management Systems – Requirements
ISO 9001 Awareness Training.
Engineering Processes
APQP PROCESS FLOW Prepare for APQP Plan and Define Program
FDA Quality System Regulation
Medical Device Design and Development
Advanced Product Quality Planning 2nd Edition
AS 9100 Awareness Training.
Engineering Processes
SDLC Phases Systems Design.
Advanced Product Quality Planning 2nd Edition
Managing Project Work, Scope, Schedules, and Cost
DOE Review of the LCLS Project October 2006
Software Reviews.
Computer System Validation
Radiopharmaceutical Production
Presentation transcript:

Corey Beth Monarch Lindsey Novak Michael Seikel Whitney Young Design Documentation Corey Beth Monarch Lindsey Novak Michael Seikel Whitney Young

Importance of Design Documentation Creates paper trail tracing design development Maintains product design knowledge base Meets governing body requirement Communicates design planning and implementation

What needs to be documented? General Meeting minutes Phone calls E-mails Technical Preliminary design sketches CAD drawings Tolerance stack-ups Testing -All meetings need to be documented – whether in-house development meetings, surgeon meetings, or meetings with government officials. Everything needs to be traced!

Minimum Necessities of Documentation Date and time Parties present Discussion items Action items Date & Time – self explanatory Parties present – A list of the people who attended the meeting, and a list of absentees who were supposed to attend Discussion items – A list of everything discussed pertaining to the project Action items – A list of activities discussed that need to be completed for the project to proceed

Good Documentation Practices http://www.youtube.com/watch?v=Q7bnVkshW Rc http://ezinearticles.com/?Learning-Good- Documentation-Practices&id=2071847

Documentation Methods and Examples Engineering Notebooks Preliminary sketches Meeting discussions Concept developments and ideas Microsoft Word and Excel documents Memorandums Analyses E-mail messages Design development discussions

Important Design Documents Drawings Design Changes Design and Process Validations/Verifications Risk Management Documentation Process Routers Inspection Criteria Design Control Plans Material Specifications Sterility and Cleaning Process Verifications Tolerance Stack-ups Device Master Record (DMR) FDA Submissions List of examples of design documents that are needed by governing bodies. Each document serves a specific purposes and needs traceability

Design History File (DHF) Compiles records describing the design history of a finished device Complies with FDA requirements for marketing medical device Specific to each company FDA Requirement: “Each manufacturer shall establish and maintain a DHF for each type of device. The Device shall contain or reference the records necessary to demonstrate that the design was developed in accordance with the approval design plan and the requirements of this part.” Code of Federal Regulations, Title 21 – Food and Drugs, Chapter I – Food and Drug Administration Department of Health and Human Services, Subchapter H – Medical Devices.

Design History File (DHF) Items can include: Customer Requirements Design Inputs Design Outputs Design review meeting information Test Procedures Biocompatibility Reports

Design Planning Outlines the activities to be taken during the design control process Sets target dates for finishing each stage of development, as well as design reviews Gantt Chart Identifies team members from each necessary department -Design plan/Gantt chart must be updated during development -Dates for completion can be adjusted as needed if problems arise -Proper planning ensures all necessary activities for development are completed and can be reported to FDA properly

Customer Requirements Defines the use for the product in the market Drives the development process Typically gathered by marketing team Customer requirements are typically seen as the most important part of product development – without customers, no revenue

Design Inputs Translate customer’s needs into design Reduce miscommunication between engineering and marketing teams if used effectively Improve efficiency of the design process Require documentation and approval Define performance and function requirements

Design Inputs Functional requirements Performance requirements Lists all functions the final product must perform Lists compatibilities with mating parts Performance requirements Benchmarks the final product must meet Include strength, durability, and lifespan

Design Inputs Sterilization Method Packaging/Labeling requirements Defines how product will be cleaned Packaging/Labeling requirements Defines specifications that labeling/packaging must meet Human Factors Specialized inputs to define how people interact with a medical device Sterilization Method Provide the ISO/ASTM specifications for cleaning the product Define whether product should be packaged sterile or be cleaned by end user Packaging/Labeling requirements -Provides ISO/ASTM standards for labeling and packaging -Must include special packaging/labeling requirements for sterile products (labeling – word STERILE visibly seen, packaging – asceptic barrier, etc.) Human factor examples Design of handles on an instrument Size of important text on an implant/instrument

Design Outputs Bring design inputs to life Outline what happened in design process Items include: Product specifications, drawings, packaging, labeling, instructions for use, design rationale

Risk Management Evaluates all risks of product and production process Identifies actions to manage unacceptable design and process risks

Risk Management Design Failure Mode Effects Analysis (DFMEA) Process Failure Mode Effects Analysis (PFMEA) Potential product failures Effects of product failures Causes of failures Corrections of failures

FMEA Example http://www.qualitydigest.com/aug06/articles/04_article.shtml

Design Review Identifies and evaluates design Utilizes knowledge base of multi-function team representatives concerned with the design stage Includes reviews conducted at specified stages of development Approved by multiple departments in order to proceed with development Packaging, Labeling, Product Development, Quality, Regulatory, etc.

Design Change Communicates and documents changes Creates links between revisions Traces development of new product Approved by appropriate departments during development

Design Verification/Validation Ensures that outputs conform to inputs Consists of tests, inspections, and analyses Documents verification activities Requires documentation of acceptance criteria and protocols

Device Master Record Compilation of records containing the specifications and procedures for a finished device Device specifications including appropriate drawings, composition, formulation, component specifications, and software applications Production process specifications including appropriate equipment specifications, production methods, production procedures, and production environment specifications

Device Master Record Items include: Quality assurance procedures and specifications including acceptance criteria and the quality assurance equipment used Packaging and labeling specifications, including methods and process used Installation, maintenance, and service procedures and methods Device master record is the end product of the design process.

Device Master Record

Design Transfer Documentation Facilitates transfer of product from design engineering to manufacturing engineering Includes detailed production specifications Increases efficiency and quality of production

Summary http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/PostmarketRequirem ents/QualitySystemsRegulations/MedicalDeviceQualitySystemsManual/ucm122416.htm

Summary Assume everything you hear, say, think, write, read, and create is important no matter how insignificant, trivial, irrelevant, immaterial, or inconsequential you might think it may be Record, date, sign, and save everything Document as though an audit will occur

Questions?