Revision as of 12:53, 12 January 2012 by Admin (Talk | contribs) (Created page with "has_type:string")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Pages using the property "Definition"

Showing 25 pages using this property.

(previous 25) (next 25)


Archetype +A re-usable, formal model of a concept expressed as a computable set of constraint statements, on an underlying reference model (URM).
Archetype Definition Language +ADL is a formal language for expressing ar ADL is a formal language for expressing archetypes. It provides a formal, textual syntax for describing constraints on any domain entity whose data is described by an information model (also known as the 'underlying reference model'). The ADL syntax is semantically equivalent to the AOM, and represents one possible serialisation of the AOM. The current version of ADL is known as 'ADL 1.5'. rent version of ADL is known as 'ADL 1.5'.
Archetype Instance +A single instantiation of data conforming to a specific archetype.
Archetype Object Model +The AOM is the definitive expression of ar The AOM is the definitive expression of archetype semantics, and is independent of any particular syntax. The AOM is defined as an object model, using a UML class diagram. It is a generic model, meaning that it can be used to express archetypes for any reference model in a standard way. Version 1.4 of the AOM was standardised in ISO-13606:2. The current version is known as 'AOM 1.5'. The current version is known as 'AOM 1.5'.
Archetype Query Language +A declarative query language developed specifically for expressing queries used for searching and retrieving the clinical data found in archetype-based EHRs


CIMI Reference Model +The information model on which CIMI's clin The information model on which CIMI's clinical models (i.e. archetypes) are defined. Usage Notes: This reference model defines a rigorous and stable set of modelling patterns, including a set of complex data types and structural patterns (e.g. composition, entry). All CIMI clinical models will be defined by constraining the CIMI reference model. by constraining the CIMI reference model.
Cardinality Constraint +A limit on the number of instances of an element that can exist in a given relationship in a model examples: '0..1', '1..Many'
Class +A class describes a set of objects that share the same specifications of features, constraints, and semantics.
Class Diagram +A UML class diagram is a structure diagram that depicts packages, classes and objects, their relationships, constraints attributes and operations.
Classification +An exhaustive set of mutually exclusive categories to aggregate data at a prescribed level of granularity for a specific purpose.
Clinical Data Repository +A data store that holds and manages clinical data collected from service encounters at the point-of-service locations
Clinical Document Architecture +The HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure and semantics of clinical documents for exchange.
Clinical Information Model +A representation of the structured clinical information (including relationships, constraints and terminology), that describes a specific clinical concept - e.g. a blood pressure observation, a Discharge Summary, or a Medication Order.
Clinical Information Modelling Initiative +An initiative established to improve the interoperability of healthcare information systems through shared implementable clinical information models
Clinical Information Modelling Initiative Specification +CIMI specifications are those specifications adopted or published by the CIMI, including the CIMI reference model, the CIMI constraint formalism, and the CIMI data types.
Clinical Model Governance +A set of policies and processes to safeguard and maintain the quality of clinical artifacts during identification, scoping, creation, storage, verification, maintenance, and distribution
Clinical Model Repository +A data store that holds clinical information models, and associated artifacts, in an agreed sharable format.
Clinical Model Verification +The act of reviewing, inspecting or testing, in order to establish that a specification meets appropriate clinical safety and quality standards.
Clinical Modelling Language +A language used to define clinical information models. Examples include: * Archetype Definition Language (ADL) * Unified Modelling Language (UML) * Ontology Web Language (OWL)
Clinical Requirement +Requirements that articulate clinical needs - including clinical practices, standards, guidelines, principles or other clinical concepts.
Code System +A managed collection of uniquely identifiable concepts with associated representations.
Common Terminology Services 2.0 +CTS2 is a specification that provides a st CTS2 is a specification that provides a standard interface to disparate terminology sources. The Information Model specifies the structural definition, attributes and associations of Resources common to structured terminologies such as Code Systems, Binding Domains and Value Sets. The Computational Model specifies the service descriptions and interfaces needed to access and maintain structured terminologies. ess and maintain structured terminologies.
Concept +An idea, independent of but usually associated with a textual or other representation
Conceptual Information Model +A representation of real-world objects and their relationships and constraints as understood by domain experts, without implementation-specific details
Constraint Model +A formal specification used for describing A formal specification used for describing constraints on an Underlying Reference Model. The Constraint Model is used to express clinical information models (i.e. archetypes). Not to be confused with the clinical information models that are instances of the constraint model. hat are instances of the constraint model.
(previous 25) (next 25)