E31.35 - Healthcare Data Analysis

SCOPE
1.1 This document describes the implementation principles needed to create a Voluntary Universal Healthcare Identification (VUHID) system. The purpose of this system is to enable unambiguous identification of individuals in order to facilitate the delivery of healthcare.
1.2 The VUHID system should be dedicated exclusively to the needs and functions of healthcare.
1.3 The VUHID system is designed to represent no, or at least minimal, increased risk to healthcare privacy and security.
1.4 The system should be as cost-effective as possible.
1.5 The system must be created and maintained in a way to provide sustained benefit to healthcare.
1.6 The system should be designed and implemented in a manner that ensures that it can operate indefinitely.
This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

SCOPE
1.1 This terminology is intended to name and document the principal concepts, and their associated terms, that are utilized in the healthcare information domain and all of its specialized subdomains. It is applicable to all areas of healthcare about which information is kept or utilized. It is intended to complement and utilize those concepts already identified by other national and international standards bodies. It will identify alternate accepted terms for the same concept and its elected term. Its terms are intended to clarify and simplify usage in the dialog and documentation about the concepts, processes and data that are used to schedule, conduct and manage all phases of healthcare. This common usage will improve the quality and management of all facets of healthcare by means of explicit information used in referring to each of these facets. These health informatics terms have been collected here specifically in order to facilitate the consistent use of common concepts in informatics standards development and use throughout healthcare. A separate process from this standard that is described in ISO 15188 will manage the approval of biomedical and healthcare terms.
This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

ABSTRACT
This guide is intended to document principal ideas which are necessary and sufficient to assign value to health classification. This guide shall serve governments, funding agencies, terminology developers, terminology integration organizations, and the purchasers and users of this classification system toward improved terminological development and recognition of value in classification. This international standard will also provide classification developers and authors with the quality guidelines needed to construct useful, maintainable classifications. It is applicable to all areas of health about which information is kept or utilized, and is intended to complement and utilize those notions already identified by other national and international standards bodies. These tenets do not attempt to specify all of the richness which can be incorporated into a classification. However, this standard does specify the minimal requirements, which if not adhered to will assure that the classification will have limited generalizability and will be very difficult if not impossible to maintain.
SCOPE
1.1 This international standard is intended to document principal ideas which are necessary and sufficient to assign value to a classification. The standard will serve as a guide for governments, funding agencies, terminology developers, terminology integration organizations, and the purchasers and users of classification systems toward improved terminological development and recognition of value in a classification. It is applicable to all areas of health about which information is kept or utilized. Appropriately, classifications should be evaluated within the context of their stated scope and purpose. It is intended to complement and utilize those notions already identified by other national and international standards bodies. This standard explicitly refers only to classifications. This international standard will also provide classification developers and authors with the quality guidelines needed to construct useful, maintainable classifications. These tenets do not attempt to specify all of the richness which can be incorporated into a classification. However, this standard does specify the minimal requirements, which if not adhered to will assure that the classification will have limited generalizability and will be very difficult if not impossible to maintain. We have used the word "Shall" to indicate mandatory requirements and the word "Should" to indicate those requirements which we feel are desirable but may not be widely achievable in current implementations. Classifications, which do not currently meet these criteria, can be in compliance with this standard by putting in place mechanisms to move toward these goals. This standard will provide classification developers with a sturdy starting point for the development of useful classifications. This foundation serves as the basis from which classification developers will build robust concept systems.

ABSTRACT
This specification updates a standard representation for storing and organizing the heterogeneous information contained in clinical practice guidelines, intended to facilitate translation of natural-language guideline documents into a format that can be processed by computers. This specification is based on the guideline elements model version 2 (GEM II) created at the Yale Center for Medical Informatics by health services researchers and informatics specialists, and designed to serve as a comprehensive XML-based guideline document representation.
SCOPE
1.1 This specification updates a standard representation for storing and organizing the heterogeneous information contained in clinical practice guidelines. This specification is intended to facilitate translation of natural-language guideline documents into a format that can be processed by computers. It can be used to represent document content throughout the entire guideline life cycle. Information at both high and low levels of abstraction can be accommodated. This specification is based on the guideline elements model (GEM) created at the Yale Center for Medical Informatics and designed to serve as a comprehensive XML-based guideline document representation.
1.2 This specification refers to and makes use of recommendations from the World Wide Web consortium, the W3C.
1.3 Standard Guideline Schema This specification defines a standard Schema for clinical practice guidelines. The Schema is included in Annex A1.
This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory requirements prior to use.

