iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
SIST

SIST EN 60601-1-4:1998/A1:2002

(Amendment)

Medical electrical equipment - Part 1-4: General requirements for safety - Collateral standard: Programmable electrical medical systems (IEC 60601-1-4:1998)

Medical electrical equipment - Part 1-4: General requirements for safety - Collateral standard: Programmable electrical medical systems (IEC 60601-1-4:1998)

EN following parallel vote

Medizinische elektrische Geräte - Teil 1-4: Allgemeine Festlegungen für die Sicherheit - Ergänzungsnorm: Programmierbare elektrische medizinische Systeme (IEC 60601-1-4:1998)

Appareils électromédicaux - Partie 1-4: Règles générales de sécurité - Norme collatérale: Systèmes électromédicaux programmables (CEI 60601-1-4:1998)

Medicinska električna oprema - 1. del: Splošne varnostne zahteve - 4. spremljevalni standard: Programirljivi električni medicinski sistemi - Dopolnilo A1(IEC 60601-1-4:1998)

General Information

Status
Withdrawn
Publication Date
31-Jan-2002
Withdrawal Date
07-Mar-2019
ICS
11.040.01 - Medical equipment in general
35.240.80 - IT applications in health care technology
Technical Committee
IEMO - Electrical equipment in medical practice
Current Stage
9900 - Withdrawal (Adopted Project)
Start Date
04-Mar-2019
Due Date
27-Mar-2019
Completion Date
08-Mar-2019
Directive
93/42/EEC - Council Directive 93/42/EEC of 14 June 1993 concerning medical devices
Mandate
M/023 - Standardization mandate to CEN/CENELEC concerning the development of European standards relating to medical devices
Ref Project
EN 60601-1-4:1996/A1:1999 - Medical electrical equipment - Part 1-4: General requirements for safety - Collateral standard: Programmable electrical medical systems

Relations

Replaced By
SIST EN 60601-1:2007 - Medical electrical equipment -- Part 1: General requirements for basic safety and essential performance
Effective Date
01-Mar-2007
Amends
SIST EN 60601-1-4:1998 - Medical electrical equipment - Part 1-4: General requirements for safety - Collateral standard: Programmable electrical medical systems (IEC 60601-1-4:1996)
Effective Date
01-Feb-2002
Replaced By
SIST EN 60601-1:2007 - Medical electrical equipment -- Part 1: General requirements for basic safety and essential performance
Effective Date
28-Jan-2023
Replaced By
SIST EN 60601-1:2007 - Medical electrical equipment -- Part 1: General requirements for basic safety and essential performance
Effective Date
07-Jun-2022
Amends
SIST EN 60601-1-4:1998 - Medical electrical equipment - Part 1-4: General requirements for safety - Collateral standard: Programmable electrical medical systems (IEC 60601-1-4:1996)
Effective Date
28-Jan-2023
Amends
SIST EN 60601-1-4:1998 - Medical electrical equipment - Part 1-4: General requirements for safety - Collateral standard: Programmable electrical medical systems (IEC 60601-1-4:1996)
Effective Date
07-Jun-2022

Buy Standard

EN 60601-1-4:1998/A1:2002EN 60601-1-4:1998/A1:2002
PreviousNext
Amendment
EN 60601-1-4:1998/A1:2002
English language
10 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Related Packages

