This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Negation Requirements Project Minutes 8 February 2017

From HL7Wiki
Revision as of 03:43, 9 February 2017 by Jlyle (talk | contribs) (→‎Meeting Information)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Back to Negation Minutes

Minutes

Meeting Information

HL7 PC-CIMI-POC Meeting Minutes

Location: PC call line

Date: 2017-01-24
Time: 11:00-12:00 ET
Facilitator Jay Lyle Note taker(s) Jay Lyle
Attendee Name Affiliation


y Jay Lyle JP Systems
y Lisa Nelson
y Ken Lord
y Rob Hausam
y Jaime Jouza
y Zahid Butt
y Andrew Haslam
Floyd Eisenberg
Susan Barber
Larry McKnight
Galen Mulrooney
Kurt Allen
Jim Case
Juliet Rubini
Hank Mayers

Agenda

Agenda Topics

  1. Ballot target: DAM; support for policy
  2. FHIR/CDA alignment
  3. Query sources

Minutes

Minutes/Conclusions Reached:

  1. Lisa's proposal: simply allow terminology in CCDA; this will support alignment with FHIR
    1. CCDA not ever easy to change, but industry is looking at it. If it can change, now is the time.
  2. Analysis positions:
    1. we want negation to be explicit (not buried in precoordinated terminology)
    2. we want negation to be concrete (not modeled as a Boolean)
    3. this means specifications should represent negation explicitly and concretely, or provide instructions on how to derive explicit & concrete information directly in the specification (i.e., not in a long separate document).
    4. Possible stronger statement: specifications should represent transform to 'other widely adopted specifications'
    5. Or even FHIR & CDA specifically?
      1. #2.4 allows extension in future. Look into mechanism for referring to current judgment on 'other widely adopted specifications'
  3. DAM for ballot
    1. Looks like a useful approach
    2. might help to map bits to RIM
    3. Ask ARB/TSC how this might support policy

Draft DAM Diagrams

NegationUseCases20160208.png

NegationClassModel20160208.png

Meeting Outcomes

Actions
  • review Use Cases for completeness, classification for accuracy (all)


Next Meeting/Preliminary Agenda Items
  • Continue review of requirements

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