35.240 - Applications of information technology
ICS 35.240 Details
Applications of information technology
Anwendungen der Informationstechnik
Applications des technologies de l'information
Uporabniške rešitve informacijske tehnike in tehnologije
General Information
Frequently Asked Questions
ICS 35.240 is a classification code in the International Classification for Standards (ICS) system. It covers "Applications of information technology". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 7786 standards classified under ICS 35.240 (Applications of information technology). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 35.240 - Applications of information technology
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document provides a set of properties for the description of learning resources from ISO 15836-1 and ISO 15836-2 using the framework provided in ISO/IEC 19788-1. This document specifies properties whose codomain is "literal" (as considered in early Dublin Core) and properties whose codomain is a resource class; the ISO 15836 series implicitly allowing both. This provides full interoperability at the time of expressing existing Dublin Core records with MLR, while allowing a linked data approach for the description of learning resources.
- Standard27 pagesEnglish languagee-Library read for1 day
The present document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4].
For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9].
For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.
- Standard66 pagesEnglish languagesale 15% off
- Technical specification66 pagesEnglish languagee-Library read for1 day
This document provides a semantic base that allows the representation of relevant information related to tourism destinations, including resources and services within the destination, travel experiences, and the destination itself. It establishes the terminology, hierarchy, and the minimum properties and relationships required for the definition of a reference semantic structure, ensuring the interoperability of local, territorial and country tourism information technology (IT) platforms with third-party digital systems. This document provides tourism destinations with semantic data structures that primarily benefit final users (i.e. tourists and other interested parties), as these structures allow destinations to provide access to relevant information in an intuitive and agile way, and improve the interaction between tourists and the systems that manage, publish, carry transactions and accompany tourists during their journey. Furthermore, destination managers, data managers and data publishers, applying this document can also benefit from such implementation.
- Standard67 pagesEnglish languagesale 15% off
This document provides a taxonomy, reference model, considerations for a security framework and a security problem definition for digital currency hardware wallets (DCHWs). It also specifies security objectives to address security issues related to the security problem definition. This document is applicable to organizations that develop and operate DCHWs, e.g. mobile device manufacturers, chip manufacturers and companies that provide DCHW solutions. This document is also relevant to third parties that provide services to these stakeholders. It addresses sovereign or fiat digital currencies issued by a specific entity, e.g. a central bank.
- Standard35 pagesEnglish languagesale 15% off
This document specifies the data exchange requirements between related systems within the smart city for electric vehicle (EV)-based demand response (DR) services utilizing nomadic devices as follows: EV-based DR service for demand reduction, called “demand response” during the shortage of reserve on electric grid or in response to a fine dust warning issued according to an air quality forecast; EV-based DR for demand increase, called “reverse demand response”, instead of curtailment during excess electricity generation by renewable energy sources such as the sun and wind. This document defines the requirements of main actors such as the EV, nomadic device, smart city cloud, charging station and service provider to support EV-based DR services. This document also defines the data set and data processing procedure requirements for EV-based DR services.
- Standard26 pagesEnglish languagesale 15% off
IEC 63278-4:2026 assumes an application perspective of the Asset Administration Shell to develop a common understanding on how to use an Asset Administration Shell.
This document defines how the Asset Administration Shell can be used in the context of the related entities and how to represent assets using the Asset Administration Shell.
Due to the more detailed description compared to IEC 63278-1, additional requirements, recommendations, and permissions for the AAS are stated towards application of the AAS in selected scenarios.
- Standard238 pagesEnglish and French languagesale 15% off
- Standard238 pagesEnglish and French languagesale 15% off
This document applies to:
Organisations:
- public sector procurement authorities at local, regional, national, and European levels;
- private sector organizations engaging in innovation partnerships with public entities;
- research and development institutions participating in cross-sector innovation;
- SMEs and large enterprises involved in public-private innovation ecosystems;
- international organizations seeking to implement European innovation procurement approaches.
Innovation Dimensions:
- dimension A: Business Model Innovation (Strategic and Tactical) - 13 innovations across circular economy, product-as-service, and collaborative models;
- dimension B: Innovative Operational Procurement - 12 innovations including enhanced PCP/PPI integration and seven-procedure frameworks;
- dimension C: Innovation Sourcing Infrastructure - 5 high-impact innovations encompassing digital portfolios, AI-driven analytics, and federated intelligence;
- dimension D: Technological Innovation - 20 innovations covering IoT, blockchain, AI, quantum computing, and emerging technologies.
Legal Framework Coverage:
- cross-sector innovation authorization beyond traditional PCP/PPI scope;
- innovation sandbox and safe harbor mechanisms for experimental approaches;
- cross-border legal harmonization for international standards development;
- system-of-Systems legal orchestration for complex multi-organizational coordination;
- liability limitation and risk protection frameworks for good faith innovation.
Scope Exclusions
This document does not cover:
- traditional procurement of standard goods and services without innovation components;
- sector-specific legal frameworks that do not involve cross-sector collaboration;
- emergency procurement procedures where innovation is not the primary objective;
- military and defense procurement subject to specific security classifications;
- legal frameworks for routine administrative procurement below innovation thresholds.
- Draft32 pagesEnglish languagee-Library read for1 day
This document establishes the technical pillar of the Strategic Trilogy, converting the 50 INNOV innovations from CEN/TR 17011-2-1 [1] into 87 comprehensive standards while operating within the legal facilitation framework provided by CEN/TR 17011-2-3 [2].
- Draft33 pagesEnglish languagee-Library read for1 day
This document specifies the requirements for digital product passport (DPP) access rights management, including IT security, data protection, and responsibility transfer between economic operators. It defines the framework for managing confidential information access, while acknowledging that public DPP data requires no access restrictions to be read.
- Draft18 pagesEnglish languagee-Library read for1 day
This document provides a set of properties for the description of learning resources from ISO 15836-1 and ISO 15836-2 using the framework provided in ISO/IEC 19788-1. This document specifies properties whose codomain is "literal" (as considered in early Dublin Core) and properties whose codomain is a resource class; the ISO 15836 series implicitly allowing both. This provides full interoperability at the time of expressing existing Dublin Core records with MLR, while allowing a linked data approach for the description of learning resources.
- Standard27 pagesEnglish languagee-Library read for1 day
This document establishes comprehensive frameworks and models for innovative developments in procurement across all sectors, providing systematic methodologies and organizational frameworks enabling transformation of procurement practices through structured governance and innovation management.
This document applies to:
— Organizations
• public sector procurement authorities at local, regional, national, and European levels;
• private sector organizations engaging in innovation partnerships with public entities;
• research and development institutions participating in cross-sector innovation;
• SMEs and large enterprises involved in public-private innovation ecosystems;
• international organizations seeking to implement European innovation procurement approaches.
— Innovation Coverage
• cross-sector innovation frameworks applicable to both public and private organizations;
• enhanced Pre-Commercial Procurement (PCP) and Public Procurement of Innovation (PPI) frameworks;
• system-of-Systems (SoS) orchestration for complex multi-organizational coordination;
• four-dimensional innovation architecture covering business models, operations, sourcing, and technology.
— Framework Applications
• strategic innovation planning and implementation across organizational boundaries;
• digital transformation and technology integration for all sectors;
• circular economy and sustainable procurement models;
• cross-border collaboration and harmonization mechanisms.
- Draft26 pagesEnglish languagee-Library read for1 day
This document defines the requirements and frameworks for secure information processing and communication to safeguard integrity, authenticity and reliability in the digital product passport (DPP) data exchange, minimizing product fraud and counterfeiting through data verification and integrity enforcement mechanisms.
This document provides a framework for establishing trust, interoperability, and interoperation via secure electronically signed data construct (ESDC) for multi-actor applications, applicable across various sectors and in multilingual environments. Existing hardware and software systems for unique product identification and storage of this identification are to be considered.
The following is out of scope of the document: system architecture for DPP, DPP use cases, secure elements related to data carriers and cryptographic security features for unique product identifiers.
NOTE 1 While not disrupting existing traceability and authentication systems, this document facilitates interoperability by introducing an ESDC scheme to be combined with existing data constructs to cover and preserve existing data models.
NOTE 2 Annex B includes illustrative examples and references to supporting implementations, intended to demonstrate approaches that promote interoperability across diverse environments. These references are provided to assist stakeholders in selecting appropriate solutions that comply with applicable legal obligations and technical standards, while preserving existing systems.
- Draft19 pagesEnglish languagee-Library read for1 day
This document specifies electronic fee collection (EFC) requirements for the preparation and evaluation of security requirements specifications, referred to as protection profiles (PP) in the ISO/IEC 15408 series and in ISO/IEC TR 15446.
- Draft54 pagesEnglish languagee-Library read for1 day
This document provides information on how to address product quality data interchange based on risk assessment for consumer product safety in e-commerce. This document: analyses e-commerce supply chain context; analyses product risk assessment in e-commerce; gives use cases on risk-based product quality data for interchange; presents the general process for product quality data interchange among e-commerce stakeholders.
- Technical report28 pagesEnglish languagesale 15% off
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);
- Technical specification167 pagesEnglish languagee-Library read for1 day
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.
- Technical specification152 pagesEnglish languagee-Library read for1 day
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).
- Standard264 pagesEnglish languagee-Library read for1 day
This document establishes a systematized framework for the competences of AI ethicists, categorizing them into knowledge, skills and attitudes related to the specific activities and tasks of the role. It specifies requirements and recommendations necessary for individuals to effectively perform as AI ethicists. These competences encompass a strong understanding of European values and fundamental rights, further enhancing the knowledge, skills and attitudes required for this profession.
This document defines the essential concepts and principles inherent to the AI ethicist role. It illustrates a clear, uniform approach to the integral components of this profession.
Moreover, the document outlines how the role of AI ethicists can be seamlessly integrated into a wide variety of organizations. These include, but are not limited to, commercial enterprises, governmental agencies and non-profit organizations.
- Standard29 pagesEnglish languagee-Library read for1 day
- Amendment7 pagesEnglish languagee-Library read for1 day
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).
- Standard130 pagesEnglish languagee-Library read for1 day
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
- Technical report159 pagesEnglish languagee-Library read for1 day
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).
- Standard187 pagesEnglish languagee-Library read for1 day
This document specifies the fundamentals and concepts for the long-term preservation of digital product and technical data. The EN 9300 series specifies various regulatory and business requirements, applicable domain specific methodologies and are extensible for future long-term archiving formats and data management practices.
- Standard27 pagesEnglish languagee-Library read for1 day
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)
- Standard292 pagesEnglish languagee-Library read for1 day
This document provides an overview description for the recommended processes for archiving of model-based product data, (e.g. 3D CAD and PDM data). The detailed processes are described in additional process parts of the EN 9300 series.
- Standard12 pagesEnglish languagee-Library read for1 day
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.
- Technical specification269 pagesEnglish languagee-Library read for1 day
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).
- Standard89 pagesEnglish languagee-Library read for1 day
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.
- Technical specification104 pagesEnglish languagee-Library read for1 day
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.
- Technical specification211 pagesEnglish languagee-Library read for1 day
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)
- Standard53 pagesEnglish languagee-Library read for1 day
- Amendment308 pagesEnglish languagee-Library read for1 day
This document specifies the requirements and provides guidance for the definition, implementation and maintenance of a quality management system for organizations that provide AI systems.
This document is intended to support the organization in meeting applicable regulatory requirements. It is primarily intended for organizations placing on the market or putting into service high-risk AI systems and is not specific to any particular sector.
- Standard51 pagesEnglish languagee-Library read for1 day
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)
- Standard90 pagesEnglish languagee-Library read for1 day
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
- Technical specification132 pagesEnglish languagee-Library read for1 day
This document specifies requirements, a framework, a general specification procedure, a guide for elaboration, and categorization of application methods of an equipment behaviour catalogue (EBC) in smart manufacturing.
- Standard21 pagesEnglish languagesale 15% off
This document provides a set of properties for the description of learning resources from ISO 15836-1 and ISO 15836-2 using the framework provided in ISO/IEC 19788-1. This document specifies properties whose codomain is "literal" (as considered in early Dublin Core) and properties whose codomain is a resource class; the ISO 15836 series implicitly allowing both. This provides full interoperability at the time of expressing existing Dublin Core records with MLR, while allowing a linked data approach for the description of learning resources.
- Standard19 pagesEnglish languagesale 15% off
The purpose of this document is to define data communication services and protocols for computer equipment used for monitoring and control of HVAC&R and other building systems and to define, in addition, an abstract, object-oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings.
- Standard1628 pagesEnglish languagee-Library read for1 day
This document specifies electronic fee collection (EFC) requirements for the preparation and evaluation of security requirements specifications, referred to as protection profiles (PP) in the ISO/IEC 15408 series and in ISO/IEC TR 15446.
- Standard47 pagesEnglish languagesale 15% off
- Standard52 pagesFrench languagesale 15% off
- Standard93 pagesEnglish languagesale 15% off
This document specifies requirements and recommendations for remote maintenance services (RMSs) of medical devices and medical information systems in healthcare facilities (HCFs). This document is applicable to HCFs and remote service centres (RSCs) providing remote maintenance services for medical devices and medical information systems. This document specifies the risk assessment necessary to protect remote maintenance activities, taking into consideration the special characteristics of the healthcare field such as patient safety, regulations and privacy protections. This document provides practical examples of risk analysis to protect both the HCF and RMS provider information assets in a safe and efficient (i.e. economical) manner. These assets are primarily the information system itself and personal health data held in the information system.
- Technical specification19 pagesEnglish languagesale 15% off
This document specifies interoperability requirements for personal health decision support (PHDS) services between actors in the PHDS environment, which include PHDS services, data providers, and PHDS clients. It includes requirements for data exchange, validation, and error handling among participants to support accurate and timely decision-making. It also describes the privacy and security considerations for PHDS. However, the specifics of how PHDS services are developed or implemented are not covered.
- Draft17 pagesEnglish languagee-Library read for1 day
This document is applicable to safety-related electronic systems using for digital communication purposes a transmission system which was not necessarily designed for safety-related applications. For transmission systems where the risk of unauthorized access is not negligible, the document defines the interface to the applicable cybersecurity standards.
Both safety-related equipment and non-safety-related equipment can be connected to the transmission system.
This document gives the specific requirements needed to achieve safety-related communication between safety-related equipment connected to the transmission system, while the general system requirements including allocation of safety requirements and content of the safety case are defined in EN 50129.
This document is not applicable to existing systems which had already been accepted prior to the release of this document. However, so far as reasonably practicable, it is applicable to modifications and extensions to existing systems, subsystems and equipment.
This document does not specify:
- the transmission system;
- equipment connected to the transmission system;
- solutions (e.g. for interoperability);
- which kind of data are safety-related and which are not.
A safety-related equipment connected through an open transmission system can be subjected to many different cybersecurity threats, against which an overall program is defined encompassing management, technical and operational aspects.
- Standard64 pagesEnglish languagee-Library read for1 day
This document is applicable to safety-related electronic systems (including subsystems and equipment) for railway signalling applications.
This document applies to generic systems (i.e. generic products or systems defining a class of applications), as well as to systems for specific applications.
The scope of this document and its relationship with other CENELEC standards are shown in Figure 1.
This document is applicable only to the functional safety of systems. It does not deal with other aspects of safety such as occupational health and safety of personnel or potential threats created by the technology regardless of their intended functions (e.g. presence of sharp edges, presence of electric voltage, presence of combustible material). Cybersecurity aspects of functional safety are addressed only to the extent consistent with the application of the relevant standards, where needed.
This document applies to all the phases of the life cycle of a safety-related electronic system, focusing in particular on phases from 4 (specification of system requirements) to 10 (system acceptance) as defined in EN 50126 1:2017.
Requirements for systems which are not related to safety are outside the scope of this document.
This document is not necessarily applicable to systems, subsystems or equipment which had already been accepted prior to the date of withdrawal (dow) of the standards conflicting with this document. However, so far as reasonably practicable, it is applicable to modifications and extensions to such systems, subsystems and equipment.
NOTE In the case of partial modifications, it can happen that the system can no longer be declared compliant with a single version of the standard, meaning that the modified part will be compliant with the current version and the unmodified parts will be compliant with the previous version.
This document is primarily applicable to systems, subsystems or equipment which have been specifically designed and manufactured for railway signalling applications. It is also applicable, to the extent of 6.2, to general-purpose or industrial equipment (e.g. power supplies, display screens, or other commercial off the shelf items) which is procured for use as part of a safety-related electronic system.
This document is aimed at railway duty holders, railway suppliers, and assessors as well as at safety authorities, although it does not define an approval process to be applied by the safety authorities.
- Standard140 pagesEnglish languagee-Library read for1 day
The scope of this document is the definition of the functional interface between the TDC and other train systems. These "Other Train Systems" are the train systems interfacing with the TDC excluding the displays (CLC/TR 50542-2), ETCS/STM onboard (Subset-121) and already designed class B ATP systems.
The functional interface deals with data exchanged between the TDC and these train systems as shown in Figure 1.
The TDC is defined in document CLC/TR 50542-1.
(...)
- Technical report11 pagesEnglish languagee-Library read for1 day
This document describes a methodology for specifying the privileges necessary to access electronic health record (EHR) data. This methodology forms part of the overall EHR communications architecture defined in ISO 13606-1 [17].
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 to 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.
- Draft38 pagesEnglish languagee-Library read for1 day
This document gives guidance on authoring, editing and evaluating specialized source language content intended for translation. In addition, this document addresses handover recommendations in connection with the production and translation of specialized content. This document is meant as a practical guidance and recognizes that not all clauses are equally applicable to every use case. This document is applicable to authors and editors of specialized content intended for translation. It also enables translators and translation service providers to assess the suitability of specialized content for translation. This document is also applicable to tool providers (e.g. to develop and improve automatic source language testing and verification procedures). This document does not apply to authoring, editing and evaluating fictional, journalistic, advertising and other non-specialized content.
- Standard50 pagesEnglish languagesale 15% off
This document provides an overview description for the recommended processes for archiving of model-based product data, (e.g. 3D CAD and PDM data). The detailed processes are described in additional process parts of the EN 9300 series.
- Standard12 pagesEnglish languagee-Library read for1 day
This document specifies the fundamentals and concepts for the long-term preservation of digital product and technical data. The EN 9300 series specifies various regulatory and business requirements, applicable domain specific methodologies and are extensible for future long-term archiving formats and data management practices.
- Standard27 pagesEnglish languagee-Library read for1 day
This document describes a methodology for specifying the privileges necessary to access electronic health record (EHR) data. This methodology forms part of the overall EHR communications architecture defined in ISO 13606-1 [17]. 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 to 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.
- Standard23 pagesEnglish languagesale 15% off
- Standard26 pagesFrench languagesale 15% off
This document specifies interoperability requirements for personal health decision support (PHDS) services between actors in the PHDS environment, which include PHDS services, data providers, and PHDS clients. It includes requirements for data exchange, validation, and error handling among participants to support accurate and timely decision-making. It also describes the privacy and security considerations for PHDS. However, the specifics of how PHDS services are developed or implemented are not covered.
- Standard11 pagesEnglish languagesale 15% off
- Standard12 pagesFrench languagesale 15% off