This wiki has undergone a migration to Confluence found Here
2016-08-05 PC CIMI POC Call Minutes
Revision as of 18:42, 5 August 2016 by Jlyle (talk | contribs) (Created page with " <!-- LOOK FOR THE APPROPRIATE SECTION ****** TO ENTER INFORMATION--> Back to PC CIMI POC Minutes ==Minutes Template== ===Meeting Information=== {|border="1" cellpadding="...")
Back to PC CIMI POC Minutes
Minutes Template
Meeting Information
HL7 PC-CIMI-POC Meeting Minutes Location: Phone |
Date: 2016-08-05 Time: 10:00-11:00 ET | ||
Facilitator | Jay Lyle | Note taker(s) | Jay Lyle |
Attendee | Name | Affiliation
| |
y | Richard Esmond | PenRad | |
Galen Mulrooney | JP Systems | ||
y | Jay Lyle | JP Systems / VA | |
Harold Solbrig | Mayo | ||
y | Susan Matney | Intermountain | |
y | Susan Campbell | Intermountain | |
Kurt Allen | Intermountain | ||
Joey Coyle | Intermountain | ||
Laura Heerman Langford | Intermountain | ||
M'Lynda Owens | Intermountain | ||
Stephen Hufnagel | Intermountain | ||
Agenda
Agenda Topics
review of exam model
- really examination observation, not exam - ok
- only including elements found in models, not entire SCT model - ok
- openEHR: redundant sites; description/findings -
- openEHR: chart by exception
- findings limited: we will extend
Minutes
Minutes/Conclusions Reached:
- Review of outcomes & news from Procedure meeting last night
- Using SCT & LOINC where there are synonyms: SOLOR will contain both, coordinated with a UUID.
- This means that the SCT & LOINC codes are really just additional terms, which may be OK
- But it also means that SOLOR won't be expressible in RF2
- In models, use SCT attribute for model bindings, if one exists. Otherwise, use an observable concept
- I find this problematic. It breaks the semantics.
- Other SOLOR questions include how extensions & module dependencies will work
- Using SCT & LOINC where there are synonyms: SOLOR will contain both, coordinated with a UUID.
- Root semantics
- Jay presented this slide deck.
- It took a while to make it comprehensible, but we seem to be in agreement
- We can use SCT concept model attributes for model attributes
- But they are attributes of something, viz., the model
- So the concept that the model represents should be asserted as a property with an "is-a" model binding
- And this approach supports the composition of models via attributes; e.g., a finding "interprets" an observable.
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.