IEC 60601-1 / 60601-1-2 / 60601-1-4 / 60601-1-6 Medical Electrical Equipment Package
IEC 60601-1 / 60601-1-2 / 60601-1-4 / 60601-1-6 Medical Electrical Equipment Package
8 documents

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 60601-1-4:1998/A1:2002
01-februar-2002
0HGLFLQVNDHOHNWULþQDRSUHPDGHO6SORãQHYDUQRVWQH]DKWHYH
VSUHPOMHYDOQLVWDQGDUG3URJUDPLUOMLYLHOHNWULþQLPHGLFLQVNLVLVWHPL'RSROQLOR$
,(&
Medical electrical equipment - Part 1-4: General requirements for safety - Collateral
standard: Programmable electrical medical systems (IEC 60601-1-4:1998)
Medizinische elektrische Geräte - Teil 1-4: Allgemeine Festlegungen für die Sicherheit -
Ergänzungsnorm: Programmierbare elektrische medizinische Systeme (IEC 60601-1-
4:1998)
Appareils électromédicaux - Partie 1-4: Règles générales de sécurité - Norme
collatérale: Systèmes électromédicaux programmables (CEI 60601-1-4:1998)
Ta slovenski standard je istoveten z: EN 60601-1-4:1996/A1:1999
ICS:
11.040.01 Medicinska oprema na Medical equipment in general
splošno
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
SIST EN 60601-1-4:1998/A1:2002 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN 60601-1-4:1998/A1:2002

---------------------- Page: 2 ----------------------

SIST EN 60601-1-4:1998/A1:2002

---------------------- Page: 3 ----------------------

SIST EN 60601-1-4:1998/A1:2002

---------------------- Page: 4 ----------------------

SIST EN 60601-1-4:1998/A1:2002
NORME CEI
INTERNATIONALE IEC
60601-1-4
INTERNATIONAL
1996
STANDARD
AMENDEMENT 1
AMENDMENT 1
1999-10
Amendement 1
Appareils électromédicaux –
Partie 1-4:
Règles générales de sécurité –
Norme collatérale: Systèmes électromédicaux
programmables
Amendment 1
Medical electrical equipment –
Part 1-4:
General requirements for safety – Collateral
standard: Programmable electrical medical
systems
 IEC 1999 Droits de reproduction réservés  Copyright - all rights reserved
International Electrotechnical Commission 3, rue de Varembé Geneva, Switzerland
Telefax: +41 22 919 0300 e-mail: inmail@iec.ch IEC web site http://www.iec.ch
CODE PRIX
Commission Electrotechnique Internationale
H
PRICE CODE
International Electrotechnical Commission
Pour prix, voir catalogue en vigueur
For price, see current catalogue

---------------------- Page: 5 ----------------------

SIST EN 60601-1-4:1998/A1:2002
60601-1-4 Amend. 1 © IEC:1999 – 3 –
FOREWORD
This amendment has been prepared by IEC technical committee 62: Electrical equipment in
medical practice.
The text of this amendment is based on the following documents:
FDIS Report of voting
62/114/FDIS 62/120/RVD
Full information on the voting for the approval of this amendment can be found in the report on
voting indicated in the above table.
–––––––––––––
Page 3
CONTENTS
Replace title of annex DDD by the following:
DDD DEVELOPMENT LIFE-CYCLE. 49
Page 9
INTRODUCTION
Replace the third dash by the following:
– methods by which SAFETY is assured;
Page 15
AFETY INTEGRITY
2.201.12 S :
Replace this definition by the following:
2.201.12 Not used.
Page 17
6 Identification, marking and documents
6.8 ACCOMPANYING DOCUMENTS
Replace 6.8.201 by the following:
6.8.201 All relevant information regarding significant RESIDUAL RISK including descriptions of
the HAZARDS and any actions by the OPERATOR or the USER necessary to avoid/mitigate them
INSTRUCTIONS FOR USE RISK MANAGEMENT FILE
shall be placed in both the and the .

---------------------- Page: 6 ----------------------

SIST EN 60601-1-4:1998/A1:2002
60601-1-4 Amend. 1 © IEC:1999 – 5 –
Add the following new subclause 6.8.202:
6.8.202 ACCOMPANYING DOCUMENTS for the PEMS shall identify, as a minimum, the
MANUFACTURER and a unique identifier such as revision level and date of release/issue.
NOTE Information pertaining to any specific EQUIPMENT that software is intended to be used in conjunction with,
and a means by which the MANUFACTURER can be contacted, can be located on the package or in the INSTRUCTIONS
FOR USE so that it is available to the USER independently of the software operation.
52 Abnormal operation and fault conditions
52.201.3c)
Replace 52.201.3 c) by the following:
c) reference to the SAFETY measures, used to eliminate or control the RISK of the HAZARD;
Page 19
Figure 201
Amend the box "VALIDATION methods and results 52.210.6" to "VALIDATION methods and results
52.210.7".
Amend the box "VERIFICATION plan 52.210.2" to "VALIDATION plan 52.210.2".
Amend, within the lower right-hand corner of the figure, the text "VERIFICATION methods and
VERIFICATION
results 52.209.3" to "Methods, techniques and results of the 52.209.4".
Page 21
52.203 DEVELOPMENT LIFE-CYCLE
Add the following new subclause 52.203.6:
52.203.6 Where appropriate, a defined system for problem resolution within and between all
phases and tasks of the DEVELOPMENT LIFE CYCLE shall be developed and maintained as part of
RISK MANAGEMENT FILE
the . Depending upon the problem, the system may have the following
characteristics:
– be defined as a part of the DEVELOPMENT LIFE-CYCLE;
– allow the reporting of potential or existing SAFETY and/or performance problems;
– include an assessment of each problem for associated RISKS;
– identify the criteria (SAFETY and/or performance) that have to be met for the issue to be
closed;
– identify the action to be taken to resolve each problem;
– identify VALIDATION methods for each action;
– identify the steps taken for VERIFICATION of continuing compliance.

