Information service
35 Information technology
New standards
EVS-EN IEC 61918:2018/A2:2024
Industrial communication networks - Installation of communication networks in industrial premises
Scope:
Amendment to EN IEC 61918:2018
Base documents:
IEC 61918:2018/AMD2:2024; EN IEC 61918:2018/A2:2024
EVS-EN ISO 9241-115:2024
Ergonomics of human-system interaction - Part 115: Guidance on conceptual design, user-system interaction design, user interface design, and navigation design (ISO 9241-115:2024)
Scope:
This document provides guidance on aspects of the design of human-system interaction, including conceptual design, user-system interaction design, user interface design and navigation design for interactive systems.
This document applies to all design and development approaches and methodologies, including human-centred design, object-oriented, waterfall, human factors integration (HFI), agile and rapid development.
It is intended for the following types of users:
— user interface designers, who will apply the guidance during the development process;
— developers, who will apply the guidance during the design and implementation of system functionality;
— evaluators, who are responsible for ensuring that products meet the recommendations;
— designers of user interface development tools and style guides to be used by user interface designers;
— project managers, who are responsible for managing development processes.
This document applies to all design and development approaches and methodologies, including human-centred design, object-oriented, waterfall, human factors integration (HFI), agile and rapid development.
It is intended for the following types of users:
— user interface designers, who will apply the guidance during the development process;
— developers, who will apply the guidance during the design and implementation of system functionality;
— evaluators, who are responsible for ensuring that products meet the recommendations;
— designers of user interface development tools and style guides to be used by user interface designers;
— project managers, who are responsible for managing development processes.
Base documents:
ISO 9241-115:2024; EN ISO 9241-115:2024
Replaces:
EVS-EN ISO 14915-2:2011
EVS-ISO/IEC 27032:2024
Cybersecurity — Guidelines for Internet security (ISO/IEC 27032:2023, identical)
Scope:
This document provides:
— an explanation of the relationship between Internet security, web security, network security and cybersecurity;
— an overview of Internet security;
— identification of interested parties and a description of their roles in Internet security;
— high-level guidance for addressing common Internet security issues.
This document is intended for organizations that use the Internet.
Base documents:
ISO/IEC 27032:2023
Replaces:
EVS-ISO/IEC 27032:2018
ISO/IEC 15944-17:2024
Information technology — Business operational view — Part 17: Fundamental principles and rules governing Privacy-by-Design (PbD) requirements in an EDI and collaboration space context
Scope:
This document:
a) focuses on PbD aspects of privacy protection requirements as external constraints on any type of Person, (e.g. organization or public administration) involved in any kind of business transaction among such Persons which involves the electronic data interchange (EDI) of any personal information;
b) establishes a fundamental set of privacy principles known as Privacy by Design and assumptions based on primary sources;
c) integrates existing normative elements in support of PbD as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO 15944-12;
d) provides overarching operational ‘best practice’ statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that need to act in support of implementing and enforcing technical mechanisms that support PbD in Open-edi transaction and collaboration space environments;
e) focuses on PbD related aspects of the life cycle management of and accountability for the personal information, i.e. the contents of SPIs (and their SRIs) related to the business transaction interchanged via EDI as information bundles and their associated semantic components among the parties to a business transaction.
This document focuses on the BOV aspects of a business transaction and does not concern itself with the technical mechanisms needed to implement the FSV aspects of the business requirements of the FSV including the specification of requirements of an FSV nature which include security techniques and services, communication protocols, etc.). The FSV includes any existing standard (or standards development of an FSV nature), which has been ratified by existing ISO, IEC, UN/ECE and/or ITU standards.
This document does not specify the technical mechanisms, i.e. FSV which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex D.
a) focuses on PbD aspects of privacy protection requirements as external constraints on any type of Person, (e.g. organization or public administration) involved in any kind of business transaction among such Persons which involves the electronic data interchange (EDI) of any personal information;
b) establishes a fundamental set of privacy principles known as Privacy by Design and assumptions based on primary sources;
c) integrates existing normative elements in support of PbD as are already identified in ISO/IEC 14662 and ISO/IEC 15944-1, ISO/IEC 15944-5, ISO/IEC 15944-8, ISO 15944-12;
d) provides overarching operational ‘best practice’ statements for associated (and not necessarily automated) processes, procedures, practices and governance requirements that need to act in support of implementing and enforcing technical mechanisms that support PbD in Open-edi transaction and collaboration space environments;
e) focuses on PbD related aspects of the life cycle management of and accountability for the personal information, i.e. the contents of SPIs (and their SRIs) related to the business transaction interchanged via EDI as information bundles and their associated semantic components among the parties to a business transaction.
This document focuses on the BOV aspects of a business transaction and does not concern itself with the technical mechanisms needed to implement the FSV aspects of the business requirements of the FSV including the specification of requirements of an FSV nature which include security techniques and services, communication protocols, etc.). The FSV includes any existing standard (or standards development of an FSV nature), which has been ratified by existing ISO, IEC, UN/ECE and/or ITU standards.
This document does not specify the technical mechanisms, i.e. FSV which are required to support BOV-identified requirements. Detailed exclusions to the scope of this document are provided in Annex D.
Base documents:
ISO/IEC 39075:2024
Information technology — Database languages — GQL
Scope:
This document defines data structures and basic operations on property graphs. It provides capabilities for creating, accessing, querying, maintaining, and controlling property graphs and the data they comprise.
This document specifies the syntax and semantics of a data management language for specifying and modifying the structure of property graphs and collections thereof.
This document provides a vehicle for portability of data definitions and manipulation among GQL-implementations. Implementations of this document can exist in environments that also support application programming languages, end-user query facilities, and various tools for database design, data administration, and performance optimization.
This document specifies the syntax and semantics of a data management language for specifying and modifying the structure of property graphs and collections thereof.
This document provides a vehicle for portability of data definitions and manipulation among GQL-implementations. Implementations of this document can exist in environments that also support application programming languages, end-user query facilities, and various tools for database design, data administration, and performance optimization.
Base documents:
ISO/IEC TR 24030:2024
Information technology — Artificial intelligence (AI) — Use cases
Scope:
This document provides a collection of representative use cases of AI applications in a variety of domains.
Base documents:
Replaces:
ISO/IEC TR 24030:2021
ISO/IEC TS 8200:2024
Information technology — Artificial intelligence — Controllability of automated artificial intelligence systems
Scope:
This document specifies a basic framework with principles, characteristics and approaches for the realization and enhancement for automated artificial intelligence (AI) systems’ controllability.
The following areas are covered:
— state observability and state transition;
— control transfer process and cost;
— reaction to uncertainty during control transfer;
— verification and validation approaches.
This document is applicable to all types of organizations (e.g. commercial enterprises, government agencies, not-for-profit organizations) developing and using AI systems during their whole life cycle.
The following areas are covered:
— state observability and state transition;
— control transfer process and cost;
— reaction to uncertainty during control transfer;
— verification and validation approaches.
This document is applicable to all types of organizations (e.g. commercial enterprises, government agencies, not-for-profit organizations) developing and using AI systems during their whole life cycle.
Base documents:
ISO/IEC 23415:2024
Information technology — Data Format Description Language (DFDL) v1.0 Specification
Scope:
Base documents:
ISO/IEC 24778:2024
Information technology — Automatic identification and data capture techniques — Aztec Code bar code symbology specification
Scope:
This document defines the requirements for the symbology known as Aztec Code. It specifies the Aztec Code symbology characteristics, including:
— data character encodation;
— rules for error control encoding;
— the graphical symbol structure;
— symbol dimensions and print quality requirements;
— a reference decoding algorithm;
— user-selectable application parameters.
— data character encodation;
— rules for error control encoding;
— the graphical symbol structure;
— symbol dimensions and print quality requirements;
— a reference decoding algorithm;
— user-selectable application parameters.
Base documents:
Replaces:
ISO/IEC 24778:2008
ISO/IEC 5212:2024
Information technology — Data usage — Guidance for data usage
Scope:
This document provides high-level guidance to data users, whether organizations or individuals, to assist in realizing the benefits from data usage while managing risks.
Base documents:
ISO/IEC 5207:2024
Information technology — Data usage — Terminology and use cases
Scope:
This document sets out terminology and use cases for data use, sharing and exchange. This document provides use cases detailing various types of data usage from both historical and hypothetical perspectives.
This document is applicable to all types of organizations.
This document is applicable to all types of organizations.
Base documents:
IEC 61784-3:2021/AMD1:2024
Amendment 1 - Industrial communication networks - Profiles - Part 3: Functional safety fieldbuses - General rules and profile definitions
Scope:
Base documents:
IEC 61784-3:2021+AMD1:2024 CSV
Industrial communication networks - Profiles - Part 3: Functional safety fieldbuses - General rules and profile definitions
Scope:
IEC 61784-3:2021+AMD1:2024 CSV explains some common principles that can be used in the transmission of safety-relevant messages among participants within a distributed network which use fieldbus technology in accordance with the requirements of IEC 61508 (all parts) for functional safety. These principles are based on the black channel approach. They can be used in various industrial applications such as process control, manufacturing automation and machinery.
Base documents:
ISO 5201:2024
Financial services — Code-scanning payment security
Scope:
This document provides an overview, risk assessment, minimum security requirements and extended security guidelines for code-scanning payment in which the payer uses a mobile device to operate the payment transaction.
This document is applicable to cases where the payment code is used to initiate a mobile payment and presented by either the payer or the payee.
The following is excluded from the scope of this document:
— details of payer and payee onboarding;
— details of the supporting payment infrastructure, as described in 5.1.
This document is applicable to cases where the payment code is used to initiate a mobile payment and presented by either the payer or the payee.
The following is excluded from the scope of this document:
— details of payer and payee onboarding;
— details of the supporting payment infrastructure, as described in 5.1.
Base documents:
ISO/TR 17783:2024
Intelligent transport systems — Mobility integration — Role and functional model for mobility services using low Earth orbit (LEO) satellite systems
Scope:
This document describes a basic role and functional model for mobility services using low Earth orbit (LEO) satellite systems for ITS services. This document provides:
a) a role and functional model using a LEO satellite system for mobility services;
b) a description of the concept of operations (CONOPS), and the relevant role models;
c) a conceptual architecture between actors involved;
d) references for the key documents on which the architecture is based;
e) a mobility service use case summary.
In-vehicle control systems are not within the scope of this document.
This document scope is limited to mobility services using physical and digital infrastructure.
NOTE Physical infrastructure facilities include for example, battery charging facilities, dynamic charging facilities for battery electric vehicles, physical infrastructure markings, physical traffic regulation signs, mobility monitoring facilities, emergency response service support facilities, traffic operation control centre facilities, fee collection service facilities (e.g. road usage fee), battery electric vehicle charging facilities, online reservation and online mobility usage fee payment facilities, and other infrastructure platform facilities that support ITS mobility services.
a) a role and functional model using a LEO satellite system for mobility services;
b) a description of the concept of operations (CONOPS), and the relevant role models;
c) a conceptual architecture between actors involved;
d) references for the key documents on which the architecture is based;
e) a mobility service use case summary.
In-vehicle control systems are not within the scope of this document.
This document scope is limited to mobility services using physical and digital infrastructure.
NOTE Physical infrastructure facilities include for example, battery charging facilities, dynamic charging facilities for battery electric vehicles, physical infrastructure markings, physical traffic regulation signs, mobility monitoring facilities, emergency response service support facilities, traffic operation control centre facilities, fee collection service facilities (e.g. road usage fee), battery electric vehicle charging facilities, online reservation and online mobility usage fee payment facilities, and other infrastructure platform facilities that support ITS mobility services.
Base documents:
ISO/IEC 33071:2016/Cor 1:2024
Information technology — Process assessment — An integrated process capability assessment model for Enterprise processes — Technical Corrigendum 1
Scope:
Corrigendum to ISO/IEC 33071:2016
Base documents:
ISO/IEC 22460-2:2024
Cards and security devices for personal identification — ISO UAS license and drone/UAS security module — Part 2: Drone/UAS security module
Scope:
This document specifies cryptographic functions of the drone/unmanned aircraft system (UAS) security module. The drone/UAS security module is a security device that serves as a container for the drone/UAS pilot license, drone/UAS operator license, and other personal identification. It provides storage space for storing optional elements and has the capability of cryptographic functions including integrity validation, authentication and data encryption.
Base documents:
CEN/TS 18026:2024
Three-level approach for a set of cybersecurity requirements for cloud services
Scope:
This Technical Specification (TS) provides a set of cybersecurity requirements for cloud services.
This TS is applicable to organizations providing cloud services and their subservice organizations
This TS is applicable to organizations providing cloud services and their subservice organizations
Base documents:
CEN/TS 18026:2024
ISO/IEC 5087-2:2024
Information technology — City data model — Part 2: City level concepts
Scope:
This document defines an ontology for city-level concepts defined using terms specified in ISO/IEC 5087-1. City-level concepts are used to represent data that is shared across multiple services and stakeholders in the city. City-level concepts are distinguished by their data being read and updated by multiple city services and stakeholders.
Base documents:
ISO 9241-820:2024
Ergonomics of human-system interaction — Part 820: Ergonomic guidance on interactions in immersive environments, including augmented reality and virtual reality
Scope:
This document identifies ergonomic or human-systems issues and guidance for the development and use of systems involving immersive environments, augmented reality and virtual reality. This includes:
a) environments where the user is provided with a perception of being physically present in a virtually-created world;
b) environments where the user is represented virtually and can interact in a real-world environment;
c) environments involving artificial reality, augmented reality, virtual reality, mixed reality and similar simulated realities;
d) computer-generated environments where the user interacts with simulated objects in a manner similar to how the user would interact with the real-world counterparts of these objects.
This document is not an exploration of the philosophical, ethical or political issues surrounding the use of immersive environments.
This document limits its treatment of the technologies used to create immersive environments to focusing on their interactions with users and does not investigate other aspects of these technologies.
The target audience for this document is decision-makers, designers and engineers who would benefit from the consideration of human-systems issues of immersive environments. Futurists, researchers, technology developers, regulators and legislators could also find this document useful.
a) environments where the user is provided with a perception of being physically present in a virtually-created world;
b) environments where the user is represented virtually and can interact in a real-world environment;
c) environments involving artificial reality, augmented reality, virtual reality, mixed reality and similar simulated realities;
d) computer-generated environments where the user interacts with simulated objects in a manner similar to how the user would interact with the real-world counterparts of these objects.
This document is not an exploration of the philosophical, ethical or political issues surrounding the use of immersive environments.
This document limits its treatment of the technologies used to create immersive environments to focusing on their interactions with users and does not investigate other aspects of these technologies.
The target audience for this document is decision-makers, designers and engineers who would benefit from the consideration of human-systems issues of immersive environments. Futurists, researchers, technology developers, regulators and legislators could also find this document useful.
Base documents:
ISO/TS 32004:2024
Document management — Portable Document Format — Integrity protection in encrypted documents in PDF 2.0
Scope:
This document specifies how to extend the ISO 32000-2:2020 specification by adding extensions to the Encrypt dictionary and trailer dictionary to provide integrity protection to the encrypted PDF document. This document also ensures that extensions are fully backward-compatible.
These extensions are intended for developers of software that creates PDF files (PDF writers), software that reads existing PDF files and (usually) interprets their contents for display (PDF readers), software that reads and displays PDF content and interacts with the computer users to possibly modify and save the PDF file (interactive PDF processors) and PDF products that read and/or write PDF files for a variety of other purposes (PDF processors).
NOTE PDF writers and PDF readers are more specialized classifications of interactive PDF processors and both are PDF processors.
This document does not specify the following:
— specific processes for converting paper or electronic documents to the PDF file format;
— specific technical design, user interface implementation, or operational details of rendering;
— specific physical methods of storing these documents such as media and storage conditions;
— methods for validating the conformance of PDF files or PDF processors;
— required computer hardware and/or operating system.
These extensions are intended for developers of software that creates PDF files (PDF writers), software that reads existing PDF files and (usually) interprets their contents for display (PDF readers), software that reads and displays PDF content and interacts with the computer users to possibly modify and save the PDF file (interactive PDF processors) and PDF products that read and/or write PDF files for a variety of other purposes (PDF processors).
NOTE PDF writers and PDF readers are more specialized classifications of interactive PDF processors and both are PDF processors.
This document does not specify the following:
— specific processes for converting paper or electronic documents to the PDF file format;
— specific technical design, user interface implementation, or operational details of rendering;
— specific physical methods of storing these documents such as media and storage conditions;
— methods for validating the conformance of PDF files or PDF processors;
— required computer hardware and/or operating system.
Base documents:
Replaced standards
EVS-EN ISO 14915-2:2011
Software ergonomics for multimedia user interfaces - Part 2: Multimedia navigation and control (ISO 14915-2:2003)
Scope:
This part of ISO 14915 provides recommendations and requirements for the design of multimedia user interfaces with respect to the following aspects: design of the organization of the content, navigation and media-control issues. This part of ISO 14915 is limited to the design of the organization of the content and does not deal with the design of the content in general. Design issues within a single medium (e.g. the lighting of a film sequence) are only addressed with respect to the ergonomic issues related to user controls. This part of ISO 14915 provides a framework for the structuring of multimedia applications, information and recommendations on the design of navigation structures and navigation mechanisms for use within multimedia applications, and information and recommendations on the design of controls for use within multimedia applications. It does not specifically address entertainment applications, although some recommendations can also be applicable to that domain. ISO 14915 does not address implementation issues. The ergonomic requirements can be realised through very different mechanisms, e.g. the delivery system, a scripting language or the application.
Base documents:
ISO 14915-2:2003; EN ISO 14915-2:2003
Replaced:
EVS-EN ISO 9241-115:2024
ISO/IEC 24778:2008
Information technology -- Automatic identification and data capture techniques -- Aztec Code bar code symbology specification
Scope:
Aztec Code is a two-dimensional matrix symbology whose symbols are nominally square, made up of square modules on a square grid, with a square bullseye pattern at their centre. Aztec Code symbols can encode from small to large amounts of data with user-selected percentages of error correction.
Manufacturers of bar code equipment and users of the technology require publicly available standard symbology specifications to which they can refer when developing equipment and application standards. The publication of standardized symbology specifications is designed to achieve this.
ISO/IEC 24778:2008 defines the requirements for the Aztec Code symbology. It specifies the Aztec Code symbology characteristics including data character encodation, rules for error control encoding, the graphical symbol structure, symbol dimensions and print quality requirements, a reference decoding algorithm, and user-selectable application parameters.
Manufacturers of bar code equipment and users of the technology require publicly available standard symbology specifications to which they can refer when developing equipment and application standards. The publication of standardized symbology specifications is designed to achieve this.
ISO/IEC 24778:2008 defines the requirements for the Aztec Code symbology. It specifies the Aztec Code symbology characteristics including data character encodation, rules for error control encoding, the graphical symbol structure, symbol dimensions and print quality requirements, a reference decoding algorithm, and user-selectable application parameters.
Base documents:
Replaced:
ISO/IEC 24778:2024
ISO/TR 11487:2008
Health informatics -- Clinical stakeholder participation in the work of ISO TC 215
Scope:
ISO/TR 11487:2008 is structured around four review areas:
stakeholder groups concerned with the work of TC 215;
potential benefits/outcomes of clinical stakeholder participation;
current nature of stakeholder participation;
recommendations for improving clinical stakeholder participation.
The review is limited to clinical stakeholder groups. Stakeholders from industry, consumer groups and other non-clinical groups are outside the scope of this Technical Report as are the specific issues related to participation of clinical stakeholders in developing countries.
The content of ISO/TR 11487:2008 is based on informal consultation among delegates attending TC 215 meetings and e-mail communication with interested individuals. Opportunities to comment on the draft report were provided prior to and during the 2007 Montreal plenary meeting in accordance with the TC Resolution at 2006 Jeju plenary.
The purposes of ISO/TR 11487:2008 are:
to clarify and confirm TC 215 support for clinical stakeholder participation;
to make recommendations to the TC and to national member organizations on approaches to improving clinical stakeholder participation based on examples of existing effective participation models.
stakeholder groups concerned with the work of TC 215;
potential benefits/outcomes of clinical stakeholder participation;
current nature of stakeholder participation;
recommendations for improving clinical stakeholder participation.
The review is limited to clinical stakeholder groups. Stakeholders from industry, consumer groups and other non-clinical groups are outside the scope of this Technical Report as are the specific issues related to participation of clinical stakeholders in developing countries.
The content of ISO/TR 11487:2008 is based on informal consultation among delegates attending TC 215 meetings and e-mail communication with interested individuals. Opportunities to comment on the draft report were provided prior to and during the 2007 Montreal plenary meeting in accordance with the TC Resolution at 2006 Jeju plenary.
The purposes of ISO/TR 11487:2008 are:
to clarify and confirm TC 215 support for clinical stakeholder participation;
to make recommendations to the TC and to national member organizations on approaches to improving clinical stakeholder participation based on examples of existing effective participation models.
Base documents:
EVS-ISO/IEC 27032:2018
Information technology - Security techniques - Guidelines for cybersecurity (ISO/IEC 27032:2012, identical)
Scope:
This International Standard provides guidance for improving the state of Cybersecurity, drawing out the unique
aspects of that activity and its dependencies on other security domains, in particular:
— information security,
— network security,
— internet security, and
— critical information infrastructure protection (CIIP).
It covers the baseline security practices for stakeholders in the Cyberspace. This International Standard provides:
— an overview of Cybersecurity,
— an explanation of the relationship between Cybersecurity and other types of security,
— a definition of stakeholders and a description of their roles in Cybersecurity,
— guidance for addressing common Cybersecurity issues, and
— a framework to enable stakeholders to collaborate on resolving Cybersecurity issues.
aspects of that activity and its dependencies on other security domains, in particular:
— information security,
— network security,
— internet security, and
— critical information infrastructure protection (CIIP).
It covers the baseline security practices for stakeholders in the Cyberspace. This International Standard provides:
— an overview of Cybersecurity,
— an explanation of the relationship between Cybersecurity and other types of security,
— a definition of stakeholders and a description of their roles in Cybersecurity,
— guidance for addressing common Cybersecurity issues, and
— a framework to enable stakeholders to collaborate on resolving Cybersecurity issues.
Base documents:
ISO/IEC 27032:2012
Replaced:
EVS-ISO/IEC 27032:2024
ISO/IEC TR 24030:2021
Information technology — Artificial intelligence (AI) — Use cases
Scope:
This document provides a collection of representative use cases of AI applications in a variety of domains.
Base documents:
Replaced:
ISO/IEC TR 24030:2024
Drafts
prEN ISO 11073-10700
Health informatics - Device interoperability - Part 10700: Point‐of‐Care Medical Device Communication - Standard for Base Requirements for Participants in a Service‐Oriented Device Connectivity (SDC) System (ISO/IEEE FDIS 11073-10700:2024)
Scope:
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.
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.
Base documents:
ISO/IEEE FDIS 11073-10700; prEN ISO 11073-10700
prEN ISO/IEEE 11073-10701
Health informatics - Device interoperability - Part 10701: Point-of-Care Medical Device Communication - Metric Provisioning by Participants in a Service-Oriented Device Connectivity (SDC) System (ISO/IEEE FDIS 11073-10701:2024)
Scope:
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.
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.
Base documents:
ISO/IEEE FDIS 11073-10701; prEN ISO/IEEE 11073-10701
prEN ISO/IEEE 11073-10472
Health informatics - Device interoperability - Part 10472: Personal Health Device Communication - Device Specialization - Medication Monitor (ISO/IEEE FDIS 11073-10472:2024)
Scope:
Within the context of the ISO/IEEE 11073 family of standards for device communication, ISO/IEEE 11073-10472:2012 establishes a normative definition of communication between personal telehealth medication monitor devices and compute engines (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, 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. ISO/IEEE 11073-10472:2012 defines a common core of communication functionality for personal telehealth medication monitor devices.
Base documents:
ISO/IEEE FDIS 11073-10472; prEN ISO/IEEE 11073-10472
prEN ISO/IEEE 110736-10425
Health informatics - Device interoperability - Part 10425: Personal Health Device Communication - Device Specialization- Continuous Glucose Monitor (CGM) (ISO/IEEE FDIS 11073-10425:2024)
Scope:
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.
Base documents:
ISO/IEEE FDIS 11073-10425; prEN ISO/IEEE 110736-10425
prEN ISO/IEEE 11073-10471
Health informatics - Device interoperability - Part 10471: Personal Health Device Communication - Device Specialization - Independent Living Activity Hub (ISO/IEEE FDIS 11073-10471:2024)
Scope:
ISO/IEEE 11073-10471:2010 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 (PnP) 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 favour of interoperability.
ISO/IEEE 11073-10471:2010 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/behaviour 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).
ISO/IEEE 11073-10471:2010 addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers
ISO/IEEE 11073-10471:2010 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/behaviour 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).
ISO/IEEE 11073-10471:2010 addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers
Base documents:
ISO/IEEE FDIS 11073-10471; prEN ISO/IEEE 11073-10471
prEN ISO 9241-161
Ergonomics of human-system interaction - Part 161: Guidance on visual user-interface elements (ISO/DIS 9241-161:2024)
Scope:
ISO 9241-161:2016 describes visual user-interface elements presented by software and provides requirements and recommendations on when and how to use them. This part of ISO 9241 is concerned with software components of interactive systems to make human-system interaction usable as far as the basic interaction aspects are concerned.
ISO 9241-161:2016 provides a comprehensive list of generic visual user-interface elements, regardless of a specific input method, visualization, and platform or implementation technology. The guidance given in this part of ISO 9241 is intended to be used in conjunction with ISO 9241 guidance on dialogue techniques. It recognizes that additional elements can evolve. It also addresses derivates, compositions (assemblies) and states of user-interface elements. It gives requirements and recommendations on selection, usage and dependencies of user-interface elements and their application. It is applicable regardless of a fixed, portable or mobile interactive system.
It does not provide detailed coverage of the methods and techniques required for design of user-interface elements. This part of ISO 9241 does not address implementation (e.g. graphical design of elements) and interaction details for specific input methods or technologies. It does not cover decorative user-interface elements that are intended to address solely aesthetic (hedonic) qualities in the user interface, e.g. background images.
The information in this part of ISO 9241 is intended for use by those responsible for the selection and implementation of visual user-interface elements in interactive systems and for evaluating user interfaces. It is intended for use by those planning and managing platform specific aspects of user interface screen design. It also provides guidance for human factors/ergonomics and usability professionals involved in human-centred design. It addresses technical issues only to the extent necessary to allow users of this part of ISO 9241 to understand the relevance and importance of a consistent interface element usage and selection in the design process as a whole.
Annex A provides a guide to selection of different visual user interface elements depending of their appropriate application.
ISO 9241-161:2016 provides a comprehensive list of generic visual user-interface elements, regardless of a specific input method, visualization, and platform or implementation technology. The guidance given in this part of ISO 9241 is intended to be used in conjunction with ISO 9241 guidance on dialogue techniques. It recognizes that additional elements can evolve. It also addresses derivates, compositions (assemblies) and states of user-interface elements. It gives requirements and recommendations on selection, usage and dependencies of user-interface elements and their application. It is applicable regardless of a fixed, portable or mobile interactive system.
It does not provide detailed coverage of the methods and techniques required for design of user-interface elements. This part of ISO 9241 does not address implementation (e.g. graphical design of elements) and interaction details for specific input methods or technologies. It does not cover decorative user-interface elements that are intended to address solely aesthetic (hedonic) qualities in the user interface, e.g. background images.
The information in this part of ISO 9241 is intended for use by those responsible for the selection and implementation of visual user-interface elements in interactive systems and for evaluating user interfaces. It is intended for use by those planning and managing platform specific aspects of user interface screen design. It also provides guidance for human factors/ergonomics and usability professionals involved in human-centred design. It addresses technical issues only to the extent necessary to allow users of this part of ISO 9241 to understand the relevance and importance of a consistent interface element usage and selection in the design process as a whole.
Annex A provides a guide to selection of different visual user interface elements depending of their appropriate application.
Base documents:
ISO/DIS 9241-161; prEN ISO 9241-161
prEN ISO 19152-2
Geographic information - Land Administration Domain Model (LADM) - Part 2: Land registration (ISO/DIS 19152-2:2024)
Scope:
This part of ISO 19152 provides the concepts and detailed structure for standardization in the land administration domain. In order to achieve public policy objectives, some regulations use geographical spaces for mandating or enabling particular behaviours or outcomes. International law, constitutional law, public law and private law define different geographical spaces that juxtapose or overlap each other to produce a complex legal reality. Harmonizing and integrating the activities related to management of these legal spaces is the overarching idea of the land administration paradigm. Even if they differ in their objectives and normative sources, objects created by geo-regulation share basic components. This part of ISO 19152 defines a general schema that permits regulatory information to be described in information systems. Essentially, legal actors – individuals, organizations, States – (party) create among themselves sets of obligations (rights, restrictions, responsibilities) with the specificity of having a geographical component (spatial unit). The way the legal spaces related to reality is defined by the survey system (survey and representation). All these elements are recognized through legal instruments and official documents (source).
The first edition of this standard, ISO 19152:2012 concentrated on Land Administration, Land Registration and Cadastre. This information is about the relationship between people and land. This is now included in Part 2 with a more refined survey model. This part of the standard provides an abstract, conceptual model with three packages and one sub-package related to
• parties (people and organizations);
• basic administrative units, rights, responsibilities, and restrictions (ownership rights) -2];
• spatial units (parcels, and the legal space of buildings and utility networks and other geometry) with a sub-package on surveying and spatial representation (geometry and topology).
The first edition of this standard, ISO 19152:2012 concentrated on Land Administration, Land Registration and Cadastre. This information is about the relationship between people and land. This is now included in Part 2 with a more refined survey model. This part of the standard provides an abstract, conceptual model with three packages and one sub-package related to
• parties (people and organizations);
• basic administrative units, rights, responsibilities, and restrictions (ownership rights) -2];
• spatial units (parcels, and the legal space of buildings and utility networks and other geometry) with a sub-package on surveying and spatial representation (geometry and topology).
Base documents:
ISO/DIS 19152-2; prEN ISO 19152-2
prEN ISO/IEC 12792
Information technology - Artificial intelligence - Transparency taxonomy of AI systems (ISO/IEC DIS 12792:2024)
Scope:
This document defines a taxonomy of information elements to assist AI stakeholders with identifying and addressing the needs for transparency of AI systems. The document describes the semantics of the information elements and their relevance to the various objectives of different AI stakeholders.
This document uses a horizontal approach and is applicable to any kind of organization and application involving AI.
This document uses a horizontal approach and is applicable to any kind of organization and application involving AI.
Base documents:
ISO/IEC DIS 12792; prEN ISO/IEC 12792