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

Difference between revisions of "CIMI WGM Agenda May 2017"

From HL7Wiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 2 users not shown)
Line 42: Line 42:
 
   <td rowspan=2>PM</td>
 
   <td rowspan=2>PM</td>
 
   <td>Q3</td>
 
   <td>Q3</td>
   <td></td>
+
   <td>Almagro</td>
 
   <td>Welcome and Agenda Review, CIMI Overview</td>
 
   <td>Welcome and Agenda Review, CIMI Overview</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
   <td></td>
+
   <td>Stan</td>
   <td></td>
+
   <td>Richard</td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
   <td></td>
+
   <td>Almagro</td>
   <td>Ballot Reconcilliation</td>
+
   <td>
  <td></td>
+
*FHIM discussion with implementers
  <td></td>
+
*Ballot Reconcilliation
 +
</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Stan</td>
 +
  <td>Galen</td>
 
  </tr>
 
  </tr>
  
Line 76: Line 79:
 
   <td rowspan=2>AM </td>
 
   <td rowspan=2>AM </td>
 
   <td>Q1</td>
 
   <td>Q1</td>
   <td></td>
+
   <td>Munich</td>
 
   <td> @ Patient Care (skin breakdown, allergies/adverse reactions) </td>
 
   <td> @ Patient Care (skin breakdown, allergies/adverse reactions) </td>
 
   <td>Patient Care</td>
 
   <td>Patient Care</td>
Line 86: Line 89:
 
  <tr>
 
  <tr>
 
   <td>Q2</td>
 
   <td>Q2</td>
   <td></td>
+
   <td>Almagro</td>
 
   <td>FHIM Coordination</td>
 
   <td>FHIM Coordination</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
   <td></td>
+
   <td>Galen</td>
   <td></td>
+
   <td>Richard</td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
 
   <td rowspan=3>PM </td><td>lunch</td>
 
   <td rowspan=3>PM </td><td>lunch</td>
   <td></td>
+
   <td>Marsella</td>
 
   <td>Lunch with FHIR: CIMI FHIR profile governance & coordination across groups
 
   <td>Lunch with FHIR: CIMI FHIR profile governance & coordination across groups
 
* Report that the CIMI datatypes now map one-to-one with the FHIR datatypes
 
* Report that the CIMI datatypes now map one-to-one with the FHIR datatypes
Line 104: Line 107:
 
   <td></td>
 
   <td></td>
 
   <td>FHIR-I</td>
 
   <td>FHIR-I</td>
   <td></td>
+
   <td>Stan</td>
   <td></td>
+
   <td>Galen</td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
 
   <td>Q3</td>
 
   <td>Q3</td>
   <td></td>
+
   <td>Almagro</td>
 
   <td>Tooling Discussion
 
   <td>Tooling Discussion
* Discuss tools and tooling, including what Claude is doing, VA tools, Intermountain tools, MDHT, etc.
+
* Discuss tools and tooling, including what Claude is doing, VA tools, Intermountain tools, MDHT, CAMEO (Mark Kramer), etc.
 
</td>
 
</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
   <td></td>
+
   <td>Richard</td>
   <td></td>
+
   <td>Galen</td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
   <td></td>
+
   <td>Estrasburgo</td>
 
   <td> @ Patient Care (negation, and other topics of joint interest) </td>
 
   <td> @ Patient Care (negation, and other topics of joint interest) </td>
 
   <td>Patient Care</td>
 
   <td>Patient Care</td>
Line 146: Line 149:
 
   <td rowspan=2>AM </td>
 
   <td rowspan=2>AM </td>
 
   <td>Q1</td>
 
   <td>Q1</td>
   <td></td>
+
   <td>Estrasburgo</td>
 
   <td> @ CQI  
 
   <td> @ CQI  
 
* status updates, alignment with QDM and CIMI coverage of VMR content
 
* status updates, alignment with QDM and CIMI coverage of VMR content
 +
* discuss KNART PSS
 +
* Discussion of using CIMI as a model for the KNARTs - Perhaps this is a separate PSS?
 
