Guidance for Off-The-Shelf Software Use in Medical Devices

More documents

Recommendations

Info

Table 1-1 summarizes the recommended contents for an OTS Software submission based onFigure 1-1.Table 1-1. Documentation Summary from Figure 1-1Minor Level of Concern before mitigationsHazard AnalysisBasic DocumentationMinor Level of Concern after mitigationsHazard AnalysisBasis DocumentationHazard MitigationsModerate Level of ConcernHazard AnalysisBasis DocumentationHazard MitigationsDescribe and Justify Residual RiskMajor Level of Concern after mitigationsHazard AnalysisBasic DocumentationHazard MitigationsDescribe and Justify Residual RiskSpecial Documentation2 OTS Software Use2.1 BASIC DOCUMENTATION for OTS SoftwareThe OTS Software BASIC DOCUMENTATION is intended to answer the following questions:1. What is it? - For each component of OTS Software used, specify the following:• Title and Manufacturer of the OTS Software.• Version Level, Release Date, Patch Number and Upgrade Designation as appropriate.• Any OTS Software documentation that will be provided to the end user.• Why is this OTS Software appropriate for this medical device?OTS Software Guidance, Final page 5
• What are the expected design limitations of the OTS Software?Note: The medical device manufacturer should only use the OTS Software as specified in anappropriate document, i.e., design record. If the version of the OTS Software changes, theappropriate document should be updated to reflect the change.2. What are the Computer System Specifications for the OTS Software? - For whatconfiguration will the OTS software be validated? Specify the following:• Hardware specifications: processor (manufacturer, speed, and features), RAM (memorysize), hard disk size, other storage, communications, display, etc.• Software specifications: operating system, drivers, utilities, etc. The software requirementsspecification (SRS) listing for each item should contain the name (e.g., Windows 95,Excel, Sun OS, etc.), specific version levels (e.g., 4.1, 5.0, etc.) and a complete list of anypatches that have been provided by the OTS Software manufacturer.3. How will you assure appropriate actions are taken by the End User?• What aspects of the OTS Software and system can (and/or must) be installed/configured?• What steps are permitted (or must be taken) to install and/or configure the product?• How often will the configuration need to be changed?• What education and training are suggested or required for the user of the OTS Software?• What measures have been designed into the medical device to prevent the operation of anynon-specified OTS Software, e.g., word processors, games? Operation of non-specifiedOTS Software may be prevented by system design, preventive measures, or labeling.Introduction may be prevented by disabling input (floppy disk, CD, tape drives, modems).4. What does the OTS Software do? – What function does the OTS software provide in thisdevice? This is equivalent to the software requirements in the Guidance for the Content ofPremarket Submissions for Software Contained in Medical Devices [4] for this OTSsoftware. Specify the following:• What is the OTS Software intended to do? The sponsor’s design documentation shouldspecify exactly which OTS components will be included in the design of the medicaldevice. Specify to what extent OTS Software is involved in error control and messagingin device error control.• What are the links with other software including software outside the medical device (notreviewed as part of this or another application)? The links to outside software should becompletely defined for each medical device/module. The design documentation shouldinclude a complete description of the linkage between the medical device software and anyoutside software (e.g., networks).5. How do you know it works? – Based on the Level of Concern:OTS Software Guidance, Final page 6
Page 1 and 2: Guidance for Industry, FDA Reviewer
Page 3 and 4: Table of Contents1 OVERVIEW........
Page 5 and 6: Contained in Medical Devices [4]. M
Page 7: 1.4 OTS Software Decision Schematic
Page 11 and 12: • A list of all potential hazards
Page 13 and 14: These approaches may involve hardwa
Page 15 and 16: Note: If such an audit is not possi
Page 17 and 18: • set the adjustable (programmabl
Page 19 and 20: 3.2.1 OTS Software Changes Requirin
Page 21 and 22: 3.7 Product LabelingFDA recommends
Page 23 and 24: 5.2 Utilities and DriversThe purpos
Page 25 and 26: Transmission of data packets and fi
Page 27 and 28: minor. Traceability between these i
Page 29: • hardware platform (e.g. micropr

Guidance for Off-The-Shelf Software Use in Medical Devices

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?