IT-tillämpningar

This document specifies an implementation schema based on the content models for geographic imagery and gridded thematic data defined in the ISO/TS 19163-1. This document defines a structure that is suitable for binding content components and specific encoding formats. It also provides an implementation schema for binding a concrete, implementable, conformance-testable coverage structure as defined in ISO 19123-2.

This document covers the digital interface at the product loading and/or discharge coupling which is used for the transfer of product related information and specifies the performance requirements, critical safety aspects and tests to provide compatibility of devices.

This document describes a methodology for specifying the privileges necessary to access EHR data. This methodology forms part of the overall EHR communications architecture defined in ISO 13606-1. This document seeks to address those requirements uniquely pertaining to EHR communications and to represent and communicate EHR-specific information that will inform an access decision. It also refers to general security requirements that apply to EHR communications and points at technical solutions and standards that specify details on services meeting these security needs. NOTE Security requirements for EHR systems not related to the communication of EHRs are outside the scope of this document.

This document gives guidelines for the implementation of the information management process, in accordance with the requirements of ISO 19650-2.

This document describes a taxonomy of the AI tasks related to computer vision. It includes AI tasks pertaining to either the analysis or generation of images and videos.

This document specifies requirements and provides guidance for risk management of AI systems. It specifies terminology, principles and a process for risk management. The process described in this document intends to assist providers of AI systems to identify the hazards associated with the AI systems, to estimate and evaluate the associated risks, to control these risks, and to monitor the effectiveness of the controls. The process described in this document applies to risks to health, safety and fundamental rights associated with an AI system. The process described in this document is applied throughout the life cycle of the AI system. This document requires providers to establish objective criteria for risk acceptability but does not specify acceptable risk levels. This document is intended for use by organizations providing AI systems, regardless of their size, nature or location. This document is not intended for managing risk faced by organizations. This document is intended to support the organization in meeting applicable regulatory requirements.

The function of EN 15430 is to combine any vehicle equipment with different board computers to any client application server. This document specifies the interface and protocol needed between the information supplier server and the client application server (flow 3 as illustrated in Figure 1) to allow distribution of data without any restrictions to the technology used to gather the data like manufacturer specific protocols, WLANS systems, memory cards, etc.

I detta dokument, som föreslås som ett tillägg till SS 12000:2024, beskrivs förslagen till ändringarna i tillägget. 

Godkända ändringar kommer att införlivas i SS 12000:2024 som då kommer att publiceras i en ny utgåva med beteckningen SS 12000:2024+T1:2026. 

I detta dokument indikeras förslagen på ändringar genom att de omsluts av följande taggar: 

Anmärkning:   SIS använder samma taggar som CEN och ISO där ”A” står för Amendment (tillägg) och siffran står för tilläggets nummer.

Detta dokument innehåller enbart den text i SS 12000:2024 som är kopplad till förslagen på ändringar. Enbart kommentarer på förslagen på ändringar kommer att beaktas

ISO/IEC 19788-4:2014 specifies, in a rule-based manner, metadata elements and their attributes for the description of learning resources. This includes the rules governing the identification of metadata elements and the specification of metadata attributes.

These metadata elements are used to form the description of a learning resource, i.e. as a metadata learning resource (MLR) record.

This part of ISO/IEC 19788 specifies, using ISO/IEC 19788-1, technical aspects of learning resources, i.e., requirements for use, location, size, etc.

This document contains the basic control strategy, minimum functionality requirements, basic driver interface elements, minimum requirements for diagnostics and reaction to failure, and performance test procedures for Adaptive Cruise Control (ACC) systems.

ACC systems are realised as either Full Speed Range Adaptive Cruise Control (FSRA) systems or Limited Speed Range Adaptive Cruise Control (LSRA) systems. LSRA systems are further distinguished into two types, requiring manual or automatic clutch. Adaptive Cruise Control is fundamentally intended to provide longitudinal control of equipped vehicles while travelling on highways (roads where non-motorized vehicles and pedestrians are prohibited) under free-flowing and for FSRA-type systems also for congested traffic conditions. ACC can be augmented with other capabilities, such as forward obstacle warning. For FSRA-type systems the system will attempt to stop behind an already tracked vehicle within its limited deceleration capabilities and will be able to start again after the driver has input a request to the system to resume the journey from standstill. The system is not required to react to stationary or slow moving objects

The ISO/IEC 19788 series specifies, in a rule-based manner, properties and their attributes for the description of learning resources. This includes the rules governing the identification of properties and the specification of their attributes. These properties may be used to form the description of a learning resource, i.e. as a metadata learning resource (MLR) record described in ISO/IEC 19788-8:2015 Data elements for MLR record.

This document is intended to help implementers with a starting point for adopting the ISO/IEC 19788-1:2024framework by defining an application profile that lists properties and rules, mostly taken from ISO/IEC 19788-2:2011/Amd 1:2016. In addition, it adds, as examples, three locally defined properties and one vocabulary

The present document is composed of the following data packages:

— Indicators;

— Reusable components;

— Explicit frames for statistics

— Query. This document itself is composed of the following parts:

