3. 情報モデルの標準化
用途、目的の共通認識
オントロジの定義
コンテキスト情報・監査情報の分離
Problem
文章による定義
• Lawrence Weed’s “problem-oriented”
method
• The model of Rector,Nwlan & Key
• The “hypothetico deductive” model
版管理 (Versioning)
COMPOSITIONがCI 相当
監査証跡・診療記録のメタデータ
COMPOSITION
• 診療記録の内容定義 ENTRY
• プロブレム
• 診療のナビゲーションに関わる定義
NAVIGATION
• SECTION
• プロブレムリスト
2階層情報モデル構造
・情報モデル(RM)
・アーキタイプ(Archetype)
情報モデル自体のオントロジの定義
ENTRY/CARE_ENTRY/EVALUATIONに所属
プロブレム記述自体のオントロジ、ターミノロジー
Problem曼陀羅@openEHR
セマンティックな接続の定義
・LINKクラスによるアーキタイプ間接続
4. The choice of these types is based on the clinical problem-solving process shown in FIGURE 17.
This figure shows the cycle of information creation due to an iterative, problem solving process typi-
cal not just of clinical medicine but of science in general. The “system” as a whole is made up of two
parts: the “patient system” and the “clinical investigator system”. The latter consists of health carers,
and may include the patient (at points in time when the patient performs observational or therapeutic
activities), and is responsible for understanding the state of the patient system and delivering care to
it. A problem is solved by making observations, forming opinions (hypotheses), and prescribing
actions (instructions) for next steps, which may be further investigation, or may be interventions
designed to resolve the problem, and finally, executing the instructions (actions).
This process model is a synthesis of Lawrence Weed’s “problem-oriented” method of EHR recording,
and later related efforts, including the model of Rector, Nowlan & Kay [7], and the “hypothetico-
ACTIVITY
FIGURE 16 The openEHR Entry model (in EHR IM)
FIGURE 17 Relationship of information types to the investigation process
opinions
observations
instructions
actions
patient
investigator
agents
investigator
- assessment
- goals
- plan
1
2
3
4
published
evidence
base
personal
knowledge
base
References:
*T Beale, S Heard,Architecture Overview Design of the openEHR EHR Rev 1.1,2007
3.Elstein AS, Shulman LS, Sprafka SA. Medical problem solving: an analysis of clinical reason- ing. Cambridge, MA: Harvard University Press, 1978
7.Rector A L, Nowlan W A, Kay S. Foundations for an Electronic Medical Record. The IMIA Yearbook of Medical Informatics 1992 (Eds. van Bemmel J, McRay A).
Stuttgart Schattauer 1994.
This process model is a synthesis of Lawrence Weed’s “problem-oriented” method of EHR recording, and later related efforts, including
the model of Rector, Nowlan & Kay [7], and the “hypothetico-
deductive” model of reasoning (see e.g. [3]). However hypothesis-making and testing is not the only successful process used by clinical
professionals - evidence shows that many (particularly those older and more experienced) rely on pattern recognition and direct retrieval
of plans used previously with similar patients or prototype models. The investigator process model used in openEHR is compatible with
both cognitive approaches, since it does not say how opinions are formed, nor imply any specific number or size of iterations to bring the
process to a conclusion, nor even require all steps to be present while iterating (e.g. GPs often prescribe without making a firm diagnosis).
Consequently, the openEHR Entry model does not impose a process model, it only provides the possible types of infor- mation that might
occur.
#奥原先生の研究にて言及
Problemの用途・目的
5. コンテキスト、監査情報の分離
• 臨床情報の記述とコンテキスト・監査用の情
報は明示的に分離する
• バージョン管理システムの概念
– 診療記録のマージなどの際に臨床情報はいじら
ずに、バージョンツリーの操作を行う
Versioning Architecture Overview
Rev 1.1
to provide a formal, general-purpose model for change control, and show how it applies to health
information.
8.2.1 Organisation of the Repository
The general organisation of a repository of complex information items such as a software repository,
or the EHR consists of the following:
• a number of distinct information items, or configuration items, each of which is uniquely
identified, and may have any amount of internal complexity;
• optionally, a directory system of some kind, in which the configurations items are organised;
• other environmental information which may be relevant to correctly interpreting the primary
versioned items, e.g. versions of tools used to create them.
In a software or document repository, the CIs are files arranged in the directories of the file system; in
an EHR based on openEHR, they are Compositions, the optional Folder structure, Parties in the
demographic service and so on. Contributions are made to the repository by users. This general
abstraction is visualised in FIGURE 24.
FIGURE 24 General Structure of a Controlled Repository
CI
CI
CI
CI
CI
CI
CI
CI
CI
Users
Repository
Users
CI
Directory
Structure Configuration
Item
F
F
F
F
contributions contributions
コンテキスト・監査情報 臨床情報
11. T Beals, S Heard,D Karla, D Lloyd, “The openEHR Reference Model” 2010
コミットした時刻の監
査証跡
Committerでコミット
した人を記録
コンテキスト・監査情報の
標準モデル
全てにおいて6W1Hが同じ
方法で記録・管理されるこ
とが重要
12. Ontological Structure of archetype
“2階層モデル”と外部概念への参照
Citation Sundvall, E., Qamar, R., Nyström, M., Forss, M., Petersson, H., Karlsson, D., Åhlfeldt, H.,Rector, A. :Integration of
tools for binding archetypes to SNOMED CT: BMC Medical Informatics and Decision Making 8, S7, 2008.
疾患概念の記述
情報モデルの抽象化
外部概念
15. 情報モデルのオントロジ
• ENTRYは”臨床記述そのもの”に対応し、ENTRYを基底クラスとしたオントロジを構
成する
• EVALUATION/INSTRUCTION/ACTION/OBSERVATIONは、”Clinical Investigator
Recording Process”のモデルに沿って分類
EHR Information Model Entry Package
Rev 5.1.1
patients or prototype models. The investigator process is compatible with both cognitive approaches,
since it does not say how opinions are formed, nor imply any specific number or size of iterations to
bring the process to a conclusion. As such, the openEHR information model does not impose any
process model, only the types of information used.
On the basis of this process, a Clinical Investigator Recording ontology is developed [4], as shown in
FIGURE 19. From this ontology, the openEHR class model for Entries is derivde. The openEHR
Entry class names are annotated next to their originating ontological categories.
FIGURE 19 The Clinical Investigator Recording (CIR) ontology
INSTRUCTIONEVALUATION
OBSERVATION ACTION
ADMIN_ENTRY
CARE_ENTRY
ENTRY
observation/
intervention
recorded
information
history opinion
assessment
care
information
admin
information
proposal
diagnosis risk recommendationgoal
intervention
scenarioprognosis
instruction
xxx
xxx = observation-related
= intervention-related
observation action
cognitive/temporal
categories
categories
analytical
categories
request
investigation
request
Problem
16. 臨床情報記述用のオントロジ
Empirical Derivation of an Electronic Clinically Useful Problem Statement
System Steven H. Brown, MS, MD; Randolph Annals of Internal Medicine Volume
131 Number 2 pp.117-126 1999
• Problemの記述に特化した用語集 CCPSS(Canonical Clinical Problem Statement
System) の評価
• 現在はCCPSSはUMLSに収録されている。
“Existing standardized vocabularies that predominantly include diagnoses or findings,
such as the International Classification of Diseases, Ninth Revision, Clinical Modification
(ICD-9-CM) (65) and the Systematized Nomenclature of Human and Veterinary Medicine
(SNOMED) (66), cannot encompass all categories of problem statements.”
“Computerized problem-statement input techniques have varied across implementation
sites because no ideal problem statement vocabulary exists”
“Because full-scale problem-oriented medical record systems are cumbersome and are
not universally accepted, most computerized medical record systems provide problem
lists but are not “problem-oriented.”
これらの指摘は現在でもあてはまる。1999年の古さを感じさせない
#Problemに関連した話題を例として
18. CEN
The Link Item class is a simplified form of the Synapses Link Item, permitting
links to be established but with limited labelling and no representation for impor-
tance.
Synapses
The Link Item class provides the means to link any arbitrary parts of a single
EHR, for the overall linkage network to be labelled and revised, and for each
direct link to be labelled explicitly. An importance attribute provides guidance on
how links should be handled if only part of a linkage network is requested by a
client process.
GEHR n/a
HL7v3 The ACT_RELATIONSHIP class in some cases appears to correspond to LINK.
Attributes Signature Meaning
1..1
meaning: DV_TEXT Used to describe the relationship, usually in
clinical terms, such as “in response to” (the
relationship between test results and an order),
“follow-up to” and so on. Such relationships
can represent any clinically meaningful connec-
tion between pieces of information.
Values for meaning include those described in
Annex C, ENV 13606 pt 2 [11] under the cate-
gories of “generic”, “documenting and report-
ing”, “organisational”, “clinical”,
“circumstancial”, and “view management”.
1..1
type: DV_TEXT The type attribute is used to indicate a clinical
or domain-level meaning for the kind of link,
for example “problem” or “issue”. If type val-
ues are designed appropriately, they can be used
by the requestor of EHR extracts to categorise
links which must be followed and which can be
broken when the extract is created.
1..1
target: DV_EHR_URI The logical “to” object in the link relation, as
per the linguistic sense of the meaning attribute.
CLASS LINK