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

Difference between revisions of "CIMI WGM Agenda May 2016"

From HL7Wiki
Jump to navigation Jump to search
 
(25 intermediate revisions by 2 users not shown)
Line 23: Line 23:
 
   <td>Q1</td>
 
   <td>Q1</td>
 
   <td></td>
 
   <td></td>
   <td>Administration (scribes, wg health) </td>
+
   <td>Administration (week planning, wg health, project status updates) </td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
Line 33: Line 33:
 
   <td>Q2</td>
 
   <td>Q2</td>
 
   <td></td>
 
   <td></td>
   <td>Governance</td>
+
   <td>Governance, what's in the modeling pipeline, how are models approved, what goes in the repository</td>
  <td>&nbsp;</td>
 
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 +
  <td>Stan</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 44: Line 44:
 
   <td>Lunch</td>
 
   <td>Lunch</td>
 
   <td></td>
 
   <td></td>
   <td><font color=#c0c0c0>NOT MEETING</font><br/>!! ''Joint meeting with the Patient Care Work Group moved to Tuesday Q1''</td>
+
   <td>How when and why are model transformations done (isosemantic, translation to design models)</td>
  <td></td>
 
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Claude, Richard</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 54: Line 54:
 
   <td>Q3</td>
 
   <td>Q3</td>
 
   <td> </td>
 
   <td> </td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>
+
   <td>Design - composition</td>
 
   <td>  </td>
 
   <td>  </td>
 
   <td></td>
 
   <td></td>
   <td></td>
+
   <td>Claude</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 64: Line 64:
 
   <td>Q4</td>
 
   <td>Q4</td>
 
   <td> </td>
 
   <td> </td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>
+
   <td>Design - Alignment with FHIM</td>
 
   <td>  </td>
 
   <td>  </td>
 
   <td></td>
 
   <td></td>
   <td></td>
+
   <td>Galen</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
   <td rowspan=5>Monday<br/>Jan 11</td>
+
   <td rowspan=5>Monday<br/>May 9</td>
 
   <td rowspan=3>AM </td>
 
   <td rowspan=3>AM </td>
 
   <td>Q1</td>
 
   <td>Q1</td>
  <td>Plaza Int'l Ballroom K</td>
 
  <td>Joint meeting with the Clinical Interoperability Council
 
* Short overview of CIMI
 
* Collaboration with CIC for expert clinical review of CIMI content
 
**      Is this role for CIC?
 
**      How would CIMI and CIC work jointly?
 
**      Does CIC have representation from professional societies or how can they be engaged?</td>
 
  <td>CIMI</td>
 
  <td>CIC</td>
 
 
   <td></td>
 
   <td></td>
 +
  <td>Tooling: ISAAC, IHTSDO, 'archetype design tool'</td>
 +
  <td></td>
 +
  <td></td>
 +
  <td>Craig, Keith, Harold, Linda</td>
 
   <td></td>
 
   <td></td>
 
  </tr>
 
  </tr>
Line 90: Line 85:
 
  <tr>
 
  <tr>
 
   <td>Q2</td>
 
   <td>Q2</td>
   <td>Plaza Int'l Ballroom K</td>
+
   <td></td>
   <td>CIMI Business
+
   <td>Semantics & alignment with models of meaning, e.g., SNOMED CT; binding; handling federated terminologies; selection of concept identifiers (e.g., LOINC vs Observable) </td>
* Model repository
 
* Tooling
 
* PSS -- Harold Solbrig, Steve Hufnagel
 
* Using CIMI models to create FHIR profiles and making visible in FHIR website
 
* Use of CIMI models as part of FHIR conformance testing
 
* CIMI Authoring Tool Overview
 
* CIMI operating principles
 
* CIMI decision practices</td>
 
  <td>&nbsp;</td>
 
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 +
  <td>Jay, Claude, Keith</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 108: Line 95:
 
  <tr>
 
  <tr>
 
   <td>lunch</td>
 
   <td>lunch</td>
  <td>?? Plaza Int'l Ballroom K</td>
 
  <td>CIMI Authoring Tool Demonstration</td>
 
 
   <td></td>
 
   <td></td>
 +
  <td>Semantics & alignment with IHTSDO</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Linda</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 119: Line 106:
 
   <td rowspan=2>PM</td>
 
   <td rowspan=2>PM</td>
 
   <td>Q3</td>
 
   <td>Q3</td>
  <td>Plaza Int'l Ballroom K</td>
 
  <td>CIMI Business
 
