Salt Lake City 2015

Venue: 
CIMI Modeling Task Force
Meeting date: 
Monday, August 10, 2015 - 09:00 to Tuesday, August 11, 2015 - 17:00

Agenda

Monday August 10, 2015 - Technical meeting: Laying out a course for CIMI to write profiles/clinical models
Topic Speaker Slides
CIMI overview and CIMI plans for creating detailed HL7 FHIR profiles
  • CIMI mission and vision
  • CIMI Reference Model
  • Scope of CIMI models is all of medicine/health/healthcare
  • Current CIMI content
  • CIMI model repository
  • CIMI model browser
  • CIMI and isosemantic families of models
  • Models as files or as rows in tables (same approach as ASN.1 implementation)
  • Need for a CIMI terminology server
  • Process for approving preferred CIMI models, including HSPC preferences
  • CIMI becoming a Working Group in HL7
  • Relationship of CIMI to other interoperability initiatives
Stan Huff Slide
Options for different levels of interoperability Tom Oniki Slide
Operational details of how CIMI models are or could be translated to FHIR profiles
  • Use of CIMI models by HL7 FHIR implementers
  • Plans for CEML / CIMI / FHIR profiles
  • Profiles of high level resources (Patient, Practitioner) versus leaf level profiles (Blood Pressure, Heart Rate, Serum Sodium Level, White Count)
  • Grahame’s knowledge dictionaries: lab + vital signs + maybe conditions
  • Examples of how detailed CIMI models and FHIR profiles are developed from Patrick Langford’s spreadsheet
  • Mapping files + automatic or semi-automatic translations
    • Lab data – simple pattern fits many items – spreadsheets
      • Heart rate – model is specific to heart rate – different kind of spreadsheet?
  • The model translation strategy will be resource-dependent, e.g., Lab observations will have a different translation strategy than conditions
Stan Huff and Patrick Langford  
Mapping clinical models like CIMI or QWIK to instantiations like FHIR and CDA Harold Solbrig, Eric Prud’hommeaux, Claude Nanjo Slide
HL7 FHIR governance and policies for HL7 FHIR profiles`
  • Plans for unifying FHIR Resource profiles and FHIR Data Elements
  • Realm specific profiles
  • Domain specific profiles
  • Where should CIMI derived (HSPC approved) FHIR profiles reside?
Grahame Grieve Slide
Knowledge services for HL7 FHIR, CIMI, and HSPC
  • APIs for terminology services (FHIR Value Set resource on top of CTS2 services)
  • Model authoring support
  • Terminology binding in CIMI models
  • Terminology binding in FHIR profiles
Stan Huff - Facilitator  
Need for tools
  • Resource and profile “diff” tool
  • Tools for model translation from one form to another
  • Tools to transform instance data from one model to another
Stan Huff - Facilitator  
Near term planning, action items, next steps Stan Huff  
Tuesday August 11, 2015 - Creating Broad Clinical Consensus towards True Interoperability Summit
Topic Speaker Slides
Introduction, getting to “true” interoperability
  • Clinical expert input and review on content
  • Agreement of clinical groups about what is important to capture
Stan Huff Slide
Overview of CIMI, FHIR – Stan Huff
  • CIMI will become a working group in HL7
  • Work completed to date
  • Plans for future work

Description of clinical needs, requirements, and opportunities

  • Quality and disease specific repositories
  • Sharing of data for patient care
  • Sharing of clinical decision support and other applications
  • Patient engagement
Stan Huff and TBD  
General options for clinical engagement – Stan Huff
  • Clinical experts attend HL7 and are part of working groups or task forces
  • Modelers and standards experts that attend meetings of professional organizations
  • A Collaboration Framework
Stan Huff, Laura Heermann Slide
Current initiatives
  • Clinicians on FHIR
  • CIC vision and work plan
TBD Slide
One possible model review process Stan Huff, Tom Oniki  
Discussion
  • How do we make clinical reviews scalable and sustainable
  • How do we make clinical reviews “authoritative” / “complete” / “actionable” (without frequent debate and re-dos?)
  • How do we get reviews/models/profiles to an “accepted state”
  • What would require a change process to update or change?
  • How do we organize professional organizations to get involved? What constitutes “involvement”?
Stan Huff - Facilitator  
Formulate a plan - Stan
  • Organize our teams to get the plan rolling!
  • Near term planning, action items, next steps
Stan Huff - Facilitator  

Issues Not Addressed in day one agenda

Policies and issues related to IP Recent approval of Archetype Modeling Language (AML) as an OMG Standard – Harold Solbrig openEHR plans for generating FHIR profiles and for use of HL7 FHIR in services – Thomas Beale Conformance testing Discuss requirements for a clinical query language to be used with FHIR Details of the technical process of creating FHIR profiles from CIMI models – Patrick Langford

Location meeting:

Presentations and documents

10 documents available. Click on title for a preview and details.

Author: Russ Leftwich Document: File CIMI, FHIR Clinicians and Interoperability

Clinicians and Interoperability

Author: Grahame Grieve Document: File Presentation CIMI + FHIR

The place of Profiles, FHIR take on Fractal Models, FHIR Solutions, FHIR Conformance Resources, Profiles, Resources, Terminology/Knowledge/Structure

Author: Harold Solbrig Document: File CIMI / FHIR and Shape Expressions

Addressing Instances, semantics, syntax, proposal, "what is missing?", RDF data shapes.

Author: Stan Huff Document: File CIMI overview and CIMI plans

Laying out a course for CIMI to write HL7 FHIR profiles/clinical models

Author: Laura Heermann Document: Office presentation icon Collaboration Framework

Collaboration Framework

Author: Viet Nguyen Document: File HL7 Clinicians on FHIR

History, Lessons Learned, clinfhir.com Demo

Author: Tom Oniki Document: File HSPC Profiles: Conformance and Interoperability

Definitions “Resource-level” Profiles, “Detail-level” Profiles.

Author: Joshua Dees Document: File Interoperability, From the Patient’s Perspective

Setting a bit of Context, A Strange Moment of Clarity, Realizing the Complexity, Pushing for Engagement