Design Documentation Clint Kehres, Brian Krouse, Jenn Shafner.

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

Integra Consult A/S Safety Assessment. Integra Consult A/S SAFETY ASSESSMENT Objective Objective –Demonstrate that an acceptable level of safety will.
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
Producing a Pharmaceutical or Biopharmaceutical
Software Quality Assurance Plan
ISO 9001 : 2000.
Validation, Verification, Qualification : Which is right and does it really matter?
Combining Product Risk Management & Design Controls
Systems Engineering for FDA Design Controls Compliance
Systems Engineering Management
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.
UNIT 3.04 Career Opportunities By PresenterMedia.comPresenterMedia.com.
4. Quality Management System (QMS)
Instructions and forms
4. Quality Management System (QMS)
Huzairy Hassan School of Bioprocess Engineering UniMAP.
EQUIPMENT QUALIFICATION/VALIDATION
Fundamentals of ISO.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Regulatory Overview.
MethodGXP The Solution for the Confusion.
1 European Conference on Training Strategies Kieran Cox -NSAI Education & Promotion-
Introduction to ISO New and modified requirements.
Introduction to Software Quality Assurance (SQA)
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.
Nikki Dillard Allison Lowry Tiffany Thomas.  “The maintenance of a history of one’s activities, as financial dealings, by entering data into ledgers.
Software Quality Assurance Activities
From Research Prototype to Production
Chapter 13: Developing and Implementing Effective Accounting Information Systems
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
Development and Regulation of Medical Products (MEDR-101)
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
Leukocyte-Reduced Blood Components Lore Fields MT(ASCP)SBB Consumer Safety Officer, DBA, OBRR, CBER September 16, 2009.
Ergonomics Regulatory Requirements Bawan Saravanabawan, Labour Program, HRSDC February 4, 2008.
Joel Gerber Zachary Reaver Kurt Schilling.  Provides physical proof of development  Maintains product design knowledge base  Meets government and corporate.
Product development Engineering & Regulatory Raj Agrawal InnAccel.
14 March 2002Update on SDoC - USA1 Update on Supplier’s Declaration of Conformity – USA William Hurst Federal Communications Commission Office of Engineering.
Producing a Pharmaceutical or Biopharmaceutical The Manufacturing Process.
Joe Selva Rohan Thakkar Jean Valderrama.  “Documentation” is what’s written on paper  Provides written details, events, and information about a particular.
DOCUMENTATION ISO/IEC 17025:2005 Documentation.
Quality Control significance in pharmaceutical industry
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Responsibilities of Test Facility Management, Study Director, Principal Investigator and Study Personnel G. Jacobs Belgian GLP Monitorate Zagreb, 17 December.
Logo area MQXF Review: Safety Thomas Otto HL-LHC Project Safety Officer With contributions by -Paolo Ferrcin and Ezio Todesco, TE-MSC -Francesca Viggiano,
Process engineering Quality controls.
Medical Device Software Development
Software Quality Control and Quality Assurance: Introduction
Raechel Huebner Ruthanne Sherer
Software and Systems Integration
Quality Systems in a Production Facility
DSQR Training Control Plans
Quality Management Systems – Requirements
FDA 21 CFR Part 11 Overview June 10, 2006.
FDA Quality System Regulation
Medical Device Design and Development
Advanced Product Quality Planning 2nd Edition
Advanced Product Quality Planning 2nd Edition
Computer System Validation
Radiopharmaceutical Production
Corey Beth Monarch Lindsey Novak Michael Seikel Whitney Young
Presentation transcript:

Design Documentation Clint Kehres, Brian Krouse, Jenn Shafner

Legal Requirements DHF- design history file 1. Not all national regulators are equal. Diligent records at every step.

Manufacturer Benefits from Design Documentation Maintain knowledge base of the product design. DHF owner = Company, not individual. Required by Governments – Document everything clearly in case audited.

Design Documents Design History File (DHF) Device Master Record (DMR) Design Changes Technical Files FDA Submissions Design and Process Validations/Verifications Risk Management Documentation – Design Failure Mode and Effects Analyses – Process Failure Mode and Effects Analyses Process Routers Drawings Meeting Minutes Inspection Criteria Laboratory Notebooks Design Control Plans Material Specifications Sterility and Cleaning Process Verifications Tolerance Stack-ups

Logical Path of Design Development/Control Every step requires design documentation. Each step has its own specific type of documents.