SCOPE
1.1 This terminology is intended to name and document the principal concepts, and their associated terms, that are utilized in the healthcare information domain and all of its specialized subdomains. It is applicable to all areas of healthcare about which information is kept or utilized. It is intended to complement and utilize those concepts already identified by other national and international standards bodies. It will identify alternate accepted terms for the same concept and its elected term. Its terms are intended to clarify and simplify usage in the dialog and documentation about the concepts, processes and data that are used to schedule, conduct and manage all phases of healthcare. This common usage will improve the quality and management of all facets of healthcare by means of explicit information used in referring to each of these facets. These health informatics terms have been collected here specifically in order to facilitate the consistent use of common concepts in informatics standards development and use throughout healthcare. A separate process from this standard that is described in ISO 15188 will manage the approval of biomedical and healthcare terms.
1.2 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

SCOPE
1.1 This specification covers a document type definition (DTD) that specifies a standard representation for storing and organizing the heterogeneous information contained in clinical practice guidelines. This specification is intended to facilitate translation of natural-language guideline documents into a format that can be processed by computers. It can be used to represent document content throughout the entire guideline life cycle. Information at both high and low levels of abstraction can be accommodated. This specification is based on the guideline elements model (GEM) created at the Yale Center for Medical Informatics and designed to serve as a comprehensive XML-based guideline document representation.
1.2 This specification refers to and makes use of recommendations from the World Wide Web consortium, the W3C.
1.3 Standard Guideline —DTDThis specification defines a standard DTD for clinical practice guidelines. The DTD is included in Annex A1.
1.4 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory requirements prior to use.

ABSTRACT
This guide is intended to document principal ideas which are necessary and sufficient to assign value to health classification. This guide shall serve governments, funding agencies, terminology developers, terminology integration organizations, and the purchasers and users of this classification system toward improved terminological development and recognition of value in classification. This international standard will also provide classification developers and authors with the quality guidelines needed to construct useful, maintainable classifications. It is applicable to all areas of health about which information is kept or utilized, and is intended to complement and utilize those notions already identified by other national and international standards bodies. These tenets do not attempt to specify all of the richness which can be incorporated into a classification. However, this standard does specify the minimal requirements, which if not adhered to will assure that the classification will have limited generalizability and will be very difficult if not impossible to maintain.
SCOPE
1.1 This international standard is intended to document principal ideas which are necessary and sufficient to assign value to a classification. The standard will serve as a guide for governments, funding agencies, terminology developers, terminology integration organizations, and the purchasers and users of classification systems toward improved terminological development and recognition of value in a classification. It is applicable to all areas of health about which information is kept or utilized. Appropriately, classifications should be evaluated within the context of their stated scope and purpose. It is intended to complement and utilize those notions already identified by other national and international standards bodies. This standard explicitly refers only to classifications. This international standard will also provide classification developers and authors with the quality guidelines needed to construct useful, maintainable classifications. These tenets do not attempt to specify all of the richness which can be incorporated into a classification. However, this standard does specify the minimal requirements, which if not adhered to will assure that the classification will have limited generalizability and will be very difficult if not impossible to maintain. We have used the word “Shall” to indicate mandatory requirements and the word “Should” to indicate those requirements which we feel are desirable but may not be widely achievable in current implementations. Classifications, which do not currently meet these criteria, can be in compliance with this standard by putting in place mechanisms to move toward these goals. This standard will provide classification developers with a sturdy starting point for the development of useful classifications. This foundation serves as the basis from which classification developers will build robust concept systems.
WITHDRAWN RATIONALE
This international standard is intended to document principal ideas which are necessary and sufficient to assign value to a classification.
Formerly under the jurisdiction of Committee E31 on Healthcare Informatics, this guide was withdrawn in January 2022 in accordance with section 10.6.3 of the Regulations Governing ASTM Technical Committees, which requires that standards shall be updated by the end of the eighth year since the last approval date.

