This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

CIMI Telecom Minutes 2017-02-09

From HL7Wiki
Jump to navigation Jump to search
<<< Approved on 2017-02-16 >>>
  • 2017 Minutes: http://wiki.hl7.org/index.php?title=CIMI_Minutes
  • Screen Sharing & Telecom Information: IHTSDO has generously provided a GoToMeeting connection for CIMI use.
    • https://global.gotomeeting.com/join/754419973 Dialin: United States : +1 (224) 501-3316 Access Code: 754-419-973
    • More phone numbers: Australia: +61 2 8355 1034, Belgium: +32 (0) 28 93 7002, Canada: +1 (647) 497-9372, Denmark: +45 89 88 03 61, Netherlands: +31 (0) 208 084 055, New Zealand: +64 4 974 7243, Spain: +34 932 20 0506, Sweden: +46 (0) 853 527 818, United Kingdom: +44 (0) 330 221 0098
    • Telecom Audio: https://1drv.ms/u/s!AlkpZJej6nh_lIN6SipbDkxhJW-rUA
    • Telecom Video: TBD (Joey Coyle or Patrick Langford)
  • Co-Chairs: Stan Huff, Linda Bird, Galen Mulrooney, Richard Esmond; where, quorum requires 2 co-chairs
  • REQUESTED ACTION: Directly edit this WIKI page or send your feedback to CIMI@lists.HL7.org with your comments, questions, suggested updates.


Attendees

Linda Bird, Bruce Bray, Linda Buhl, Joey Coyle, Gary Dickinson, John Donally, Richard Esmond, Bret Heale, Stan Huff, Steve Hufnagel, Mark Kramer, Patrick Langford, Jay Lyle, Chris Macintosh, Susan Matney, Chris Melo, Galen Mulrooney, Claude Nanjo, Brian Pech Craig Parker, Serafina Versaggi.

Highlighted names were in attendance.

Executive Summary

  1. Simplifying CIMI communications with BMM Mind Maps [Steve]
  2. Adding a "Base Assertion Class" [Claude]
  3. Inherent difference between CSMs and DCMs [Joey]
  4. Skin Wound DCM Requirements [Jay, Susan], Friday, Patient Care workgroup telecom.
  5. 2017-02-09 Action-01 (CIMI WG): What should be the distinction between CIMI Practitioner Guide vs CIMI Style Guide
    1. CIMI Practitioner Guide is at: http://wiki.hl7.org/index.php?title=CIMI_Practitioners%27_Guide where, it is
      1. holistically re-organized weekly, based on working draft information for verification-and-validation by stakeholders
      2. focused on communicating with clinicians, program and business analysts, venders and implementers; where,
        1. it explains and simplifies proposed UML model changes
        2. uses mind maps to augment the UML for non-modeler stakeholders
        3. provides source material, which may be used in the CIMI Style Guide
    2. CIMI Style Guide is at: https://1drv.ms/b/s!AlkpZJej6nh_k_k0S35x3xeCNfvPng where it is:
      1. governed, configuration managed and peer-reviewed by the HL7 ballot process.
      2. typically updated on an annual or bi-annual basis as an HL7 informative-standard.
      3. targeted to meet the needs of modelers, informaticists and implementers.
  6. 2017-02-09 Action-02 (Steve): Transition Mayo 2010-2015 CIMI-WIMI content to HL7 CIMI-WIKI.
  7. 2017-02-09 Action-03 (Galen): Submit Notification of Intent to Ballot Form

