Changes between Version 3 and Version 4 of Archtectural Overview Integrating openEHR


Ignore:
Timestamp:
Oct 4, 2007, 10:09:25 PM (14 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Integrating openEHR

    v3 v4  
    1 14 openEHRと他システムとの統合
    2 
     1= 14 openEHRと他システムとの統合 =
     2[[TOC]]
    3314 Integrating openEHR with other Systems
    44
    5 14.1 概要
     5== 14.1 概要 ==
    66
    7714.1 Overview
     
    2323In 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.
    2424
    25 14.2 統合アーキタイプ
     25== 14.2 統合アーキタイプ ==
    2626
    272714.2 Integration Archetypes
     
    5353In 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.
    5454
    55 14.3 データ・コンバージョンのアーキテクチャー
     55== 14.3 データ・コンバージョンのアーキテクチャー ==
    5656
    575714.3 Data Conversion Architecture