This wiki has undergone a migration to Confluence found Here
2016-04-29 PC CIMI POC Call Minutes
Revision as of 22:27, 29 April 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: PC call line |
Date: 2016-04-22 Time: 15:00-16:00 ET | ||
Facilitator | Jay Lyle | Note taker(s) | Jay Lyle |
Attendee | Name | Affiliation
| |
Richard Esmond | PenRad | ||
Galen Mulrooney | JP Systems | ||
Jay Lyle | JP Systems / VA | ||
Stan Huff | Intermountain | ||
Susan Matney | Intermountain | ||
Susan Campbell | |||
Michael Sterly | |||
Gerard Frieks | |||
Serafina Versaggi | |||
Agenda
Agenda Topics
- Review of candidates
- Archetype compositional architecture
Minutes
Minutes/Conclusions Reached:
- review of candidates
- Skin Inspection (coded elements)
- Braden Scale, adult (Ordinal, INT, scale)
- Ulcer (date, PQ, negation, composition (with wound))
- archetype architecture
- inheritance map (see inheritance map)
- in light of Stan's pulse example: should this be more complex, or should we assemble atoms into molecules?
- assumption: composition. 5 atomic skin inspection component obs; one aggregation.
- everyone on call agrees
- openEHR usually groups them.
- in light of Stan's pulse example: should this be more complex, or should we assemble atoms into molecules?
- in light of Claude's contextual axes,
- does skin inspection have an order state?
- does it have an assertion kind?
- these matter one level higher than our skin inspection level
- assertion would be different semantics (pt has dry skin, not 'dry')
- this style works especially for Q/A concepts
- maturity of draft
- firm but not concrete
- inheritance map (see inheritance map)
- Clinical observations
- may need atrophic (thin) value for condition
- are condition & moisture duplicative?
- what would this be in FHIR? observation probably
- changed 'examination' to 'evaluation' to remove visual connotation. 'assessment' also an option
- loinc & sct
- Stan: could have used LOINC codes for model binding
- IM style: no code at model root. unique id for model. with relationshps
- then code = concept (L or SCT. either way)
- L more complex for defining expression;
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.