Archetype (information science)

Last updated

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.

Contents

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.

Formal specifications

The modern archetype formalism is specified and maintained by the openEHR Foundation, [oe 1] and although originally developed for the health IT domain, is completely domain-independent, and has been used in geospatial modelling, telecommunications, and defence.

The archetype formalism consists of a number of specifications [oe 2] including:

The Archetype Technology Overview [oe 3] provides a short technical overview of the archetype formalism useful for new users.

The ADL/AOM 1.4 specifications [oe 4] [oe 5] were provided to ISO TC 215 in 2008 by the openEHR Foundation and became the ISO 13606-2 standard, [2] extant until 2019. ISO TC 215 accepted the AOM 2 specification [oe 6] as the basis for a revision of this standard, which was issued in 2019. [3]

In late 2015, the Object Management Group (OMG) accepted an RfP entitled 'Archetype Modeling Language (AML)' as a new candidate standard. [4] This specification is a form of ADL re-engineered as a UML profile so as to enable archetype modelling to be supported within UML tools.

Tools

A number of tools area available for working with archetypes. Most are listed on the openEHR modelling tools page. [oe 7] They include:

See also

Related Research Articles

The XML Metadata Interchange (XMI) is an Object Management Group (OMG) standard for exchanging metadata information via Extensible Markup Language (XML).

A modeling language is any artificial language that can be used to express data, information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure Programing language.

Health Level Seven or HL7 is a range of global standards for the transfer of clinical and administrative health data between applications. The HL7 standards focus on the application layer, which is "layer 7" in the Open Systems Interconnection model. The standards are produced by Health Level Seven International, an international standards organization, and are adopted by other standards issuing bodies such as American National Standards Institute and International Organization for Standardization. There are a range of primary standards that are commonly used across the industry, as well as secondary standards which are less frequently adopted.

The Object Constraint Language (OCL) is a declarative language describing rules applying to Unified Modeling Language (UML) models developed at IBM and is now part of the UML standard. Initially, OCL was merely a formal specification language extension for UML. OCL may now be used with any Meta-Object Facility (MOF) Object Management Group (OMG) meta-model, including UML. The Object Constraint Language is a precise text language that provides constraint and object query expressions on any MOF model or meta-model that cannot otherwise be expressed by diagrammatic notation. OCL is a key component of the new OMG standard recommendation for transforming models, the Queries/Views/Transformations (QVT) specification.

A stereotype is one of three types of extensibility mechanisms in the Unified Modeling Language (UML), the other two being tags and constraints. They allow designers to extend the vocabulary of UML in order to create new model elements, derived from existing ones, but that have specific properties that are suitable for a particular domain or otherwise specialized usage. The nomenclature is derived from the original meaning of stereotype, used in printing. For example, when modeling a network you might need to have symbols for representing routers and hubs. By using stereotyped nodes you can make these things appear as primitive building blocks.

Architecture description languages (ADLs) are used in several disciplines: system engineering, software engineering, and enterprise modelling and engineering.

<span class="mw-page-title-main">Information model</span>

An information model in software engineering is a representation of concepts and the relationships, constraints, rules, and operations to specify data semantics for a chosen domain of discourse. Typically it specifies relations between kinds of things, but may also include relations with individual things. It can provide sharable, stable, and organized structure of information requirements or knowledge for the domain context.

openEHR is an open standard specification in health informatics that describes the management and storage, retrieval and exchange of health data in electronic health records (EHRs). In openEHR, all health data for a person is stored in a "one lifetime", vendor-independent, person-centred EHR. The openEHR specifications include an EHR Extract specification but are otherwise not primarily concerned with the exchange of data between EHR-systems as this is the focus of other standards such as EN 13606 and HL7.

Classification Markup Language (ClaML) is an XML data format specification meant for the exchange of medical classifications, which are code numbers for of medical diagnoses and procedures.

Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem. Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing concepts.

<span class="mw-page-title-main">Systems modeling language</span> General-purpose modeling language

The systems modeling language (SysML) is a general-purpose modeling language for systems engineering applications. It supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems.

<span class="mw-page-title-main">RM-ODP</span> Reference model in computer science

