Changes between Version 13 and Version 14 of Archetype FAQ
- Timestamp:
- Jul 26, 2007, 7:32:58 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Archetype FAQ
v13 v14 87 87 Not at all. Archetypes are designed to provide systematic interface with terminologies. They are, in themselves, terminology-neutral, because there is no (and probably will never be) single terminology or ontology which describes the whole of medicine in the myriad points of view needed in clinical information systems. For a discussion of the problems with terminology, see the ADL specification (section: The Problem of Terminology). ADL is designed to have bindings to terminologies, and any given archetype can include bindings to more than one. A binding is the set of mappings from archetype local term and constraint codes to terminology codes and query expressions respectively. See this archetype for an example (scroll to the ontology section). 88 88 89 == What is the difference between archetypes and ontologies? == 89 == アーキタイプとオントロジーの違いは何？ == 90 91 What is the difference between archetypes and ontologies? 92 93 90 94 91 95 An easy way to think about archetypes and ontologies is based on undertanding what they say. Archetypes model information, while ontologies model reality. For example an archetype for "systemic arterial blood pressure measurement" is a model of what information should be captured for this kind of measurement - usually systolic and diastolic pressure, plus (optionally) patient state (position, exersion level) and instrument or other protocol information. In contrast, an ontology would describe in more or less detail what blood pressure is. This archetype tutorial (PPT) provides a detailed example on slide 12.
