In Partnership with NORMADOC
Your purchasing center for standards regulations & technical and legal books
Checklist for IEC 62304:2015 Standard
Checklist for IEC 62304 Standard

IEC 62304:2015 Medical device software - Software life cycle processes.. (Complete Document)

Revision / Edition:    Chg: REAF     Date: 00/00/00   Abbreviations Definitions

Active, Most Current

Published By: Software Engineering Process Technology (SEPT)

Page Count: 130

SOFTWARE ENGINEERING PROCESS TECHNOLOGY-EVIDENCE PRODUCT CHECKLIST FOR STANDARD IEC 62304:2015 "MEDICAL DEVICE SOFTWARE - SOFTWARE LIFE CYCLE PROCESSES"

To get more product information or to order click on buy
For more information on ICE 62304:2015 see below

IEC 62304:2015 Checklist

standard defines the life cycle requirements for MEDICAL DEVICE SOFTWARE. The set of PROCESSES, ACTIVITIES, and TASKS described in this standard establishes a common framework for MEDICAL DEVICE SOFTWARE life cycle PROCESSES. This is the latest update of the standard, replacing the former 2006 version.

Field of application

IEC 62304

applies to the development and maintenance of MEDICAL DEVICE SOFTWARE.

IEC 62304 Checklist

standard applies to the development and maintenance of MEDICAL DEVICE SOFTWARE when software is itself a MEDICAL DEVICE or when software is an embedded or integral part of the final MEDICAL DEVICE.

IEC 62304 Checklist

does not cover validation and final release of the MEDICAL DEVICE, even when the MEDICAL DEVICE consists entirely of software.

Relationship to other standards

This MEDICAL DEVICE SOFTWARE life cycle standard is to be used together with other appropriate standards when developing a MEDICAL DEVICE. Annex C shows the relationship between this standard and other relevant standards.

Compliance

IEC 62304

Compliance with is defined as implementing all of the PROCESSES, ACTIVITIES, and TASKS identified in this standard in accordance with the software safety class.

NOTE The software safety classes assigned to each requirement are identified in the normative text following the requirement.

Compliance is determined by inspection of all documentation required by this standard including the RISK MANAGEMENT FILE, and assessment of the PROCESSES, ACTIVITIES and TASKS required for the software safety class. See Annex D.

NOTE 1 This assessment could be carried out by internal or external audit.

NOTE 2 Although the specified PROCESSES, ACTIVITIES, and TASKS are performed, flexibility exists in the methods of implementing these PROCESSES and performing these ACTIVITIES and TASKS.

NOTE 3 Where any requirements contain “as appropriate” and were not performed, documentation for the justification is necessary for this assessment.

NOTE 4 The term “conformance” is used in ISO/IEC 12207 where the term “compliance” is used in this standard.

Related Products