Changes between Version 5 and Version 6 of Archtectural Overview Integrating openEHR


Ignore:
Timestamp:
Apr 18, 2008, 11:02:10 PM (11 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Integrating openEHR

    v5 v6  
    11[wiki:"Archtectural Overview index" TOC] [wiki:"Archtectural Overview Deployment" PREV] [wiki:"Archtectural Overview Relationship to Standards" NEXT]
    2 
     2[[TOC]]
    33この文書は[http://svn.openehr.org/specification/TAGS/Release-1.0.1/publishing/html/architecture/overview/Output/front.html Archtectural Overview]の[http://www.openehr.org/svn/specification/TAGS/Release-1.0.1/publishing/html/architecture/overview/Output/integration.html 14 Integrating openEHR with other Systems]の翻訳である。正確性については保証しないので,適宜原文を参照すること
    44
    55= 14 openEHRと他システムとの統合 =
    6 [[TOC]]
     6
    7714 Integrating openEHR with other Systems
    88
    9 == 14.1 概要 ==
     9== 14.1 概要 == #overview
    1010
    111114.1 Overview
     
    2727In technical terms, a number of types of incompatibility have to be dealt with. There is no guarantee of correspondence of scope of incoming transactions and target openEHR structures - an incoming document for example might correspond to a number of clinical archetypes. Structure will not usually correspond, with legacy data (particularly messages) usually having flatter structures than those defined in target archetypes. Terminology use is extremely variable in existing systems and messages, and also has to be dealt with. Data types will also not correspond directly, so that for example, a mapping between an incoming string "110/80 mmHg" and the target openEHR form of two DV_QUANTITY objects each with their own value and units has to be made.
    2828
    29 == 14.2 統合アーキタイプ ==
     29== 14.2 統合アーキタイプ == #integration
    3030
    313114.2 Integration Archetypes
     
    5757In the data integration environment, "designed" archetypes always define the target structures, coding and other semantics of data, while "integration" archetypes provide the means mapping of external data into the openEHR environment.
    5858
    59 == 14.3 データ・コンバージョンのアーキテクチャー ==
     59== 14.3 データコンバージョンのアーキテクチャ == #conversion
    6060
    616114.3 Data Conversion Architecture
    6262
    63 データをopenEHRシステムにインポートするための統合アーキタイプベースの戦略は、図39に示す通り、2つのステップからなる。
     63データをopenEHRシステムにインポートするための統合アーキタイプベースの戦略は、図39に示す通り、2つのステップからなる。
    6464
    6565The integration archetype-based strategy for importing data into an openEHR system, shown in FIGURE 39, consists of two steps.