Informationsteknik, kontorsutrustning

Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal basic electrocardiograph (ECG) devices and managers (e.g. cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability is established in ISO/IEEE11073-10406:2012. Appropriate portions of existing standards including ISO/IEEE 11073 terminology and IEEE 11073-20601 information models are leveraged. The use of specific term codes, formats and behaviours in telehealth environments restricting optionality in base frameworks in favour of interoperability is specified. A common core of communication functionality for personal telehealth basic ECG (1- to 3-lead ECG) devices is defined. Monitoring ECG devices are distinguished from diagnostic ECG equipment with respect to support for wearable ECG devices, limiting the number of leads supported by the equipment to three, and not requiring the capability of annotating or analysing the detected electrical activity to determine known cardiac phenomena. ISO/IEEE 11073-10406:2012 is consistent with the base framework and allows multifunction implementations by following multiple device specializations (e.g. ECG and respiration rate).

Within the context of the ISO/IEEE 11073 family of standards for device communication, ISO/IEEE 11073-10417:2017 establishes a normative definition of communication between personal telehealth glucose meter devices and compute engines (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, information models, 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 for personal telehealth glucose meters.

This standard will provide a description of the numbering system replacing the DOMES numbering. The description of the DOMES numbering can be found in MERIT/COTES joint working groups, MERIT campaign: connection of reference frames, implementation plan, 1983. The standard will provide to the geodetic data producers and users a proper identification of the permanently instrumented stations, (e.g. those used in the production of the International Terrestrial Reference Frame and other similar stations), with special emphasis on the backward compatibility with existing DOMES numbers, which will have a positive impact on interoperability issues when merging several data from different communities. This standard will: • support interoperability among GNSS providers (GPS, GLONASS, GALILEO, BEIDOU, …) • clarify the potential confusion between communities which have already adopted their own numbering systems • support the UNGGIM GGRF resolution on global geodetic infrastructure.

Abstract: Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal strength fitness devices 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 optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for personal telehealth strength fitness devices. In this context, strength fitness devices are being used broadly to cover strength fitness devices that measure musculo-skeletal strength-conditioning activities. Keywords: medical device communication, personal health devices, strength fitness equipment

This standard establishes a normative definition of communication between personal telehealth insulin pump 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 functionality of personal telehealth insulin pump devices. In the context of personal health devices (PHDs), an insulin pump is a medical device used for the administration of insulin in the treatment of diabetes mellitus, also known as continuous subcutaneous insulin infusion (CSII) therapy. This standard provides the data modeling according to ISO/IEEE 11073-20601 and does not specify the measurement method.

Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal basic electrocardiograph (ECG) devices and managers (e.g. cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability is established in ISO/IEEE11073-10406:2012. Appropriate portions of existing standards including ISO/IEEE 11073 terminology and IEEE 11073-20601 information models are leveraged. The use of specific term codes, formats and behaviours in telehealth environments restricting optionality in base frameworks in favour of interoperability is specified. A common core of communication functionality for personal telehealth basic ECG (1- to 3-lead ECG) devices is defined. Monitoring ECG devices are distinguished from diagnostic ECG equipment with respect to support for wearable ECG devices, limiting the number of leads supported by the equipment to three, and not requiring the capability of annotating or analysing the detected electrical activity to determine known cardiac phenomena. ISO/IEEE 11073-10406:2012 is consistent with the base framework and allows multifunction implementations by following multiple device specializations (e.g. ECG and respiration rate).

Within the context of the ISO/IEEE 11073 family of standards for device communication, ISO/IEEE 11073-10417:2017 establishes a normative definition of communication between personal telehealth glucose meter devices and compute engines (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, information models, 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 for personal telehealth glucose meters.

Abstract: Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal strength fitness devices 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 optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for personal telehealth strength fitness devices. In this context, strength fitness devices are being used broadly to cover strength fitness devices that measure musculo-skeletal strength-conditioning activities. Keywords: medical device communication, personal health devices, strength fitness equipment

Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal basic electrocardiograph (ECG) devices and managers (e.g. cell phones, personal computers, personal health appliances, and set top boxes) in a manner that enables plug-and-play interoperability is established in ISO/IEEE11073-10406:2012. Appropriate portions of existing standards including ISO/IEEE 11073 terminology and IEEE 11073-20601 information models are leveraged. The use of specific term codes, formats and behaviours in telehealth environments restricting optionality in base frameworks in favour of interoperability is specified. A common core of communication functionality for personal telehealth basic ECG (1- to 3-lead ECG) devices is defined. Monitoring ECG devices are distinguished from diagnostic ECG equipment with respect to support for wearable ECG devices, limiting the number of leads supported by the equipment to three, and not requiring the capability of annotating or analysing the detected electrical activity to determine known cardiac phenomena. ISO/IEEE 11073-10406:2012 is consistent with the base framework and allows multifunction implementations by following multiple device specializations (e.g. ECG and respiration rate).

This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services and re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of their content and syntax. The data structures are specified as communications-agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.

This document specifies:

—   the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;

—   an exchange of information between the back-office system of the two roles of service provision and toll charging, e.g.:

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

—  administrative data (trust objects, EFC context data, etc.), and

—  confirmation data;

—   transfer mechanisms and supporting functions;

—   information objects, data syntax and semantics.

This document is applicable for any vehicle-related toll service and any technology used for charging.

The data types and associated coding related to the data elements described in Clause 6 are specified in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.

This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).

This document does not specify, amongst others:

—   any communication between TC or TSP with any other involved party;

—   any communication between elements of the TC and the TSP that is not part of the back-office communication;

—   interfaces for EFC systems for public transport;

—   any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve several APDU exchanges;

—   processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;

—   definitions of service communication channels, protocols and service primitives to transfer the APDU.

Amendment

1  Scope

Replace the last paragraph with the following text (in which “any complex transfers (transactions), i.e. 

sequences of inter-related ADUs that can possibly involve several APDU exchanges has been removed”):

This document does not specify, amongst others:

— any communication between TC or TSP with any other involved party;

— any communication between elements of the TC and the TSP that is not part of the back-office 

communication;

— interfaces for EFC systems for public transport;

— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;

— definitions of service communication channels, protocols and service primitives to transfer the APDU.

This document specifies methodologies for measuring the performance of AI models for classification, regression, clustering and recommendation tasks.

This document specifies the test method and performance metrics to evaluate the behaviour of a vehicle equipped with rear cross traffic alerting system during several collision scenarios. These collisions occur during straight-line reverse manoeuvres when the vehicle under test (VUT) approaches other vehicles or traffic participants.

This document applies to M1 category vehicles.

Note: Depending on accidentology, only a part of the scenarios can be used for an evaluation of performance.

This document specifies the test method and performance metrics to evaluate the behaviour of a vehicle equipped with rear cross traffic alerting system during several collision scenarios. These collisions occur during straight-line reverse manoeuvres when the vehicle under test (VUT) approaches other vehicles or traffic participants.

This document applies to M1 category vehicles.

Note: Depending on accidentology, only a part of the scenarios can be used for an evaluation of performance.

The scope of this project is to provide guidelines for information exchange between BIM and GIS. As part of a series of proposed international standards for BIM-GIS information exchange, Part 01: core principles and specifications will provide guidance on how to use existing standards adequately so that each domain can provide and request information properly. This work needs to be sufficiently broad by integrating ISO Standards and the latest developments from OGC and buildingSMART. The work will also cover the core principles of working with BIM and GIS, namely ensuring the Georeferencing of BIM models.

The scope of this project is to provide guidelines for information exchange between BIM and GIS. As part of a series of proposed international standards for BIM-GIS information exchange, Part 02: Facilitating data exchange through metadata will aim to solve metadata issues to support bidirectional GIS/BIM information exchange and suggest technical requirements based on use case scenarios. Metadata give great opportunities to find, evaluate and manage relevant information for the bidirectional information exchange. To ensure the interoperability between GIS and BIM information models, it is critical for one domain experts to understand the metadata generated from the other domain and vice versa. The work will review existing methodologies and research with regard to bidirectional GIS/BIM information exchange, especially in terms of metadata and item registration. It will provide a use case scenario to give a certain context of bidirectional exchange of metadata. The use case will also provide the context within which the interaction that needs to be taken place between GIS and BIM model experts. With the use of the use case scenario, the process of properly generating metadata for each domain to ensure the bidirectional exchange can be identified. It will then list the technical requirements to support the process and provide a guideline to follow.

This document outlines the conceptual framework and methodology for linking abstract concepts between BIM and GIS standards to facilitate BIM/GIS interoperability. This document provides the mechanisms to establish links between abstract concepts in both domains in terms of metamodels, abstract conceptual schemas and application schemas.

This document specifies additional requirements to ISO/IEC 17021-1. The requirements contained in this document, when implemented, support the demonstration of competence, consistency and reliability by the bodies performing auditing and certification of an artificial intelligence management system (AIMS) according to ISO/IEC 42001 for organizations that provide, develop or use AI systems. Certification of AIMS is a third-party conformity assessment activity (as described in ISO/IEC 17000:2020, 4.5), and bodies performing this activity are third-party conformity assessment bodies. This document also provides the necessary information and confidence to customers about the way certification has been granted. NOTE This document can be used as a criteria document for accreditation or peer assessment.

This document provides a high-level framework and guidance for the development and operation of conformity assessment schemes, including certification schemes, for artificial intelligence (AI) systems.

This standard proposal outlines artificial intelligence (AI) concepts, applications, and implications, as well as benefits, risks, governance framework, and scope for use by organizations within the context of project, programme, and portfolio management (P3M). This proposed standard is intended to supplement the other TC 258 standards and is in direct alignment with standards prepared by ISO/TC 258. This document provides guidance for organizations on what to consider when adopting or looking to improve on existing AI technologies that directly support P3M. This proposed standard is applicable to any organization, including public, private, and charitable, as well as to any type of project, regardless of purpose, delivery approaches, project or programme lifecycle model used, complexity, size, cost, or duration. This document also provides (P3M) practitioners (including top-level management, project managers, PMO’s, etc.) with AI-related guidance and consideration in the areas of security, privacy, transparency, and bias, as well as related data governance, ethical and risk considerations.