* Plans for May WG meeting</td>
 
 
   <td></td>
 
   <td></td>
 +
  <td>Quality Metrics for DCMs, incl. ISO</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Sun-Ju</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 130: Line 116:
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
  <td>Plaza Int'l Ballroom K</td>
 
  <td>Joint meeting with Vocabulary Work Group and possibly the HL7 Terminology Authority
 
* Short overview of CIMI
 
* Value sets and value set binding syntax
 
* Value set document under development by Vocabulary Work Group
 
* Value set creation and coordination with other groups, e.g., IHTSDO, NLM/VSAC
 
* Developing a unified strategy across CIMI and Vocabulary Work Group
 
* Relationship to national initiatives
 
* Use of CIMI SCT extension</td>
 
  <td>CIMI</td>
 
  <td>Vocab and HTA</td>
 
 
   <td></td>
 
   <td></td>
 +
  <td>Tooling 2: SCT CIMI identifer tool, knowledge management, experimental integration with CQL</td>
 +
  <td></td>
 +
  <td></td>
 +
  <td>Harold, Richard</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 158: Line 137:
  
 
  <tr>
 
  <tr>
   <td rowspan=6>Tuesday<br/>Jan 12</td>
+
   <td rowspan=5>Tuesday<br/>May 10</td>
   <td rowspan=3>AM </td>
+
   <td rowspan=2>AM </td>
 
   <td>Q1</td>
 
   <td>Q1</td>
   <td>Plaza Int'l Ballroom I</td>
+
   <td>Salon 6 & 7</td>
   <td>Joint meeting with the Patient Care Work Group
+
   <td> @ Patient Care, skin breakdown</td>
* Short overview of CIMI
 
* Relationship of CIMI work to PCWG DCMs
 
* What PCWG projects are ongoing where CIMI could provide value
 
</td>
 
 
   <td>Patient Care</td>
 
   <td>Patient Care</td>
 
   <td>CIMI</td>
 
   <td>CIMI</td>
   <td></td>
+
   <td>Jay, Susan, Harold</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 175: Line 150:
 
  <tr>
 
  <tr>
 
   <td>Q2</td>
 
   <td>Q2</td>
   <td></td>
+
   <td>Salon Drummond Centre</td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>
+
   <td>Argonauts</td>
 
   <td> </td>
 
   <td> </td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
   <td></td>
+
   <td>Stan</td>
 
   <td></td>
 
   <td></td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
   <td>lunch</td>
+
   <td rowspan=3>PM </td><td>lunch</td>
   <td>Florida Ballroom B<br/>
+
   <td><br/></td>
''Get food from buffet and take to Ballroom''</td>
+
   <td>No meeting. Previously CIMI meeting with FHIR Core Team</td>
   <td>CIMI meeting with FHIR Core Team
+
   <td></td>
* CIMI models in FHIR profiles
+
   <td></td>
* Using CIMI models in FHIR conformance testing
 
* Use of CIMI logical models in FHIR profiles</td>
 
   <td>CIMI</td>
 
   <td>FHIR Core Team</td>
 
 
   <td></td>
 
   <td></td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
Line 198: Line 169:
  
 
  <tr>
 
  <tr>
  <td rowspan=3>PM</td>
 
 
   <td>Q3</td>
 
   <td>Q3</td>
   <td></td>
+
   <td>Salle De Bal East</td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>
+
   <td>At Vocabulary</td>
   <td> </td>
+
   <td> Vocabulary </td>
   <td></td>
+
   <td>CIMI</td>
 
   <td></td>
 
   <td></td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
Line 210: Line 180:
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
   <td>&nbsp;</td>
+
   <td>Salon 6 & 7</td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>
+
   <td>Vocabulary</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
Line 218: Line 188:
 
  </tr>
 
  </tr>
  
