12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

permission to specific device manufacturers to reference the master file <strong>in</strong> their premarketsubmissions. In<strong>for</strong>mation regard<strong>in</strong>g device master files is conta<strong>in</strong>ed <strong>in</strong> DSMA’s “PremarketApproval (PMA) Manual”, or via Facts-on-Demand or from the FDA home page(http://www.fda.gov/cdrh/dsma/pmaman/front.html)5.5 Ma<strong>in</strong>tenance and ObsolescenceThis appendix addresses relevant ma<strong>in</strong>ta<strong>in</strong>ability issues with regard to OTS Sotware <strong>in</strong> medicaldevices.Ma<strong>in</strong>tenance activities are generally considered to beg<strong>in</strong> subsequent to the establishment anddistribution of a medical device product basel<strong>in</strong>e. <strong>The</strong> dist<strong>in</strong>ction between ma<strong>in</strong>tenance andproduct development is an important one. Product development design activities generally lead toa system structure of highly <strong>in</strong>tegrated components and logic. Ma<strong>in</strong>tenance activities <strong>in</strong>troducechanges <strong>in</strong>to this structure which may lead to a loss <strong>in</strong> the <strong>in</strong>tegrity of the structure. Structure<strong>in</strong>tegrity may be affected through changes due to new design requirements, corrections, orenvironmental adaptations. <strong>The</strong>se types of changes may impact the <strong>in</strong>tegrity of the structureorganization, architecture, logic, <strong>in</strong>tegration, or any comb<strong>in</strong>ation of these characteristics.Ma<strong>in</strong>tenance of products with OTS <strong>Software</strong> components may be particularly problematic <strong>for</strong>reasons discussed <strong>in</strong> the ma<strong>in</strong> body of this document, i.e., the sponsor does not have control ofthe OTS <strong>Software</strong> component life cycle process.In particular, this section identifies general safety and effectiveness, design, verification /validation, change, <strong>in</strong>stallation, and decommission<strong>in</strong>g concerns. <strong>The</strong>se concerns may be appliedto all regulated medical device software and stand-alone medical software devices. <strong>The</strong>appropriate evaluation will depend on the Level of Concern.Assumptions <strong>for</strong> this section <strong>in</strong>clude:• Manufacturer Good <strong>Software</strong> Development Practices (GSDP)s and Good Corrective ActionPractices (GCAP) are <strong>in</strong> place.• A product basel<strong>in</strong>e exists.• A new product basel<strong>in</strong>e based on a prior product basel<strong>in</strong>e is under CDRH review.Each concern below corresponds to a product development life cycle phase. <strong>The</strong> concernsidentify fundamental ma<strong>in</strong>tenance concerns relevant to all regulated PEMS and stand-alonemedical software devices. <strong>Guidance</strong> <strong>in</strong> the ma<strong>in</strong> body of this document provides the proceduralfoundation <strong>for</strong> concerns <strong>in</strong> this section.5.5.1 SafetyIntroduction of new or modified OTS components to a product basel<strong>in</strong>e may impact the safety ofthe product. <strong>The</strong>re<strong>for</strong>e a safety impact assessment of the medical device must be per<strong>for</strong>med andassociated hazards documented <strong>in</strong> a Failure Modes and Effects Analysis (FMEA) table. Eachhazard’s consequence should be provided and expressed qualitatively; e.g. major, moderate, orOTS <strong>Software</strong> <strong>Guidance</strong>, F<strong>in</strong>al page 23

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!