Changes between Version 6 and Version 7 of Archtectural Overview Identification


Ignore:
Timestamp:
Nov 21, 2007, 12:07:49 AM (16 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Identification

    v6 v7  
    1414In a distributed environment, the correspondence of EHR ids to subjects (i.e. patients) is variable, and depends on the level of integration of the environment. In non-integrated or sporadically connected environments, the same patient is likely to have a separate EHR at each institution, each with its own unique EHR id, but the same subject id. If copies of parts of the patient EHR at one location is requested by another provider, the received items will be merged into the local EHR for that patient. Merges of persistent Compositions in such circumstances are likely to require human intervention. Multiple EHR ids per patient in a distributed context are evidence of a lack of systematic connectivity or identification service.
    1515
     16完全に統合された分散環境においては,複数の場所にローカルのEHRを持つが,それぞれが同じEHR IDを持つことになる。患者が新しい場所に現れると,その環境の識別サービスに対して,この患者のEHRが既にどこ何あるのではないかということを決定するための要求が行われるであろう。もし,存在するのであれば既存のEHRの全体/部分的なクローンが作られるか,新しく何も情報がないEHRが作成されるが,すべての場合においてEHR IDは同じ患者であれば他の場所で使われたものと同じものとなるだろう。
     17
    1618In a fully integrated distributed environment, the typical patient will still have local EHRs in multiple locations, but each carrying the same EHR id. When a patient presents in a new location, a request to the environment's identification service could be made to determine if there is already an EHR for this patient. If there is, a clone of all or part of the existing EHR could be made, or a new empty EHR could be created, but in all cases, the EHR id would be the same as that used in other locations for the same patient.
     19
     20上記のロジックでは,openEHRのEHRがどの場所にあるのかだけを保持していることに注意しなくてはならない。
    1721
    1822Note that the above logic only holds where the EHR in each location is an openEHR EHR.
     
    2428=== 9.2.1 汎用スキーム ===
    25299.2.1 General Scheme
     30
     31EHRの識別がopenEHRでは完全に定義できるものではないのとはことなり,EHRに伴うアイテムの識別は完全に定義されている。ここで記述されたスキーマでは,2種類の「識別子(identifier)」が必要とされる。識別子そのものと参照,それとロケータである。
    2632
    2733While identification of EHRs is not completely definable by openEHR, the identification of items with an EHR is fully defined. The scheme described here requires two kinds of "identifier": identifiers proper and references, or locators. An identifier is a unique (within some context) symbol or number given to an object, and usually written into the object, whereas a reference is the use of an identifier by an exterior object, to refer to the object containing the identifier in question. This distinction is the same as that between primary and foreign keys in a relational database system.