Changes between Version 30 and Version 31 of Archtectural Overview Design of the openEHR EHR

Timestamp:

Oct 22, 2007, 8:56:49 PM (17 years ago)

Author:

KOBAYASHI, Shinji

Comment:

--

Archtectural Overview Design of the openEHR EHR

@@ -168 +168 @@
  * support for automated workflow, without requiring it. 
 
-Coupled with the comprehensive versioning capabilities of openEHR, the Instruction/Action design allows clinical users of the record to define and manage interventions for the patient in a distributed environment.
+openEHRのわかりやすい更新管理能力と、INSTRUCTION/ACTIONの設計のおかげで、分散環境において臨床家に定義すべき記録や、患者に対する介入を管理することができるようになっている。
 
+Coupled with the comprehensive versioning capabilities of openEHR, the Instruction/Action design allows clinical users of the record to define 
+
+and manage interventions for the patient in a distributed environment.
+
+== 6.6 EHRでの時間 ==
 6.6 Time in the EHR
 
-Time is well-known as a challenging modelling problem in health information. In openEHR, times that are a by-product of the investigation process (e.g. time of sampling or collection; time of measurement, time of a healthcare business event, time of data committal) described above are concretely modelled, while other times specific to particular content (e.g. date of onset, date of resolution) are modelled using archetyping of generic data attributes. The following figure shows a typical relationship of times with respect to the observation process, and the corresponding attributes within the openEHR reference model. Note that under different scenarios, such as GP consultation, radiology reporting and others, the temporal relationships may be quite different than those shown in the figure. Time is described in detail in the EHR Information Model document.
+時間は健康情報をモデル化する際の取り組むべき問題点として知られている。openEHRでは、時間は[[BR]]Time is well-known as a challenging modelling problem in health information. In openEHR, times that are a by-product of the investigation process (e.g. time of sampling or collection; time of measurement, time of a healthcare business event, time of data committal) described above are concretely modelled, while other times specific to particular content (e.g. date of onset, date of resolution) are modelled using archetyping of generic data attributes. The following figure shows a typical relationship of times with respect to the observation process, and the corresponding attributes within the openEHR reference model. Note that under different scenarios, such as GP consultation, radiology reporting and others, the temporal relationships may be quite different than those shown in the figure. Time is described in detail in the EHR Information Model document.
 
 6.7 Language