Changes between Version 3 and Version 4 of Archtectural Overview Integrating openEHR
- Timestamp:
- Oct 4, 2007, 10:09:25 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Archtectural Overview Integrating openEHR
v3 v4 1 14 openEHRと他システムとの統合 2 1 = 14 openEHRと他システムとの統合 = 2 [[TOC]] 3 3 14 Integrating openEHR with other Systems 4 4 5 14.1 概要 5 == 14.1 概要 == 6 6 7 7 14.1 Overview … … 23 23 In 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. 24 24 25 14.2 統合アーキタイプ 25 == 14.2 統合アーキタイプ == 26 26 27 27 14.2 Integration Archetypes … … 53 53 In 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. 54 54 55 14.3 データ・コンバージョンのアーキテクチャー 55 == 14.3 データ・コンバージョンのアーキテクチャー == 56 56 57 57 14.3 Data Conversion Architecture
