Changes between Version 2 and Version 3 of Archtectural Overview Identification

Timestamp:

Nov 6, 2007, 4:34:35 PM (16 years ago)

Author:

KOBAYASHI, Shinji

Comment:

--

Archtectural Overview Identification

@@ -6 +6 @@
 9.1 Identification of the EHR
 
+openEHRシステムでは、EHRはそれぞれにEHR idとして知られ、各EHRを示すルートEHRオブジェクトでもある固有の識別子を持つ。EHR IDは信頼できるOIDやGUIDを作成するような全体で固有の「強い」識別子である。一つのシステム内に同じ対象を示す二つのEHRがあってはならない。もし、そうでない場合には、EHRシステムは対象となるEHRの存在を発見できず、対象に与えられたデモグラフィック属性を適合する子ともできないということになる.
+
 In an openEHR system, each EHR has a unique identifier, known as the EHR id, found in the root EHR object of each EHR. EHR ids should be "strong" globally unique identifiers such as reliably created Oids or Guids. No single system should contain two EHRs for the same subject. If this is not the case, it means that the EHR system has failed to detect the existence of an EHR for a subject, or failed to match provided demographic attributes to the subject.
+
+分散環境では，EHR ID
 
 In 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.