Difference between revisions of "CIMI RM Patterns"

From CIMI
Jump to: navigation, search
Line 13: Line 13:
 
|  ||  Key concept + qualifiers + modifiers ||  Intermountain Healthcare CEMs[http://informatics.mayo.edu/sharp/index.php?title=File:CEReference20081114.pdf&limit=20] ||  Method of referencing terminology concept and adding context-specific information
 
|  ||  Key concept + qualifiers + modifiers ||  Intermountain Healthcare CEMs[http://informatics.mayo.edu/sharp/index.php?title=File:CEReference20081114.pdf&limit=20] ||  Method of referencing terminology concept and adding context-specific information
 
|-
 
|-
|  ||  data / state / qualifier || openEHR Entry pattern: spec[http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/ehr_im.pdf]; FAQ[http://www.openehr.org/wiki/display/resources/openEHR+ENTRY+Types+FAQs]; UML [http://www.openehr.org/wiki/download/attachments/196630/openehr_entry_uml.jpg?version=1&modificationDate=1193397393000] <br/>DCM2010 ISO13972 ||  In observation data, separate out data, patient state and qualifiers  
+
|  ||  data / state / qualifier || openEHR: Entry classes spec[http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/ehr_im.pdf]; FAQ[http://www.openehr.org/wiki/display/resources/openEHR+ENTRY+Types+FAQs]; UML [http://www.openehr.org/uml/release-1.0.1/Browsable/_9_0_76d0249_1109249648736_872559_12384Report.html] <br/>DCM2010 ISO13972 ||  In observation data, separate out data, patient state and qualifiers  
 
|-
 
|-
 
| Structure ||  ||  ||  
 
| Structure ||  ||  ||  
 
|-
 
|-
|  ||  Tree structure ||  Generalised free-form tree for containing clusters of data items, e.g. the 5+1 Apgar items, numerous microbiology result items, etc. ||  openEHR RM, 13606 RM, HL7 (all)
+
|  ||  Tree structure || openEHR: spec[http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/data_structures_im.pdf]; UML[http://www.openehr.org/uml/release-1.0.1/Browsable/_9_0_76d0249_1109581075362_259917_1445Report.html], [http://www.openehr.org/uml/release-1.0.1/Browsable/_9_0_76d0249_1109346709572_859750_3810Report.html] <br/> 13606 RM<br/> 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 ||  ||  ||  
 
| Actors ||  ||  ||  
 
|-
 
|-
|  || Participation ||  A pattern defining the connection between parties (people, organisations, devices) and other information. ||  HL7 (all), openEHR, 13606
+
|  || Participation ||  HL7; <br/>openEHR: spec[http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/common_im.pdf]; UML[http://www.openehr.org/uml/release-1.0.1/Browsable/_9_5_1_76d0249_1140169202660_257304_813Report.html] <br/> ISO 13606  || A pattern defining the connection between parties (people, organisations, devices) and other information.
 
|-
 
|-
 
|  ||  Party + role + accountability ||  A pattern defining relationships between parties, including those that are roles played by some underlying actor. ||  HL7 RIM, openEHR
 
|  ||  Party + role + accountability ||  A pattern defining relationships between parties, including those that are roles played by some underlying actor. ||  HL7 RIM, openEHR
Line 27: Line 27:
 
| Clinical process ||  ||  ||   
 
| Clinical process ||  ||  ||   
 
|-
 
|-
|  ||  History of events ||  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; used in Observation type ||  openEHR RM
+
|  ||  History of events || openEHR: spec[http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/data_structures_im.pdf]; UML[http://www.openehr.org/uml/release-1.0.1/Browsable/_9_0_76d0249_1109157527311_729550_7234Report.html]  ||  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 ||  Distinguish key Entry types based on clinical / scientific problem solving process, including Observation, Evaluation, Instruction (order), Action, Admin entry, Generic (any content) entry ||  CIR
+
|  ||  Entry / clinical statement types || openEHR ontology[[media:MedInfo2007-BealeHeard.pdf‎|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
 
|-
 
|-
|  ||  Observation: (Classifiers?) data / state / protocol (/reasoning) ||  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) ||  openEHR RM
+
|  ||  Entry: data / state / protocol (/reasoning) ||  openEHR: Entry classes spec[http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/rm/ehr_im.pdf]; FAQ[http://www.openehr.org/wiki/display/resources/openEHR+ENTRY+Types+FAQs]; UML [http://www.openehr.org/uml/release-1.0.1/Browsable/_9_0_76d0249_1109249648736_872559_12384Report.html] || 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 ||  ||  ||  
 
| Workflow ||  ||  ||  

Revision as of 09:58, 30 July 2012

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 DTs[1];
ISO 21090 Data Types;
HL7 FHIR[2]
Generalised data types for key atomic data representation, including text, coded text, quantity, dates & times, etc
Key concept + qualifiers + modifiers Intermountain Healthcare CEMs[3] Method of referencing terminology concept and adding context-specific information
data / state / qualifier openEHR: Entry classes spec[4]; FAQ[5]; UML [6]
DCM2010 ISO13972
In observation data, separate out data, patient state and qualifiers
Structure
Tree structure openEHR: spec[7]; UML[8], [9]
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[10]; UML[11]
ISO 13606
A pattern defining the connection between parties (people, organisations, devices) and other information.
Party + role + accountability A pattern defining relationships between parties, including those that are roles played by some underlying actor. HL7 RIM, openEHR
Clinical process
History of events openEHR: spec[12]; UML[13] 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 ontologyBeale 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[14]; FAQ[15]; UML [16] 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 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 openEHR RM, HL7 RIM
Clinical process event links A pattern for representing temporal links between related events in a clinical process HL7 RIM Act Rel, openEHR / 13606 LINKs
EHR
Composition / document 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. openEHR, 13606, CDA