BS EN 82304-1:2017

FOREWORD
INTRODUCTION
1 Scope
2 Normative references
3 Terms and definitions
4 HEALTH SOFTWARE PRODUCT requirements
5 HEALTH SOFTWARE - Software life cycle processes
6 HEALTH SOFTWARE PRODUCT VALIDATION
7 HEALTH SOFTWARE PRODUCT identification and
  ACCOMPANYING DOCUMENTS
8 Post-market activities for the HEALTH SOFTWARE
  PRODUCT
Annex A (informative) - Rationale
Bibliography
Annex ZA (normative) - Normative references to
         international publications with their
         corresponding European publications

Pertains 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.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. IEC82304-1 does not apply to health software which is intended to become part of a specific hardware designed for health use. Specifically, IEC82304-1 does not apply to: medical electrical equipment or systems covered by the IEC60601/IEC80601 series; in vitro diagnostic equipment covered by the IEC61010 series; or implantable devices covered by the ISO14708 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/IEC12207 where the term “compliance” is used in this document.