---------------------- Page: 7 ----------------------

SIST EN 60601-1-4:1998/A1:2002
60601-1-4 Amend. 1 © IEC:1999 – 7 –
Page 21
52.204.3.1 HAZARD ANALYSIS
Replace on page 23, in subclause 52.204.3.1.5, the first dash by the following:
– human factors including ergonomic limitations;
Page 25
52.204.4 RISK control
Add, in subclause 52.204.4.3, the following new sentence:
The likelihood that the means for RISK reduction will perform correctly shall be specified
quantitatively or qualitatively; see annex CCC.
52.206 Requirement specification
Replace 52.206.3 by the following new subclause 52.206.3:
52.206.3 The requirement specification shall include the information necessary to assure that
RISK control measures satisfactorily reduce the identified RISKS.
Page 27
52.207 Architecture
Replace 52.207.3 by the following new subclause 52.207.3:
52.207.3 Where appropriate, the architecture specification of a PEMS and its subsystems shall
address the RISK CONTROL requirements by reducing the corresponding likelihood of the HAZARD
or by reducing the SEVERITY of the HAZARD or both.
Add the following new subclauses 52.207.4 and 52.207.5:
52.207.4 Where appropriate, to reduce the likelihood of the HAZARD, the architecture
specification shall make use of:
a) highly reliable components;
b) fail-safe functions;
c) redundancy;
d) diversity;
e) defensive design;
f) limits on potentially hazardous effects, for example by restricting the available output power
and/or by introducing means to limit the travel of actuators.

---------------------- Page: 8 ----------------------

SIST EN 60601-1-4:1998/A1:2002
60601-1-4 Amend. 1 © IEC:1999 – 9 –
52.207.5 The architecture specification shall take the following into consideration:
a) allocation of RISK control measures to subsystems and components of the PEMS;

...

Questions, Comments and Discussion

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

This May Also Interest You

SIST
SIST EN IEC 81001-5-1:2022(Main)
Health software and health IT systems safety, effectiveness and security - Part 5-1: Security - Activities in the product life cycle (IEC 81001-5-1:2021)
EN IEC 81001-5-1:2022

