Changes between Version 1 and Version 2 of Archtectural Overview Integrating openEHR


Ignore:
Timestamp:
Sep 21, 2007, 5:32:29 PM (17 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Archtectural Overview Integrating openEHR

    v1 v2  
    2626
    2727In 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.
     28
    282914.3 Data Conversion Architecture
    2930
    3031The integration archetype-based strategy for importing data into an openEHR system, shown in FIGURE 39, consists of two steps.
    3132
     33[[Image(integrationa.gif)]]
     34
    3235Firstly, data are converted from their original syntactic format into openEHR COMPOSITION/SECTION/GENERIC_ENTRY structures, shown in the openEHR integration switch. Most of the data will appear in the GENERIC_ENTRY part, controlled by an integration archetype designed to mimic the incoming structure (such as an HL7v2 lab message) as closely as possible; FEEDER_AUDIT structures are used to contain integration meta-data. The result of this step is data that are expressed in the openEHR type system (i.e. as instances of the openEHR reference model), and are immediately amenable to processing with normal openEHR software.
    3336