2016-10-19PC DrugAllergySubstance Call Minutes

Back to Negation_Requirements

Minutes Template

Meeting Information

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

Agenda Topics

1. review assessment content requirements
   1. how many 'about' codes
   2. body site: coded, with modifier, and * (contiguous)
   3. can we make 'related observation' more specific?
   4. composition: lab/exam then qual/quant, or vice versa? or compositional?
2. review assertion content requirements
   1. course & mechanism are precoordinated in SCT
   2. drainage:
      1. confirm type list
      2. status: values?
      3. qualitative volume values?
   3. undermining & tunneling:
      1. properties, or new associated lesions? restrict their properties?
      2. normalize dimensional measurements to a single 'dimension/magnitude' property?
3. concept alignment
   1. Is an assertion a finding?
   2. 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 begin construction of test classes

Next Meeting/Preliminary Agenda Items Review test class progress & tooling

© 2012 Health Level Seven® International. All rights reserved.