1.1 Purpose
This document defines the LIFE CYCLE requirements for development and maintenance of HEALTH SOFTWARE needed to support conformity to IEC 62443-4-1 - taking the specific needs for HEALTH SOFTWARE into account. The set of PROCESSES, ACTIVITIES, and TASKS described in this document establishes a common framework for secure HEALTH SOFTWARE LIFE CYCLE PROCESSES.
[Fig. 1]
The purpose is to increase the information SECURITY of HEALTH SOFTWARE by establishing certain ACTIVITIES and TASKS in the HEALTH SOFTWARE LIFE CYCLE PROCESSES and also by increasing the SECURITY of SOFTWARE LIFE CYCLE PROCESSES themselves.
It is important to maintain an appropriate balance of the key properties SAFETY, effectiveness and SECURITY as discussed in IEC 81001-1.
This document excludes specification of ACCOMPANYING DOCUMENTATION contents.
1.2 Field of application
This document applies to the development and maintenance of HEALTH SOFTWARE by a MANUFACTURER, but recognizes the critical importance of bi-lateral communication with organizations (e.g. HDOs) who have SECURITY responsibilities for the HEALTH SOFTWARE and the systems it is incorporated into, once the software has been developed and released. The IEC/ISO 81001-5 series of standards (for which this is part 1, is therefore being designed to include future parts addressing SECURITY that apply to the implementation, operations and use phases of the LIFE CYCLE for organizations such as HDOs.
Medical device software is a subset of HEALTH SOFTWARE. Therefore, this document applies to:
− Software as part of a medical device;
− Software as part of hardware specifically intended for health use;
− Software as a medical device (SaMD); and
− Software-only PRODUCT for other health use.
Note: In this document, the scope of software considered part of the LIFE CYCLE ACTIVITIES for secure HEALTH SOFTWARE is larger and includes more software (drivers, platforms, operating systems) than for SAFETY, because for SECURITY the focus will be on any use including foreseeable unauthorized access rather than just the INTENDED USE.
[Fig. 2]
1.3 Conformance
HEALTH SOFTWARE conformance with this document is defined as implementing all of the PROCESSES, ACTIVITIES, and TASKS identified in the normative parts of this document - with the exception of Annex F.
Conformance of TRANSITIONAL HEALTH SOFTWARE with Annex F of this document is defined as only implementing the PROCESSES, ACTIVITIES, and TASKS identified in Annex F of this document.
Conformance is determined by inspection and establishing traceability of the PROCESSES, ACTIVITIES and TASKS required.
The quality management system may be implemented according to ISO 13485 or other equivalent quality management system standards.
IEC 62304 specifies ACTIVITIES, based on the software SAFETY classification. The required ACTIVITIES are indicated in the normative text of IEC 62304 as "[Class A, B, C]", "[Class B, C]" or "[Class C]", indicating that they are required selectively depending on the classification of the software to which they apply. The requirements in this document have a special focus on information SECURITY and therefore do not follow the concept of SAFETY classes. For conformity to this document the selection of ACTIVITIES is independent of SAFETY classes.
Implementing the PROCESSES, ACTIVITIES and TASKS specified in this document is sufficient to implement the PROCESS requirements of IEC 62443-4-1. MANUFACTURERS may implement the specifications for Annex E in order to achieve full conformity to IEC 62443-4-1.
This document requires establishing one or more PROCESSES that comprise of identified ACTIVITIES. The LIFE CYCLE PROCESSES shall implement these ACTIVITIES. None of the requirements in this document requires to implement these ACTIVITIES as one single PROCESS or as separate PROCESSES. The ACTIVITIES specified in this document will typically be part of an existing LIFE CYCLE PROCESS.

  • Standard
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN IEC 80001-1:2022(Main)
Application of risk management for IT-networks incorporating medical devices - Part 1: Safety, effectiveness and security in the implementation and use of connected medical devices or connected health software (IEC 80001-1:2021)
EN IEC 80001-1:2021

This document specifies general requirements for ORGANIZATIONS in the application of RISK
MANAGEMENT before, during and after the connection of a HEALTH IT SYSTEM within a HEALTH IT
INFRASTRUCTURE, by addressing the KEY PROPERTIES of SAFETY, EFFECTIVENESS and SECURITY
whilst engaging appropriate stakeholders.

  • Standard
    39 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN 80001-1:2011
Application of risk management for IT-networks incorporating medical devices - Part 1: Roles, responsibilities and activities (IEC 80001-1:2010)
EN 80001-1:2011

Recognizing that MEDICAL DEVICES are incorporated into IT-NETWORKS to achieve desirable benefits (for example, INTEROPERABILITY), this international standard defines the roles, responsibilities and activities that are necessary for RISK MANAGEMENT of IT-NETWORKS incorporating MEDICAL DEVICES to address SAFETY, EFFECTIVENESS and DATA AND SYSTEMSECURITY (the KEY PROPERTIES). This international standard does not specify acceptable RISK levels.
NOTE 1 The RISK MANAGEMENT activities described in this standard are derived from those in ISO 14971 [4]. The relationship between ISO 14971 and this standard is described in Annex A.
This standard applies after a MEDICAL DEVICE has been acquired by a RESPONSIBLE ORGANIZATION and is a candidate for incorporation into an IT-NETWORK.
NOTE 2 This standard does not cover pre-market RISK MANAGEMENT.
This standard applies throughout the life cycle of IT-NETWORKS incorporating MEDICAL DEVICES.
NOTE 3 The life cycle management activities described in this standard are very similar to those of
ISO/IEC 20000-2 [10]. The relationship between ISO/IEC 20000-2 and this standard is described in Annex D.
This standard applies where there is no single MEDICAL DEVICE manufacturer assuming responsibility for addressing the KEY PROPERTIES of the IT-NETWORK incorporating a MEDICAL
DEVICE.
NOTE 4 If a single manufacturer specifies a complete MEDICAL DEVICE that includes a network, the installation or assembly of the MEDICAL DEVICE according to the manufacturer’s ACCOMPANYING DOCUMENTS is not subject to the provisions of this standard regardless of who installs or assembles the MEDICAL DEVICE.
NOTE 5 If a single manufacturer specifies a complete MEDICAL DEVICE that includes a network, additions to that MEDICAL DEVICE or modification of the configuration of that MEDICAL DEVICE, other than as specified by the manufacturer, is subject to the provisions of this standard.
This standard applies to RESPONSIBLE ORGANIZATIONS, MEDICAL DEVICE manufacturers and
providers of other information technology for the purpose of RISK MANAGEMENT of an ITNETWORK incorporating MEDICAL DEVICES as specified by the RESPONSIBLE ORGANIZATION.
This standard does not apply to personal use applications where the patient, OPERATOR and RESPONSIBLE ORGANIZATION are one and the same person.
NOTE 6 In cases where a MEDICAL DEVICE is used at home under the supervision or instruction of the provider, that provider is deemed to be the RESPONSIBLE ORGANIZATION. Personal use where the patient acquires and uses a MEDICAL DEVICE without the supervision or instruction of a provider is out of scope of this standard. This standard does not address regulatory or legal requirements.

  • Standard
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN IEC 81001-5-1:2022(Main)
Health software and health IT systems safety, effectiveness and security - Part 5-1: Security - Activities in the product life cycle (IEC 81001-5-1:2021)
EN IEC 81001-5-1:2022

1.1 Purpose
This document defines the LIFE CYCLE requirements for development and maintenance of HEALTH SOFTWARE needed to support conformity to IEC 62443-4-1 - taking the specific needs for HEALTH SOFTWARE into account. The set of PROCESSES, ACTIVITIES, and TASKS described in this document establishes a common framework for secure HEALTH SOFTWARE LIFE CYCLE PROCESSES.
[Fig. 1]
The purpose is to increase the information SECURITY of HEALTH SOFTWARE by establishing certain ACTIVITIES and TASKS in the HEALTH SOFTWARE LIFE CYCLE PROCESSES and also by increasing the SECURITY of SOFTWARE LIFE CYCLE PROCESSES themselves.
It is important to maintain an appropriate balance of the key properties SAFETY, effectiveness and SECURITY as discussed in IEC 81001-1.
This document excludes specification of ACCOMPANYING DOCUMENTATION contents.
1.2 Field of application
This document applies to the development and maintenance of HEALTH SOFTWARE by a MANUFACTURER, but recognizes the critical importance of bi-lateral communication with organizations (e.g. HDOs) who have SECURITY responsibilities for the HEALTH SOFTWARE and the systems it is incorporated into, once the software has been developed and released. The IEC/ISO 81001-5 series of standards (for which this is part 1, is therefore being designed to include future parts addressing SECURITY that apply to the implementation, operations and use phases of the LIFE CYCLE for organizations such as HDOs.
Medical device software is a subset of HEALTH SOFTWARE. Therefore, this document applies to:
− Software as part of a medical device;
− Software as part of hardware specifically intended for health use;
− Software as a medical device (SaMD); and
− Software-only PRODUCT for other health use.
Note: In this document, the scope of software considered part of the LIFE CYCLE ACTIVITIES for secure HEALTH SOFTWARE is larger and includes more software (drivers, platforms, operating systems) than for SAFETY, because for SECURITY the focus will be on any use including foreseeable unauthorized access rather than just the INTENDED USE.
[Fig. 2]
1.3 Conformance
HEALTH SOFTWARE conformance with this document is defined as implementing all of the PROCESSES, ACTIVITIES, and TASKS identified in the normative parts of this document - with the exception of Annex F.
Conformance of TRANSITIONAL HEALTH SOFTWARE with Annex F of this document is defined as only implementing the PROCESSES, ACTIVITIES, and TASKS identified in Annex F of this document.
Conformance is determined by inspection and establishing traceability of the PROCESSES, ACTIVITIES and TASKS required.
The quality management system may be implemented according to ISO 13485 or other equivalent quality management system standards.
IEC 62304 specifies ACTIVITIES, based on the software SAFETY classification. The required ACTIVITIES are indicated in the normative text of IEC 62304 as "[Class A, B, C]", "[Class B, C]" or "[Class C]", indicating that they are required selectively depending on the classification of the software to which they apply. The requirements in this document have a special focus on information SECURITY and therefore do not follow the concept of SAFETY classes. For conformity to this document the selection of ACTIVITIES is independent of SAFETY classes.
Implementing the PROCESSES, ACTIVITIES and TASKS specified in this document is sufficient to implement the PROCESS requirements of IEC 62443-4-1. MANUFACTURERS may implement the specifications for Annex E in order to achieve full conformity to IEC 62443-4-1.
This document requires establishing one or more PROCESSES that comprise of identified ACTIVITIES. The LIFE CYCLE PROCESSES shall implement these ACTIVITIES. None of the requirements in this document requires to implement these ACTIVITIES as one single PROCESS or as separate PROCESSES. The ACTIVITIES specified in this document will typically be part of an existing LIFE CYCLE PROCESS.

  • Standard
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN IEC 80001-1:2022(Main)
Application of risk management for IT-networks incorporating medical devices - Part 1: Safety, effectiveness and security in the implementation and use of connected medical devices or connected health software (IEC 80001-1:2021)
EN IEC 80001-1:2021

This document specifies general requirements for ORGANIZATIONS in the application of RISK
MANAGEMENT before, during and after the connection of a HEALTH IT SYSTEM within a HEALTH IT
INFRASTRUCTURE, by addressing the KEY PROPERTIES of SAFETY, EFFECTIVENESS and SECURITY
whilst engaging appropriate stakeholders.

  • Standard
    39 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN ISO 11073-10418:2014/AC:2017(Corrigendum)
Health informatics - Personal health device communication - Part 10418: Device specialization - International Normalized Ratio (INR) monitor - Technical Corrigendum 1 (ISO/IEEE 11073-10418:2014/Cor 1:2016)
EN ISO 11073-10418:2014/AC:2016

ISO corr

  • Corrigendum
    20 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN ISO 11073-10418:2014(Main)
Health informatics - Personal health device communication - Part 10418: Device specialization: International Normalized Ratio (INR) monitor (ISO 11073-10418:2014, Corrected version 2014-05-01)
EN ISO 11073-10418:2014

The scope of this standard is to establish a normative definition of communication between personal telehealth International Normalized Ratio (INR) devices (agents) and managers (e.g. cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability. It leverages work done in other ISO/IEEE 11073 standards including existing terminology, information profiles, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of functionality of INR devices. In the context of personal health devices, INR monitoring refers to the measurement of the prothrombin time (PT) that is used to assess the level of anticoagulant therapy and its presentation as the International Normalized Ratio compared to the prothrombin time of normal blood plasma. Applications of the INR monitor include the management of the therapeutic level of anticoagulant used in the treatment of a variety of conditions. This standard provides the data modeling and its transport shim layer according to IEEE Std 11073-20601aTM-2010 and does not specify the measurement method.

  • Standard
    76 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    76 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN 80001-1:2011
Application of risk management for IT-networks incorporating medical devices - Part 1: Roles, responsibilities and activities (IEC 80001-1:2010)
EN 80001-1:2011

Recognizing that MEDICAL DEVICES are incorporated into IT-NETWORKS to achieve desirable benefits (for example, INTEROPERABILITY), this international standard defines the roles, responsibilities and activities that are necessary for RISK MANAGEMENT of IT-NETWORKS incorporating MEDICAL DEVICES to address SAFETY, EFFECTIVENESS and DATA AND SYSTEMSECURITY (the KEY PROPERTIES). This international standard does not specify acceptable RISK levels.
NOTE 1 The RISK MANAGEMENT activities described in this standard are derived from those in ISO 14971 [4]. The relationship between ISO 14971 and this standard is described in Annex A.
This standard applies after a MEDICAL DEVICE has been acquired by a RESPONSIBLE ORGANIZATION and is a candidate for incorporation into an IT-NETWORK.
NOTE 2 This standard does not cover pre-market RISK MANAGEMENT.
This standard applies throughout the life cycle of IT-NETWORKS incorporating MEDICAL DEVICES.
NOTE 3 The life cycle management activities described in this standard are very similar to those of
ISO/IEC 20000-2 [10]. The relationship between ISO/IEC 20000-2 and this standard is described in Annex D.
This standard applies where there is no single MEDICAL DEVICE manufacturer assuming responsibility for addressing the KEY PROPERTIES of the IT-NETWORK incorporating a MEDICAL
DEVICE.
NOTE 4 If a single manufacturer specifies a complete MEDICAL DEVICE that includes a network, the installation or assembly of the MEDICAL DEVICE according to the manufacturer’s ACCOMPANYING DOCUMENTS is not subject to the provisions of this standard regardless of who installs or assembles the MEDICAL DEVICE.
NOTE 5 If a single manufacturer specifies a complete MEDICAL DEVICE that includes a network, additions to that MEDICAL DEVICE or modification of the configuration of that MEDICAL DEVICE, other than as specified by the manufacturer, is subject to the provisions of this standard.
This standard applies to RESPONSIBLE ORGANIZATIONS, MEDICAL DEVICE manufacturers and
providers of other information technology for the purpose of RISK MANAGEMENT of an ITNETWORK incorporating MEDICAL DEVICES as specified by the RESPONSIBLE ORGANIZATION.
This standard does not apply to personal use applications where the patient, OPERATOR and RESPONSIBLE ORGANIZATION are one and the same person.
NOTE 6 In cases where a MEDICAL DEVICE is used at home under the supervision or instruction of the provider, that provider is deemed to be the RESPONSIBLE ORGANIZATION. Personal use where the patient acquires and uses a MEDICAL DEVICE without the supervision or instruction of a provider is out of scope of this standard. This standard does not address regulatory or legal requirements.

  • Standard
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST-TP CEN/TR 12349:2023(Main)
Mechanical vibration - Guide to the health effects of vibration on the human body
CEN/TR 12349:2023

The aim of this CEN report is to provide information on the possible adverse health effects caused by exposure to vibration at work.  the report addresses manufacturers as well as employers and employees using vibrating machinery in order to improve their understanding of the possible health problems arising from occupational exposure to vibration.

  • Technical report
    17 pages
    English language
    sale 10% off
    e-Library read for
    1 day
SIST
SIST EN ISO 80004-1:2023(Main)
Nanotechnologies - Vocabulary - Part 1: Core vocabulary (ISO 80004-1:2023)
EN ISO 80004-1:2023

This document defines core terms in the field of nanotechnology. This document is intended to facilitate communication between organizations and individuals in industry and those who interact with them.

  • Standard
    24 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    25 pages
    English language
    sale 10% off
    e-Library read for
    1 day