Medical device software - Part 1: Guidance on the application of ISO 14971 to medical device software

IEC/TR 80002-1:2009(E) provides guidance for the application of the requirements contained in ISO 14971:2007, Medical devices - Application of risk management to medical devices to medical device software with reference to IEC 62304:2006, Medical device software - Software life cycle processes. It does not add to, or otherwise change, the requirements of ISO 14971:2007 or IEC 62304:2006. IEC/TR 80002-1:2009(E) is aimed at risk management practitioners who need to perform risk management when software is included in the medical device/system, and at software engineers who need to understand how to fulfil the requirements for risk management addressed in ISO 14971. ISO 14971, recognized worldwide by regulators, is widely acknowledged as the principal standard to use when performing medical device risk management. IEC 62304:2006, makes a normative reference to ISO 14971 requiring its use. The content of these two standards provides the foundation for this technical report. It should be noted that even though ISO 14971 and this technical report focus on medical devices, this technical report may be used to implement a safety risk management process for all software in the healthcare environment independent of whether it is classified as a medical device. IEC/TR 80002-1:2009 is not intended to be used as the basis of regulatory inspection or certification assessment activities.

General Information

Status
Published
Publication Date
22-Sep-2009
Current Stage
PPUB - Publication issued
Start Date
15-Dec-2009
Completion Date
23-Sep-2009
Ref Project

Buy Standard

Technical report
IEC TR 80002-1:2009 - Medical device software - Part 1: Guidance on the application of ISO 14971 to medical device software
English language
64 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


IEC/TR 80002-1
Edition 1.0 2009-09
TECHNICAL
REPORT
colour
inside
Medical device software –
Part 1: Guidance on the application of ISO 14971 to medical device software

IEC/TR 80002-1:2009(E)
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC/TR 80002-1
Edition 1.0 2009-09
TECHNICAL
REPORT
colour
inside
Medical device software –
Part 1: Guidance on the application of ISO 14971 to medical device software

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XB
ICS 11.040.01 ISBN 978-2-88910-779-7

– 2 – TR 80002-1 © IEC:2009(E)
CONTENTS
FOREWORD.4
INTRODUCTION.6
1 General .7
1.1 Scope.7
1.2 Normative references .7
2 Terms and definitions .8
3 General requirements for RISK MANAGEMENT.8
3.1 RISK MANAGEMENT PROCESS .8
3.2 Management responsibilities .11
3.3 Qualification of personnel.13
3.4 RISK MANAGEMENT plan .14
3.5 RISK MANAGEMENT FILE .16
4 RISK ANALYSIS .17
4.1 RISK ANALYSIS PROCESS.17
4.2 INTENDED USE and identification of characteristics related to the SAFETY of the
MEDICAL DEVICE .18
4.3 Identification of HAZARDS .20
4.4 Estimation of the RISK(S) for each HAZARDOUS SITUATION .22
5 RISK EVALUATION .25
6 RISK CONTROL .26
6.1 RISK reduction .26
6.2 RISK CONTROL option analysis .26
6.3 Implementation of RISK CONTROL measure(s) .35
6.4 RESIDUAL RISK EVALUATION .36
6.5 RISK/benefit analysis .36
6.6 RISKS arising from RISK CONTROL measures .37
6.7 Completeness of RISK CONTROL.37
7 Evaluation of overall residual risk acceptability.38
8 Risk management report.38
9 Production and POST-PRODUCTION information.39
Annex A (informative)  Discussion of definitions.41
Annex B (informative) Examples of software causes .43
Annex C (informative) Potential software-related pitfalls .53
Annex D (informative) Life-cycle/risk management grid.57
Annex E (informative) SAFETY cases .70H60
34HBibliography.71H61
35HIndex .72H62
36HIndex of defined terms .73H63

Figure 1 – Pictorial representation of the relationship of HAZARD, sequence of events,
HAZARDOUS SITUATION and HARM – from ISO 14971:2007 Annex E .74H24
Figure 2 – FTA showing RISK CONTROL measure which prevents incorrect software
HARM .75H28
outputs from causing
Figure A.1 – Relationship between sequence of events, HARM and HAZARD .76H41

TR 80002-1 © IEC:2009(E) – 3 –

Table 1 – Requirements for documentation to be included in the RISK MANAGEMENT FILE
in addition to ISO 14971:2007 requirements .17
Table A.1 – Relationship between HAZARDS, foreseeable sequences of events,
HAZARDOUS SITUATIONS and the HARM that can occur .42
Table B.1 – Examples of causes by software function area .43
Table B.2 – Examples of software causes that can introduce side-effects .48
Table B.3 – Methods to facilitate assurance that RISK CONTROL methods are likely to
perform as intended.52
Table C.1 – Potential software-related pitfalls to avoid.53
Table D.1 – LIFE-CYCLE/RISK MANAGEMENT grid .57

– 4 – TR 80002-1 © IEC:2009(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
MEDICAL DEVICE SOFTWARE –
Part 1: Guidance on the application of ISO 14971
to medical device software
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
The main task of IEC technical committees is to prepare International Standards. However, a
technical committee may propose the publication of a technical report when it has collected
data of a different kind from that which is normally published as an International Standard, for
example "state of the art".
IEC 80002-1, which is a technical report, has been prepared by a joint working group of
subcommittee 62A: Common aspects of electrical equipment used in medical practice, of IEC
technical committee 62: Electrical equipment in medical practice, and ISO technical
committee 210: Quality management and corresponding general aspects for MEDICAL DEVICES.

TR 80002-1 © IEC:2009(E) – 5 –
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
62A/639A/DTR 62A/664/RVC
Full information on the voting for the approval of this technical report can be found in the
report on voting indicated in the above table. In ISO, the technical report has been approved
by 16 P-members out of 17 having cast a vote.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
In this technical report the following print types are used:
• requirements and definitions: in roman type.
• informative material appearing outside of tables, such as notes, examples and references: in smaller type.
Normative text of tables is also in a smaller type.
• TERMS USED THROUGHOUT THIS TECHNICAL REPORT THAT HAVE BEEN DEFINED IN CLAUSE 2 AND
ALSO GIVEN IN THE INDEX: IN SMALL CAPITALS.
A list of all parts of the IEC 80002 series, published under the general title Medical device
software, can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The “colour inside” logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this publication using a colour printer.

– 6 – TR 80002-1 © IEC:2009(E)
INTRODUCTION
Software is often an integral part of MEDICAL DEVICE technology. Establishing the SAFETY and
effectiveness of a MEDICAL DEVICE containing software requires knowle
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.