ITC - Information technology

This document specifies requirements and the minimum actions performed by an evaluator in order to conduct an evaluation using the criteria and evaluation evidence defined in the ISO/IEC 15408 series evaluation.

This document provides guidance for information security controls, based on ISO/IEC 27002, applicable to the provision and use of cloud services. This document provides:
additional guidance for relevant controls specified in ISO/IEC 27002:2022;
additional controls with guidance that specifically relate to cloud services.
This document provides controls and guidance for cloud service customers (CSCs) and cloud service providers (CSPs).
This document is considered to be a horizontal document as it provides a foundation and a common understanding of security regarding the provision and use of cloud services.
NOTE            This document applies to all types of cloud deployment models including the private cloud. When applying this document to the private cloud, the controls and guidance of this document are applicable, although adjustments can be necessary to adapt to the relationships and abilities of an organization’s internal departments.

This document specifies requirements and a standardized framework for specifying objective, repeatable and reproducible evaluation methods and evaluation activities.
This document does not specify how to evaluate, adopt, or maintain evaluation methods and evaluation activities. These aspects are a matter for those originating the evaluation methods and evaluation activities in their particular area of interest.

This document specifies the security assurance requirements of the ISO/IEC 15408 series. It includes the individual assurance components from which the evaluation assurance levels and other packages contained in ISO/IEC 15408-5 are composed, and the criteria for evaluation of Protection Profiles (PPs), PP-Configurations, PP-Modules and Security Targets (STs).

This document gives guidelines for:
a process on privacy impact assessments, and
a structure and content of a PIA report.
It is applicable to all types and sizes of organizations, including public companies, private companies, government entities and not-for-profit organizations.
This document is relevant to those involved in designing or implementing projects, including the parties operating data processing systems and services that process PII.

This document specifies requirements for the required structure and content of security functional components for use during a security evaluation. It includes a catalogue of functional components that meet the common security functionality requirements of many IT products.

This document specifies controls, purpose, and guidance for implementing controls, to meet the requirements identified by a risk and impact assessment related to the protection of personally identifiable information (PII).
In particular, this document specifies requirements and guidance based on ISO/IEC 27002, taking into consideration the controls for processing PII that can be applicable within the context of an organization's information security risk environment(s).
This document is applicable to all types and sizes of organizations acting as PII controllers (as defined in ISO/IEC 29100), including public and private companies, government entities and not-for-profit organizations that process PII, in particular, organizations that do not establish or operate a privacy information management system.

This document establishes the general concepts and principles of information technology (IT) security evaluation. It specifies the general model of evaluation given in this document, which in its entirety is intended to be used as the basis for evaluation of security properties of IT products.
This document provides an overview of all parts of the ISO/IEC 15408 series. It describes the various parts of the ISO/IEC 15408 series i.e.
defines the terms and abbreviations used in all parts of the series; establishes the core concept of a Target of Evaluation (TOE);
describes the evaluation context; and
describes the audience to which the evaluation criteria is addressed.
Additionally, this document introduces the basic security concepts necessary for the evaluation of IT products.

This document incorporates the following main data packages:
-   Dated Production Components;
-   Call;
-   Dated Call;
-   Production Plan;
-   Detecting & Monitoring;
-   Situation;
-   Messaging;
-   Control Action;
-   Operational Event & Incident;
-   Facility Monitoring & Availability;
-   Occupancy.
It is composed of the following parts:
-   main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
-   Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
-   Annex B presenting the model evolution (informative);
-   Annex C detailing the mapping to DATEX-II and SIRI (informative).
-   Annex D, providing details of the significant technical changes between this document and EN 12896 4:2019 (informative).

The document incorporates the following main data packages:
-   Trip Description;
-   Passenger Information Queries.
It is composed of the following parts:
-   main document representing the data model for the concepts shared by the different fare domains covered by Transmodel (normative);
-   Annex A, containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with the definitions (normative);
-   Annex B presenting the model evolution (informative).
-   Annex C, providing details of the significant technical changes between this document and EN 12896 6:2019 (informative).

This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the Cross Industry Invoice in the UN/CEFACT XML syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.

