CIMI RM Patterns

From CIMI
Revision as of 10:16, 30 July 2012 by Thomas Beale (Talk | contribs)

Jump to: navigation, search

This page is for recording notes about CIMI RM patterns. The original 'Technical Architecture' page containing early discussions is here, including an original table of RM patterns.

A version of this table is shown below.


CATEGORY PATTERN ORIGINAL DESCRIPTION(S) CIMI DESCRIPTION
Primitives
Data types openEHR: spec[1]; UML[2]
ISO 21090 Data Types
HL7 FHIR[3]
Generalised data types for key atomic data representation, including text, coded text, quantity, dates & times, etc
Key concept + qualifiers + modifiers Inter-mountain Healthcare CEMs[4] Method of referencing terminology concept and adding context-specific information
Structure
Tree structure openEHR: spec[5]; UML[6], [7]
ISO 13606: RM
HL7: RIM
Generalised free-form tree for containing clusters of data items, e.g. the 5+1 Apgar items, numerous microbiology result items, etc.
Actors
Participation HL7:
openEHR: spec[8]; UML[9]
ISO 13606
A pattern defining the connection between parties (people, organisations, devices) and other information.
Party + role + accountability HL7: RIM
openEHR demographics: spec[]; UML[10]
A pattern defining relationships between parties, including those that are roles played by some underlying actor.
Clinical process
History of events openEHR: spec[11]; UML[12] A structure containing 1..* Events, allowing data and patient state at each one, supporting intervals, point events, and math functions, e.g. ave/delta/max/min
Entry / clinical statement types openEHR: Beale Heard 2007 Medinfo paper Distinguish key Entry types based on clinical / scientific problem solving process, including Observation, Evaluation, Instruction (order), Action, Admin entry, Generic (any content) entry
Entry: data / state / protocol (/reasoning) openEHR: Entry classes spec[13]; FAQ[14]; UML [15] In observation data, separate out data (actual datum being recorded e.g. BP) from patient state (e.g. lying, standing) and protocol (cuff type, instrument type)
Workflow
Order state machine + careflow mapping openEHR:
HL7: RIM
A way of recording current state in progression through a standard state machine applying to any ‘order’, and mapping any specific careflow step to a standard state machine transition, enabling standardised querying
Clinical process event links HL7: RIM Act Relationship
openEHR: LINK class spec[16]; UML[17]
A pattern for representing temporal links between related events in a clinical process
EHR
Composition / document openEHR: spec[18]; UML[19]
ISO 13606:
HL7 CDA:
An aggregation concept acting as a ‘bucket’ for information recorded by a professional at a given time for a given subject of care, supporting audit & context meta-data.