ISO 13972:2022 健康情報学—臨床情報モデル—特性、構造、および要件 | ページ 6

3.1.1

concept

unit of thought

3.1.2

concept analysis

formal linguistic strategy that enables the defining attributes or characteristics of a concept to be examined

[SOURCE:Reference [19]]

3.1.3

concept definition

description of the attributes of a concept to delineate its meaning

3.1.4

clinical concept

concept expressed by means of characteristics or attributes pertinent to its use in health or health care

3.1.5

model

abstract description of reality in any form (including concepts, data elements, terms, and their relationships, statistical, theoretical, mathematical, physical, symbolic, graphical or descriptive form of a domain) that presents a certain aspect of that reality

Note 1 to entry: It is often further specified to distinguish between conceptual, logical and computational models.

[SOURCE:ISO/TR 23087:2018, 3.5, modified —"concepts, data elements, terms and their relationships, added statistical, theoretical" and Note 1 to entry have added.]

3.1.6

modelling

construction of abstract representations in the course of design, for example to represent the logical structure of software applications before coding

[SOURCE:Reference [21]]

3.1.7

conceptual model

model that describes common concepts and their relationships, particularly in order to facilitate exchange of information between parties within a specific domain of healthcare

Note 1 to entry: This pertains in particular to concepts representing clinical information in conceptual models.

[SOURCE:ISO/TS 18864:2017, 3.6, modified —"description" changed to"model that describes", Note 1 to entry added.]

3.1.8

logical information model

logical model

information model that specifies the structures and relationships between data elements but is independent of any particular technology or implementation environment

[SOURCE:ISO/TR 20514:2005, 2.29, modified —"information" replaced with"data elements", note removed.]

3.1.9

physical level

level of consideration at which all aspects deal with the physical representation of data structures and with mapping them on corresponding storage organizations and their access operations in a data processing system

Note 1 to entry: This document focuses on the flow from business concepts in any domain via clinical (logical) information models to their technical implementation in a specific application or system.

[SOURCE:ISO/IEC 20944-1:2013, 3.14.3.6, modified — Note 1 to entry added.]

3.1.10

information

knowledge concerning objects, such as facts, events, things, processes, or ideas, including concepts, that within a certain context has a particular meaning

Note 1 to entry: Information is something that is meaningful. Data might be regarded as information once its meaning is revealed.

[SOURCE:ISO/IEC 2382:2015, 2121271, modified — Notes to entry removed, new Note 1 to entry added.]

3.1.11

healthcare information

clinical information

information about a person, relevant to his or her health or health care

Note 1 to entry: This does include activities in which a patient and care professional interact directly or indirectly.

Note 2 to entry: Healthcare information about a patient can include information about the patient's environment and/or about related people where this is relevant.

[SOURCE:ISO 13940:2015, 3.9.4, modified —"clinical information" added as a term,"health" added, Notes to entry added.]

3.1.12

context

related conditions and situations that provide a useful understanding and meaning of a subject

[SOURCE:ISO/TR 17119:2005, 2.4]

3.1.13

clinical information model

CIM

health and care information model

HCIM

information model that expresses in a standardized and reusable manner one or more healthcare or clinical concepts and their context in a conceptual and logical model, specifying healthcare information as a discrete set of data elements, their characteristics and relationships, and appropriate terminology bindings

3.1.14

medical knowledge

field of knowledge pertaining to the structure, function, or dysfunction of the human body and how these can be influenced by external or internal factors and interventions

Note 1 to entry: Medical does not imply “physician”, all health professionals have medical knowledge according to this definition.

Note 2 to entry: This would pertain to observations, findings, diagnoses, outcomes, therapy, etc., to alleviate disease/dysfunction.

[SOURCE:ISO 13119:2012, 2.1, modified — Note 1 to entry modified, Note 2 to entry added.]

3.1.15

semantic interoperability

ability for data shared by systems to be understood at the level of fully defined domain concepts

Note 1 to entry: EC Recommendation, COM (2008) 3282 final, stresses that this implies to work for any other system or application the defined domain concepts were not initially developed for.

[SOURCE:ISO 18308:2011, 3.45, modified — Note 1 to entry added.]

3.1.16

data

reinterpretable representation of information in a formalized manner suitable for communication, interpretation or processing

[SOURCE:ISO/IEC 2382:2015, 2121272, modified — Notes to entry removed.]

3.1.17

data element

variable, clinical elements are considered synonyms in a clinical information model unit of data that is considered, in context, to be indivisible

[SOURCE:ISO/IEC 14957:2010, 3.1, modified —"variable, clinical elements are considered synonyms in a clinical information model" added.]

3.1.18

attribute

characteristic of an object or set of objects

Note 1 to entry: In the context of this document it can be a specific characteristic of a data element.

[SOURCE:ISO/IEC 11179‑1:2015, 3.1.1, modified — Note 1 to entry added.]

3.1.19

data model

description of the organization of data in a manner that reflects an information structure

[SOURCE:ISO 5127:2017, 3.1.13.33]

3.1.20

datatype

set of distinct values, characterized by properties of those values and by operations on those values

[SOURCE:ISO/IEC 11404:2007, 3.12]

3.1.21

metadata

data that defines and describes other data

Note 1 to entry: In the context of this document, the metadata that describe clinical information models are meant to govern the clinical information model (CIM) as objects, for instance to retrieve specific CIMs and to maintain CIM versions.

