Health informatics - Detailed clinical models, characteristics and processes
Introduction: In current healthcare information technology, there is an identified need for clinical information recorded by one professional or in one information system and transferred electronically to another professional or information system to retain enough of its intended and precise meaning to be safe and useful [HL7, ISO 13606, EC Recommendation COM (2008) 3282 final]. In particular, clinical safety requires that the receiving system and user of all data elements contributing to clinical knowledge makes the exact same interpretation of their meaning as applied in the source system. Semantic interoperability enables actors in a clinical process to cooperate by ensuring they share a common understanding of information and activities pertinent to the clinical process. When actors in a clinical process use a combined system containing two (or more) information systems, semantic interoperability occurs as an emergent (whole system) characteristic of those data exchanges that constitute meaningful communications between actors using different information systems. As is typical for engineering properties of systems, semantic interoperability is not absolute. It enables sufficiently unambiguous understanding of stored, used, and communicated data so that patients, health care professionals, and others including automated systems can interpret and act upon data in health care information systems (health IT systems) consistently and accurately. Semantic interoperability is defined as “ensu
Scope: This Technical Specification: — Describes requirements and recommended methods against which clinicians can gather, analyse and, specify the clinical context, content, and structure of Detailed Clinical Models. — Defines Detailed Clinical Models (DCMs) in terms of an underlying logical model. They are logical models of clinical concepts and can be used to define and to structure clinical information. — Describes requirements and principles for DCMs, meta-data, versioning, content and context specification, data element specification and data element relationships, and provide guidance and examples. — Specifies DCM governance principles to ensure conceptual integrity of all DCM attributes and logical model accuracy. — Describes DCM development and the methodology principles for use that will support the production of quality DCMs to minimize risk and ensure patient safety. This Technical Specification is not applicable to: — Details of the content of instances of Detailed Clinical Models. e.g. This Technical Specification will not specify the concrete data elements for the Glasgow Coma Scale, body height, and such (apart from some examples to explain the clauses). It will however give guidance on how to properly specify the clinical knowledge of Glasgow Coma Scale or body height, how to correctly identify, name and model the data elements for these clinical concepts, and how to give unique codes to each data element and, where possible, value set. In other words, it will explain the how to create instances, but not offer the instances themselves. — Specifications of dynamic modelling, for example workflow. — Specifications for modelling entire domains or aggregates of many Detailed Clinical Models such as complete assessment documents or discharge summaries. It will not specify DCM compositions. 2 Terms and definition For the purposes of this document, the following terms and definitions apply. 2.1 archetype model of a clinical or other domain-specific concept which defines the structure and business rules of the concept [SOURCE: ISO/TR 20514:2005] 2.2 archetype model information model of the metadata to represent the domain-specific characteristics of Electronic