<tr>
 
  <td bgcolor=#dddddd>Q6 7-9PM</td>
 
  <td bgcolor=#dddddd>Plaza Int'l Ballroom F</td>
 
  <td bgcolor=#dddddd>The FHIR project will be holding a mapping BOF at the Orlando meeting, Tues Q6. In this meeting, we'll be:
 
* seeing some mapping tool demos
 
* considering how to flesh out an interoperable format for mappings, and create an eco-system around that
 
* gathering a set of requirements to drive the format./eco-system
 
* identifying significant applications where exchanging mappings will be useful (e.g. CCDA...)
 
  
If you'd like to make a presentation on the night, please let Lloyd or Grahame know</td>
 
  <td bgcolor=#dddddd>FHIR</td>
 
  <td bgcolor=#dddddd></td>
 
  <td bgcolor=#dddddd>Lloyd or Grahame</td>
 
  <td bgcolor=#dddddd>&nbsp;</td>
 
</tr>
 
  
 
  <tr bgcolor=#f0f0f0>
 
  <tr bgcolor=#f0f0f0>
Line 247: Line 203:
  
 
  <tr>
 
  <tr>
   <td rowspan=4>Wednesday<br/>Jan 13</td>
+
   <td rowspan=4>Wednesday<br/>May 11</td>
 
   <td rowspan=2>AM </td>
 
   <td rowspan=2>AM </td>
 
   <td>Q1</td>
 
   <td>Q1</td>
   <td>&nbsp;</td>
+
   <td>Salon Hemon</td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>
+
   <td>@ CQI</td>
   <td>&nbsp;</td>
+
   <td>CQI</td>
   <td>&nbsp;</td>
+
   <td>CIMI</td>
   <td>&nbsp;</td>
+
   <td>Claude, Bryn, Ken</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 260: Line 216:
 
  <tr>
 
  <tr>
 
   <td>Q2</td>
 
   <td>Q2</td>
   <td>Winter Park 53</td>
+
   <td>Salon Hemon</td>
   <td>CIMI meeting with Grahame Grieve
+
   <td>FHIR semantics; representing archetypes as structure definitions</td>
* Grahame's logical models
 
* Repository of FHIR profiles -- status, plans
 
* CIMI models in FHIR profiles
 
* Using CIMI models in FHIR conformance testing
 
* Use of CIMI logical models in CIMI profiles
 
</td>
 
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
   <td>&nbsp;</td>
+
   <td>Grahame</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>
Line 277: Line 227:
 
   <td rowspan=2>PM </td>
 
   <td rowspan=2>PM </td>
 
   <td>Q3</td>
 
   <td>Q3</td>
   <td></td>
+
   <td>Salon Hemon</td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>
+
   <td>RM (status); AML to ADL transforms (i.e., FHIM); possible RDF support</td>
  <td></td>
 
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Michael</td>
 
   <td></td>
 
   <td></td>
 
  </tr>
 
  </tr>
Line 287: Line 237:
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
   <td>Plaza Int'l Ballroom K</td>
+
   <td>Salle De Bal East</td>
   <td>Joint meeting with CQI and CDS Work Groups
+
   <td></td>
* Use of CIMI models as the CQI/CDS logical models</td>
 
 
   <td>CIMI</td>
 
   <td>CIMI</td>
 
   <td>CQI and CDS</td>
 
   <td>CQI and CDS</td>
   <td></td>
+
   <td>Claude, Bryn, Ken</td>
 
   <td></td>
 
   <td></td>
 
  </tr>
 
  </tr>
Line 309: Line 258:
 
   
 
   
 
  <tr>
 
  <tr>
   <td rowspan=4>Thursday<br/>Jan 14</td>
+
   <td rowspan=4>Thursday<br/>May 12</td>
 
   <td rowspan=2>AM </td>
 
   <td rowspan=2>AM </td>
 
   <td>Q1</td>
 
   <td>Q1</td>
   <td></td>
+
   <td>Suite 701</td>
   <td><font color=#c0c0c0>NOT MEETING</font></td>  
+
   <td>@ CIC DAM Data Elements</td>  
   <td></td>