This document incorporates data structures used by all other data domains of Transmodel. It is composed of the following data packages:
-   versions and validity;
-   responsibility;
-   generic framework;
-   reusable components;
-   explicit frames referring to generic data.
The data structures represented in this part are either generic patterns that can be explicitly reused in other domains (e.g., a generic model for version frames, a generic grouping mechanism, etc.) or are referenced by different other parts (e.g., service calendar model).
This document itself is composed of the following parts:
-   main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
-   Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts present in the main document, together with their definitions (normative);
-   Annex B, indicating the data model evolutions (informative),
-   Annex C, presenting the Transmodel development history (informative),
-   Annex D, describing all conventions, methodology and notations for conceptual modelling (informative),
-   Annex E, providing a clear overview to help readers understand the core principles, structure, and purpose of Transmodel (informative),
-   Annex F, providing information on the Functional domains and Modes of operation (informative).
-   Annex G, providing details of the significant technical changes between this document and EN 12896-1:2015 (informative).

This document entitled “Public transport – Reference data model – Part 5: Fare Management” is composed of the following data packages:
⎯ Fare Structure;
⎯ Access Right Assignment;
⎯ Fare Pricing;
⎯ Sales Description;
⎯ Sales Transaction;
⎯ Fare Roles;
⎯ Validation and Control;
⎯ Explicit Frames for Fares.
This document itself is composed of the following parts:
⎯ Main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
⎯ Annex A, containing the data dictionary and attribute tables, i.e., the list of all the concepts presented in the main document together with the definitions (normative);
⎯ Annex B, presenting the model evolution (informative).
⎯ Annex C, providing details of the significant technical changes between this document and EN 12896-5:2019 (informative)

This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the ISO/IEC 9735 (UN/EDIFACT) syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents.

The CEN/TS 18212 series [4] specifies a generic framework for the establishment of requirements and their evaluation methodology for biometric products. The requirements depend on the biometric mode considered, and are adapted to each scenario, through the definition of a variety of application profiles.
The CEN/TS 18212 series [4] specifies the evaluation methodology, the individual TESTs, and the application profiles (with their particular requirements).
This document is focussed on face biometrics, and provides the specifics of this biometric mode for the application of all the specifications provided in parts 1 till 3 from CEN/TS 18212 series [4]. It also defines a set of application profiles, that detail the applicable TESTs, the evaluation parameters and the assessment criteria.
In detail, this document defines, for face biometric products:
-   general aspects of a face biometric product;
-   common resources needed for the evaluation;
-   each of the possible TESTs to be applied;
-   application profiles for different kinds of face biometrics products.
NOTE 1   National regulations and requirements can apply.
NOTE 2   Regarding biometrics for public sector applications, see also BSI TR 03121 [10] which can apply.
NOTE 3   For an overview of sectors addressed in the Cybersecurity Act, see Regulation (EU) 2019/881[11].
NOTE 4   This part defines all potential TESTs that could be applicable when evaluating the functionality of a biometric product using this biometric mode. It will be the relevant application profile (3.1.1), the one that will specify which of these TESTs are applicable.
The following topics are left out of the scope of this document:
-   Vulnerability assessment of the storage system used for the biometric reference/s.
-   Vulnerability assessment of communication protocols and interfaces dealing with the operation of the biometric product.
-   Evaluation of the performance of human operators in terms of identity proofing.
-   Validation of documents providing the biometric reference

This document specifies data model structures that are applicable for traffic management applications in the urban environment. This document addresses data concepts to support the exchange of traffic management plans, rerouting and extensions of the existing DATEX II core model to better support application to the urban environment.

This document incorporates the following main data packages:
-   Network Description;
-   Fixed Object;
-   Tactical Planning Components;
-   Explicit Frame.
It is composed of the following parts:
-   main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
-   Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
-   Annex B presenting the model evolution (informative).
-   Annex C, providing details of the significant technical changes between this document and EN 12896-2:2016 (informative).

The present document is composed of the following data packages:
— journey and Interchange;
— vehicle Journey Assignment;
— journey Times;
— block and Vehicle Service;
— dated Journey;
— explicit Frame.
This document itself is composed of the following parts:
— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
— Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative);
— Annex B presenting the model evolution (informative);
— Annex C, providing details of the significant technical changes between this document and EN 12896-1:2015 (informative)

