In the field of informatics, an archetype is a formal re-usable model of a domain concept. Traditionally, the term archetype is used in psychology to mean an idealized model of a person, personality or behaviour (see Archetype). The usage of the term in informatics is derived from this traditional meaning, but applied to domain modelling instead.
An archetype is defined by the OpenEHR Foundation (for health informatics) as follows:[1]
- An archetype is a computable expression of a domain content model in the form of structured constraint statements, based on some reference model. openEHR archetypes are based on the openEHR reference model. Archetypes are all expressed in the same formalism. In general, they are defined for wide re-use, however, they can be specialized to include local particularities. They can accommodate any number of natural languages and terminologies.
The use of archetypes in health informatics was first documented by Thomas Beale, who stated the concept was coined by Derek Renouf. According to Beale, Renouf applied archetypes to configuring Smalltalk systems.[2]
See also
- EHRcom
- European Institute for Health Records
- Good European Health Record
- HISA
- Information science
- OpenEHR
References
- ^ S Heard & T Beale (eds) (2005-03-14). "Archetype Principles". http://svn.openehr.org/specification/TRUNK/publishing/architecture/am/archetype_principles.pdf. Retrieved 2006-05-18.
- ^ Thomas Beale (2001-08-21). "Archetypes: Constraint-based Domain Models for Futureproof Information Systems". http://www.deepthought.com.au/it/archetypes/archetypes.pdf.
 |
This computer science article is a stub. You can help Wikipedia by expanding it. |
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)
