This wiki has undergone a migration to Confluence found Here
Difference between revisions of "2016-10-14PC CIMI POC Call Minutes"
Jump to navigation
Jump to search
(Created page with " <!-- LOOK FOR THE APPROPRIATE SECTION ****** TO ENTER INFORMATION--> Back to PC CIMI POC Minutes ==Minutes Template== ===Meeting Information=== {|border="1" cellpadding="...") |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 53: | Line 53: | ||
|colspan="2"| JP Systems | |colspan="2"| JP Systems | ||
|- | |- | ||
| − | | | + | | y || Jay Lyle |
|colspan="2"| JP Systems / VA | |colspan="2"| JP Systems / VA | ||
|- | |- | ||
| Line 62: | Line 62: | ||
|colspan="2"| Intermountain | |colspan="2"| Intermountain | ||
|- | |- | ||
| − | | | + | | y || Susan Campbell |
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
| − | | | + | | y || Jim Case |
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
| − | | | + | | y || Chris Johnson |
|colspan="2"| Intermountain | |colspan="2"| Intermountain | ||
|- | |- | ||
| Line 74: | Line 74: | ||
|colspan="2"| Intermountain | |colspan="2"| Intermountain | ||
|- | |- | ||
| − | | | + | | y || Claude Nanjo |
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
| Line 104: | Line 104: | ||
# review assertion content requirements | # review assertion content requirements | ||
## course & mechanism are precoordinated in SCT | ## course & mechanism are precoordinated in SCT | ||
| − | # drainage: | + | ## drainage: |
| − | ## confirm type list | + | ### confirm type list |
| − | ## status: values? | + | ### status: values? |
| − | ## qualitative volume values? | + | ### qualitative volume values? |
| − | # undermining & tunneling: | + | ## undermining & tunneling: |
| − | ## properties, or new associated lesions? restrict their properties? | + | ### properties, or new associated lesions? restrict their properties? |
| − | ## normalize dimensional measurements to a single 'dimension/magnitude' property? | + | ### normalize dimensional measurements to a single 'dimension/magnitude' property? |
# concept alignment | # concept alignment | ||
## Is an assertion a finding? | ## Is an assertion a finding? | ||
## Is an evaluation an observable + a finding? | ## Is an evaluation an observable + a finding? | ||
| − | |||
| − | |||
===Minutes=== | ===Minutes=== | ||
| Line 130: | Line 128: | ||
'''Minutes/Conclusions Reached:'''<br/> | '''Minutes/Conclusions Reached:'''<br/> | ||
| − | + | * Jim had questions about the use of attribute bindings. Jay attempted to answer them, with the assistance of [[media:Candidate Approach for Semantic Binding.pptx | this]] slide. | |
| + | ** Jim still has misgivings about using Situation, at least partly due to potential conflict between absence values & findings. | ||
| + | * Jay to schedule offline review of requirements with Susan due to scheduling conflicts | ||
| + | * We need to address code vs reference for devices, procedures, etc. | ||
| + | ** For the finding, we are interested in the type (cuff, scale, thermometer, etc.), not the device itself. | ||
| + | ** But we might link to the device itself to support retrieval of the type | ||
| + | ** Or we could assert that we don't care; if you link to support retrieval, go ahead and retrieve. | ||
| + | *** If you need the device, record it under an actual procedure. | ||
| + | ** If we decide we do need both, then are code & reference two distinct properties? | ||
| + | * Consider 'link' for typed references. | ||
| + | ** Claude: slicing is difficult | ||
| + | ** Jay: define archetypes for Braden parts & panel; include parts in panel. Is that slicing, & is it difficult? | ||
| + | ** tabled | ||
| + | * Precondition range is limited | ||
| + | ** some required precondition values are findings, some qualifiers. | ||
| + | ** request expansion of range to accommodate non-lab | ||
| + | ** or just use related finding instead | ||
| + | ** Jay to provide Vitals use case to Linda for consideration (review with Claude) | ||
| + | |||
===Meeting Outcomes=== | ===Meeting Outcomes=== | ||
{|border="1" cellpadding="2" cellspacing="0" | {|border="1" cellpadding="2" cellspacing="0" | ||
Latest revision as of 15:29, 14 October 2016
Back to PC CIMI POC Minutes
Minutes Template
Meeting Information
| HL7 PC-CIMI-POC Meeting Minutes Location: Phone |
Date: 2016-10-14 Time: 10:00-11:00 ET | ||
| Facilitator | Jay Lyle | Note taker(s) | Jay Lyle |
| Attendee | Name | Affiliation
| |
| Richard Esmond | PenRad | ||
| Galen Mulrooney | JP Systems | ||
| y | Jay Lyle | JP Systems / VA | |
| Harold Solbrig | Mayo | ||
| Susan Matney | Intermountain | ||
| y | Susan Campbell | ||
| y | Jim Case | ||
| y | Chris Johnson | Intermountain | |
| Laura Heerman Langford | Intermountain | ||
| y | Claude Nanjo | ||
| Rob McClure | |||
Agenda
Agenda Topics
- review assessment content requirements
- how many 'about' codes
- body site: coded, with modifier, and * (contiguous)
- can we make 'related observation' more specific?
- composition: lab/exam then qual/quant, or vice versa? or compositional?
- review assertion content requirements
- course & mechanism are precoordinated in SCT
- drainage:
- confirm type list
- status: values?
- qualitative volume values?
- undermining & tunneling:
- properties, or new associated lesions? restrict their properties?
- normalize dimensional measurements to a single 'dimension/magnitude' property?
- concept alignment
- Is an assertion a finding?
- Is an evaluation an observable + a finding?
Minutes
Minutes/Conclusions Reached:
- Jim had questions about the use of attribute bindings. Jay attempted to answer them, with the assistance of this slide.
- Jim still has misgivings about using Situation, at least partly due to potential conflict between absence values & findings.
- Jay to schedule offline review of requirements with Susan due to scheduling conflicts
- We need to address code vs reference for devices, procedures, etc.
- For the finding, we are interested in the type (cuff, scale, thermometer, etc.), not the device itself.
- But we might link to the device itself to support retrieval of the type
- Or we could assert that we don't care; if you link to support retrieval, go ahead and retrieve.
- If you need the device, record it under an actual procedure.
- If we decide we do need both, then are code & reference two distinct properties?
- Consider 'link' for typed references.
- Claude: slicing is difficult
- Jay: define archetypes for Braden parts & panel; include parts in panel. Is that slicing, & is it difficult?
- tabled
- Precondition range is limited
- some required precondition values are findings, some qualifiers.
- request expansion of range to accommodate non-lab
- or just use related finding instead
- Jay to provide Vitals use case to Linda for consideration (review with Claude)
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.
