This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Negation Requirements Project Minutes 8 February 2017"
Jump to navigation
Jump to search
(One intermediate revision by the same user not shown) | |||
Line 47: | Line 47: | ||
|- | |- | ||
<!-- ********add attendee information here *********--> | <!-- ********add attendee information here *********--> | ||
− | | | + | | y || Jay Lyle |
|colspan="2"| JP Systems | |colspan="2"| JP Systems | ||
|- | |- | ||
− | | | + | | y || Lisa Nelson |
− | |colspan="2"| | + | |colspan="2"| |
|- | |- | ||
− | | | + | | y || Ken Lord |
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
− | | | + | | y || Rob Hausam |
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
− | | | + | | y || Jaime Jouza |
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
− | | | + | | y || Zahid Butt |
− | |colspan="2"| | + | |colspan="2"| |
|- | |- | ||
− | | | + | | y || Andrew Haslam |
|colspan="2"| | |colspan="2"| | ||
|- | |- |
Latest revision as of 03:43, 9 February 2017
Back to Negation Minutes
Contents
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
- Ballot target: DAM; support for policy
- FHIR/CDA alignment
- Query sources
Minutes
Minutes/Conclusions Reached:
- Lisa's proposal: simply allow terminology in CCDA; this will support alignment with FHIR
- CCDA not ever easy to change, but industry is looking at it. If it can change, now is the time.
- Analysis positions:
- we want negation to be explicit (not buried in precoordinated terminology)
- we want negation to be concrete (not modeled as a Boolean)
- 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).
- Possible stronger statement: specifications should represent transform to 'other widely adopted specifications'
- Or even FHIR & CDA specifically?
- #2.4 allows extension in future. Look into mechanism for referring to current judgment on 'other widely adopted specifications'
- DAM for ballot
- Looks like a useful approach
- might help to map bits to RIM
- Ask ARB/TSC how this might support policy
Draft DAM Diagrams
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.