The present document aims to establish the necessary requirements for a QKD module to have a high probability of detecting and responding precisely and timely to attempts of direct physical access, and use or modification of modules inside. The principal objective is to detect any possible penetration with high probability, and resulting in the immediate zeroization of all Critical Security Parameters in plain text.
Quantum key distribution (QKD) comprises technologies that use quantum mechanical effects to distribute private keys to distant partners. The goals of the present document are as follows:
to make precise the nature of the security claim, including its statistical component;
to list meaningful restrictions of adversarial action;
to clarify the difference between security claim of a protocol (based on models) and the security claim of its implementation;
to carefully list all the usual components of a QKD protocol with their critical characterizations.
The present document is intended to specify an Application Programming Interface (API) between a QKD key manager and applications. The function of a QKD key manager is to manage the secure keys produced by an implementation of a QKD protocol and to deliver the identical set of keys, via this API, to the associated applications at the communication end points.
The Use Cases Document shall provide an overview of possible application scenarios in which Quantum Key Distribution (QKD) systems ([i.1]) can be used as building blocks for high security Information and communication technology (ICT) systems.
The present document collects together definitions and abbreviations used in relation to Quantum Key Distribution (QKD) and ETSI ISG-QKD documents. QKD introduces new concepts and technologies to the field of telecommunications and considerable related vocabulary. Many terms derive from the wider fields of quantum physics and classical cryptography but in some cases terms assume a modified or more specific meaning when applied to QKD. The main objectives of the present document are:
to improve the consistency with which terminology and abbreviations are used within ISG-QKD documents;
to provide a reference document to reduce confusion by readers who may not be familiar with QKD.
This document defines the core data set for a patient summary document that supports continuity of care for a person and coordination of their healthcare. It is specifically aimed at supporting the use case’ scenario for ‘unplanned, cross border care’ and is intended to be an international patient summary (IPS). Whilst the data set is minimal and non-exhaustive, it provides a robust, well-defined core set of data items. The tight focus on this use case also enables the IPS to be used in planned care. This means that both unplanned and planned care can be supported by this data set within local and national contexts, thereby increasing its utility and value.
It uses the European Guideline from the eHN as the initial source for the patient summary requirements, then takes into consideration other international patient summary projects to provide an interoperable data set specification that has global application.
This document provides an abstract definition of a Patient Summary from which derived models are implementable. Due to its nature therefore, readers should be aware that the compliance with this document does not imply automatic technical interoperability; this result, enabled by this document, can be reached with the conformity to standards indicated in the associated technical specification and implementation guides.
The scope of this standard is a service-oriented medical device architecture and communication protocol specification for distributed system of Point-of-Care (PoC) medical devices and medical IT systems that need to exchange data or safely control networked PoC medical devices. It identifies the functional components, their communication relationships as well as the binding of the components and communication relationships to protocol specifications.
This Technical Specification (TS) provides implementation guidance to support the use of the International Patient Summary dataset in a European context. The focus of this technical specification takes into consideration European specific jurisdictional requirements, needs and contexts that Europe requires to be satisfied for effective implementation. It addresses both functional and non-functional requirements for the dataset’s interchange. As part of the usability of the International Patient Summary, European perspectives, directives and regulations contextualise and add value to generic reference implementations for use by Member States. The TS applies the refined European Interoperability Framework (ReEIF), which describes legal, organisational, semantic and technological considerations for interoperability. These considerations highlight the eHealth Network’s (eHN) guidance for cross-border care and underpin the care process. The TS formalises principles to support the safe and legitimate use of patient summary data and afford protection for efficient cross-border data interchange within scenarios for unscheduled care. This Technical Specification gives selection criteria and provides examples of various transport formats and terminologies shown to be suitable for interchanging the International Patient Summary dataset. Compliance, deployment & migration Guidance are also included. The TS distinguishes between cross-border only requirements for interchanging the dataset and those that are generally applicable within national borders.
The scope of this project is to define a general object-oriented information model that may be used to structure information and identify services used in point-of-care (POC) medical device communications. The scope is primarily focused on acute care medical devices and the communication of patient vital signs information.
This document specifies the common conventions required for the cart-to-host as well as cart-to-cart interchange of specific patient data (demographic, recording, ...), ECG signal data, ECG measurement and ECG interpretation results. This document specifies the content and structure of the information which is to be interchanged between digital ECG carts and computer ECG management systems, as well as other computer systems where ECG data can be stored
This document specifies the requirements for developing a knowledge base for drug-related problems that cohere with the intended drug use, to be used in rule-based clinical decision support systems (CDSS), such as the criteria for selecting a raw data source and the quality criteria for the development and maintenance for the rules or clinical rules for drug safety. It also describes the process of how to develop a knowledge base, the topics to be considered by the developers of a knowledge base, and it gives guidance on how to do this. This document gives guidelines for the development of a knowledge base: — with rules to enhance decisions and actions in drug-related problems that cohere with the intended drug use; — which can be used by all kinds of healthcare professionals, such as those who prescribe, dispense, administer or monitor medicines; — which can be used in every care setting, including chronic and acute care, primary and specialized care; — which is a repository of evidence/practice bases rules, assessed by experts; — which is meant to be used in conjunction with a medicinal product dictionary; — whose knowledge is structured in rules and therefore to be used in the type of rule-based CDSS. This document does not: — describe the exact content of a knowledge base i.e. the outcome of the process of developing rules. — provide the requirements for a clinical decision support system, the software that uses the knowledge base combined with the patient's data, and presents the outcome of the rules to the healthcare professional. These requirements are described in ISO/DTS 22703[1]. — give the requirements for non-medication knowledge bases. Some aspects of the requirements in this document are general in nature and applicable to other kinds of knowledge bases, but this document does not address all of the requirements of non-medication knowledge bases. [1] Under preparation. Stage at the time of publication: ISO/DTS 22703.