+
   <td>CIC</td>
   <td></td>
+
   <td>CIMI</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
Line 364: Line 313:
  
 
  <tr>
 
  <tr>
   <td rowspan=4>Friday<br/>Jan 15</td>
+
   <td rowspan=4>Friday<br/>May 13</td>
 
   <td rowspan=2>AM</td>
 
   <td rowspan=2>AM</td>
 
   <td>Q1</td>
 
   <td>Q1</td>
Line 407: Line 356:
  
 
</table>
 
</table>
 
Icons:
 
*{{Business}} Business meeting
 
*{{Reconciliation}} Ballot Reconciliation meeting
 
*{{Technical}} Technical discussion
 
  
 
=Minutes=
 
=Minutes=
Line 446: Line 390:
  
 
'''Minutes/Conclusions Reached:'''<br/>
 
'''Minutes/Conclusions Reached:'''<br/>
 +
 +
 +
==Sunday Q4==
 +
Attendees
 +
Michale Van der Zel, Jay Lyle, Chris Millet, Floyd Eisenberg, Susan Matney, Craig Parker, Joey Coyle, Stan Huff, Linda Bird, Harold Solbrig, Claude Nanjo, Richard Esmond, 3-6 others
 +
 +
* Jay presented the FHIM at a high level, including intended uses and a brief view of the model.
 +
* The expectation is that FHIM could provide a framework for inserting CIMI components.
 +
* The question of composition was addressed. A CIMI indivisible model must provide the context necessary for its interpretation, so logically, a panel would contain repetitive context information, but an implementation could use pointers to avoid excessive repetition.
 +
* We need to address the compositional dimensions Claude brings up; they seem to be orthogonal to the compositional concept of FHIM/CIMI
 +
* Question: is this specialization or constraint? Does it matter?
 +
* We need an approach for templating (localizing) archetypes
 +
* Stan to provide a list of questions already identified for task force
 +
 +
 +
==Monday Q2==
 +
* Claude and Harold presented slides on the CQI approach to model composition and on AML representation of terminology bindings.
 +
* Linda presented ongoing work on IHTSDO syntax development and a preview of some SCT/FHIR mapping thoughts.
 +
** File too big to upload; cut in three & some decorative graphics removed from the first:
 +
** [[Media: HL7_FHIR_SNOMED_Bindings_(20160509)_Amod.pptx | HL7 FHIR SNOMED Bindings A]]
 +
** [[Media: HL7_FHIR_SNOMED_Bindings_(20160509)_B.pptx | HL7 FHIR SNOMED Bindings B]]
 +
** [[Media: HL7_FHIR_SNOMED_Bindings_(20160509)_C.pptx | HL7 FHIR SNOMED Bindings C]]
 +
* Jay presented [[Media:Transforming_CIMI_into_SNOMED_expressions_160508.pptx | slides]] on a project to use xslt to transform archetypes into owl xml. Questions included the following:
 +
** Maturity of CIMI models: actually, current drafts are based on extensive harmonization, and model bindings to SCT may be incomplete but are vetted. What we are actually missing is a clear governance path so you can tell what's official and what's in process.
 +
** Maturity of Observable model: a new version is available, or is to be available.
 +
** Value set binding syntax: it's a URI. How this is to be resolved is the responsibility of a service, not CIMI.
 +
** Refset bindings will require a service in order to create closure axioms for owl.
 +
** XML version of CIMI archetypes is not normative. This one we should discuss.
 +
 +
==Monday Lunch==

Latest revision as of 12:30, 7 June 2016

Return to Clinical_Information_Modeling_Initiative_Work_Group main page


Agenda

