Informationsteknik, kontorsutrustning

This document describes the key actors in the eCall chain of service provision in hybrid circuit switched/packet switched network environments as: 1) In-Vehicle System (IVS)/vehicle, 2) Mobile Network Operator (MNO), 3) Public Safety Answering Point (PSAP), and to provide conformance tests for actor groups 1) – 3). NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service. NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this deliverable. This is because the core TPS-eCall standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider. NOTE 3 These conformance tests are partly based on the appropriate conformance tests from EN 16454 and CEN/prEN 17240. This deliverable therefore adapts and revises Conformance Test Protocols (CTP) from EN 16454 and CEN/prEN 17240 for hybrid circuit switched/packet switched network environments. This document complements EN 16454 and CEN/prEN 17240 and provides a suite of conformance tests for IVS equipment, MNOs and PSAPs, required to ensure and demonstrate compliance with CEN/prEN 17905. The scope covers conformance testing of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.

This document provides the principles, concepts, terms and definitions for health software and health IT systems, key properties of safety, effectiveness and security, across the full life cycle, from concept to decommissioning, as represented in Figure 1. It also identifies the transition points in the life cycle where transfers of responsibility occur, and the types of multi-lateral communication that are necessary at these transition points. This document also establishes a coherent concepts and terminology for other standards that address specific aspects of the safety, effectiveness, and security (including privacy) of health software and health IT systems.

This document is applicable to all parties involved in the health software and health IT systems life cycle including the following:

a) Organizations, health informatics professionals and clinical leaders designing, developing, integrating, implementing and operating health software and health IT systems – for example health software developers and medical device manufacturers, system integrators, system administrators (including cloud and other IT service providers);

b) Healthcare service delivery organizations, healthcare providers and others who use health software and health IT systems in providing health services;

c) Governments, health system funders, monitoring agencies, professional organizations and customers seeking confidence in an organization’s ability to consistently provide safe, effective and secure health software, health IT systems and services;

d) Organizations and interested parties seeking to improve communication in managing safety, effectiveness and security risks through a common understanding of the concepts and terminology used in safety, effectiveness and security management;

e) Providers of training, assessment or advice in safety, effectiveness and security risk management for health software and health IT systems;

f) Developers of related safety, effectiveness and security standards.

This document specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This document is not intended to specify the internal architecture or database design of such systems. The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person's care. Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people's records, are not the focus of this document but such secondary uses could also find the document useful. This document defines a set of interfaces to request and provide: — an EHR_EXTRACT for a given subject of care as defined in ISO 13606-1; — one or more ARCHETYPE(s) as defined in ISO 13606-2; — an EHR_AUDIT_LOG_EXTRACT for a given subject of care as defined in ISO 13606-4. This document defines the set of interactions to request each of these artefacts, and to provide the data to the requesting party or to decline the request. An interface to query an EHR or populations of EHRs, for example for clinical audit or research, are beyond its scope, although provision is made for certain selection criteria to be specified when requesting an EHR_EXTRACT which might also serve for population queries. This document defines the Computational Viewpoint for each interface, without specifying or restricting particular engineering approaches to implementing these as messages or as service interfaces. This document effectively defines the payload to be communicated at each interface. It does not specify the particular information that different transport protocols will additionally require, nor the security or authentication procedures that might be agreed between the communicating parties or required by different jurisdictions.

This document comprises multiple human and machine-readable resources with different roles that together define a vocabulary for representing some spatial information according to a data model and extensions to a query language for accessing that information. See the Introduction section 0.4 for details of the parts.

It does not define a comprehensive vocabulary for representing all spatial information: it only defines a core set of classes, properties and datatypes that can be used to construct query patterns. Many useful extensions to this vocabulary are possible, and we intend for the Semantic Web and Geospatial communities to develop additional vocabularies for describing spatial information.