This document covers:
— Provision of a catalogue of fares
— Request for specific fare offers (including specific search criteria),
— Selection of one or several formal offers by the customer (pre-purchase),
— Initiation of the purchase,
— Commitment to buy,
— Reservation of a place on a specific journey,
— Reception of evidence of the purchase,
— Management after purchase (basic after-sale actions),
— All interactions that can be related to a persistent identity.
These functions can be seen as the minimum required for the data flow of reservation from the travellers’ perspective.
Though some of the studied APIs have functions beyond just reservation and involving other parties, the following activities are not in scope of this document nor the CoRoM project:
— Creation and distribution of the travel document,
— Travel planning,
— Payment interfaces with banking information systems,
— Validation of purchased access rights during travel,
— Control of purchased access rights during travel

This document is composed of the following data packages:
— Driver;
— Driver Schedule;
— Rostering;
— Personnel Disposition;
— Driver Control Action.
This document itself is composed of the following parts:
— main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative);
— Annex A containing the data dictionary and attribute tables, i.e., the list of all the concepts presented in the main document together with their definitions (normative);
— Annex B presenting the model evolution (informative).
— Annex C, providing details of the significant technical changes between this document and EN 12896-7:2019 (informative)

This document defines and describes the concept of on-boarding of person identification data (PID) within a Wallet. The scope of this document includes cases where a natural person is the User in control of a Wallet. This includes a natural person who is in control of their own information, as well as natural persons who control information to represent another natural person or a legal person. This document considers a single set of PID attributes linked to a single Wallet Unit. This does not exclude the issuance of multiple PIDs representing the same set of PID attributes, e.g. batch issuance.
It also provides the general workflow, the roles and responsibilities at stake, and links the on-boarding with the Level of Assurance concept underpinning eIDAS [1];
The scope of this document includes cases where a natural person is the User in control of a wallet. This includes a natural person who is in control of their own data as well as natural persons who control data to represent another natural person or legal person.
EXAMPLE     If a natural person represents a legal person, the PID provider can issue a "representation PID" in an own Wallet Unit for representation purposes controlled by the natural person Wallet User. The "representation PID" is a kind of attestation which contains PID about the natural person (representative) and about the legal person (representee).
This document is limited to the on-boarding of an unique set of person identification data, complying with the legal provisions of eIDAS [1], in particular (1) issued in accordance with Union or National laws, and (2) conformant with the relevant implementing act [5].
The following aspects are out of scope of this document:
—   the on-boarding of person identification data within a Wallet where the User is a legal person;
—   other types of on-boarding, such as:
—   provisioning of person identification data after revocation, expiration or deletion;
—   addition of other Attributes (under the shape of attestations) in accordance with the requirement of Level of Assurance “High” which are not part of the set of person identification data but are part of the legal identity under National’s laws;
—   management of person identification data (deletion, update, etc.);
—   provisioning of person identification data which is not compliant with the relevant implementing act [5];
—   provisioning of a partial set of person identification data;
—   provisioning of supplemental set(s) of person identification data (multiple PIDs);

This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the UBL syntax. For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.

This document provides the minimum requirements for the knowledge and skills of assessment body testers and validators performing testing activities and validating activities for a conformance scheme using ISO/IEC 19790 and ISO/IEC 24759.

This document describes a cybersecurity evaluation methodology that can be implemented using pre-defined time and workload resources, for ICT products. It is intended to be applicable for all three assurance levels defined in the CSA (i.e. basic, substantial and high).
The methodology comprises different evaluation blocks including assessment activities that comply with the evaluation requirements of the CSA for the mentioned three assurance levels. Where appropriate, it can be applied both to third-party evaluation and self-assessment.

This document provides packages of security assurance and security functional requirements that are intended to be useful in support of common usage by stakeholders.
The users of this document can include consumers, developers and evaluators of secure IT products.