Reference Model of Open Distributed Processing (RM-ODP) is a reference model in computer science, which provides a co-ordinating framework for the standardization of open distributed processing (ODP). It supports distribution, interworking, platform and technology independence, and portability, together with an enterprise architecture framework for the specification of ODP systems.

The European Committee for Standardization (CEN) Standard Architecture for Healthcare Information Systems, Health Informatics Service Architecture or HISA is a standard that provides guidance on the development of modular open information technology (IT) systems in the healthcare sector. Broadly, architecture standards outline frameworks which can be used in the development of consistent, coherent applications, databases and workstations. This is done through the definition of hardware and software construction requirements and outlining of protocols for communications. The HISA standard provides a formal standard for a service-oriented architecture (SOA), specific for the requirements of health services, based on the principles of Open Distributed Processing. The HISA standard evolved from previous work on healthcare information systems architecture commenced by Reseau d’Information et de Communication Hospitalier Europeen (RICHE) in 1989, and subsequently built upon by a number of organizations across Europe.

The Health informatics - Electronic Health Record Communication was the European Standard for an information architecture to communicate Electronic Health Records (EHR) of a patient. The standard was later adopted as ISO 13606 and later replaced with ISO 13606-2 and recently ISO 13606-5:2010.

The ISO/TC 215 is the International Organization for Standardization's (ISO) Technical Committee (TC) on health informatics. TC 215 works on the standardization of Health Information and Communications Technology (ICT), to allow for compatibility and interoperability between independent systems.

The system of concepts to support continuity of care, often referred to as ContSys, is an ISO and CEN standard . Continuity of care is an organisational principle that represents an important aspect of quality and safety in health care. Semantic interoperability is a basic requirement for continuity of care. Concepts that are needed for these purposes must represent both the content and context of the health care services.

Health Level Seven International (HL7) is a non-profit ANSI-accredited standards development organization that develops standards that provide for global health data interoperability.

<span class="mw-page-title-main">Enterprise Architect (software)</span> Visual modeling and design tool

Sparx Systems Enterprise Architect is a visual modeling and design tool based on the OMG UML. The platform supports: the design and construction of software systems; modeling business processes; and modeling industry based domains. It is used by businesses and organizations to not only model the architecture of their systems, but to process the implementation of these models across the full application development life-cycle.

<span class="mw-page-title-main">Dipak Kalra</span>

Dipak Kalra is President of the European Institute for Health Records and of the European Institute for Innovation through Health Data. He undertakes international research and standards development, and advises on adoption strategies, relating to Electronic Health Records.

Clinical data standards are used to store and communicate information related to healthcare so that its meaning is unambiguous. They are used in clinical practice, in activity analysis and finding, and in research and development.

References

  1. ↑ S. Heard & T. Beale. (eds.) (2005). "Archetype definitions and principles" (PDF). openEHR. Retrieved 22 May 2013.{{cite web}}: |author= has generic name (help)
  2. ↑ "ISO 13606-2:2008 Health informatics -- Electronic health record communication -- Part 2: Archetype interchange specification". ISO TC 215. Retrieved 23 May 2016.
  3. ↑ "ISO 13606-2:2019 Health informatics — Electronic health record communication — Part 2: Archetype interchange specification". ISO TC 215. Retrieved 30 Nov 2019.
  4. ↑ "Archetype Modeling Language™ (AML™)". Object Management Group.
  5. ↑ "LinkEHR". Veratech for Health. Retrieved 24 Aug 2023.

References (openEHR)

  1. ↑ "openEHR website". openEHR Foundation.
  2. ↑ "openEHR Archetype specifications". openEHR.org. openEHR Foundation. Retrieved 30 Nov 2019.
  3. ↑ "Archetype Technology Overview". openEHR.org. openEHR Foundation. Retrieved 30 Nov 2019.
  4. ↑ "Archetype Definition Language 1.4 specification". openEHR Foundation. Retrieved 23 May 2016.
  5. ↑ "Archetype Object Model (AOM) 1.4". openEHR Foundation. Retrieved 23 May 2016.
  6. ↑ "Archetype Object Model 2 (AOM2) Specification". openEHR Foundation. Retrieved 30 Nov 2019.
  7. ↑ "Archetype modelling tools". openEHR Foundation. Retrieved 23 May 2016.
  8. ↑ "ADL Designer". openEHR ADL Designer team.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.