Changes between Version 34 and Version 35 of Archtectural Overview Archetypes


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

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Archetypes

    v34 v35  
    11[wiki:"Archtectural Overview index" TOC] [wiki:"Archtectural Overview Identification" PREV] [wiki:"Archtectural Overview Paths" 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://svn.openehr.org/specification/TAGS/Release-1.0.1/publishing/html/architecture/overview/Output/archetyping.html 10 Archetypes and Templates]の翻訳である。内容の正確性については保証しないので,正確な内容については原文を参照すること
    44
     
    6610 Archetypes and Templates
    77
    8 == 10.1 概観 ==
     8== 10.1 概要 == #overview
    9910.1 Overview
    1010
     
    3838
    3939
    40 == 10.2 アーキタイプの形式論とモデル ==
     40== 10.2 アーキタイプの形式論とモデル == #formalism
    414110.2 Archetype Formalisms and Models
    4242
    43 === 概観 ===
     43=== 概要 === #form_overview
    444410.2.1 Overview
    4545
     
    5757openEHR Templates are represented as dADL documents whose object model conforms to the Template Object Model (TOM).
    5858
    59 === 10.2.2 アーキタイプ間の時間関係性 ===
     59=== 10.2.2 アーキタイプ間の時間関係性 === #design_time
    6060
    616110.2.2 Design-time Relationships between Archetypes
     
    7777The second relationship possible between archetypes is composition, allowing large data structures to be flexibly constrained via the hierarchical re-use of smaller archetypes. Composition is defined in terms of `slots' within an archetype. A slot is a point in an archetype structure where, instead of specifying an object type inline, a special allow_archetype constraint is used to specify other archetypes constraining that same type, that may be used at that point. For example, the archetype openEHR-EHR-SECTION.vital_signs.v1 defines a heading structure for headings to do with vital signs. It also defines as its items attribute value (i.e. what comes under the heading) a number of possible Observations; however, rather than defining these inline, it specifies an archetype slot in the form of constraints on Observation archetypes that are allowed at that point. The simplest kind of constraint is in terms of regular expressions on archetype identifiers. More complex constraints can be stated in terms of paths in other archetypes (for example exists(/some/path[at0005])). A slot thus defines a `chaining point' in terms of possible archetypes allowed or excluded at that point; limiting this to a single archetype is of course possible. Templates are used to choose which particular archetypes allowed at a slot will actually be used in a given circumstance.
    7878
    79 == 10.3 データに対するアーキタイプとテンプレートの関係 ==
     79== 10.3 データに対するアーキタイプとテンプレートの関係 == #relationship
    8080
    818110.3 Relationship of Archetypes and Templates to Data
     
    8888[[Image(archetypinga.gif)]]
    8989
    90 == 10.4 アーキタイプ利用可能な参照モデルデータ  ==
     90== 10.4 アーキタイプ利用可能な参照モデルデータ  == #reference
    919110.4 Archetype-enabling of Reference Model Data
    9292
     
    110110The 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.
    111111
    112 == 10.5 アーキタイプ、テンプーレートならびにパスについて ==
     112== 10.5 アーキタイプ、テンプーレートならびにパスについて == #templates_path
    113113
    11411410.5 Archetypes, Templates and Paths
     
    124124[[Image(archetypingb.gif)]]
    125125
    126 == 10.6 実行時におけるアーキタイプとテンプレート ==
     126== 10.6 実行時におけるアーキタイプとテンプレート == #rumtime
    12712710.6 Archetypes and Templates at Runtime
    128128
    129 === 10.6.1 概観 ===
     129=== 10.6.1 概要 === #rumtime_overview
    13013010.6.1 Overview
    131131
     
    134134openEHR archetypes and templates were designed as formal artefacts, so as to be computable at runtime. They perform two key functions. The first is to facilitate data validation at data capture or import time, i.e. to guarantee that data conform to not just the reference model, but also to the archetypes themselves. Data validation with archetypes is mediated by the use of openEHR Templates. The second function is as a design basis for queries. Since data are captured based on archetypes, all openEHR data are guaranteed to conform to the "semantic paths" that are created by the composition of archetypes within a template. The paths (such as those shown in FIGURE 31 above) are incorporated within a familiar SQL-style syntax, to form queries that can be evaluated to retrieve items on a semantic basis.
    135135
    136 === 10.6.2 アーキタイプとテンプレートの配置 ===
     136=== 10.6.2 アーキタイプとテンプレートの配置 === #deploy
    137137
    13813810.6.2 Deploying Archetypes and Templates
     
    178178[[Image(archetyping4.gif)]]
    179179
    180 === 10.6.3 データ取得時の検証 ===
     180=== 10.6.3 データ取得時の検証 === #validation
    181181
    18218210.6.3 Validation during Data Capture
     
    202202If data are later modified, they are brought into the kernel along with the relevant template and archetypes, and the embedded node identifiers allow the kernel to continue to perform appropriate checking of changes to the data.
    203203
    204 === 10.6.4  照会 ===
     204=== 10.6.4  照会 === #query
    205205
    20620610.6.4 Querying
     
    221221 
    222222
    223 == 10.7 openEHRアーキタイプ ==
     223== 10.7 openEHRアーキタイプ == #openehr
    22422410.7 The openEHR Archteypes
    225225