</td>
 
</td>
 
   <td>CQI</td>
 
   <td>CQI</td>
Line 158: Line 163:
 
  <tr>
 
  <tr>
 
   <td>Q2</td>
 
   <td>Q2</td>
   <td></td>
+
   <td>Frankfurt</td>
 
   <td> @ CIC
 
   <td> @ CIC
 
* Next steps for integrating the Data Elements into CIMI models
 
* Next steps for integrating the Data Elements into CIMI models
 
* How to support DE->FHIR project
 
* How to support DE->FHIR project
 +
* How CIC DAMs relate to CIMI
 
</td>
 
</td>
 
   <td>CIC</td>
 
   <td>CIC</td>
Line 171: Line 177:
 
  <tr>
 
  <tr>
 
   <td rowspan=2>PM </td>
 
   <td rowspan=2>PM </td>
   <td>Q3</td>
+
   <td >[[#Wednesday_Q3 | Q3]]</td>
   <td></td>
+
   <td>Almagro</td>
   <td>(Placeholder) Semantics for Assertion & Evaluation. Review of Vital Signs Profile(s)</td>
+
   <td>Semantics for Assertion & Evaluation. Review of Vital Signs Profile(s)</td>
  <td></td>
 
  <td></td>
 
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Jay</td>
 +
  <td>Richard</td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
   <td></td>
+
   <td>Burdeos</td>
 
   <td> @ CDS
 
   <td> @ CDS
 
* alignment with the Topic/Context pattern, how they'll be used in knowledge artifacts, generation of FHIR Profiles for DCMs and how they'd be used in CDS services
 
* alignment with the Topic/Context pattern, how they'll be used in knowledge artifacts, generation of FHIR Profiles for DCMs and how they'd be used in CDS services
Line 208: Line 214:
 
   <td rowspan=2>AM </td>
 
   <td rowspan=2>AM </td>
 
   <td>Q1</td>
 
   <td>Q1</td>
   <td></td>
+
   <td>Almagro</td>
 
   <td>Ballot Reconcilliation</td>
 
   <td>Ballot Reconcilliation</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
   <td></td>
+
   <td>Richard</td>
   <td></td>
+
   <td>Galen</td>
 
  </tr>
 
  </tr>
  
 
  <tr>
 
  <tr>
 
   <td>Q2</td>
 
   <td>Q2</td>
   <td></td>
+
   <td>Almagro</td>
   <td>Ballot Reconcilliation</td>
+
   <td>
  <td></td>
+
*Ballot Reconcilliation
  <td></td>
+
*Discusss relationship between "Models of Meaning" vs "Models of Use" - "Topic" - and Ontology/Description Logic
 +
*How does LEGO question/answer relate to CIMI?</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Richard</td>
 +
  <td>Galen</td>
 
  </tr>
 
  </tr>
  
Line 229: Line 238:
 
   <td rowspan=2>PM</td>
 
   <td rowspan=2>PM</td>
 
   <td>Q3</td>
 
   <td>Q3</td>
   <td></td>
+
   <td>Alcudia</td>
 
   <td> @ Vocabulary
 
   <td> @ Vocabulary
 
* Discuss CIMI SNOMED CT namespace
 
* Discuss CIMI SNOMED CT namespace
Line 243: Line 252:
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
   <td></td>
+
   <td>Almagro</td>
   <td>September Ballot Planning</td>
+
   <td>
  <td></td>
+
*September Ballot Planning
  <td></td>
+
*How do we prioritize outside requests for CIMI models / outreach</td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 
   <td></td>
 +
  <td>Stan</td>
 +
  <td>Steve H</td>
 
  </tr>
 
  </tr>
  
Line 307: Line 318:
  
 
</table>
 
</table>
 +
 +
===Wednesday Q3===
 +
Attendees
 +
*
 +
Review of Vitals effort
 +
* Susan collecting requirements
 +
* A vitals archetype is just another observation that happens to be in one (or more) panels called 'Vitals'
 +
* Fractal edges: SpO2 can be done with "room air" or "on O2" but not with all the devices, rate, %, ventilator settings, etc. If we do this one, it will probably be a lite version.
 +
Jay began presenting proposal for semantic alignment of assertion & evaluation patterns
 +
* Vehement discussion of whether we should support isosemanticity ensued; topic not broached

Latest revision as of 16:29, 10 May 2017

Return to Clinical_Information_Modeling_Initiative_Work_Group main page

Agenda

Day Time   Room Event Host Joining Chair/Lead Scribe
Monday
May 8
AM Q1 NOT MEETING
Q2 NOT MEETING
PM Q3 Almagro Welcome and Agenda Review, CIMI Overview Stan Richard
Q4 Almagro
  • FHIM discussion with implementers
  • Ballot Reconcilliation
Stan Galen
Day Time   Room Event Host Joining Chair/Lead Scribe
Tuesday
May 9
AM Q1 Munich @ Patient Care (skin breakdown, allergies/adverse reactions) Patient Care (Pt Care) n/a
Q2 Almagro FHIM Coordination Galen Richard
PM lunch Marsella Lunch with FHIR: CIMI FHIR profile governance & coordination across groups
  • Report that the CIMI datatypes now map one-to-one with the FHIR datatypes
  • Describe the plan for the CIIC meeting to be held at NIH on July 13
  • Our plans for the September ballot
FHIR-I Stan Galen
Q3 Almagro Tooling Discussion
  • Discuss tools and tooling, including what Claude is doing, VA tools, Intermountain tools, MDHT, CAMEO (Mark Kramer), etc.
Richard Galen
Q4 Estrasburgo @ Patient Care (negation, and other topics of joint interest) Patient Care (Pt Care) n/a
Day Time   Room Event Host Joining Chair/Lead Scribe
Wednesday
May 10
AM Q1 Estrasburgo @ CQI
  • status updates, alignment with QDM and CIMI coverage of VMR content
  • discuss KNART PSS
  • Discussion of using CIMI as a model for the KNARTs - Perhaps this is a separate PSS?
CQI (CQI) n/a
Q2 Frankfurt @ CIC
  • Next steps for integrating the Data Elements into CIMI models
  • How to support DE->FHIR project
  • How CIC DAMs relate to CIMI
CIC (CIC) n/a
PM Q3 Almagro Semantics for Assertion & Evaluation. Review of Vital Signs Profile(s) Jay Richard
Q4 Burdeos @ CDS
  • alignment with the Topic/Context pattern, how they'll be used in knowledge artifacts, generation of FHIR Profiles for DCMs and how they'd be used in CDS services
CDS (CDS) n/a
Day Time   Room Event Host Joining Chair/Lead Scribe
Thursday
May 11
AM Q1 Almagro Ballot Reconcilliation Richard Galen
Q2 Almagro
  • Ballot Reconcilliation
  • Discusss relationship between "Models of Meaning" vs "Models of Use" - "Topic" - and Ontology/Description Logic
  • How does LEGO question/answer relate to CIMI?
Richard Galen
PM Q3 Alcudia @ Vocabulary
  • Discuss CIMI SNOMED CT namespace
  • what edition should people start from?
  • binding policies, procedures, semantics
Vocabulary (Vocabulary) n/a
Q4 Almagro
  • September Ballot Planning
  • How do we prioritize outside requests for CIMI models / outreach
Stan Steve H
Day Time   Room Event Host Joining Chair/Lead Scribe
Friday
May 12
AM Q1 NOT MEETING
Q2 NOT MEETING
PM Q3 NOT MEETING
Q4 NOT MEETING

Wednesday Q3

Attendees

Review of Vitals effort

  • Susan collecting requirements
  • A vitals archetype is just another observation that happens to be in one (or more) panels called 'Vitals'
  • Fractal edges: SpO2 can be done with "room air" or "on O2" but not with all the devices, rate, %, ventilator settings, etc. If we do this one, it will probably be a lite version.

Jay began presenting proposal for semantic alignment of assertion & evaluation patterns

  • Vehement discussion of whether we should support isosemanticity ensued; topic not broached