Difference between revisions of "2016-10-19PC DrugAllergySubstance Call Minutes"

Revision as of 13:52, 19 October 2016

HL7 Negation Requirements Meeting Minutes Location: Phone		Date: 2016-10-19 Time: 9:00-10:00 ET
Facilitator	Jay Lyle	Note taker(s)	Jay Lyle

Attendee	Name	Affiliation
y	Jay Lyle	JP Systems / VA
y	Froukje Harkes-Idzinga	Nictiz
y	Rob Hausam	Hausam Consulting
y	Serafina Versaggi	Versaggi Consulting
y	Joe Quinn	Optum

Agenda Topics

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)

Actions

Next Meeting/Preliminary Agenda Items

@@ Line 79: / Line 79: @@
 ===Agenda===
 '''Agenda Topics''' <br/>
-# review assessment content requirements
+# confirm goals
-## how many 'about' codes
+# address open questions
-## body site: coded, with modifier, and * (contiguous)
+# identify gaps & tasks
-## 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===