| 13 | | * they allow domain experts such as clinicians to create the definitions which will define the data structuring in their information systems |
| 14 | | * they provide runtime validation of data input via GUI or any batch process |
| 15 | | * they provide a basis for intelligent querying of data. |
| | 17 | * 臨床家といった特定のドメインの専門家に情報システムのデータ構造を規定するための諸定義を作成させることができる |
| | 18 | * GUIやバッチ処理などによる実行時のデータ検証を提供することができる。 |
| | 19 | * データに対する知的な問い合わせの基本となることができる。 |
| | 20 | |
| | 21 | * they allow domain experts such as clinicians to create the definitions which will define the data structuring in their information systems |
| | 22 | * they provide runtime validation of data input via GUI or any batch process |
| | 23 | * they provide a basis for intelligent querying of data. |
| 73 | | 1. |
| 74 | | |
| 75 | | identify the need: e.g. "we need an archetype to describe the care plan in a discharge summary" |
| 76 | | 2. |
| 77 | | |
| 78 | | determine if there are already archetypes for this purpose: logon to an archetype library and interrogate it. Study the archetypes which already exist and determine if they can be used, or else specialised for your purpose |
| 79 | | 3. |
| 80 | | |
| 81 | | if you need to build a new archetype, you will most likely have professional colleagues (perhaps international) with whom you should discuss the problem and consider the design |
| 82 | | 4. |
| 83 | | |
| 84 | | to actually create an archetype will require an editor; archetypes will be saved in an interoperable format, e.g. ADL |
| 85 | | 5. |
| 86 | | |
| 87 | | when a draft archetype has reached a point where you want to share it, you will upload it to the archetype library |
| 88 | | 6. |
| 89 | | |
| 90 | | changes to the archetype will occur with version control and audit trailing, just like in document authoring systems |
| 91 | | 7. |
| 92 | | |
| 93 | | at some point, your organisation will propose the archetype to a body capable of doing certification - i.e. quality assurance |
| 94 | | 8. |
| 95 | | |
| 96 | | archetypes certified for use can be injected into an online network of archetype servers, making them available to archetype-enabled systems |
| 97 | | 9. |
| 98 | | |
| 99 | | systems using archetypes, such as EHRs will retrieve the archetypes they need from a local archetype server, and may well convert them to a locally efficient form |
| 100 | | 10. |
| 101 | | |
| 102 | | at runtime, locally defined templates will cause archetypes to be invoked and put into action, performing their main job, i.e. data structuring and validation. |
| | 81 | 1. identify the need: e.g. "we need an archetype to describe the care plan in a discharge summary" |
| | 82 | 1. determine if there are already archetypes for this purpose: logon to an archetype library and interrogate it. Study the archetypes which already exist and determine if they can be used, or else specialised for your purpose |
| | 83 | 1. if you need to build a new archetype, you will most likely have professional colleagues (perhaps international) with whom you should discuss the problem and consider the design |
| | 84 | 1. to actually create an archetype will require an editor; archetypes will be saved in an interoperable format, e.g. ADL |
| | 85 | 1. when a draft archetype has reached a point where you want to share it, you will upload it to the archetype library |
| | 86 | 1. changes to the archetype will occur with version control and audit trailing, just like in document authoring systems |
| | 87 | 1. at some point, your organisation will propose the archetype to a body capable of doing certification - i.e. quality assurance |
| | 88 | 1. archetypes certified for use can be injected into an online network of archetype servers, making them available to archetype-enabled systems |
| | 89 | 1. systems using archetypes, such as EHRs will retrieve the archetypes they need from a local archetype server, and may well convert them to a locally efficient form |
| | 90 | 1. at runtime, locally defined templates will cause archetypes to be invoked and put into action, performing their main job, i.e. data structuring and validation. |
| 117 | | * The anti-coagulation EHR system developed by CHIME, UCL, and in production at Whittington Hopsital, Archway, London. This system's architecture is based on the Synapses project, and uses a reference model based on CEN ENV 13606:2000, and an "Object Dictionary" of structures akin to the "legacy archetypes" described above. |
| 118 | | * Various GeHR projects in Australia, funded by the RACGP GPCG (General Practice Computing Group). |
| 119 | | * The HealthConnect diabetic shared care EHR system being built in Brisbane, Australia by the DSTC. This is based on the openEHR reference model and ADL. |
| 120 | | * The Systematic Software Engineering (SSE) EHR system in production in Aarhus County in Denmark. This is a significant system, built using its own reference model and archetype 'language'. It has an archetype editor, and all information in the system is archetyped. It was designed independently of the openEHR archetype approach; however, there have been discussions between people working on openEHR and SSE regarding potential use of ADL and other public specifications. openEHR is also likely to benefit from the experience gained by SSE and the system's users. |
| | 105 | * The anti-coagulation EHR system developed by CHIME, UCL, and in production at Whittington Hopsital, Archway, London. This system's architecture is based on the Synapses project, and uses a reference model based on CEN ENV 13606:2000, and an "Object Dictionary" of structures akin to the "legacy archetypes" described above. |
| | 106 | * Various GeHR projects in Australia, funded by the RACGP GPCG (General Practice Computing Group). |
| | 107 | * The HealthConnect diabetic shared care EHR system being built in Brisbane, Australia by the DSTC. This is based on the openEHR reference model and ADL. |
| | 108 | * The Systematic Software Engineering (SSE) EHR system in production in Aarhus County in Denmark. This is a significant system, built using its own reference model and archetype 'language'. It has an archetype editor, and all information in the system is archetyped. It was designed independently of the openEHR archetype approach; however, there have been discussions between people working on openEHR and SSE regarding potential use of ADL and other public specifications. openEHR is also likely to benefit from the experience gained by SSE and the system's users. |
| 132 | | * which archetypes are "chained" together in the composition |
| 133 | | * removes optional parts of archetypes not needed in the context of use |
| 134 | | * selects the language and terminologies to be used from among those available in the archetypes |
| 135 | | * further constrains existing constraints in the archetypes. |
| | 120 | * which archetypes are "chained" together in the composition |
| | 121 | * removes optional parts of archetypes not needed in the context of use |
| | 122 | * selects the language and terminologies to be used from among those available in the archetypes |
| | 123 | * further constrains existing constraints in the archetypes. |
| 152 | | * A new paper on archetypes - Archetypes: Constraint-based Domain Models for Future-proof Information Systems. Thomas Beale, 2002, prepared for OOPSLA 2002 - Haim Kilov's workshop on Behavioural Semantics ( PDF 171kb, 17pp) |
| 153 | | * The original paper - Archetypes - An Interoperable Knowledge Methodology for Future-proof Information Systems.Thomas Beale 2000. (PDF 700 kb, 80pp) |
| 154 | | * A paper comparing Archetypes and Templates: Templates and Archetypes: how do we know what we are talking about? Sam Heard et al. February 2003. (PDF 94KB) |
| 155 | | * A paper for standardisation: A Shared Archetype Language: A Position Paper for HL7, CEN TC 251, openEHR and other organisations. Thomas Beale, Sam Heard. Jan 2003 ( Word 155KB) |
| | 140 | * A new paper on archetypes - Archetypes: Constraint-based Domain Models for Future-proof Information Systems. Thomas Beale, 2002, prepared for OOPSLA 2002 - Haim Kilov's workshop on Behavioural Semantics ( PDF 171kb, 17pp) |
| | 141 | * The original paper - Archetypes - An Interoperable Knowledge Methodology for Future-proof Information Systems.Thomas Beale 2000. (PDF 700 kb, 80pp) |
| | 142 | * A paper comparing Archetypes and Templates: Templates and Archetypes: how do we know what we are talking about? Sam Heard et al. February 2003. (PDF 94KB) |
| | 143 | * A paper for standardisation: A Shared Archetype Language: A Position Paper for HL7, CEN TC 251, openEHR and other organisations. Thomas Beale, Sam Heard. Jan 2003 ( Word 155KB) |
