Changes between Version 6 and Version 7 of openEHR Models, Archetypes and Biomedical Ontologies


Ignore:
Timestamp:
Aug 5, 2007, 3:02:35 PM (12 years ago)
Author:
Tatsukawa, Akimichi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • openEHR Models, Archetypes and Biomedical Ontologies

    v6 v7  
    204204          * Evidence codes
    205205    * Basic Formal Ontology (BFO) [home page] (「現実」を対象としたオントロジーである), 以下のオントロジーと協調する:
    206           * SNAP, an ontology of substantial entities, tropes (their qualities and functions) and spatial regions
    207           * SPAN, an ontology of process, temporal and spatio-temporal regions
    208           * The paper "Biodynamic Ontology: Applying BFO in the Biomedical Domain" by Grenon, Smith and Goldberg is a good introduction to BFO in the biomedical domain. [ref]
     206          * SNAP, 実在、トロープ(その性質と機能)、空間に関するオントロジーである
     207
     208          * SPAN, 過程、時間的ならびに時空に関するオントロジーである
     209          * Grenon、Smith、Goldbergらによる論文"Biodynamic Ontology: Applying BFO in the Biomedical Domain"は医学生物学領域におけるよい導入になっている [ref]
    209210
    210211
     
    218219          * The paper "Biodynamic Ontology: Applying BFO in the Biomedical Domain" by Grenon, Smith and Goldberg is a good introduction to BFO in the biomedical domain. [ref]
    219220
    220 [top]
     221= openEHRのどの部分がオントロジーと関係するか? =
     222
    221223What parts of openEHR have Ontological Relevance?
    222224
     225openEHRの環境では、オントロジーの観点から独立していると考えられる3つ実体がある。それは、参照モデル、アーキタイプ、語彙(openEHRの内部で定義された語彙のみならず、ICDコード, ICPC, LOINC and SNOMED CTなどの外部で定義されたものも含まれる)
     226
    223227Within the openEHR environment there are 3 entities that can be considered in an ontological way: the reference model, the archetypes, and terminology (both the internal openEHR vocabularies and well-known external terminologies such as ICDx, ICPC, LOINC and SNOMED CT).
     228
     229== openEHR参照モデル ==
     230
    224231The openEHR Reference Model
     232
     233openEHRの参照モデルは多数のクラスを定義しているが、オントロジーの観点からもっとも大切なモデルは、'Entry'の部分である。この部分はopenEHRの情報モデルにおいて形式的に定義されており、オンラインで詳細なUML図を見ることができる。Entryタイプの簡略化されたUML図は下に図示している。
     234
    225235The openEHR Reference Model defines many classes, but the part of the model of most ontological interest is the 'Entry' part, which is formally specified in the openEHR EHR Information Model; it can also be seen online as detailed UML. A summarised UML form of the Entry types in openEHR is illustrated below.
    226 Entry types     The 6th type is called GENERIC_ENTRY, and is designed for mapping into and out of legacy and integration structures such as CEN EN13606, HL7 CDA, message and relational databases. The UML model of this type is here; it is documented in the openEHR Integration IM. All of these types are extremely generic and archetypes are used to define the specific business/domain content models under each of these types - see archetype mindmap for examples.
     236
     237== Entry型 ==
     238Entry types
     239
     2406番目の型は GENERIC_ENTRYと呼ばれ、旧式のシステムとCEN EN13606, HL7 CDAなどの統合のための構造とをマッピングし、またメッセージと関係データベースとの対応付けを行なう。この型のUMLモデルはこちらにある。すなわち、openEHR の統合IMに文書がある。これらの型はみな極めて汎用的であり、アーキタイプを用いて特定の対象領域に関するモデルを定義する。例えば、アーキタイプのmindmapを参照のこと。
     241
     242The 6th type is called GENERIC_ENTRY, and is designed for mapping into and out of legacy and integration structures such as CEN EN13606, HL7 CDA, message and relational databases. The UML model of this type is here; it is documented in the openEHR Integration IM. All of these types are extremely generic and archetypes are used to define the specific business/domain content models under each of these types - see archetype mindmap for examples.
    227243
    228244The openEHR Entry model has an ontological design which is described in a forthcoming MedInfo 2007 paper (in-press copies are available on request). We can summarise the approach with the following three diagrams. The first is a model of process (shown in two ways); the second shows a cycle of information creation due to the process, and the last shows the information ontology developed in openEHR for recorded clinical information.