Changes between Version 1 and Version 2 of Archtectural Overview Versioning


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

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Versioning

    v1 v2  
    1 = 8 更新管理 ==
     1= 8 更新管理 =
    228 Versioning
    33[[TOC]]
    4 == 外観 ==
     4== 8.1 外観 ==
    558.1 Overview
    66
    7 更新管理はopenEHRアーキテクチャ
     7更新管理はopenEHRアーキテクチャでは欠くことのできない部分である。
    88
    99Version control is an integral part of the openEHR architecture. An openEHR repository for EHR or demographic information is managed as a change-controlled collection of "version containers" (modelled by the VERSIONED_OBJECT<T> class in the common.change_control package), each containing the versions of a top-level content structure (such as a Composition or Party) as it changes over time. A version-controlled top-level content structure is visualised in FIGURE 23.
     
    1212
    1313These concepts are well-known in configuration management (CM), and are used as the basis for most software and other change management systems, including numerous free and commercial products available today. They are a central design feature of openEHR architecture. The following sections provide more details
     14
     15== 8.2 設定管理パラダイム ==
    14168.2 The Configuration Management Paradigm
    1517
    1618The "configuration management" (CM) paradigm is well-known in software engineering, and has its own IEEE standard1. CM is about managed control of changes to a repository of items (formally called "configuration items" or CIs), and is relevant to any logical repository of distinct information items which changes in time. In health information systems, at least two types of information require such management: electronic health records, and demographic information. In most analyses in the past, the need for change management has been expressed in terms of specific requirements for audit trailing of changes, availability of previous states of the repository and so on. In openEHR, the aim is to provide a formal, general-purpose model for change control, and show how it applies to health information.
     19
     20=== 8.2.1 組織とリポジトリ ===
    17218.2.1 Organisation of the Repository
    1822
     
    2529In a software or document repository, the CIs are files arranged in the directories of the file system; in an EHR based on openEHR, they are Compositions, the optional Folder structure, Parties in the demographic service and so on. Contributions are made to the repository by users. This general abstraction is visualised in FIGURE 24.
    2630
     31=== 8.2.2 変更管理 ===
    27328.2.2 Change Management
    2833
     
    4247    * all changes are audit-trailed.
    4348
     49== 変更時間の管理 ==
    44508.3 Managing Changes in Time
    4551
     
    5965
    6066For the purposes of openEHR, a Contribution is considered as being the set of Versions created or attested at one time, as implied by FIGURE 26.
     67
     68=== 8.3.1 偏光を管理されたリポジトリの汎用モデル ===
    61698.3.1 General Model of a Change-controlled Repository
    6270
     
    6977The actual type of links between the controlled repository and the other entities might vary - in some cases it might be association, in others aggregation; cardinalities might also vary. FIGURE 27 therefore provides a guide to the definition of actual controlled repositories, such as an EHR, rather than a formal specification for them.
    7078
     79== 8.4 「仮想バージョンツリ」ー ==
    71808.4 The "Virtual Version Tree"
    7281