Changes between Version 26 and Version 27 of Archtectural Overview Versioning

Timestamp:

Nov 5, 2007, 11:32:08 PM (16 years ago)

Author:

KOBAYASHI, Shinji

Comment:

--

Archtectural Overview Versioning

@@ -148 +148 @@
 An underlying design concept of the versioning model defined in openEHR is known as a "virtual version tree". The idea is simple in the abstract. Information is committed to a repository (such as an EHR) in lumps, each lump being the "data" of one Version. Each Version has its place within a version tree, which in turn is maintained inside a Versioned object (or "version container"). The virtual version tree concept means that any given Versioned object may have numerous copies in various systems, and that the creation of versions in each is done in such a way that all versions so created are in fact compatible with the "virtual" version tree resulting from the superimposition of the version trees of all copies. This is achieved using simple rules for version identification and is done to facilitate data sharing. Two very common scenarios are served by the virtual version tree concept:
 
- * 
+ * ｢処方｣や｢問題リスト｣といった患者の状態をしめす代替となる長期にわたるデータ（openEHRでは永続的COMPOSITION）が医療機関や介護機関で作成され，そのほかの多くの施設にわたって共有されるように維持管理される
+ * あるひとつの場所にあるEHRサーバ内のEHRがほかのEHRサーバにミラーリングされる(たとえば，関連のある患者が同じように治療を受けるケア事業者）。ミラーリング処理はサーバ間で継ぎ目なく，位置や時間，データを作成した著者にかかわりなく非同期に同期されることが要求されている。
 
     * longitudinal data that stands as a proxy for the state or situation of the patient such as "Medications" or "Problem list" (persistent Compositions in openEHR) is created and maintained in one or more care delivery organisations, and shared across a larger number of organisations;
     * some EHRs in an EHR server in one location are mirrored into one or more other EHR servers (e.g. at care providers where the relevant patients are also treated); the mirroring process requires asynchronous synchronisation between servers to work seamlessly, regardless of the location, time, or author of any data created. 
+
+openEHRのバージョニングの仕組みはデータが作成されたりコピーされた場所を問わないこと，共有する際に矛盾がないこと，論理的コピーが明示的に表されることが保証されている。それにより共有されるケアの内容についてのデータの共有について直接的に支援している。
 
 The versioning scheme used in openEHR guarantees that no matter where data are created or copied, there are no inconsistencies due to sharing, and that logical copies are explicitly represented. It therefore provides direct support for shared data in a shared care context.