Note 2 to entry: It is possible to relate to persistent instance data using metadata that are based on the clinical information models in any storage or exchange format, for example to identify on which CIM specific data are based.

[SOURCE:ISO/IEC 11179‑1:2015, 3.2.16, modified — Notes to entry added.]

3.1.22

term

designation that represents a general concept by linguistic means

[SOURCE:ISO 1087:2019, 3.4.2, modified — EXAMPLE, modified, Note to entry, removed.]

3.1.23

terminological system

set of concepts structured according to the relations among them, each concept being represented by a sign which denotes it

Note 1 to entry: In terminology work, and in this document, three types of such signs (designations) are distinguished: symbols, appellations and terms.

[SOURCE:ISO 18308:2011, 3.50, modified — Note 1 to entry removed, Note 2 to entry has become new Note 1 to entry.]

3.1.24

coding system

combination of a set of code meanings and a set of code values, based on a coding scheme

Note 1 to entry: Code meanings are typically represented by terms or rubrics, but they can have other representations. Code values are typically numeric or alphanumeric.

Note 2 to entry: For clinical information models, the coding schemes are typically derived from terminological systems, for example because they have coding schemes included.

[SOURCE:ISO/TR 12300:2014, 2.2.5, modified — Notes to entry added.]

3.1.25

code value

result of applying a coding scheme to a code meaning

[SOURCE:EN 1068:2005, 3.6, modified — Example added.]

3.1.26

value set

uniquely identifiable set of valid concept representations ここで, any concept representation can be tested to determine whether it is a member

Note 1 to entry: A value set is intended to be a set in the formal sense, and so should contain only one code for each uniquely identifiable concept that it contains.

[SOURCE:ISO/TS 18864:2017, 3.32, modified —"of the value set" removed.]

3.1.27

reference model for open distributed processing

RM-ODP

standardized approach to design and governance of information systems, in particular systems involving data communications between organizations that have different computing platforms.

[SOURCE:ITU-T Rec. X.901-X.904, Reference [36]]

3.1.28

use case

set of scenarios that address a particular business/clinical domain or topic

Note 1 to entry: It specifies interactions between external actors and the system to attain particular goals or a particular methodology.

Note 2 to entry: Use cases can be used in system analysis to identify, clarify, and organize system requirements or process steps.

[SOURCE:ISO/TR 19669:2017, 3.17, modified — Note to entry removed, new Notes to entry added.]

3.1.29

archetype

instance of an archetype model, specifying the clinical concept and the value constraints that apply to one class of record component instances in an electronic health record extract

[SOURCE:ISO 13606-1:2019, 3.3.2]

3.1.30

archetype model

information model of the metadata to represent the domain-specific characteristics of electronic health record entries, by specifying values or value constraints for classes and attributes in the electronic health record reference model

[SOURCE:ISO 13606‑1:2019, 3.3.3]

3.1.31

clinical template

clinical information model that structures information around discrete clinical concepts in a way that supports reuse of components across different clinical communication and record keeping activities and promotes common approaches to clinical information system development and interoperability

3.1.32

electronic health record

EHR

information relevant to the wellness, health and healthcare of an individual, in computer-processable form and represented according to a standardized information model

Note 1 to entry: It is the logical representation of information regarding or relevant to the health of a subject of care.

[SOURCE:ISO 18308:2011, 3.20, modified — Note to entry added.]

3.1.33

electronic health record architecture

formal description of a system of components and services for recording, retrieving and handling information in electronic health records

Note 1 to entry: It is about the logical components defined in terms of information models, and the computational services.

Note 2 to entry: The two-level modelling principle can be applied in electronic health record architectures using one generic information model for the whole system and specifying the details in clinical information models.

[SOURCE:ISO 18308:2011, 3.21, modified — Notes to entry added.]

3.1.34

association

relationship in which classes in a model relate to each other via a connector or link

3.1.35

aggregation

special type of association in which child classes are configured together to create a more complex parent class

3.1.36

composition

special type of association in which a child class cannot exist independent of the parent class

3.1.37

generalization

mechanism to combine similar classes into one single, more generic class

3.1.38

specialization

mechanism to create new sub-classes from one existing class

3.1.39

information governance

processes by which an organization obtains assurance that the risks to its information and thereby the operational capabilities and integrity of the organization are effectively identified and managed

[SOURCE:ISO/TS 14441:2013, 3.25]

3.1.40

lifecycle

sequence of events that mark the development and use of an information resource

Note 1 to entry: Clinical information models are seen as information resources that undergo governance, for which a lifecycle is a key part.

[SOURCE:ISO 15836-1:2017, 3.1.2, modified —"of a resource" removed from term and"information" added to definition, Note 1 to entry added.]

3.1.41

quality

degree to which a set of inherent characteristics of an object fulfils requirements

Note 1 to entry: This defines the degree to which all the properties and characteristics of a product, process, or service satisfy the requirements that ensue from the purpose for which that product, process, or service is to be used.

Note 2 to entry: In the context of clinical information models this is about the quality of the models, the quality of the developmental process and the services as to the governance of clinical information models.

[SOURCE:ISO 9000:2015, 3.6.2, modified — Notes to entry deleted, new notes to entry added.]

3.1.42

quality management system

QMS

[SOURCE:ISO 9000:2015, 3.5.4, modified — Note to entry added.]