Standard

ISO/IEC 29182-2:2013 is intended to facilitate the development of International Standards in sensor networks. It presents terms and definitions for selected concepts relevant to the field of sensor networks. It establishes a general description of concepts in this field and identifies the relationships among those concepts. It may also be used as guidance for development of other parts of ISO/IEC 29182 and any other sensor network related standard.

ISO/IEC 29182-1:2013 provides a general overview of the characteristics of a sensor network and the organization of the entities that comprise such a network. It also describes the general requirements that are identified for sensor networks.

ISO/IEC TR 22560:2017(E) This Technical Report describes the concepts, issues, objectives, and requirements for the design of an active air-flow control (AFC) system for commercial aircraft based on a dense deployment of wired and wireless sensor and actuator networks. It focuses on the architecture design, module definition, statement of objectives, scalability analysis, system-level simulation, as well as networking and implementation issues using standardized interfaces and service-oriented middleware architectures.

ISO/IEC TR 22417:2017(E) This technical report identifies IoT scenarios and use cases based on real-world applications and requirements. The use cases provide a practical context for considerations on interoperability and standards based on user experience. They also clarify where existing standards can be applied and highlight where standardization work is needed.

ISO/IEC 30140-4:2018 The ISO/IEC 30140 series provides general requirements, reference architecture and high-level interface guidelines supporting interoperability among underwater acoustic sensor networks (UWASNs). Part 4 provides information on interoperability requirements among entities within a UWASN and among various UWASNs.

Master-Slave/Token-Passing (MS/TP) is a medium access control method for the RS-485 physical layer and is used primarily in building automation networks. This specification defines the frame format for transmission of IPv6 packets and the method of forming link-local and statelessly autoconfigured IPv6 addresses on MS/TP networks.

This document specifies a set of representational primitives and semantic relations needed for an unambiguous representation of explicit time-related expressions in health informatics. This document does not introduce or force a specific ontology of time, nor does it force the use of a fixed representation scheme for such an ontology. Rather this document provides a set of principles for syntactic and semantic representation that allow the comparability of specific ontologies on time and the exchange of time-related information that is expressed explicitly. This document applies to both the representation of actual phenomena occurring in the real world (e.g. registrations in medical records) and to the description of concepts (e.g. medical knowledge bases). This document is applicable to a) developers of medical information systems where there might be a need for explicit time-related concepts for internal organization (e.g. temporal databases, temporal reasoning systems), b) information modellers or knowledge engineers building models for the systems mentioned in a), c) experts involved in the development of semantic standards on precise subdomains in health care where time-related information needs to be covered, (e.g. in the study of pathochronology, i.e. the discipline dealing with the time course of specific diseases), and d) developers of interchange formats for messages in which time-related information is embedded. This document is not intended to be used directly for — representing what is true in time, — reasoning about time, or — representation of metrological time.

The Unique Device Identifier (UDI) Pattern provides the guidelines for exchanging UDI information associated with medical devices, initially implantable devices in patients.  This document will not give implementation guidance for specific use cases and worfklows, but will set the overarching guidelines for all working groups that need to exchange the unique device identification on the fields and format intended for expressing UDI related data using V2, V3, and FHIR.  The goal of the UDI Pattern is to enable semantic interoperability for recording UDI information on medical devices used on or implanted in patients regardless of the information exchange standard used to move the information across (e.g., HL7 Version 2.x, HL7 v3 messages or CDA, HL7 FHIR).

The scope of the standard is to define the message for exchanging information electronically between Regulators and Industry, and between sets of regulators. The message provides the ability to describe the contents of the regulatory exchange and all information needed to process the exchange between parties. This message is designed to be flexible enough to be used to support regulatory exchanges for any regulated product.

The Privacy and Security Architecture Framework (PSAF) is the overarching package that contains four balloted specifications and an informative guide.  The specific normative components include: 1) Trust Framework for Federated Authorization Conceptual Model, 2) Trust Framework for Federated Authorization Behavioral Model, 3) Provenance Domain Analysis Model and 4) Audit.  The intent of these standards is to provide an integrated package of a set of standards to advance communication and interoperability among partners in a shared trust framework environment.

Many seemingly healthy babies with Critical Congenital Heart Disease (CCHD) may suffer negative health outcomes if the birth defect is not identified shortly after birth. International efforts have precipitated both program and legislative initiatives to promote and/or mandate universal newborn screening for Critical Congenital Heart Disease using pulse oximetry devices. When pulse oximetry devices are able to exchange data with information systems, the use of standards helps with the seamless exchange of data and improve patient safety. This implementation guide focuses on the transmission of CCHD screening data from the device to the public health program, other potential recipients including providers and electronic health records.

Early Hearing Detection and Intervention (EHDI) programs exist world-wide to help identify children with hearing loss. Because newborn hearing loss is a neuro-developmental emergency, children with hearing loss need to be identified shortly after birth to help them achieve better communication outcomes. This implementation guide focuses on the transmission of the hearing screening data elements from the hearing screening device to a recipient of data, which may be an electronic health record (EHR) or a Public Health Information System.