SIGNIFICANCE AND USE
5.1 This standard describes a proposal to provide unambiguous personal identification for any patient who requests it. In today’s world of specialized healthcare and mobile patients it is typical for clinical information on a single patient to reside in a variety of locations, some using manual data storage techniques, but an increasing number using electronic means. In order for a clinician to provide safe and appropriate clinical care in this environment it is necessary to be able to aggregate appropriate clinical information on a specific patient in order to gain an accurate and comprehensive picture of that patient’s clinical situation. This implies that all information relating to each patient should be identified in a unique manner to facilitate the process of accurately aggregating appropriate information.  
5.2 The converse of the need for data aggregation is the patient’s need to protect the privacy of their information. Unless patients are confident that they can avoid inappropriate sharing of clinical information they will not readily share that information with caregivers. Thus, the same system that supports unambiguous linkage of all information concerning a patient must also play a role in protecting the privacy of that information.  
5.3 The proposed patient identification system must be able to avoid or overcome the numerous objections that have prevented implementation of a universal patient identification system in the past including issues related to:  
5.3.1 Technology—The proposed system must be technically feasible in a manner that promotes scalability, availability, and ease of implementation.  
5.3.2 Integration with Existing Systems—To the maximum extent possible the proposed identification system should work seamlessly with existing information systems.  
5.3.3 Cost-effectiveness—The proposed system should balance the costs and benefits required to implement a fully functional voluntary universal healthcare identification system.  
5....
SCOPE
1.1 This document describes the implementation principles needed to create a Voluntary Universal Healthcare Identification (VUHID) system. The purpose of this system is to enable unambiguous identification of individuals in order to facilitate the delivery of healthcare.  
1.2 The VUHID system should be dedicated exclusively to the needs and functions of healthcare.  
1.3 The VUHID system is designed to represent no, or at least minimal, increased risk to healthcare privacy and security.  
1.4 The system should be as cost-effective as possible.  
1.5 The system must be created and maintained in a way to provide sustained benefit to healthcare.  
1.6 The system should be designed and implemented in a manner that ensures that it can operate indefinitely.  
1.7 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.
WITHDRAWN RATIONALE
This document describes the implementation principles needed to create a Voluntary Universal Healthcare Identification (VUHID) system.
Formerly under the jurisdiction of Committee E31 on Healthcare Informatics, this guide was withdrawn in January 2022 in accordance with section 10.6.3 of the Regulations Governing ASTM Technical Committees, which requires that standards shall be updated by the end of the eighth year since the last approval date.

SIGNIFICANCE AND USE
3.1 This standard vocabulary is intended to be used as a reference about terms used in standards for healthcare informatics and in general discussions about informatics issues relating to the healthcare sector, including: clinical care, resource management, policy, clinical or health services research or biomedical research in basic or applied areas of science that refer to the healthcare sector. It contains “Elected Terms” rather than the “Preferred” terms used in the terminologic literature. This is a usage coined within the CEN TC-251 community to reflect the fact that there is consensus agreement on the usage of a particular form rather than an imposition. This consensual agreement to usage better reflects the incentives for common usage rather than mandates. Alternate forms (Synonymy) of an elected term exist and are cataloged for the same concept, in accordance with ISO/DIS 1087-1, ISO 704, ISO 12620, and EN-12017, ISO/DIS 860, EN-12264, and ANSDIT.  
3.2 The system used to classify these terms is in the full context of all of the terminology of biomedicine, as well as about the healthcare system itself as it is used throughout the health domain. It has drawn on the terms used in both EN-12017 and in UMLS for biomedicine (Guide E1284, Specification E1633, ISO 12200, GALEN). The coding scheme described in Section 5 used to represent this classification was developed for this terminology from the Unified Medical Language System documentation produced by the National Library of Medicine.
SCOPE
1.1 This terminology is intended to name and document the principal concepts, and their associated terms, that are utilized in the healthcare information domain and all of its specialized subdomains. It is applicable to all areas of healthcare about which information is kept or utilized. It is intended to complement and utilize those concepts already identified by other national and international standards bodies. It will identify alternate accepted terms for the same concept and its elected term. Its terms are intended to clarify and simplify usage in the dialog and documentation about the concepts, processes and data that are used to schedule, conduct and manage all phases of healthcare. This common usage will improve the quality and management of all facets of healthcare by means of explicit information used in referring to each of these facets. These health informatics terms have been collected here specifically in order to facilitate the consistent use of common concepts in informatics standards development and use throughout healthcare. A separate process from this standard that is described in ISO 15188 will manage the approval of biomedical and healthcare terms.  
1.2 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.
WITHDRAWN RATIONALE
This terminology is intended to name and document the principal concepts, and their associated terms, that are utilized in the healthcare information domain and all of its specialized subdomains.
Formerly under the jurisdiction of Committee E31 on Healthcare Informatics, this terminology was withdrawn in January 2022 in accordance with section 10.6.3 of the Regulations Governing ASTM Technical Committees, which requires that standards shall be updated by the end of the eighth year since the last approval date.

