BS EN 82304-1:2017
$167.15
Health Software – General requirements for product safety
| Published By | Publication Date | Number of Pages |
| BSI | 2017 | 34 |
1.1 Purpose
This Part of 82304 applies to the safety and security of health software products designed to operate on general computing platforms and intended to be placed on the market without dedicated hardware, and its primary focus is on the requirements for manufacturers.
1.2 Field of application
This document covers the entire lifecycle including design, development, validation, installation, maintenance, and disposal of health software products.
In each referenced standard, the term “medical device” or “medical device software” is to be substituted by the term “health software” or “health software product”, as appropriate.
Where the term “patient” is used, either in this document or in a referenced standard, it refers to the person for whose health benefit the health software is used.
IEC 82304-1 does not apply to health software which is intended to become part of a specific hardware designed for health use. Specifically, IEC 82304-1 does not apply to:
-
medical electrical equipment or systems covered by the IEC 60601/IEC 80601 series;
-
in vitro diagnostic equipment covered by the IEC 61010 series; or
-
implantable devices covered by the ISO 14708 series.
NOTE This document also applies to health software products (e.g. medical apps, health apps) intended to be used in combination with mobile computing platforms.
1.3 Compliance
Compliance with this document is determined by inspection of all documentation required by this document.
Assessment of compliance is carried out and documented by the manufacturer. Where the health software product is subject to regulatory requirements, external assessment may take place.
Where this document normatively references parts or clauses of other standards focused on safety or security, the manufacturer may use alternative methods to demonstrate compliance with the requirements of this document. These alternative methods may be used if the process results of such alternative methods, including traceability, are demonstrably equivalent and the residual risk remains acceptable.
NOTE The term “conformance” is used in ISO/IEC 12207 where the term “compliance” is used in this document.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | National foreword |
| 7 | English CONTENTS |
| 8 | FOREWORD |
| 10 | INTRODUCTION |
| 11 | 1 Scope 1.1 Purpose 1.2 Field of application 1.3 Compliance 2 Normative references |
| 12 | 3 Terms and definitions |
| 15 | 4 * Health software product requirements 4.1 General requirements and initial risk assessment |
| 16 | 4.2 Health software product use requirements 4.3 Verification of health software product use requirements |
| 17 | 4.4 Updating health software product use requirements 4.5 System requirements 4.6 Verification of system requirements 4.7 Updating health software product system requirements |
| 18 | 5 * Health software – Software life cycle processes 6 * Health software product validation 6.1 Validation plan 6.2 Performing validation |
| 19 | 6.3 Validation report 7 Health software product identification and accompanying documents 7.1 * Identification 7.2 Accompanying documents 7.2.1 General |
| 20 | 7.2.2 Instructions for use |
| 22 | 7.2.3 Technical description |
| 23 | 8 Post-market activities for the health software product 8.1 General |
| 24 | 8.3 Re-validation 8.4 Post-market communication on the health software product 8.5 Decommissioning and disposal of the health software product |
| 25 | Annex A (informative)Rationale A.1 General |
| 26 | A.2 Requirements for health software products Table A.1 – Examples of software (SW) in or not in the scope of this document |
| 27 | A.3 Rationale for particular clauses and subclauses Figure A.1 – Health software application domains and scope of related standards |
| 28 | Figure A.2 – IEC 82304-1: Health software product processes |
| 31 | Bibliography |
