ENV 13609-2:2000
(Main)Health informatics - Messages for maintenance of supporting information in healthcare systems - Part 2: Updating of medical laboratory-specific information
- BACK
- 23-May-2000
- 13-Apr-2025
- 35.240.80
- CEN/TC 251
Health informatics - Messages for maintenance of supporting information in healthcare systems - Part 2: Updating of medical laboratory-specific information
This First Working Document specifies messages for electronic information exchange between computer systems used by healthcare parties for the purposes of updating supplementary information that is attached to code values within a coding scheme. In particular, this message is intended to provide information to clinicians that are requesting tests within the specialties of: - haematology; - clinical chemistry; - cytology; - biochemistry; - immunology.
Zdravstvena informatika – Sporočila za vzdrževanje informacijske podpore pri sistemih zdravstvenega varstva – 2. del: Obnavljanje medicinskih laboratorijskih informacij
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-oktober-2003
=GUDYVWYHQDLQIRUPDWLND±6SRURþLOD]DY]GUåHYDQMHLQIRUPDFLMVNHSRGSRUHSUL
VLVWHPLK]GUDYVWYHQHJDYDUVWYD±GHO 2EQDYOMDQMHPHGLFLQVNLKODERUDWRULMVNLK
LQIRUPDFLM
Health informatics - Messages for maintenance of supporting information in healthcare
systems - Part 2: Updating of medical laboratory-specific information
Ta slovenski standard je istoveten z: ENV 13609-2:2000
ICS:
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
SIST ENV
...
This May Also Interest You
This document applies to situations in which such data is recorded on or transported by patient healthcards compliant with the physical dimensions of ID-1 cards defined by ISO/IEC 7810.
This document specifies the basic structure of the data contained within the medication data object, but does not specify or mandate particular data sets for storage on devices.
The purpose of this document is for cards to provide information to other health professionals and to the patient or its non-professional caregiver.
It can also be used to carry a new prescription from the prescriber to the dispenser/pharmacy in the design of its sets.
Medication data include the following four components:
— medication notes: additional information related to medication and the safe use of medicines by the patient such as medication history, sensitivities and allergies;
— medication prescriptions: to carry a new prescription from the prescriber to the dispenser/pharmacy;
— medication dispensed: the records of medications dispensed for the patient;
— medication references: pointers to other systems that contain information that makes up medication prescription and the authority to dispense.
The following topics are beyond the scope of this document:
— physical or logical solutions for the practical functioning of particular types of data cards;
— how the message is processed further “downstream” of the interface between two systems;
— the form which the data takes for use outside the data card, or the way in which such data is visibly represented on the data card or elsewhere.
NOTE Not only does the definition of “medicinal products” differ from country to country, but also the same name can relate to entirely different products in some countries. Therefore, it is important to consider the safety of the patient when the card is used across borders.
This document describes and defines the Medication data objects used within or referenced by patient-held health data cards using UML, plain text and Abstract Syntax Notation (ASN.1).
This document does not describe nor define the common objects defined within ISO 21549-2.
- Standard51 pagesEnglish languagesale 10% offe-Library read for×1 day
- 20-Feb-2024
- 35.240.80
- CEN/TC 251
This document establishes the Reference Standards Portfolio (RSP) for the clinical imaging domain (as defined in Clause 4).
An RSP lists the principle health information technology (HIT) standards that form the basis of implementing and deploying interoperable applications in the target domain.
An RSP includes a description of the domain, a normative list of standards, and an informative framework for mapping the standards to example deployment use cases.
The lists do not include standards that are specifically national in scope.
The primary target audience for this document is policy makers (governmental or organizational), regulators, project planners and HIT managers. This document will also be of interest to other stakeholders such as equipment and HIT vendors, clinical and health information management (HIM) professionals and standards developers.
The intended usage of this document is to inform decisions about selecting the standards that will form the basis of integration projects in geographic regions or healthcare organizations. For example:
— What standards to use for capturing/encoding/exchanging certain types of information
— What standards to use for interfaces between the devices and information systems that support information capture, management, exchange, processing and use
— What standards to use for specific use cases/deployment scenarios
The selected standards, and/or corresponding RSP clauses, might be useful when drafting project specifications.
- Standard59 pagesEnglish languagesale 10% offe-Library read for×1 day
- 20-Feb-2024
- 35.240.80
- CEN/TC 251
The objective of this document is to establish common principles for the creation, assessment, selection and maintenance of maps between terminological resources used to describe and code IDMP therapeutic indications for investigational and medicinal products, medical devices, combination products, biologics and companion diagnostics. Core maintenance principles, such as reliability, reproducibility and quality assurance of the maps for future indication terminology use, are also discussed. The intended audience for this document includes:
a) Global regulators, pharmaceutical/biopharmaceutical companies, Clinical Research Organizations (CROs) and universities/scientific institutes involved in the development, authorization and marketing of medicinal products
b) Implementers of IDMP seeking more information about coding of Therapeutic Indications
c) Healthcare providers
d) Standards Organizations
e) Implementers and software vendors developing and implementing terminology map sets
f) Patients
- Technical specification32 pagesEnglish languagesale 10% offe-Library read for×1 day
- 06-Feb-2024
- 35.240.80
- CEN/TC 251
This document defines a set of high-level categories of purposes for which personal health information can be processed: collected, used, stored, accessed, analysed, created, linked, communicated, disclosed or retained. This is in order to provide a framework for classifying the various specific purposes that can be defined and used by individual policy domains (e.g. healthcare organisation, regional health authority, jurisdiction, country) as an aid to the consistent management of information in the delivery of health care services and for the communication of electronic health records across organisational and jurisdictional boundaries.
Health data that have been irreversibly de-identified are outside the scope of this document, but since de-identification processes often includes some degree of reversibility, this document can also be used for disclosures of de-identified and/or pseudonymised health data whenever practicable.
This classification, whilst not defining an exhaustive set of purposes categories, provides a common mapping target to bridge between differing national lists of purpose and thereby supports authorised automated cross-border flows of EHR data.
- Technical specification20 pagesEnglish languagesale 10% offe-Library read for×1 day
- 16-Jan-2024
- 35.240.80
- CEN/TC 251
This document specifies the characteristics of categorial structures, representing nursing practice. The overall aim of this document is to support interoperability in the exchange of meaningful information between information systems in respect of nursing diagnoses, nursing actions and nurse sensitive outcomes. Categorial structures for nursing diagnoses, nursing actions, nurse sensitive outcomes and associated categories support interoperability by providing common frameworks with which to
a) analyse the features of different terminologies, including pre- and post-coordinated expressions, those of other healthcare disciplines, and to establish the nature of the relationship between them,[3][4][5][6][7][8]
b) develop terminologies for representing nursing diagnoses, nursing actions,[9][10][11][12] and nurse sensitive outcomes,
c) develop terminologies that are able to be related to each other,[3][8][13] and
d) establish relationships between terminology models, information models, including archetypes, and ontologies in the nursing domain.[14][15][16][45]
There is early evidence that the categorial structures can be used as a framework for analysing nursing practice,[17] for developing nursing content of electronic record systems,[18][19] document the value of nursing services provided and to make nursing’s contribution visible[16][36][47][50].
- Standard45 pagesEnglish languagesale 10% offe-Library read for×1 day
- 12-Dec-2023
- 35.240.80
- CEN/TC 251
This document describes and defines the basic structure of the identification data objects held on healthcare data cards, but it does not specify particular data sets for storage on devices.
This document does not apply to the detailed functions and mechanisms of the following services (although its structures can accommodate suitable data objects elsewhere specified):
— security functions and related services that are likely to be specified by users for data cards depending on their specific application, e.g. confidentiality protection, data integrity protection and authentication of persons and devices related to these functions;
— access control services;
— the initialization and issuing process (which begins the operating lifetime of an individual data card, and by which the data card is prepared for the data to be subsequently communicated to it according to this document).
Therefore, this document does not cover:
— physical or logical solutions for the practical functioning of particular types of data card;
— the forms that data take for use outside the data card, or the way in which such data are visibly represented on the data card or elsewhere.
- Standard17 pagesEnglish languagesale 10% offe-Library read for×1 day
- 07-Nov-2023
- 35.240.80
- CEN/TC 251
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.
- Standard135 pagesEnglish languagesale 10% offe-Library read for×1 day
- 29-Aug-2023
- 35.240.80
- CEN/TC 251
ISO 17117-1:2018 defines universal and specialized characteristics of health terminological resources that make them fit for the purposes required of various applications. It refers only to terminological resources that are primarily designed to be used for clinical concept representation or to those parts of other terminological resources designed to be used for clinical concept representation.
ISO 17117-1:2018 helps users to assess whether a terminology has the characteristics or provides the functions that will support their specified requirements. The focus of this document is to define characteristics and functions of terminological resources in healthcare that can be used to identify different types of them for categorization purposes. Clauses 4 and 5 support categorization according to the characteristics and functions of the terminological resources rather than the name.
NOTE Categorization of healthcare terminological systems according to the name of the system might not be helpful and has caused confusion in the past.
The target groups for this document are:
a) organizations wishing to select terminological systems for use in healthcare information systems;
b) developers of terminological systems;
c) developers of terminology standards;
d) those undertaking independent evaluations/academic reviews of terminological resources;
e) terminology Registration Authorities.
ISO 17117-1:2018 contains general characteristics and criteria with which systems can be evaluated.
The following considerations are outside the scope of this document.
- Evaluations of terminological resources.
- Health service requirements for terminological resources and evaluation criteria based on the characteristics and functions.
- The nature and quality of mappings between different terminologies. It is unlikely that a single terminology will meet all the terminology requirements of a healthcare organization: some terminology providers produce mappings to administrative or statistical classifications such as the International Classification of Diseases (ICD). The presence of such maps would be a consideration in the evaluation of the terminology.
- The nature and quality of mappings between different versions of the same terminology. To support data migration and historical retrieval, terminology providers can provide maps between versions of their terminology. The presence of such maps would be a consideration in the evaluation of the terminology.
- Terminology server requirements and techniques and tools for terminology developers.
- Characteristics for computational biology terminology. Progress in medical science and in terminology science will necessitate updating of this document in due course.
- Standard38 pagesEnglish languagesale 10% offe-Library read for×1 day
- 18-Jul-2023
- 21-Aug-2022
- 01.020
- 35.240.80
- CEN/TC 251
This document specifies:
— the data elements, structures and relationships between the data elements required for the exchange of information, which uniquely and with certainty identify pharmaceutical dose forms, units of presentation, routes of administration and packaging items (containers, closures and administration devices) related to medicinal products;
— a mechanism for the association of translations of a single concept into different languages, which is an integral part of the information exchange;
— a mechanism for the versioning of the concepts in order to track their evolution;
— rules to help regional authorities to map existing regional terms to the terms created using this document, in a harmonized and meaningful way.
- Standard37 pagesEnglish languagesale 10% offe-Library read for×1 day
- 13-Jun-2023
- 35.240.80
- CEN/TC 251
This document describes data elements and structures for the unique identification and exchange of regulated information on pharmaceutical dose forms, units of presentation, routes of administration and packaging.
Based on the principles outlined in this document, harmonised controlled terminologies will be developed according to an agreed maintenance process, allowing users to consult the terminologies and locate the appropriate terms for the concepts that they wish to describe. Provisions to allow for the mapping of existing regional terminologies to the harmonised controlled terminologies will also be developed in order to facilitate the identification of the appropriate terms. The codes provided for the terms can then be used in the relevant fields in the PhPID, PCID and MPID in order to identify those concepts.
This document is intended for use by:
— any organization that might be responsible for developing and maintaining such controlled vocabularies;
— any regional authorities or software vendors who want to use the controlled vocabularies in their own systems and need to understand how they are created;
— owners of databases who want to map their own terms to a standardized list of controlled vocabularies;
— other users who want to understand the hierarchy of the controlled vocabularies in order to help identify the most appropriate term to describe a particular concept.
This document does not specify a particular terminology for the implementation of ISO 11239.
- Technical specification53 pagesEnglish languagesale 10% offe-Library read for×1 day
- 11-Apr-2023
- 35.240.80
- CEN/TC 251
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.