— main document representing the conceptual foundations and corresponding data model (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-8:2019 (informative) 

This document provides terminology, concepts, requirements, and guidance for logging of AI systems. It is primarily intended for organizations placing on the market or putting into service AI systems and is not specific to any particular sector.

This document specifies interoperable application profiles for the information exchange between toll chargers (TCs) and toll service providers (TSPs), by selecting suitable options from the base standard EN ISO 12855:2025.

This document covers: 

— exchange of information between back-end systems of TCs and TSPs, e.g.: 

— charging related data (toll declarations, billing details, payment claims, payment 

announcements); 

— administrative data (trust objects, EFC context data, contact details for enforcement, etc.); 

— user related data (exception lists, user details, abnormal behaviour information, CCC 

event data, user complaints); 

— confirmation data. 

— transfer mechanisms and supporting functions; 

— semantics of data elements;

— definitions (Annex A) of restrictions on data types w.r.t. the ASN.1 definitions in the base 

standard EN ISO 12855:2025 by introducing an XML Schema Definition (XSD) for each specified 

profile; 

— implementation conformance statement (ICS) proforma (Annex B), as a basis for evaluation of 

implementation for conformity to this document; 

— an interoperability statement proforma (Annex C), as a basis for assessment of transactional 

interoperability between the technical implementation of a TC and a TSP; 

— a web service definition (Annex D) covering the use of simple object access protocol (SOAP) 

services as communication technology. 

The implementation of the underlying back-end systems and their business processes is not covered. 

Therefore, the following aspects are outside the scope of this document: 

— details about how back-end systems use the authenticator data elements of the base standard to 

implement security; 

— how to use the data exchange to operate compliance checking and the enforcement process; 

— commercial aspects; 

— definition of non-functional features such as key performance indicators, acceptable fault levels, 

availability of interfaces of TC and TSP, and reporting requirements. 

This document further explains the correspondence between the European electronic toll service (EETS) 

legislation and this document (Annex E). 

ISO/PAS 15339-2 specifies a limited number of characterized reference printing conditions that span the expected range of colour gamuts used for the production of printed materials from digital data, regardless of the printing process used. Their use is described in ISO/PAS 15339‑1.

ISO 25237:2017 contains principles and requirements for privacy protection using pseudonymization services for the protection of personal health information. This document is applicable to organizations who wish to undertake pseudonymization processes for themselves or to organizations who make a claim of trustworthiness for operations engaged in pseudonymization services. ISO 25237:2017 - defines one basic concept for pseudonymization (see Clause 5), - defines one basic methodology for pseudonymization services including organizational, as well as technical aspects (see Clause 6), - specifies a policy framework and minimal requirements for controlled re-identification (see Clause 7), - gives an overview of different use cases for pseudonymization that can be both reversible and irreversible (see Annex A), - gives a guide to risk assessment for re-identification (see Annex B), - provides an example of a system that uses de-identification (see Annex C), - provides informative requirements to an interoperability to pseudonymization services (see Annex D), and - specifies a policy framework and minimal requirements for trustworthy practices for the operations of a pseudonymization service (see Annex E).

This document specifies the customer (natural or legal person) data access and portability in the insurance sector based on the insurance-specific part of the proposed EU FIDA Regulation and therefore contains:

• Semantic specifications for the processes to support the data access and portability. These specifications define on the business level the functions and the behaviour for the following process interfaces:

 Request of the customer to the data holder for an actual transfer of the customer data (FIDA Article 4).

 Transfer of the requested customer data from the data holder to the requesting customer (FIDA Article 4).

 Request of a data user to a data holder for an actual transfer of customer data under a permission of the customer (FIDA Article 5).

 Transfer of the requested customer data from the data holder to the requesting data user (FIDA Article 5).

• Semantic specifications for the customer data to be transferred by the above processes. The scope of the customer data is limited to the insurance-specific part defined in the proposed FIDA Regulation Article 2 (1) and Article 3 (3). These specifications define on the business level each element of the customer data with unique name, precise definition, and value type (text, number, amount, quantity, percentage, date, etc.). The composition of these data elements forms a semantic data model for the insurance-specific customer data. The data model consists of the following parts:

 General data of the insurance client (including personal details, address, contact information, payment means, etc.).

 General data of the insurance policy (including policy number, insurance product and coverages, insured period, premium amounts, etc.).

 Data specific to the insurance client’s assets and risks, collected in an assessment for the purposes of a demands and needs test.

 Data depending on line of business, such as

 Motor insurance (details about vehicle, usage, drivers),

 Property insurance (details about building, household, or other objects),

 Liability insurance (details about insured parties and their activities),

 Personal accident insurance (details about insured persons and their activities),

 Legal expenses insurance (details about insured parties and objects),

 Travel insurance (details about insured parties and objects),

 Financial loss insurance (details about insured parties and risks),

 Insurance-based investment products and private and occupational pension products (details about insured persons and the savings, investments, pension rights, etc.).

This document defines the semantic process specifications for the data access from a customer or a data user to the data holder for the customer, policy, and claims data. The processes for the identification, authentication, and authorisation of customers and data users and the processes for the handling of customer permissions are not in the scope of this standard.

This document specifies the processes and the data models on the semantic level in a syntax-neutral format, independent from its representation in a concrete implementation syntax. Separate CEN Technical Specifications describe the application programming interfaces (API) at the technical implementation level, such as FprCEN/TS 18356-2, in the Open API Technology.

The focus of this document is on the data elements usually required for the customer data access in European insurance markets. For a concrete implementation of the customer data access in a specific market, this standard could be extended by market-specific data elements. Many data elements in this standard utilize coded value lists, some of which are based on ISO or other internationally standardised code value lists, such as country or currency code values. Other code value lists are implemented on a market-specific basis, as the requirements for the value lists are very different due to diverse market conditions. This document makes no attempt to standardise these code value lists.