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

CIMI Telecom Minutes 2017-01-05

From HL7Wiki
Jump to navigation Jump to search

REQUESTED ACTION: Feel free to directly edit this WIKI page or send your feedback to CIMI@lists.HL7.org with your comments, updates and corrections.

Attendees

Linda Buhl, Joey Coyle, Richard Esmond, Bret Heale, Stan Huff, Steve Hufnagel, Mark Kramer, Patrick Langford, Jay Lyle, Chris Macintosh, Susan Matney, Galen Mulrooney, Craig Parker, Deepak Sharma, Serafina Versaggi

Annotated Agenda (Minutes)

Italicized lines were discussed

  • Record this call
  • Agenda review
  • Meeting schedule
    • Meeting next week on January 12?
  • Updates on active projects (standing item)
    • Skin and wound assessments – Jay and Susan
    • Reference Archetype/Patterns
      • FHIM Medication classes transformed to ADL – Galen
  • 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)
  • Cognitive is providing a resource to convert CIMI archetypes to FHIR logical models to FHIR profiles
  • Agenda planning for San Antonio WGM
    • See attached session outline from HL7 headquarters
    • Plans for Saturday session
    • Stan will only be available Saturday thru Tuesday lunch
  • Recap of recent email exchange - All
  • FHIM – CIMI integration issues and discussion - Galen
  • Review CIMI models for January comment only ballot – Claude, All
  • Continued modeling of assertions if time allows – Stan
  • Future topics
    • Review CIMI Observation Result pattern
    • Harmonization of CIMI and FHIR datatypes - Richard
    • 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
    • Model approval process
      • What models do we want to ballot?
    • IHTSDO work for binding SNOMED CT to FHIR resources – Linda, Harold
    • Which openEHR archetypes should we consider converting to CIMI models?
    • Model transformations
    • Transform of ICD-10 CM to CIMI models – Richard
    • Others?
  • Any other business

Discussion Topics

  • Galen Mulrooney presented meeting plan http://wiki.hl7.org/index.php?title=CIMI_WGM_Agenda_January_2017
  • “Semantic relationships” are clinically important (BP is-a vital sign)
  • “Structural relationships” (BP vs. Femur length may have the same structure)
    • In general, we should follow SNOMED
    • ASSERTION style are things we can state about an individual can be made into an EVALUATION Q&A style
    • Every EVALUATION cannot always be converted into an ASSERTION
    • ISSUE: Mapping consistent ASSERTIONs & EVALUATIONs may not consistently map to FHIR CONDITIONS and OBSERVATIONs
  • Mark: How do we model "What contraceptive are you using."
  • Susan: Breath sounds normal, increased or decreased are EVALUATION with different value sets
  • Stan: Breath sounds are wheezing; rouse or rhonchi is different
  • Jay: patient says they have a cough ASSERTION … Can change to Q&A EVALUATION style What was the patient complaint? It was cough.
  • Galen: this may be a Quick carry over.
  • Stan: Patient has a skin ulcer is an ASSERTION. Something about individual EVALUATION is named characteristic with value. EVALUATION can mean a condition is present. Definition of a condition is an ASSERTION …
  • What does a SNOMED code mean? Does it mean a patient has or the meaning of the condition.
  • FINDING uses situational CONTEXT.

Screen Sharing & Telecom Information

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