Day Time   Room Event Host Joining Chair Scribe
Sunday
May 8
AM Q1 Administration (week planning, wg health, project status updates)    
Q2 Governance, what's in the modeling pipeline, how are models approved, what goes in the repository     Stan  
PM Lunch How when and why are model transformations done (isosemantic, translation to design models) Claude, Richard  
Q3 Design - composition Claude  
Q4 Design - Alignment with FHIM Galen  
Monday
May 9
AM Q1 Tooling: ISAAC, IHTSDO, 'archetype design tool' Craig, Keith, Harold, Linda
Q2 Semantics & alignment with models of meaning, e.g., SNOMED CT; binding; handling federated terminologies; selection of concept identifiers (e.g., LOINC vs Observable)     Jay, Claude, Keith  
lunch Semantics & alignment with IHTSDO Linda  
PM Q3 Quality Metrics for DCMs, incl. ISO Sun-Ju  
Q4 Tooling 2: SCT CIMI identifer tool, knowledge management, experimental integration with CQL Harold, Richard  
Day Time   Room Event Host Joining Chair Scribe
Tuesday
May 10
AM Q1 Salon 6 & 7 @ Patient Care, skin breakdown Patient Care CIMI Jay, Susan, Harold  
Q2 Salon Drummond Centre Argonauts   Stan
PM lunch
No meeting. Previously CIMI meeting with FHIR Core Team  
Q3 Salle De Bal East At Vocabulary Vocabulary CIMI  
Q4 Salon 6 & 7 Vocabulary        
Day Time   Room Event Host Joining Chair Scribe
Wednesday
May 11
AM Q1 Salon Hemon @ CQI CQI CIMI Claude, Bryn, Ken  
Q2 Salon Hemon FHIR semantics; representing archetypes as structure definitions Grahame  
PM Q3 Salon Hemon RM (status); AML to ADL transforms (i.e., FHIM); possible RDF support Michael
Q4 Salle De Bal East CIMI CQI and CDS Claude, Bryn, Ken
Day Time   Room Event Host Joining Chair Scribe
Thursday
May 12
AM Q1 Suite 701 @ CIC DAM Data Elements CIC CIMI
Q2 NOT MEETING
PM Q3 NOT MEETING  
Q4   NOT MEETING        
Day Time   Room Event Host Joining Chair Scribe
Friday
May 13
AM Q1 NOT MEETING  
Q2   NOT MEETING        
PM Q3   NOT MEETING        
Q4   NOT MEETING        

Minutes

Sunday Q3

HL7 CIMI Meeting Agenda/Minutes
Location: Room xyz Date: 2016-01-10
Time: 11:00 AM Central
Facilitator: Note taker(s):
Attendee Name, Affiliation
. .
Quorum Requirements Met (co-chair plus 3 counting staff):

Minutes/Conclusions Reached:


Sunday Q4

Attendees Michale Van der Zel, Jay Lyle, Chris Millet, Floyd Eisenberg, Susan Matney, Craig Parker, Joey Coyle, Stan Huff, Linda Bird, Harold Solbrig, Claude Nanjo, Richard Esmond, 3-6 others

  • Jay presented the FHIM at a high level, including intended uses and a brief view of the model.
  • The expectation is that FHIM could provide a framework for inserting CIMI components.
  • The question of composition was addressed. A CIMI indivisible model must provide the context necessary for its interpretation, so logically, a panel would contain repetitive context information, but an implementation could use pointers to avoid excessive repetition.
  • We need to address the compositional dimensions Claude brings up; they seem to be orthogonal to the compositional concept of FHIM/CIMI
  • Question: is this specialization or constraint? Does it matter?
  • We need an approach for templating (localizing) archetypes
  • Stan to provide a list of questions already identified for task force


Monday Q2

  • Claude and Harold presented slides on the CQI approach to model composition and on AML representation of terminology bindings.
  • Linda presented ongoing work on IHTSDO syntax development and a preview of some SCT/FHIR mapping thoughts.
  • Jay presented slides on a project to use xslt to transform archetypes into owl xml. Questions included the following:
    • Maturity of CIMI models: actually, current drafts are based on extensive harmonization, and model bindings to SCT may be incomplete but are vetted. What we are actually missing is a clear governance path so you can tell what's official and what's in process.
    • Maturity of Observable model: a new version is available, or is to be available.
    • Value set binding syntax: it's a URI. How this is to be resolved is the responsibility of a service, not CIMI.
    • Refset bindings will require a service in order to create closure axioms for owl.
    • XML version of CIMI archetypes is not normative. This one we should discuss.

Monday Lunch