This document provides requirements and recommendations related to the concepts required to associate pharmaceutical products or groups of pharmaceutical products with an appropriate set of PhPID(s) in accordance with ISO 11616.
Pharmaceutical product identifiers and the related elements are intended to represent pharmaceutical products as defined within a medicinal product by a medicines regulatory authority. While the ISO standards on IDMP can be applied to off-label usage of medicinal products, such applications are currently outside of the scope of this document.
Reference to ISO 11238, ISO 11239, ISO 11240, ISO 11615, HL7 V3 messaging standards (HL7 Reference Information Model (RIM)[8], HL7 Common Product Model (CPM)[9] and HL7 V3 Structured Product Labelling (SPL)[10], and HL7 FHIR[11] can be applied for pharmaceutical product information in the context of this document.

The CEN/TS 18212 series specifies a generic framework for the establishment of requirements and their evaluation methodology for biometric products. The requirements depend on the biometric mode considered and are adapted to each scenario, through the definition of a variety of application profiles.
The CEN/TS 18212 series specifies the evaluation methodology, the individual tests and the application profiles (with their particular requirements).
This document specifies:
—   The different kind of evaluations to be performed.
—   The terms used during the description of the tests to be applied.
—   The parameters used, whose values are defined by each application profile, for each of the individual tests.
—   Test data used, and considerations dealing with personal data protection.
—   How to perform technology evaluations.
—   Execution flow for functionality scenario evaluations.
—   Execution flow for attack resistance evaluations.
NOTE 1   Future parts of the CEN/TS series are planned to address the specifics of each biometric mode.
For each of these modalities, this document specifies application-independent tests, as well as a set of application profiles, that detail the applicable tests, the evaluation parameters and the passing criteria.
The CEN/TS 18212 series can be taken by any certification body and/or sector, to define and evaluate the requirements for their biometric products within their selected applications.
NOTE 2   National regulations and requirements can apply.
NOTE 3   Regarding biometrics for public sector applications, see also BSI TR-03121 [8] which can apply.
NOTE 4   For an overview of sectors addressed in the Cybersecurity Act, see Regulation (EU) 2019/881 [2].

This document describes the transaction information requirements of the transactions used in the basic
collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies.
For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements.
The document describes the following transactions:
1) Catalogue;
2) Catalogue Response
3) Pre-award Catalogue Request
4) Pre-award Catalogue
5) Shopping Cart
How to claim compliance to a transaction is described in paragraph 6.
How to claim conformance to a transaction is described in paragraph 6.

This document defines the purpose, governance and functional requirements of the eInvoicing Registry for CIUS and Extension Specifications. This document is not to be confused with other business / project focused Technical Specifications. It follows CEN rules and will be published as a CEN document with normative statements.
A key part of this document is to provide a functional specification, which will describe the various functions of eInvoice Registry Services.
The Registry is intended to serve as a structured, transparent and publicly accessible repository that facilitates the discovery, registration and management of eInvoicing Specifications that either restrict the conditional elements of the Core Invoice Model and/or extend it in conformance with Part 5 Extension Methodology.
The scope of this document includes:
- Definition of Registry Services - the structure and capabilities of the Registry including the types of artefacts it stores or references, e.g. CIUS, Extension Specifications, Validation Artefacts and Services, and Code Lists;
- Governance Model - the roles and responsibilities of entities involved in managing and maintaining the Registry;
- Submission and Verification Processes - how Specifications are submitted, reviewed and verified for inclusion in the Registry;
- Functional Specification - the required functionality, processes and procedures that enable the Registry to operate efficiently.

This document provides requirements on identification and labelling of medicinal products from the point of manufacturing of packaged medicinal product to the point of dispensing the product.
This document outlines commonly accepted international practices for automatic identification and data capture (AIDC) barcoding solutions for applications and applies to manufacturers, distributors, healthcare facilities and all parties involved in labelling and distribution of packaged medicinal products. These users can, however, consider the coding interoperability requirements for other AIDC technologies, e.g. radio frequency identification (RFID); that technology is not addressed in this document except as for information.

This document defines and establishes a framework for access management (AM) and the secure management of the process to access information and information and communications technologies (ICT) resources, associated with the accountability of a subject within some contexts.
This document provides concepts, terms and definitions applicable to distributed access management techniques in network environments.
This document also provides explanations about related architecture, components and management functions.
The subjects involved in access management can be uniquely recognized to access information systems, as defined in the ISO/IEC 24760 series.
The nature and qualities of physical access control involved in access management systems are outside the scope of this document.

This Technical Specification (TS) series provide a generic framework for the establishment of requirements and their evaluation methodology for biometric products. The requirements depend on the biometric mode considered, and are adapted to each scenario, through the definition of a variety of application profiles (APs). In addition, this TS series provides the definition of the individual tests that can be applied to a biometric product.
This document specifies the context for the evaluation of biometric products within the context of the European Union, as well as the general requirements for such evaluation. This will be defined in a biometric mode-independent point of view, as well as not being biased by the particular application which is the target of the biometric product to be assessed.
This first part defines the following items:
-   biometric evaluation process;
-   biometric evaluation phases;
-   how to define each particular biometric test;
-   how to define the profiling for a particular application.
NOTE 1   Future parts of the CEN/TS series are planned to address the specifics of each biometric mode. For each of these modalities, this document specifies application-independent tests, as well as a set of APs, that detail the applicable tests, the evaluation parameters, and the passing criteria.
NOTE 2   Regarding biometrics for public sector applications, see also BSI TR 03121 [7] which can apply.
NOTE 3   For an overview of sectors addressed in the Cybersecurity Act, see Regulation (EU) 2019/881.

