Difference between revisions of "Clinical Information Modeling Initiative Work Group"
MulrooneyG (talk | contribs) |
|||
| Line 2: | Line 2: | ||
== Agendas == | == Agendas == | ||
| + | * [[CIMI_WGM_Agenda_May_2017| May 2017 Madrid]] | ||
| + | |||
* [[CIMI_WGM_Agenda_January_2017| January 2017 San Antonio]] | * [[CIMI_WGM_Agenda_January_2017| January 2017 San Antonio]] | ||
Revision as of 21:43, 19 January 2017
Welcome to the wiki of the Clinical Information Modeling Initiative (CIMI) Work Group.
Contents
Agendas
Minutes
- 2016-10-26 CIMI Approved Strategy for Assertions
- 2016-10-20 CIMI Agenda and Minutes
- File:2016-07-07 CIMI Agenda and Minutes.docx
- File:2016-06-30 CIMI Agenda and Minutes.docx
- 2016-06-30 CIMI Agenda and Minutes
- 2016-06-16 CIMI Agenda and Minutes
- 2016-05-19 CIMI Agenda and Minutes
- 2016-02-25 CIMI Agenda and Minutes
...
Mission
Improve the interoperability of healthcare systems through shared implementable clinical information models
Strategic Goal
- Be able to share data, applications, reports, alerts, protocols, and decision support modules with anyone in the WORLD
- To have “plug-n-play” interoperability
Deliverables
- Shared repository of detailed clinical information models
- One single formalism (two modelling styles)
- A common set of base data types
- Formal bindings of the models to standard coded terminologies
- Open Repository and models that are free for use at no cost
- Models that support multiple contexts
Target domains
- EHR data storage
- Message and service payloads
- Decision logic (queries of EHR data)
- Clinical trials data (clinical research)
- Quality measures
- Normalization of data for secondary use
- Creation of structured data entry screens
- Capture of coding output from NLP
CIMI Practitioners Guide to HIE Interoperability
The HL7 CIMI WG is developing this ‘Guide’ and a Computer Aided Design (CAD) ‘Tool’ for analysts, architects and implementers; where, ‘The Guide and Tool’ are about CIMI models and their effective-and-efficient use in specifying and implementing interoperable Health Information Exchange (HIE) solutions. The ‘Guide’ also documents the Jan-Sep 2016 CIMI sponsored Investigative Study of a CIMI compliant Federal Health Information Model (FHIM) profile; where, FHIM defines healthcare domains and high-level information-exchange classes (aka entities) in those domains; and where, FHIM classes are the context for CIMI Clinical-Model Patterns constrained into CIMI Detailed Clinical Models (DCMs). Model Driven Health Tool and Model Driven Message Interface (MDHT-MDMI) tooling can transform DCMs into Implementation Guides (IGs). The CIMI compliant FHIM profile and DCMs are collectively referred to and will be balloted as the CIMI curated “HL7 Common Logical Information Model (CLIM)”. This work is being done in collaboration with The Open Group Healthcare Forum.
- The "CIMI Practitioners Guide to HIE Interoperability" is a living document; where, the current version is at:
Tooling
The following is a list of tools that might be pertinent to investigate as we develop CIMI tooling:
- Terminology Browsers
- Value Set Editors
- CIMI Model Authoring Tool
- ADL 2.0 web based archetype and template editors
- Results 4 Care tool for online authoring of clinical content for Detailed Clinical Models
- Results 4 Care UML template and Model creation / validation tool for Detailed Clinical Models
- [Spanish ADL Authoring Tool from Spain (Gerard Freriks to provide info)]
- FHIR Profile Editors
- CIMI to FHIR Profile Conversion
- CIMI (mini)RM UML
- Sparx Enterprise Architect Project 3.0.5 EAP
- BMM Extension
Models
- Models managed in Git version control repository: GitHub
- Models published in a web browser, processed by ADL workbench and available as ADL, XML, JSON, graphical tree, etc.: ClinicalElement
- Browser pubs periodically refreshed from Git & may be out of synch
- Reference model requirements
