Changes between Version 11 and Version 12 of Archtectural Overview Archetypes


Ignore:
Timestamp:
Oct 8, 2007, 6:15:14 PM (14 years ago)
Author:
Tatsukawa, Akimichi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Archetypes

    v11 v12  
    105105In this way, each archetyped data composition1 in openEHR data has a generating archetype which defines the particular configuration of instances to create the desired composition. An archetype for "biochemistry results" is an OBSERVATION archetype, and constrains the particular arrangement of instances beneath an OBSERVATION object; a "problem/SOAP headings" archetype constrains SECTION objects forming a SOAP headings structure. In general, an archetyped data composition is any composition of data starting at a root node and continuing to its leaf nodes, at which point lower-level compositions, if they exist, begin. Each of the archetyped areas and its subordinate archetyped areas in FIGURE 30 is an archetyped data composition.
    106106
     107電子カルテシステム(他のシステムでも)にてアーキタイプを利用してデータを生成することは、どんな上位レベルのオブジェクトにおいてもそのデータ構造がテンプレートから選択されたアーキタイプの合成によって定義された制約に適合していることが保証されることを意味している。その制約はオプションや値あるいは語彙に関する制約をも含むものである。
     108
    107109The result of the use of archetypes to create data in the EHR (and other systems) is that the structure of data in any top-level object conforms to the constraints defined in a composition of archetypes chosen by a template, including all optionality, value, and terminology constraints.
    108110