This document describes the transaction information requirements of the transactions used in the collaborations described in EN 17016-1:2024. For each transaction are specified the transaction business requirements, the transaction information data model containing definitions of terms, usage descriptions and cardinality of the information elements and the transaction business rules.
This document describes the following transactions:
1)   Order;
2)   Order Change;
3)   Order Cancellation;
4)   Order Response Simple
5)   Order Confirmation;
6)   Order Rejection;
7)   Order Response;
8)   Order Change Confirmation;
9)   Order Change Rejection;
10)   Order Cancellation Confirmation;
11)   Order Cancellation Rejection;
12)   Order Agreement.
How to claim compliance to a transaction is specified in Clause 6.
How to claim conformance to a transaction is also specified in Clause 6.

The CEN/TS 18212 series specifies a generic framework for the establishment of requirements and their evaluation methodology for biometric products. The requirements depend on the biometric mode considered, and are adapted to each scenario, through the definition of a variety of application profiles (APs).
This series of standards are expected to provide the evaluation methodology, the individual tests, and the APs (with their particular requirements).
This document specifies:
-   tests for evaluating the interoperability of all biometric input data (received or read);
-   test for evaluating the interoperability of all biometric output data (stored or transmitted);
-   test for evaluating the interoperability of all exchange of information between the TOE and external components or devices.
NOTE 1   Additional parts are provided covering the specifics of each biometric mode. For each of these modalities, application-independent tests are defined, as well as a set of APs, that detail the applicable tests, the evaluation parameters, and the passing criteria.
The Technical Specifications within this series can be taken by any certification body and/or sector, to define and evaluate the requirements for their biometric products within their selected applications.
NOTE 2   Regarding biometrics for public sector applications, see also BSI TR 03121 [2] which can apply.
NOTE 3   For an overview of sectors addressed in the Cybersecurity Act, see Regulation (EU) 2019/881.
NOTE 4   This part defines all potential tests that could be applicable when evaluating the interoperability of a biometric product. It will be the relevant AP, the one that will specify which of these tests are applicable.

This document describes a standardized methodology and framework for the development and representation of an ontology that supports a global, open-source approach to implementing the ISO standards on the identification of medicinal products (IDMP) (ISO 11615, ISO/TS 20443, ISO/TS 20451, ISO 11238; ISO/TS 19844, ISO 11239, ISO/TS 20440, and ISO 11240). Realization of the full potential of IDMP requires fully self-describing data. For this purpose, this document describes a methodology and framework that complements the existing conceptual and logical models in the ISO documents on IDMP with an IDMP ontology that enables deep, semantic interoperability based on findable, accessible, interoperable and reusable (FAIR) data principles. This methodology and framework enhance the usage of the IDMP data model as the foundation of medicinal product identification and will ultimately enable collaboration towards drug safety and overall operational efficiency.
This document also describes a methodology for the agile adaptation of the ISO documents on IDMP in connection with cross-jurisdictional IDMP-related legislation and initiatives. This document is intended to be complementary to and independent from formal regulatory guidance. Thus, it enables cross-jurisdictional consistency and supports stakeholders in their regional implementations of IDMP standards. This document does not mandate any specific ontology as an implementation tool, nor is it an instructional guideline on how to build ontologies, which is out of scope of this document.
This document includes key use cases described in the ISO documents on IDMP ISO 11615, ISO 11238 and ISO/TS 19844, as well as further use cases arising from the comprehensive deployment of the ISO documents on IDMP via an ontological framework. Thus, an ontology that represents the IDMP standards aims to cover the complete collection of ISO standards on IDMP regarding key interoperability issues that implementing stakeholders are facing.

