(Sample Pages of) EVIDENCE PRODUCT CHECKLIST For the FDA Document

Transcription

1 (Sample Pages of) EVIDENCE PRODUCT CHECKLIST For the FDA Guidance for the Content of Pre-market Submissions for Contained in Medical Devices

2 Guidance for the Content of Pre-market Submissions for Contained in Medical Devices EVIDENCE PRODUCT CHECKLIST Introduction The process of defining what is necessary for compliance with a software engineering process standard such as FDA Guidance for the Content of Pre-market Submissions for Contained in Medical Devices is sometimes confusing and laborious because the directions contained in the standard may be unclear or ambiguous. To aid in determining what is actually required by the standard in the way of physical evidence of compliance, the experts at SEPT have produced this checklist. This checklist is constructed around a classification scheme of physical evidence comprised of procedures, plans, records, documents, audits, and reviews. SEPT has carefully reviewed this document, FDA Guidance for the Content of Pre-market Submissions for Contained in Medical Devices. (Note: This document will be referred to as FDA Guidance from this point forward in this checklist). SEPT has conducted a second review of the complete list to ensure that the standard s producers did not leave out a physical piece of evidence that a reasonable person would expect to find. It could certainly be argued that if the document did not call it out then it is not required; however if the standard were used by an enterprise to improve its software process, then it would make sense to recognize missing documents. Therefore, there are documents specified in this checklist that are implied by the standard, though not specifically called out in the standard, and they are designated by an asterisk throughout this checklist. If a document is called out more than one time, only the first reference is stipulated. FDA Guidance Checklist This checklist was prepared by analyzing each section of the FDA Guidance for the key words that signify a: Procedure Plans Records Audit Review This checklist specifies evidence that is software unique. After reviewing the completed document, the second review was conducted from a common sense reasonable man approach. If a document or other piece of evidence appeared to be required, but was not called out in the document, then it is added with an asterisk (*) after its notation in the checklist. The information was transferred into checklist tables, based on the type of product or evidence. 2

3 Guidance for. 3.0 ation in a Premarket Submission ation 3.1 Level of Concern Procedures for Determination of Level of Concern* 3.2 Description Development and Maintenance (Primary) 3.3 Device Hazard Device Hazard ation Plan* ation Records* User Manuals* Development Process* ation Plan* User Manual* Level of Concern Description Device Hazard Level of Concern Description Device Hazard 3

4 Guidance for. 3.4 Requirements Specification Requirements Specification (For minor concern only functional requirements are required) System Requirement Requirements System Requirement System and Development Audit* 4

5 Guidance for. 3.5 Architecture Design Chart System and Architectural Design (Chart) and. (for minor concern, only a chart is required that shows the partitioning of the software into subsystems) System and Architecture 5