This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Clinical Information Modeling Initiative WG September 2017 San Diego, CA"
Jump to navigation
Jump to search
MulrooneyG (talk | contribs) |
MulrooneyG (talk | contribs) |
||
Line 77: | Line 77: | ||
<tr> | <tr> | ||
− | <td rowspan=4>Monday<br/> | + | <td rowspan=4>Monday<br/>September 11</td> |
<td rowspan=2>AM </td> | <td rowspan=2>AM </td> | ||
<td>Q1</td> | <td>Q1</td> | ||
Line 131: | Line 131: | ||
</tr> | </tr> | ||
+ | <!--------------- TUESDAY ---------------> | ||
<tr> | <tr> | ||
− | <td rowspan= | + | <td rowspan=4>Tuesday<br/>September 12</td> |
<td rowspan=2>AM </td> | <td rowspan=2>AM </td> | ||
<td>Q1</td> | <td>Q1</td> | ||
Line 184: | Line 185: | ||
<tr> | <tr> | ||
<td>Q4</td> | <td>Q4</td> | ||
− | <td> | + | <td>(tbd)</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 222: | Line 223: | ||
<tr> | <tr> | ||
<td>Q2</td> | <td>Q2</td> | ||
− | <td> | + | <td>(tbd)</td> |
<td> @ CIC | <td> @ CIC | ||
+ | * Next steps for Cancer Interoperability PSS - how to work within HL7 | ||
* 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 |
Revision as of 20:28, 17 August 2017
Return to Clinical_Information_Modeling_Initiative_Work_Group main page
Agenda
Day | Time | Room | Event | Host | Joining | Chair/Lead | Scribe | |
---|---|---|---|---|---|---|---|---|
Sunday September 10 |
AM | Q1 | NOT MEETING | |||||
Q2 | NOT MEETING | |||||||
PM | Q3 | (tbd) | Week Planning / Cram Session | |||||
Q4 | (tbd) | Week Planning / Cram Session | ||||||
Day | Time | Room | Event | Host | Joining | Chair/Lead | Scribe | |
Monday September 11 |
AM | Q1 | NOT MEETING | |||||
Q2 | NOT MEETING | |||||||
PM | Q3 | (tbd) | Joint with EHR, PC, EC (Mega-Report-out) | Stan | Richard | |||
Q4 | (tbd) | Welcome and Agenda Review, CIMI Overview | Stan | Galen | ||||
Day | Time | Room | Event | Host | Joining | Chair/Lead | Scribe | |
Tuesday September 12 |
AM | Q1 | Munich | @ Patient Care (skin breakdown, allergies/adverse reactions) | Patient Care | (Pt Care) | n/a | |
Q2 | Almagro | *FHIM discussion with implementers
|
Galen | Richard | ||||
PM | lunch | Marsella | Lunch with FHIR: CIMI FHIR profile governance & coordination across groups
|
FHIR-I | Stan | Galen | ||
Q3 | Almagro | Tooling Discussion
|
Richard | Galen | ||||
Q4 | (tbd) | @ 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
|
CQI | (CQI) | n/a | |
Q2 | (tbd) | @ CIC
|
CIC | (CIC) | n/a | |||
PM | Q3 | Almagro | Semantics for Assertion & Evaluation. Review of Vital Signs Profile(s) | Jay | Richard | |||
Q4 | Burdeos | @ CDS
|
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 |
|
Richard | Galen | ||||
PM | Q3 | Alcudia | @ Vocabulary
|
Vocabulary | (Vocabulary) | n/a | ||
Q4 | Almagro |
|
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