What is an archetype?
An archetype is a re-usable, formal definition of domain level information. The formal concept was originally described in detail in a paperby Thomas Beale. The key feature of the archetype approach to computing is a complete separation of information models (such as object models of software, models of database schemas) from domain models. Thus, archetypes are not part of the software or database of a system. A short document on archetype principles is here(90k PDF). Technical specifications: ADL 1.4; ADL 1.5 draft.
Archetypes have a number of key purposes:
- they allow domain experts such as clinicians to create the definitions which will define the data structuring in their information systems
- they provide runtime validation of data input via GUI or any batch process
- they provide a basis for intelligent querying of data.
In health, information, or 'content' that can be modelled using archetypes includes things like:
- Observations: weight measurement, blood pressure, microbiology results
- Reports: discharge referral
- Orders: prescription
- Assessments: diagnosis
and many others. From the user's point of view, these are the kinds of data which occur in health information systems. Each archetype is a text file, expressed in either ADL syntax or its XML derivative.