Design History File… Exact requirements depend on specific company. -Most are self regulated. FDA States, “Each manufacturer shall establish and maintain a DHF for each type of device. The DHF shall contain or reference the records necessary to demonstrate that the design was developed in accordance with the approved design plan and the requirements of this part”.

Methods of Documentation Hard Copy DHF’s and Paperwork Images and Photos Excel and Word Documents Company specific document templates and regulations Digital Document Management System Specific Document Management Departments

Design Inputs: The design input requirements shall be documented and shall be reviewed and approved by designated individual(s). The approval, including the date and signature of the individual(s) approving the requirements, shall be documented. Customer requirements must be translated into engineering design inputs. ◦The customer requirements and design inputs are arguably the most important items in a design. ◦Because of their importance, they must be documented very comprehensively and avoid being vague. Requirements are often identified from Marketing team. - Good documentation reduces poor assumptions between the engineering and marketing teams. - Comprehensive identification/documentation of design inputs increases the likelihood of having an efficient development process.

Design Outputs: Each manufacturer shall establish and maintain procedures for defining and documenting design output in terms that allow an adequate evaluation of conformance to design input requirements. Result of detailed designed process addressing design inputs. Outputs include risk management, product specifications, drawings, packaging, etc. Includes a Design Rationale ◦Detailed description of product functions or features ◦Includes general description of various parts of device, functional purpose of device, compatibility with other devices, etc.

Risk Management: Design/Production team need to evaluate all risks associated with product and production process. Investigation to identify hazards, estimate risk and identify actions to manage unacceptable design and process risks. Often Document: ◦Potential failures of product ◦Failure’s effect on the consumer and severity ◦Cause of failure ◦Actions to reduce failure or risk occurrence

Design Changes Very common Communicate the change Document control department: ◦Documents are properly identified ◦A master list or index of documents is compiled. ◦Govern entry of documents into the document control system (ECO’s) ◦A history of document revisions ◦Procedures for distributing copies ◦Removal and deletion of obsolete documents.

Design Validation/Verification: The results of the design verification, including identification of the design, method(s), the date, and the individual(s) performing the verification, shall be documented in the Design History File. Verification ensures that outputs conform to inputs. ◦Tests, inspections, analyses ◦Mechanical testing data, tolerance stack-ups, mathematical models ◦Detailed reports are required to document verification activities. Validation ensures that outputs meet ultimate user needs. -Product should be tested in actual or simulated use environment. -This would include clinical trials if necessary. ((Cadaver Labs)) -Test protocols and acceptance criteria must be documented. -For a complex design, the detailed results may be contained in a variety of separate documents and summarized in a validation report.

Device Master Record  Purpose – DMR is a compilation of those 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.  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.

Design Transfer Documentation Once a product has been designed, it must be transferred to the production phase. The manufacturing facility needs detailed production specifications. ◦These include: detailed product drawings, workmanship standards, manufacturing instructions, inspection criteria, heat treat conditions, etc. ◦Comprehensive documentation is required for efficient and high quality production of the product.  One must remember that a different supplier in the future may make the product.

Design/Project Review Each manufacturer shall establish and maintain procedures to ensure that formal documented reviews of the design results are planned and conducted at appropriate stages of the device's design development. The procedures shall ensure that participants at each design review include representatives of all functions concerned with the design stage being reviewed and an individual(s) who does not have direct responsibility for the design stage being reviewed, as well as any specialists needed. The results of a design review, including identification of the design, the date, and the individual(s) performing the review, shall be documented in the design history file (the DHF).

DHF SENIOR DESIGN REQUIREMENT A design history file will be required for each groups senior design project. This DHF will be submitted in the Spring semester with the final report

SUMMARY ASSUME EVERYTHING YOU HEAR, SAY, THINK, WRITE, READ, AND CREATE IS IMPORTANT! NO MATTER HOW INSIGNIFICANT, TRIVIAL, IRRELEVANT, IMMATERIAL, OR INCONSEQUNETIAL YOU THINK IT MAY BE. RECORD, DATE, SIGN, AND SAVE EVERYTHING! You will be audited!

uidanceDocuments/ucm htm#_Toc http:// uidanceDocuments/ucm htm#_Toc A39&dq=design+transfer+documentation&source=bl&ots=coHNb3R DYz&sig=cUvLb6VDHI3dLXu2B9cb9bfjgFs&hl=en&ei=rQXvSvjRPM 6TlAfn4az_BA&sa=X&oi=book_result&ct=result&resnum=2&ved=0C A4Q6AEwAQ#v=onepage&q=design%20transfer%20documentation &f=false