Working group

This document specifies the requirements for developing a knowledge base for drug-related problems that cohere with the intended drug use, to be used in rule-based clinical decision support systems (CDSS), such as the criteria for selecting a raw data source and the quality criteria for the development and maintenance for the rules or clinical rules for drug safety. It also describes the process of how to develop a knowledge base, the topics to be considered by the developers of a knowledge base, and it gives guidance on how to do this. This document gives guidelines for the development of a knowledge base: — with rules to enhance decisions and actions in drug-related problems that cohere with the intended drug use; — which can be used by all kinds of healthcare professionals, such as those who prescribe, dispense, administer or monitor medicines; — which can be used in every care setting, including chronic and acute care, primary and specialized care; — which is a repository of evidence/practice bases rules, assessed by experts; — which is meant to be used in conjunction with a medicinal product dictionary; — whose knowledge is structured in rules and therefore to be used in the type of rule-based CDSS. This document does not: — describe the exact content of a knowledge base i.e. the outcome of the process of developing rules. — provide the requirements for a clinical decision support system, the software that uses the knowledge base combined with the patient's data, and presents the outcome of the rules to the healthcare professional. These requirements are described in ISO/DTS 22703[1]. — give the requirements for non-medication knowledge bases. Some aspects of the requirements in this document are general in nature and applicable to other kinds of knowledge bases, but this document does not address all of the requirements of non-medication knowledge bases. [1] Under preparation. Stage at the time of publication: ISO/DTS 22703.

This document provides guidelines on identification and labelling of medicinal products from the point of manufacture of packaged medicinal product to the point of dispensing the product. This document outlines best practice for AIDC barcoding solutions for applications. Users can, however, consider the coding interoperability requirements for other AIDC technologies, e.g. Radio Frequency Identification (RFID)

Experiential Networked Intelligence (ENI)- Terminology for Main Concepts in ENI

The ITU-T Focus Group on Machine Learning for Future Networks including 5G was established by ITU-T Study Group 13 at its meeting in Geneva, 6-17 November 2017. The Focus Group will draft technical reports and specifications for machine learning (ML) for future networks, including interfaces, network architectures, protocols, algorithms and data formats.

GR ENI 003 Experiential Networked Intelligence (ENI); Context-Aware Policy Management Gap Analysis

Experiential Networked Intelligence (ENI); Proof of Concepts Framework

ISG NFV has developed over 80 different reports and specifications for the virtualisation of network functions. NFV publications describe and specify virtualisation requirements, architecture framework, functional components and their interfaces, as well as the protocols and the APIs for these interfaces. ISG NFV also studies VNF performance, reliability, and resiliency matters, analyses the security challenges linked to virtualisation (trust, attestation, regulation). NFV specifies requirements for Management and Orchestration, for hardware acceleration, etc. And a lot is ongoing!

The present document specifies the structure of the Network Service Descriptor (NSD) file archive and the naming conventions for the different files it contains, fulfilling the requirements specified in ETSI GS NFV-IFA 014 [1] for an NSD file structure.

The Cloud Security Alliance Cloud Controls Matrix (CCM) is specifically designed to provide fundamental security principles to guide cloud vendors and to assist prospective cloud customers in assessing the overall security risk of a cloud provider. The CSA CCM provides a controls framework that gives detailed understanding of security concepts and principles that are aligned to the Cloud Security Alliance guidance in 13 domains. The foundations of the Cloud Security Alliance Controls Matrix rest on its customized relationship to other industry-accepted security standards, regulations, and controls frameworks such as the ISO 27001/27002, ISACA COBIT, PCI, NIST, Jericho Forum and NERC CIP and will augment or provide internal control direction for service organization control reports attestations provided by cloud providers.

This working group aims at creating PLA templates that can be a powerful self-regulatory harmonization tool, which is almost impossible to achieve at global level using traditional legislative means. This will provide a clear and effective way to communicate to (potential) customers a CSP’s level of personal data protection, especially when trans-border data flaw is concerned.

The CSA Open Certification WG is an industry initiative to allow global, accredited, trusted certification of cloud providers. It is a program for flexible, incremental and multi-layered cloud provider certification according to the CSA’s industry leading security guidance and control objectives. The program will integrate with popular third-party assessment and attestation statements developed within the public accounting community to avoid duplication of effort and cost.