This document specifies a semantic data model of the core elements of an Electronic invoice. The semantic data model includes only the essential information elements that an Electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and domestic trade. The semantic data model can be applied by organizations in the private and the public sector for public procurement invoicing. It can also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers.
This document complies at least with the following criteria:
— it is technologically neutral;
— it is compatible with relevant international standards on electronic invoicing;
— the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection bydesign, data minimization, purpose limitation, necessity and proportionality;
— it is consistent with the relevant provisions of Directive 2006/112/EC [2];
— it allows for the establishment of practical, user-friendly, flexible and cost-efficient electronic invoicing systems;
— it takes into account the special needs of small and medium-sized enterprises as well as of subcentral contracting authorities and contracting entities;
— it is suitable for use in commercial transactions between enterprises.

NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V6.2 (EN 12896 series) and SIRI (CEN/TS 15531-4/-5 and EN 15531-1/-2/-3) and supports the exchange of information of relevance for passenger information about public transport services and also for running Automated Vehicle Monitoring Systems (AVMS).
NOTE Many NeTEx concepts are taken directly from Transmodel. The definitions and explanation of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptions in order to fit the NeTEx context.
Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger information systems and AVMS with data from public transport scheduling systems, it is not restricted to this purpose. NeTEx can also provide an effective solution to many other use cases for transport data exchange.

This document is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information.
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems.
As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.

This document presents Part 2 of the European Technical Specification known as “NeTEx”. NeTEx provides a framework for specifying communications and data exchange protocols for organisations wishing to exchange scheduled Information relating to public transport operations. As defined by Transmodel, 'Public transport' has to be understood as services advertised and available for use by the general public carried out by any means of transport.
This Technical Specification is made up of six parts defining a single European Standard, which provides a complete exchange format for public transport networks, timetable description and fare information.
Part 1 is the description of the public transport network topology exchange format. It also contains use case shared with part 2, and modelling rules and the description of a framework shared by all parts.
Part 2 is the description of the scheduled timetables exchange format.
Part 3 is the description of the fare information exchange format.
Part 4 is the description of the European passenger information profile.
Part 5 is the description of the alternative modes exchange format.
Part 6 is the description of the European passenger information accessibility profile.
Part 1 is fully standalone, and parts 2, 3, 4, 5 and 6 rely on Part 1 and possibly any previous part..
The XML schema can be downloaded from http://netex-cen.eu (or directly from https://github.com/NeTEx-CEN/NeTEx), along with available guidance on its use, example XML files, and case studies of national and local deployments.
This document is highly technical, and a special care has been taken to keep the text readable. In particular a set of formatting conventions is followed that enhances the usual CEN writing rules in order to distinguish references to elements of the formal models within text:
Transmodel terms and NeTEx conceptual model elements are in capital letters (JOURNEY PATTERN for example).
NeTEx physical model names are in bold italic font and use CamelCase style with no spaces (JourneyPattern, for example).
NeTEx physical model attribute types are in italic font and use CamelCase style with no spaces (TypeOfEntity, for example).

Within the field of health informatics, the DICOM (digital imaging and communication in medicine) standard addresses the exchange of digital images, and information related to the production and management of those images, between both medical imaging equipment and systems concerned with the management and communication of that information, such as Picture Archiving anc Communication System (PACS), Hospital Information System (HIS) and Radiology Information System (RIS).
This document is equivalent to part 1 of DICOM. As such, it normatively describes the content of DICOM (Clause 6) and the requirements to make a claim of conformance (Clause 5).
The DICOM standard is applicable to diagnostic medical imaging as practiced in radiology, cardiology, pathology, dentistry, ophthalmology and related disciplines, and image-based therapies such as interventional radiology, radiotherapy and surgery. It is also applicable to a wide range of image and non-image related information exchanged in clinical, research, veterinary, and other medical environments.

This document establishes a framework and specifies electronic fee collection (EFC) functions for the personalization process of on-board equipment (OBE) used for EFC.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
This document is applicable to the EFC interface, e.g. using dedicated short-range communication or integrated circuit(s) card, between the personalization equipment (PE) and OBE as shown in Figure 1.
This document does not cover the following:
whether the personalization functionality resides completely in the PE or whether this functionality instead resides in a central system, where the PE is more or less “transparent”;
the exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and are described in subsequent parts of the ISO 21719 series);
the test procedures for evaluation of an implementation for conformity to the requirements in this document;
setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party).
NOTE            Some of the issues listed above are subject to separate documents prepared by ISO/TC 204, CEN/TC 278 and the European Telecommunications Standards Institute – Electromagnetic compatibility and Radio Spectrum Matters (ETSI ERM).