Minutes (Annotated Agenda)

  • Scribe: Stan.Huff@imail.org
  • REQUESTED ACTION: Update wiki directly or send suggested changes to Scribe or cimi@lists.hl7.org
  • Bolded Items were discussed/annotated to the agenda


  • Record this call
  • Agenda review
  • Review/Approval of Jan 26 minutes and Action Items
  • Updates on active projects (standing item)
    • Skin and wound assessments – Jay and Susan
      • Finalizing the data items, value sets
    • FHIM – CIMI integration – Galen
    • Harmonization of CIMI and FHIR datatypes - Richard
    • Graph/STAMP modeling paradigm – Richard
    • Conversion of CIMI archetypes to FHIR logical models to FHIR profiles – Claude
    • BMM parsing and serialization code – Claude
    • Creating ADL models from CEMs – Joey
    • LOKI – Patrick
    • Conclusions from the CIMI FHIM Task Force – Stan Huff
      • Stan will update the document based on previous discussion, and bring the document back for review and approval in a few weeks (still not done)
  • Review plans for May ballot
    • Status of the submission of the Notification of Intent to Ballot Form - Galen
    • Work plan
      • 3/26 pub date
      • 3/1 full content draft
      • 3/10 content done
      • 3/14 docs done: to Patrick for editing
    • Ballot content (top priorities)
      • Modeling content [Claude, Galen]
        • Claude and Galen will meet and make a prioritized list and figure out how far they can reach down the list
          • Claude and Galen did not get a chance to meet
          • Will try to meet soon
        • Skin and wound assessments – plans are in place
        • Quality measure – Jay and Claude to meet tomorrow, then reach out to Ken Kawamoto and Floyd Eisenberg
        • Skin and wound assessment quality measure use case
      • Documentation [Patrick, Editor]
        • Documents created and edited on Google Docs, and then published to the wiki
        • Overview/marketing pitch [Stan, Jay, Claude, Steve, Nona, Ask Laura]
        • Updated and fleshed out style guide [Susan, Jay, Steve]
        • Architecture guide [Claude]
          • Holding off until the architecture is more stable, then he will do a new version that incorporates all of the changes
        • Refine CIMI Process Definition for CIC #3 [Steve, Claude, Jay, Galen]
        • (Help to create documentation) Tool that reads a model and generates wiki pages (a document generation tool) [Michael van der Zel, Claude]
        • Tool that takes the BMM patterns and produces FHIR profiles [Richard, Michael van der Zel]
        • Ken Lord MDMI tool – Steve and Richard to follow up
  • Wiki and website issues
    • Mayo wiki  HL7 wiki migration
    • Status of www.opencimi.org website
      • Who manages the website? How can content be updated, Should we use or link to the HL7 website?
        • Porta Vita has voluntarily maintained the opencimi website for us
        • We own the opencimi DNS, Joey can make subdomains as needed, and people can control their own subdomains
        • It would be helpful to post “work in progress” models where they are visible.
        • Claude will work with Patrick to see if we could add new content to the current CIMI Browser.
    • Look, feel and content of restructured HL7 Wiki
  • Mindmaps from Steve Hufnagel
    • We will consider how these or other representations might be used in the ballot material to make the model as understandable as possible.
  • Posting models to opencimi.org
  • Additional changes to the model – Claude
  • Review of updated assertion/evaluation table content - Stan
  • Future topics
    • Loading of concepts into SOLOR – Susan Matney
    • Review CIMI Observation Result pattern - Stan
    • How will CIMI coordinate with DAF? - Claude
    • Granularity of models (schematic anchors) – from Richard
    • We need a way to identify the focal concept in indivisible and group statements
      • We would probably use the new metadata element
    • New principle: Don’t include static knowledge such as terminology classifications in the model: class of drug, invasiveness of procedure, etc.
    • Proposed policy that clusters are created in their own file – Joey, Stan
    • The role of openEHR-like templating in CIMI’s processes - Stan
    • IHTSDO work for binding SNOMED CT to FHIR resources – Linda, Harold
    • Which openEHR archetypes should we consider converting to CIMI models?
    • Transform of ICD-10 CM to CIMI models – Richard
    • Others?
  • Any other business


Plan and Schedule

Plan and Schedule


Annotated Figures

  • Scribe: Stephen.Hufnagel.HL7@gmail.com
  • REQUESTED ACTION: Directly edit this page or send suggested changes to scribe or cimi@lists.hl7.org


Proposed Focal Assertion Class
  • Claude: Changes to the Assertion Model
    • Focal Assertion specialization helps reduce the size of Assertion by specifying Body Location
    • This is a "Design by Extension", which is preferred in object-oriented programming
    • Another Base Assertion specialization is Device, which may have different attributes than other types of Assertions
  • Stan: This Focal Assertion Model approach encourages post-coordination
    • Name: fracture
    • Body Location: femur
    • pattern suitable for lacerations, ulcers, etc.
    • previous Assertion model's name field will have redundant information or pre-coordinated concepts.
  • Steve's Mind Map (below): includes the femur example's preferred post-coordinated and alternative pre-coordinated representations based-on Stan's Example Spread Sheet


DCM-context Mind-Map


Proposed Focal Assertion Class Mind Map


Mind Map Legend

PC Requirements for Skin-Wound DCM

  • 2917-02-09-1000 ET Patient Care Workgroup Telecom
  • Attendees: Jay, Susan, Richard, Claude, Steve
  1. Skin Wound content & scope
    1. Braden
    2. Skin Assessment
    3. Wound Assessment, with Pressure Ulcer specialization
    4. No Skin Risk Assessment (out of scope)
  2. Schedule
    1. Feb 13: Requirements UML and Terminology spreadsheet finished
    2. Feb 13 to Mar 3 - VA verification and validation of spreadsheet
      1. Diagram
      2. Data-Element and Value-Set Spreadsheet
    3. Mar 8: Presented at LOINC conference by Susan


Skin Wound UML Requirements


Skin Wound Context Mind Map.jpg


Skin Wound Detail-1


Skin Wound Detail-2


Skin Wound Detail-3