Changes between Version 13 and Version 14 of Archtectural Overview Aims


Ignore:
Timestamp:
Aug 28, 2007, 1:54:31 AM (14 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Aims

    v13 v14  
    2020In this figure, each bubble represents a set of requirements, being a superset of all requirements of bubbles contained within it. Requirements for a generic record of care for any kind of subject in a local deployment are represented by the top left bubble. The subsequent addition of requirements corresponding to living subjects and then human subjects is represented by the bubbles down the left side of the diagram. The requirements represented by the largest bubble on the left hand side correspond to "local health records for human care", such as radiology records, hospital EPRs and so on. Additional sets of requirements represented by wider bubbles going across the diagram correspond to extending the scope of the content of the care record first to a whole subject (resulting in a patient-centric, longitudinal health record) and then to populations or cohorts of subjects, as done in population health and research. From the (human) healthcare point of view, the important requirements groups extend all the way to the bottom row of the diagram.
    2121
    22 図の下になればなるほど,ケアの対象の特異度が(「すべて」から「ヒト」へと)増加します。これはopenEHRではアーキタイプによってほとんど実装されます。図を横切って
     22図の下になればなるほど,ケアの対象の特異度が(「すべて」から「ヒト」へと)増加する。これはopenEHRではアーキタイプによってほとんど実装される。図を横切って要件は記録内容の範囲が(部分的なものから全体へと)ひろがり、さまざまな場所に配備されることで主に表現され、単独での利用から相互利用可能な形式として徐々に利用される。今日のEHRに関する主な要望の一つは、ケアを共有するために統合された情報フレームワークによって提供される「統合されたケアの記録」である[[FootNote(The Integrated Care EHR is described in ISO/TR 20514 (2005))]]。
    2323
    2424Going down the diagram, requirements corresponding to increasing specificity of subject of care (from "any" to "human") are mostly implemented in openEHR by the use of archetypes. Going across the diagram, the requirements corresponding to increasing scope of record content (from episodic to population) are mainly expressed in different deployments, generally going from standalone to a shared interoperable form. One of the key aspirations for EHRs today is the "integrated care record" sought by many health authorities today1, which provides an informational framework for integrated shared care.
     25
     26openEHRによるアプローチの結果として、コンポーネントとアプリケーションは統合され、共有されたケア記録による要件を満たすために作成されており、(例えば)部分的な放射線記録システムとしても作成されている。
    2527
    2628As a result of the approach taken by openEHR, components and applications built to satisfy the requirements of an integrated shared care record can also be deployed as (for example) an episodic radiology record system.
     
    95973see http://svn.openehr.org/specification/TRUNK/publishing/requirements/iso18308_conformance.pdf
    9698
     99[[FootNote]]
     100
    97101[wiki:"Archtectural Overview index" TOC]        [wiki:"Archtectural Overview Overview" PREV]    [wiki:"Archtectural Overview Design Principles" NEXT]