16614 (NeTEx) is composed of a series of standards:
-   Part 1: Description of the public transport network topology exchange format.
-   Part 2: Description of the scheduled timetables exchange format.
-   Part 3: Description of the fare information exchange format.
-   Part 4: Description of the passenger information European profile (EPIP).
-   Part 5: Description of the alternative modes exchange format.
-   Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
-   Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
-   Physical layout of compound vehicles (e.g. train composition),
-   Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.

This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However, as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12), ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document.
This document specifies the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE, NR and their successors) 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 based on the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and
revise Conformance Test Procedures (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 112-eCall (Pan European eCall) tests provided in EN 16454 are
specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO’s, and PSAPs, required to ensure and demonstrate compliance to EN 17184.
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.

16614 (NeTEx) is composed of a series of standards:
-   Part 1: Description of the public transport network topology exchange format.
-   Part 2: Description of the scheduled timetables exchange format.
-   Part 3: Description of the fare information exchange format.
-   Part 4: Description of the passenger information European profile (EPIP).
-   Part 5: Description of the alternative modes exchange format.
-   Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
-   Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
-   Physical layout of compound vehicles (e.g. train composition),
-   Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.

In respect of pan European eCall (operating requirements defined in EN 16072), this document defines
the high level application protocols, procedures and processes required to provide the eCall service via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to
automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102.
This document makes reference to those provisions but does not duplicate them.

This document establishes a common framework of process descriptions for describing the life cycle of systems created by humans, defining a set of processes and associated terminology from an engineering viewpoint. These processes can be applied to systems of interest, their system elements, and to systems of systems. Selected sets of these processes can be applied throughout the stages of a system's life cycle. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.
This document defines a set of processes to facilitate system development and information exchange among acquirers, suppliers, and other stakeholders in the life cycle of a system.
This document specifies processes that support the definition, control, and improvement of the system life cycle processes used within an organization or a project. Organizations and projects can use these processes when acquiring and supplying systems.
This document applies to organizations in their roles as both acquirers and suppliers.
This document applies to the full life cycle of systems, including conception, development, production, utilization, support and retirement of systems, and to the acquisition and supply of systems, whether performed internally or externally to an organization. The life cycle processes of this document can be applied iteratively and concurrently to a system and recursively to the system elements.
This document applies to one-of-a-kind systems, mass-produced systems, and customised, adaptable systems. It also applies to a complete stand-alone system and to systems that are embedded and integrated into larger more complex and complete systems.
This document does not prescribe a specific system life cycle model, development methodology, method, modelling approach or technique.
This document does not detail information items in terms of name, format, explicit content, and recording media. ISO/IEC/IEEE 15289 addresses the content for life cycle process information items (documentation).

This document describes:
-   business processes and the technical environments in which simplified invoices and e-receipts are exchanged; and
-   the needed syntax bindings of electronic simplified invoices and e-receipts.

This document provides information security controls, including implementation guidance, for health organizations. It is based on ISO/IEC 27002:2022
In addition to generic ICT equipment and software used in many other environments, the scope of this document includes software and systems specifically for healthcare, such as electronic health record systems and medical devices incorporating health software. Such medical devices can be programmed or programmable and can contain software, firmware or both.
Other digital equipment (such as that for environmental and infection control, building management, and physical security), which can be used in premises where healthcare is provided, is also in scope.
This document applies to information in all its aspects, whatever form the information takes (including text and numbers, sound recordings, drawings, images and video), by whatever means it has been acquired or captured, whatever means are used to store it (such as printing or writing on paper or storage electronically), and whatever means are used to transfer or exchange it (orally, by hand, by post, movement of storage media, direct links or networking).
This document is for organizations of all types and sizes that provide healthcare or are custodians of personal health information for other reasons. The information that they are responsible for can be stored and processed in many possible ways and locations, including on premises or in the cloud, but remains in scope.
This document applies to all physical settings where healthcare is intended to be delivered, such as hospitals, clinics and other locations or facilities designated for healthcare purposes such as ambulances and mobile imaging or diagnostic units. It also applies to care provided elsewhere, such as in residential premises. In addition to the range of settings, this document applies to all methods of service provision including remote or virtual healthcare.