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 7502 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 defines general information and use cases for providing road safety enhancement services to all types of road users with a nomadic device in urban localized areas by sharing status or intent messages between nomadic device users and conventional ITS stations. The road users in this document include all type of road users with nomadic device such as vulnerable road users (VRU) including pedestrians, bicyclists, kickboard users, as well as connected automated mobility users including conventional vehicles, automated or connected driving system equipped vehicles. In addition, this document considers a sensor-equipped roadside ITS station with AI-supported road user behaviour detection function to support overall road safety enhancement services by sharing status or intents information of all type of road users such as VRUs without a nomadic device and road vehicles without equipped ITS stations. This document also specifies general information, such as category of nomadic device supported road safety service, overall access technology in nomadic device, actors, and communication architecture to support use cases. This document also defines safety enhancement use cases to enhance overall road safety of all types of road users with nomadic device as well as road users without nomadic device with a connectivity of sensor-equipped roadside ITS station. The use cases are applicable to provide road safety enhancement service in a specific urban localized area such as an un-signalized intersection, T-intersection, roundabout, low speed zone, school zone, no turn on red zone, weaving area, etc.
- Technical report42 pagesEnglish languagesale 15% off
This document prescribes:
— how to document a use case with an associated business context and exchange requirements;
— a methodology to identify and specify the information exchanges required at identified times during the life cycle of assets.
This document presents the information delivery manual (IDM) in natural language terms to facilitate interoperability between software applications used during all phases of the life cycle of assets (both buildings and infrastructure). It promotes digital collaboration between actors within the identified business context and provides a basis for accurate, reliable, repeatable and high-quality information exchange.
The information delivery manual (IDM) methodology specified in this document can be applied to any information management trigger event to identify the details of the information required to be exchanged.
- Standard41 pagesEnglish languagee-Library read for1 day
This document defines the conceptual framework and mechanisms for mapping information elements from building information modelling (BIM) to geographic information systems (GIS) to access the required information based on specific user requirements.
The conceptual framework for mapping BIM information to GIS is defined with the following three mapping mechanisms:
— BIM to GIS perspective definition (B2G PD);
— BIM to GIS element mapping (B2G EM);
— BIM to GIS level of detail (LOD) mapping (B2G LM).
This document does not describe physical schema integration or mapping between BIM and GIS models because the physical schema integration or mapping between two heterogeneous models is very complex and can cause a variety of ambiguity problems (see Annex D). Developing a unified information model between BIM and GIS is a desirable goal, but it is out of the scope of this document.
This document is applicable to the following concepts:
— definition for BIM to GIS conceptual mapping requirement description;
— definition of BIM to GIS conceptual mapping framework and component;
— definition of mapping for export from one schema into another.
This document does not apply to the following concepts:
— definition of any particular mapping application requirement and mechanism;
— bi-directional mapping method between BIM and GIS;
— definition of physical schema mapping between BIM and GIS;
— definition of coordinate system mapping between BIM and GIS;
— definition of relationship mapping between BIM and GIS;
— implementation of the application schema.
NOTE For cases involving requirements related to geo-referencing for providing the position and orientation of the BIM model based on GIS, other standards exist such as ISO 19111 and the Information Delivery Manual (IDM) from buildingSMART on Geo-referencing BIM.
- Technical specification32 pagesEnglish languagee-Library read for1 day
This document defines biometric services used for identity assurance that are invoked over a services-based framework. It provides a generic set of biometric and identity-related functions and associated data definitions to allow remote access to biometric services. The binding of these services to specific frameworks is not included in this document but is the subject of other parts of the ISO/IEC 30108 series. Although focused on biometrics, this document includes support for other related identity assurance mechanisms such as biographic and document capabilities. IAVS is intended to be compatible with and used in conjunction with other biometric standards as described in Clause 6. Specification of biometric functionality is limited to remote (backend) services. Services between a client-side application and biometric capture devices are not within the scope of this document. Integration of biometric services as part of an authentication service or protocol is not within the scope of this document.
- Standard79 pagesEnglish languagesale 15% off
This document covers heavy rail rolling stock.
This document does not cover urban rail rolling stock.
NOTE 1 EN 17355 covers communication device requirements for urban rail rolling stock.
This document specifies:
- the functional requirements for a call for aid system and communication device system;
- the dynamic analysis of the call for aid system.
NOTE 2 "Dynamic analysis" is understood here as a sequence of actions.
NOTE 3 In a formation of vehicles where one complies with this document with one that does not, it is possible that the call for aid system is not fully functional.
NOTE 4 The call for aid system function is separate from the Passenger Alarm System (PAS) function, which is provided to deal with emergency situations. The PAS is described in EN 16334-1:2014+A1:2022.
NOTE 5 The communication device system can be different from the PAS, but it can share some or all parts of the PAS to achieve its functionalities.
NOTE 6 The PAS is regarded as a safety relevant system whereas the CFA system and communication device system are non-safety relevant aids to passengers.
- Standard21 pagesEnglish languagee-Library read for1 day
This document presents a case study of a quality management process to support the integration of medical information storage within a hierarchical storage structure, across multiple medical sites. This case study examines how it was used within the MID-NET® Project,[5] utilizing the hierarchical storage structure conformant with ISO/TS 24289. This document does not address issues related to the protection of patient privacy, network security, or the management of patient identifiers and information processes.
- Technical report16 pagesEnglish languagesale 15% off
This document specifies a methodology for describing and managing interactions and a format for digital communication between actors in any use case associated with the management of an asset during all life cycle stages.
It provides:
— a methodology that describes an interaction framework for a use case;
— an appropriate way to map responsibilities and interactions that provides a process context for information flow;
— a format in which the interaction framework is specified and executed.
This document is intended to promote secure, verifiable, traceable and high-quality digital IDM communication between actors during all phases of the life cycle of assets, facilitate interoperability between software applications used, and to provide a basis for data- and process-driven information exchange and traceability of communication.
- Draft95 pagesEnglish languagee-Library read for1 day
The eighth edition of ICAO Doc 9303 progresses from using the first edition of the ISO/IEC 19794 series for encoding biometric reference data in electronic machine-readable travel documents to using the ISO/IEC 39794 series for this purpose. This document specifies how to use ISO/IEC 39794-4 for fingerprint image data stored in electronic machine-readable travel documents.
- Draft26 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] and ETSI TS 101 671 [4]. 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.
- Standard64 pagesEnglish languagesale 15% off
- Technical specification64 pagesEnglish languagee-Library read for1 day
This document specifies considerations that can be of use to implementers and developers that elect to participate in work around updates to ISO/IEC TS 18013-7 . These considerations are intended to support the improvements, to maximize backward compatibility and to, at minimum, maintain the security and privacy properties already embodied in ISO/IEC TS 18013-7 . This document also provides additional information related to these considerations.
- Technical report3 pagesEnglish languagesale 15% off
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.
- Standard72 pagesEnglish languagesale 15% off
- Standard82 pagesFrench languagesale 15% off
The European Commission will in its project "VAT in the digital age" (ViDA) mandate that VAT reporting on intra-EU transactions is performed in near real-time and based on EN 16931-1. This Technical Report defines the impact of this legislation on the various deliverables of CEN/TC 434, with a focus on the subset to be sent to tax authorities and how EN 16931-1 needs to be changed. The ViDA package applies to all EU member states and specific territories where the VAT legislation applies (e.g. Northern Ireland in respect to goods).
This document does not define the content of the common electronic message based on the electronic invoice to be sent to the authorities. The definition of that common electronic message (DRR message) is a task of the European Commission, possibly with help of CEN. As the DRR message is not an invoice, but a VAT report, it is not to be regarded as a Core Invoice Usage Specification (CIUS). The DRR message therefore needs not to obey the rules for developing a CIUS. For example, not all mandatory elements in the invoice need to be part of the DRR message.
- Draft31 pagesEnglish languagee-Library read for1 day
This document defines the calibration and validation of Earth observing (EO) data acquired by synthetic aperture radar (SAR) sensors and products derived from SAR data. The specified SAR sensors include general working modes and advanced working modes. In this document, calibration addresses the process to correct the data, not only geometrically and radiometrically, but also characteristically for qualitative and quantitative applications. Validation addresses an evaluation of the quality and accuracy of the calibrated data and derived products. This document also addresses the associated metadata related to calibration and validation that has not been defined in other geographic information International Standards. This document does not apply to the calibration of SAR sensors and validation of SAR sensor calibration, which are covered by ISO/TS 19159-3. However, the calibration and validation procedure can be also applied and referenced among others.
- Technical specification39 pagesEnglish languagesale 15% off
This document describes how product catalogue data for building services products is exchanged by means of ISO 16739-1 (Industry Foundation Classes, IFC) and EN 17549-2 from manufacturers to designers of building services systems.
This document specifies how the product catalogue structures and content are set up using the definitions stored in a data dictionary.
In scope of this document are:
— processes for the provision and exchange of product catalogues;
— rules for the geometrical representation of products;
— representation of products, product classes, ports, in/outlets, components and accessories by using IFC;
— representation of properties in IFC and the use of IFC constraints for the representation of product variants;
— representation of parametric geometry and the generation of IFC geometries for selected variants;
— calculation of article number.
The resulting product catalogue can be used by designers to select the desired products and integrate them into their model of the building services system.
The expected audience of this document are software providers for the built environment sector and professionals working in the sector who create product catalogues or use product catalogues by means of software tools.
Not in scope of this document is the representation of properties in data dictionaries. The use of data dictionaries is described in ISO 16757-4.
- Standard98 pagesEnglish languagee-Library read for1 day
This document specifies requirements for data dictionaries that are used by product catalogues for building services to provide the semantics of their definitions and data modelling. For this purpose, it defines an overall model that contains:
— subject kinds that allow to distinguish:
— product subjects representing products in product catalogues;
— catalogue subjects comprising meta data of product catalogues;
— various kinds of blocks that collect properties of complex product features, including ports and in/outlets;
— relationship types that allow to distinguish between different kinds of relationships like isSubtypeOf, hasPart, or hasBlock;
— property kinds to distinguish between:
— static properties describing products by providing property values in product catalogues;
— dynamic properties that describe the behaviour of products;
— external properties that represent external conditions that influence the behaviour of the product by influencing the values of dynamic properties.
This document also describes a mapping of the overall model to the data dictionary model of ISO 12006-3 by introducing a dictionary meta level.
Finally, to overcome deficiencies of the standards underlying ISO 16757-5 in capturing all aspects of product catalogues, this document provides some rules and recommendations for required data dictionary elements.
This document does not describe how product catalogues have to be organized, and it does not describe any formats for the exchange of product catalogues. Product catalogues are described in ISO 16757-5.
- Standard34 pagesEnglish languagee-Library read for1 day
This document provides a mapping between the ISO/IEC 11179-34 metamodel for computable data registration and the IEEE 2791 standard for bioinformatics analyses generated by high-throughput sequencing (HTS), to facilitate the production of IEEE 2791 objects from instances of ISO/IEC 11179-34 metamodel and the registration of IEEE 2791 objects as computable data within an MDR conforming to ISO/IEC 11179-34. This document is applicable to those who are submitting data to organizations that require metadata submissions in IEEE 2791 compliant format, as well as those aiming to register IEEE 2791 objects into an MDR that conforms to ISO/IEC 11179-34.
- Standard50 pagesEnglish languagesale 15% off
This document showcases existing practices to monitor supply chains as implemented in the healthcare supply chains, by making use of medicines verification or authentication systems, or both, traceability tools, safe communication technology solutions, and more. This document also discusses the potential benefits of expanding the identification of medicinal products (IDMP) to provide global identifiers for medicinal products, ingredients and batches. It also addresses potential pathways to a global registration system.
- Technical report13 pagesEnglish languagesale 15% off
This document gives guidance relating to successful, secure and usable implementation of biometric enrolment processes, while indicating risk factors that organizations which use biometric technologies can address during procurement, design, deployment and operation. Much of this document is generic to many types of applications, e.g. from national scale commercial and government applications, to closed systems for in-house operations, and to consumer applications. However, the intended application and its purpose often have influence on the necessary enrolment data quality and are taken into account when specifying an enrolment system and process. This document specifies the differences in operation relating to specific types of application, e.g. where self-enrolment is more appropriate than attended enrolment. This document focuses on mandatory, attended enrolment at fixed locations. It ultimately consolidates information relating to better practices for the implementation of biometric enrolment capability in various business contexts including considerations of process, function (system), and technology, as well as legal/privacy and policy aspects. This document provides guidance on collection and storage of biometric enrolment data and the impact on dependent processes of verification and identification. This document does not include material specific to forensic and law enforcement applications.
- Technical specification48 pagesEnglish languagesale 15% off
This document specifies a methodology for describing and managing interactions and a format for digital communication between actors in any use case associated with the management of an asset during all life cycle stages. It provides: - a methodology that describes an interaction framework for a use case; - an appropriate way to map responsibilities and interactions that provides a process context for information flow; - a format in which the interaction framework is specified and executed. This document is intended to promote secure, verifiable, traceable and high-quality digital IDM communication between actors during all phases of the life cycle of assets, facilitate interoperability between software applications used, and to provide a basis for data- and process-driven information exchange and traceability of communication.
- Standard82 pagesEnglish languagesale 15% off
- Standard85 pagesFrench languagesale 15% off
This document specifies a common, interoperable set of extensible properties for the description of resource content, functionality, user needs and preferences, to enable network-supported individualization of resources, services and environments to match the unique needs and preferences of the individual. This document includes all relevant mechanisms for the publication of terminology for such descriptions, including publicly available registries of properties and related metadata resources such as application profiles. This document takes an inclusive approach to individualization, since any user can experience a mismatch of their individual needs and preferences and the content or services delivered; it is not restricted to descriptions related to stereotypical notions of disability. It provides properties for describing access attributes of resources. It does not ascribe medical conditions to such properties (e.g. ‘non-visual’ as a property value does not infer visual disability, as when the user’s eyes are busy watching the road). This document defines a set of core Access for All (AfA) properties that can be used in a digital resource description (DRD), an AfA record, and equally in a stored personal needs and preferences profile, also an AfA record. It also includes how to extend or add a property or its value using an application profile as defined by ISO/IEC 19788-1.
- Standard31 pagesEnglish languagesale 15% off
This document specifies a framework for representing data recorded in terminological data collections (TDCs). This framework includes a metamodel and methods for describing specific terminological markup languages (TMLs), exemplified in this document in eXtensible Markup Language (XML). The mechanisms for implementing constraints in a TML are defined, but not the specific constraints for individual TMLs. This document is designed to support the development and use of computer applications for terminological data and the exchange of such data between different applications. This document also defines the conditions that allow the data expressed in one TML to be mapped onto another TML.
- Standard18 pagesEnglish languagesale 15% off
- Draft21 pagesEnglish languagee-Library read for1 day
The present document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Realtime Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IP MM services as described by the Recommendations ITU-T H.323 [6] and H.248-1 [i.3]. The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2]. The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [1].
- Standard30 pagesEnglish languagesale 15% off
- Technical specification30 pagesEnglish languagee-Library read for1 day
This document describes the core principles for supporting the development, implementation and ongoing maintenance of IDMP identifiers and terminologies. This document provides considerations for the evaluation and/or design when considering current or future operations and service level agreements for systems and terminology support services in conformity with IDMP.
- Technical report15 pagesEnglish languagesale 15% off
The purpose of this deliverable is to specify and describe the reference architecture applied as the basis for the development of Business Interoperability Interface specifications in the eProcurement domain by the TC 440 technical committee.
- Draft37 pagesEnglish languagee-Library read for1 day
This document defines markers of harm in online gambling. It is a minimum set of markers to analyse. The individual indicators can be analysed over additional time spans as well as in excess of those re-quired, and other markers can be added to the analysis as well.
In the event that the collection or analysis of data for a limited set of markers is prohibited within a spe-cific jurisdiction (for example, where legislation prevents it), operators can still be compliant with the standard provided that only these markers are omitted, and only for players who fall under that specific jurisdiction.
This document does not provide guidelines regarding the interventions to be employed when addressing individuals with gambling issues, nor does it establish predefined thresholds for intervention.
- Standard19 pagesEnglish languagee-Library read for1 day
This document defines the conceptual framework and mechanisms for mapping information elements from building information modelling (BIM) to geographic information systems (GIS) to access the required information based on specific user requirements.
The conceptual framework for mapping BIM information to GIS is defined with the following three mapping mechanisms:
— BIM to GIS perspective definition (B2G PD);
— BIM to GIS element mapping (B2G EM);
— BIM to GIS level of detail (LOD) mapping (B2G LM).
This document does not describe physical schema integration or mapping between BIM and GIS models because the physical schema integration or mapping between two heterogeneous models is very complex and can cause a variety of ambiguity problems (see Annex D). Developing a unified information model between BIM and GIS is a desirable goal, but it is out of the scope of this document.
This document is applicable to the following concepts:
— definition for BIM to GIS conceptual mapping requirement description;
— definition of BIM to GIS conceptual mapping framework and component;
— definition of mapping for export from one schema into another.
This document does not apply to the following concepts:
— definition of any particular mapping application requirement and mechanism;
— bi-directional mapping method between BIM and GIS;
— definition of physical schema mapping between BIM and GIS;
— definition of coordinate system mapping between BIM and GIS;
— definition of relationship mapping between BIM and GIS;
— implementation of the application schema.
NOTE For cases involving requirements related to geo-referencing for providing the position and orientation of the BIM model based on GIS, other standards exist such as ISO 19111 and the Information Delivery Manual (IDM) from buildingSMART on Geo-referencing BIM.
- Technical specification32 pagesEnglish languagee-Library read for1 day
This document provides a specification for QR codes for mobile (instant) credit transfers (MCTs) whereby the payer uses a mobile device to initiate the payment transaction. The QR code is used to exchange data between the payer and the payee to enable the initiation of the (instant) credit transfer by the payer.
This document is applicable to both cases where the QR code is presented by the payee or by the payer.
This document excludes the following from its scope:
— The details of technical requirements and the supporting infrastructure to achieve interoperability amongst mobile (instant) credit transfer (MCT) service providers;
— The detailed implementation specification of the payload included in the QR code.
- Draft36 pagesEnglish languagee-Library read for1 day
This document defines universal and specialized characteristics of health terminological resources that make them fit for the purposes required of various applications. It covers only terminological resources that are primarily designed to be used for clinical concept representation or to those parts of other terminological resources designed to be used for clinical concept representation.
This document helps users to assess whether a terminology has the characteristics or provides the functions that will support their specified requirements. In order to do that, this document focuses on defining characteristics and functions of terminological resources in healthcare that can be used to identify different types of terminological resources for categorization purposes.
NOTE 1 Categorization of healthcare terminological systems according to the name of the system might not be helpful and has caused confusion in the past.
The following aspects are not covered in this document:
— evaluations of terminological resources;
— health service requirements for terminological resources and evaluation criteria based on the characteristics and functions;
— the nature and quality of mappings between different terminologies;
NOTE 2 It is unlikely that a single terminology will meet all the terminology requirements of a healthcare organization: some terminology providers produce mappings to administrative or classification systems such as the International Classification of Diseases (ICD). The presence of such maps would be a consideration in the evaluation of the terminology.
— the nature and quality of mappings between different versions of the same terminology;
NOTE 3 To support data migration and historical retrieval, terminology providers can provide maps between versions of their terminology. The presence of such maps would be a consideration in the evaluation of the terminology.
— terminology server requirements and techniques and tools for terminology developers;
— characteristics for computational biology terminology.
- Draft29 pagesEnglish languagee-Library read for1 day
This document prescribes:
— how to document a use case with an associated business context and exchange requirements;
— a methodology to identify and specify the information exchanges required at identified times during the life cycle of assets.
This document presents the information delivery manual (IDM) in natural language terms to facilitate interoperability between software applications used during all phases of the life cycle of assets (both buildings and infrastructure). It promotes digital collaboration between actors within the identified business context and provides a basis for accurate, reliable, repeatable and high-quality information exchange.
The information delivery manual (IDM) methodology specified in this document can be applied to any information management trigger event to identify the details of the information required to be exchanged.
- Standard41 pagesEnglish languagee-Library read for1 day
This document provides a framework that applies to all resources and specifies how to describe resources. It includes rules governing the way in which descriptions are made.
This document provides principles, rules and structures for specifying the description of any type of resource; it identifies and establishes attributes for specifying properties, resources classes, vocabularies and application profiles and the rules governing their use. The key principles set out in this document are framed in a user-centric context and aim to meet the requirements of multilingual and cultural adaptability from a global perspective.
This document can be used for the specification of metadata describing any type of resource (not only learning resources). This document is information-technology-neutral and defines a set of common approaches.
This document specifies generic properties, generic resource classes and predefined rule sets for content value rules. These generic elements are proposed in such a way that they can be widely reused, thereby promoting interoperability.
This document is applicable to the development of:
— application profiles based on the ISO/IEC 19788 series but not part of it or any other document based on it,
— standards consisting of the description of resources (in a broad sense), whether they belong to the domain of education or to any other domain.
- Standard90 pagesEnglish languagee-Library read for1 day
This document specifies test methods for testing conformity of a mobile driving licence (mDL) or an mDL reader to ISO/IEC 18013-5. This document specifies test methods for: - mDL on its interface to an mDL reader; - mDL reader on its interface to an mDL; - mDL reader on its (optional) interface to an issuing authority infrastructure. Test cases for an issuing authority infrastructure on its interface to an mDL reader are not included in this document. Test cases for the use of OpenID Connect (OIDC) by an mDL reader on its interface to an issuing authority infrastructure are not included in this document. This document only provides test cases for the use of WebAPI on this interface. This document only addresses the functional behaviour of an implementation under test (IUT) on its interface(s) in scope. It does not address: - the internal implementation of an IUT, such as a secure area in an mDL; - any functional requirements to an IUT not specified in ISO/IEC 18013-5, for example, requirements of a particular issuing authority; - non-functional aspects of the IUT, nor IUT interfaces not listed above, such as the interface from an issuing authority infrastructure to an mDL, used to provision mDL data.
- Technical specification58 pagesEnglish languagesale 15% off
This document defines the conceptual framework and mechanisms for mapping information elements from building information modelling (BIM) to geographic information systems (GIS) to access the required information based on specific user requirements. The conceptual framework for mapping BIM information to GIS is defined with the following three mapping mechanisms: - BIM to GIS perspective definition (B2G PD); - BIM to GIS element mapping (B2G EM); - BIM to GIS level of detail (LOD) mapping (B2G LM). This document does not describe physical schema integration or mapping between BIM and GIS models because the physical schema integration or mapping between two heterogeneous models is very complex and can cause a variety of ambiguity problems (see REF Annex_D \r \h Annex D 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000800000041006E006E00650078005F0044000000 ). Developing a unified information model between BIM and GIS is a desirable goal, but it is out of the scope of this document. This document is applicable to the following concepts: - definition for BIM to GIS conceptual mapping requirement description; - definition of BIM to GIS conceptual mapping framework and component; - definition of mapping for export from one schema into another. This document does not apply to the following concepts: - definition of any particular mapping application requirement and mechanism; - bi-directional mapping method between BIM and GIS; - definition of physical schema mapping between BIM and GIS; - definition of coordinate system mapping between BIM and GIS; - definition of relationship mapping between BIM and GIS; - implementation of the application schema. NOTE For cases involving requirements related to geo-referencing for providing the position and orientation of the BIM model based on GIS, other standards exist such as REF ISO_19111 \r \h ISO 19111 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000A000000490053004F005F00310039003100310031000000 and the Information Delivery Manual (IDM) from buildingSMART on Geo-referencing BIM.
- Technical specification24 pagesEnglish languagesale 15% off
This document defines universal and specialized characteristics of health terminological resources that make them fit for the purposes required of various applications. It covers only terminological resources that are primarily designed to be used for clinical concept representation or to those parts of other terminological resources designed to be used for clinical concept representation. This document helps users to assess whether a terminology has the characteristics or provides the functions that will support their specified requirements. In order to do that, this document focuses on defining characteristics and functions of terminological resources in healthcare that can be used to identify different types of terminological resources for categorization purposes. NOTE 1 Categorization of healthcare terminological systems according to the name of the system might not be helpful and has caused confusion in the past. The following aspects are not covered in this document: - evaluations of terminological resources; - health service requirements for terminological resources and evaluation criteria based on the characteristics and functions; - the nature and quality of mappings between different terminologies; NOTE 2 It is unlikely that a single terminology will meet all the terminology requirements of a healthcare organization: some terminology providers produce mappings to administrative or classification systems such as the International Classification of Diseases (ICD). The presence of such maps would be a consideration in the evaluation of the terminology. - the nature and quality of mappings between different versions of the same terminology; NOTE 3 To support data migration and historical retrieval, terminology providers can provide maps between versions of their terminology. The presence of such maps would be a consideration in the evaluation of the terminology. - terminology server requirements and techniques and tools for terminology developers; - characteristics for computational biology terminology.
- Standard23 pagesEnglish languagesale 15% off
- Standard25 pagesFrench languagesale 15% off
This document defines markers of harm in online gambling. It is a minimum set of markers to analyse. The individual indicators can be analysed over additional time spans as well as in excess of those re-quired, and other markers can be added to the analysis as well.
In the event that the collection or analysis of data for a limited set of markers is prohibited within a spe-cific jurisdiction (for example, where legislation prevents it), operators can still be compliant with the standard provided that only these markers are omitted, and only for players who fall under that specific jurisdiction.
This document does not provide guidelines regarding the interventions to be employed when addressing individuals with gambling issues, nor does it establish predefined thresholds for intervention.
- Standard19 pagesEnglish languagee-Library read for1 day
This document specifies the categorial structure within the subject field of acupuncture by defining a set of domain constraints of sanctioned characteristics, each composed of a semantic link and an applicable characterizing category, in order to represent the concept of acupuncture point.
- Standard10 pagesEnglish languagesale 15% off
This document prescribes: - how to document a use case with an associated business context and exchange requirements; - a methodology to identify and specify the information exchanges required at identified times during the life cycle of assets. This document presents the information delivery manual (IDM) in natural language terms to facilitate interoperability between software applications used during all phases of the life cycle of assets (both buildings and infrastructure). It promotes digital collaboration between actors within the identified business context and provides a basis for accurate, reliable, repeatable and high-quality information exchange. The information delivery manual (IDM) methodology specified in this document can be applied to any information management trigger event to identify the details of the information required to be exchanged.
- Standard32 pagesEnglish languagesale 15% off
- Standard34 pagesFrench languagesale 15% off
This standard provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS including:
(a) support of each claimed BACnet service, either as an initiator, executor, or both,
(b) support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(c) support of the BACnet network layer protocol,
(d) support of each claimed data link option, and
(e) support of all claimed special functionality.
- Standard990 pagesEnglish languagee-Library read for1 day
This document provides a list of recommended ISO cryptographic algorithms for use within applicable ISO TC 68, Financial services, standards. It also provides strategic guidance on key lengths and associated parameters and usage dates. This document focuses on core algorithms, key lengths and frequently used mechanisms. The included algorithms are considered to be fit for purpose for financial service use. For additional algorithms, see the body of standards produced by ISO/IEC JTC 1 SC 27, Information security, cybersecurity and privacy protection. For standards on key management, see ISO 11568. The categories of algorithms covered are: a) block ciphers and modes of operation; b) stream ciphers; c) message authentication codes (MACs); d) authenticated encryption algorithms; e) format preserving encryption; f) hash functions; g) asymmetric algorithms: 1) digital signature schemes giving message recovery; 2) digital signatures with appendix; 3) asymmetric ciphers. h) authentication mechanisms; i) key derivation, establishment and agreement mechanisms; j) key transport mechanisms: 1) key wrapping. This document does not define any cryptographic algorithms. However, the standards to which this document refers contain necessary implementation information as well as more detailed guidance regarding choice of security parameters, security analysis and other implementation considerations.
- Technical specification36 pagesEnglish languagesale 15% off
This standard specifies a set of Participant Key Purposes (PKPs) pertaining to metric data exchange for the Service-oriented Device Connectivity (SDC) series of standards. PKPs are role-based sets of requirements for products in order to support safe, effective, and secure interoperability in medical IT networks at point-of-care environments such as the intensive care unit (ICU), operating room (OR) or other acute care settings. This standard specifies both product development process and technical requirements.
- Standard46 pagesEnglish languagee-Library read for1 day
The management of electronic transport regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network.
This document describes the operational concept (ConOps) for METR in a format that is consistent with ISO/IEC/IEEE 29148.
- Technical report94 pagesEnglish languagee-Library read for1 day
This standard specifies the base set of Participant Key Purposes (PKPs) for the Service-oriented Device Connectivity (SDC) series of standards. PKPs are role-based sets of requirements for products in order to support safe, effective, and secure interoperability in medical IT networks at point-of-care environments such as the intensive care unit (ICU), operating room (OR) or other acute care settings. This standard specifies both product development process and technical requirements.
- Standard59 pagesEnglish languagee-Library read for1 day
This standard establishes a normative definition of communication between personal health continuous glucose monitor (CGM) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages work done in other ISO/IEEE 11073 standards including existing terminology, information profiles, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments, restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality of CGM devices. In this context, CGM refers to the measurement of the level of glucose in the body on a regular (typically 5 minute) basis through a sensor continuously attached to the person.
- Standard85 pagesEnglish languagee-Library read for1 day
Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between medication monitoring devices and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards, including ISO/IEEE 11073 terminology, information models and application profile. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting ambiguity in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for medication monitors. In this context, medication monitors are defined as devices that have the ability to determine and communicate (to a manager) measures of a user’s adherence to a medication regime.
- Standard82 pagesEnglish languagee-Library read for1 day
This document provides the findings of a global, country-based survey on the current state, challenges and need for standardization in secondary use of clinical genomics data in medicine. This document excludes the primary use of clinical genomics data as well as specific data, metadata, or policies regarding the secondary use of clinical genomics data.
- Technical report13 pagesEnglish languagesale 15% off
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard56 pagesEnglish languagee-Library read for1 day
IEC 63489:2025 specifies the definition of cross-domain product data concepts (classes and properties) in the context of smart manufacturing.
This document will be published as a set of concepts within cross-domain data dictionary "General Items (IEC 61360-7)” in the IEC CDD.
- Standard13 pagesEnglish languagee-Library read for1 day
IEC 62541-18: 2025 defines an Information Model. The Information Model describes the basic infrastructure to model role-based security.
NOTE In the previous version, Role-Based Security was in IEC 62541-5:2020, Annex F.
- Standard34 pagesEnglish languagee-Library read for1 day
This document extends the base nomenclature provided in ISO/IEEE 11073-10101:2020 to support terminology for implantable cardiac devices. Devices within the scope of this nomenclature are implantable devices such as pacemakers, defibrillators, devices for cardiac resynchronization therapy, and implantable cardiac monitors. This nomenclature defines the terms necessary to convey a clinically relevant summary of the information obtained during a device interrogation. The nomenclature extensions may be used in conjunction with other IEEE 11073 standard components (e.g., ISO/IEEE 11073-10201 [B2] ) or with other standards, such as Health Level Seven International (HL7).
- Standard145 pagesEnglish languagee-Library read for1 day
Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between independent living activity hubs and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards, including ISO/IEEE 11073 terminology and information models. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting ambiguity in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for independent living activity hubs. In this context, independent living activity hubs are defined as devices that communicate with simple situation monitors (binary sensors), normalize information received from the simple environmental monitors, and provide this normalized information to one or more managers. This information can be examined, for example, to determine when a person’s activities/behaviors have deviated significantly from what is normal for them such that relevant parties can be notified. Independent living activity hubs will normalize information from the following simple situation monitors (binary sensors) for the initial release of the proposed standard: fall sensor, motion sensor, door sensor, bed/chair occupancy sensor, light switch sensor, smoke sensor, (ambient) temperature threshold sensor, personal emergency response system (PERS), and enuresis sensor (bed-wetting).
- Standard46 pagesEnglish languagee-Library read for1 day