ABSTRACT
This specification updates a standard representation for storing and organizing the heterogeneous information contained in clinical practice guidelines, intended to facilitate translation of natural-language guideline documents into a format that can be processed by computers. This specification is based on the guideline elements model version 2 (GEM II) created at the Yale Center for Medical Informatics by health services researchers and informatics specialists, and designed to serve as a comprehensive XML-based guideline document representation.
SCOPE
1.1 This specification updates a standard representation for storing and organizing the heterogeneous information contained in clinical practice guidelines. This specification is intended to facilitate translation of natural-language guideline documents into a format that can be processed by computers. It can be used to represent document content throughout the entire guideline life cycle. Information at both high and low levels of abstraction can be accommodated. This specification is based on the guideline elements model (GEM) created at the Yale Center for Medical Informatics and designed to serve as a comprehensive XML-based guideline document representation.
1.2 This specification refers to and makes use of recommendations from the World Wide Web consortium, the W3C.  
1.3 Standard Guideline Schema—This specification defines a standard Schema for clinical practice guidelines. The Schema is included in Annex A1.
1.4 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory requirements prior to use.
WITHDRAWN RATIONALE
This specification updates a standard representation for storing and organizing the heterogeneous information contained in clinical practice guidelines.
Formerly under the jurisdiction of Committee E31 on Healthcare Informatics, this specification was withdrawn in January 2021 in accordance with section 10.6.3 of the Regulations Governing ASTM Technical Committees, which requires that standards shall be updated by the end of the eighth year since the last approval date.

SCOPE
1.1 This specification covers the documentation of the principal notions necessary and sufficient to assign value to a controlled health vocabulary. This specification will serve as a guide for governments, funding agencies, terminology developers, terminology integration organizations, and the purchasers and users of controlled health terminology systems working toward improved terminological development and recognition of value in a controlled health vocabulary. It is applicable to all areas of health care about which information is kept or utilized. It is intended to complement and utilize those notions already identified by other national and international standards bodies.
1.2 This specification will provide vocabulary developers and authors with the guidelines needed to construct useful, maintainable controlled health vocabularies. These tenets do not attempt to specify all of the richness that can be incorporated into a health terminology. However this specification does specify the minimal requirements, which, if not adhered to, will ensure that the vocabulary will have limited generalizability and will be very difficult, if not impossible, to maintain. This specification will provide terminology developers with a sturdy starting point for the development of controlled health vocabularies. This foundation serves as the basis from which vocabulary developers will build robust, large-scale, reliable and maintainable terminologies.
1.3 This specification explicitly does not refer to classifications or coding systems (for example, a simple list of pairs of rubrics and codes) that are not designed to be used clinically.
WITHDRAWN RATIONALE
This specification covers the documentation of the principal notions necessary and sufficient to assign value to a controlled health vocabulary. This specification will serve as a guide for governments, funding agencies, terminology developers, terminology integration organizations, and the purchasers and users of controlled health terminology systems working toward improved terminological development and recognition of value in a controlled health vocabulary. It is applicable to all areas of health care about which information is kept or utilized. It is intended to complement and utilize those notions already identified by other national and international standards bodies.
Formerly under the jurisdiction of Committee E31 on Healthcare Informatics, this specification was withdrawn in February 2009 in accordance with section 10.5.3.1 of the Regulations Governing ASTM Technical Committees, which requires that standards shall be updated by the end of the eighth year since the last approval date.