This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Negation Requirements Project Minutes 27 June 2018"
Jump to navigation
Jump to search
(Created page with "<!-- LOOK FOR THE APPROPRIATE SECTION ****** TO ENTER INFORMATION--> Back to Negation Minutes ==Minutes== ===Meeting Information=== {|border="1" cellpadding="2" cellspacin...") |
|||
Line 107: | Line 107: | ||
<!-- **** Delete instructions and fill in minutes ON NEXT LINES ******--> | <!-- **** Delete instructions and fill in minutes ON NEXT LINES ******--> | ||
− | # Schedule | + | # Schedule: Things are getting tight; those interested in seeing the work go forward please recruit resources. |
## 23-May choose meeting times | ## 23-May choose meeting times | ||
## 30-May agree on objectives; dispose ballot | ## 30-May agree on objectives; dispose ballot | ||
Line 113: | Line 113: | ||
## 13-Jun assign parts; review sample part for common look and feel | ## 13-Jun assign parts; review sample part for common look and feel | ||
## 20-Jun review drafts; agree on format -- not achieved. need samples for next week. | ## 20-Jun review drafts; agree on format -- not achieved. need samples for next week. | ||
− | ## 27-Jun review of chunk 1 | + | ## 27-Jun review of chunk 1 -- Note: schedule is yellow |
## 4-Jul review of chunk 2 | ## 4-Jul review of chunk 2 | ||
## 11-Jul review of chunk 3 | ## 11-Jul review of chunk 3 | ||
Line 123: | Line 123: | ||
## 19-Aug Final content submission due | ## 19-Aug Final content submission due | ||
# Examples: | # Examples: | ||
− | ## | + | ## George: family history. CCDA uses normal observation negation, with related subject in organizer. |
− | ## | + | ### FHIR uses terminology, like allergy. Only specified value is 'No current problems or disability' |
− | ## | + | ### [is there an allergy extension?] |
− | ## | + | ## Jay: allergy |
− | ## | + | ### *include verification status example - refuted. Only for phase 2, FHIR to CDA. |
− | ## | + | ### *include refutation of specific allergy. (done) |
− | ## | + | ### can we assert a pattern: no double negatives? |
− | ## | + | #### If a FHIR resource contains a negated code: both statuses should be null. |
− | ## | + | #### would we ever need to refute a negative? edge case. |
− | ## | + | #### what is case for refutation? |
− | ## | + | ##### only previously asserted, or include differential, suspected, or even not previously suspected? |
− | ## | + | ##### UI: just uncheck the box |
− | ## | + | ##### 'we'd never extract an allergy that wasn't active' |
− | ## | + | ###### is this an axiom? |
− | ## | + | ###### or might we need to support intra-system operations that do include refuted or inactive items? |
− | ## | + | ##### case: pt reports allergy, records it. Provider determines it's an intolerance, may give anyway. |
− | ## | + | ##### question of use of refuted: open. |
+ | ###### one option: if it's FHIR refuted, it doesn't go in CCDA. Or entered-in-error. | ||
+ | ####### and it likely won't be sent in FHIR. | ||
+ | ### current scope: CCDA to FHIR only, to start? | ||
+ | #### Lisa moves, Ken seconds: we're starting with CCDA to FHIR in this iteration and we'll return to address FHIR-to-C-CDA (5-0-0) | ||
===Meeting Outcomes=== | ===Meeting Outcomes=== |
Revision as of 21:54, 27 June 2018
Back to Negation Minutes
Minutes
Meeting Information
HL7 PC-CIMI-POC Meeting Minutes Location: PC call line |
Date: 2018-06-27 Time: 4:00-5:00 PM ET | ||
Facilitator | Jay Lyle | Note taker(s) | Jay Lyle |
Attendee | Name | Affiliation
| |
Jay Lyle | JP Systems | ||
Yanyan Hu | Joint Commission | ||
Senthil Nachimuthu | 3M | ||
Ken Lord | |||
Gay Dolin | IMO | ||
Rob Hausam | Optum | ||
George Dixon | Allscripts | ||
Lisa Nelson | |||
Emma Jones | Allscripts | ||
Agenda
Agenda Topics
- Review schedule draft
- Review sample examples
Minutes
- Schedule: Things are getting tight; those interested in seeing the work go forward please recruit resources.
- 23-May choose meeting times
- 30-May agree on objectives; dispose ballot
- 6-Jun agree on outline & schedule
- 13-Jun assign parts; review sample part for common look and feel
- 20-Jun review drafts; agree on format -- not achieved. need samples for next week.
- 27-Jun review of chunk 1 -- Note: schedule is yellow
- 4-Jul review of chunk 2
- 11-Jul review of chunk 3
- 18-Jul review of chunk 4
- 25-Jul review of chunk 5
- 1-Aug review of chunk 6
- 8-Aug final comments to editor
- 15-Aug finalize submission; due 8/19
- 19-Aug Final content submission due
- Examples:
- George: family history. CCDA uses normal observation negation, with related subject in organizer.
- FHIR uses terminology, like allergy. Only specified value is 'No current problems or disability'
- [is there an allergy extension?]
- Jay: allergy
- *include verification status example - refuted. Only for phase 2, FHIR to CDA.
- *include refutation of specific allergy. (done)
- can we assert a pattern: no double negatives?
- If a FHIR resource contains a negated code: both statuses should be null.
- would we ever need to refute a negative? edge case.
- what is case for refutation?
- only previously asserted, or include differential, suspected, or even not previously suspected?
- UI: just uncheck the box
- 'we'd never extract an allergy that wasn't active'
- is this an axiom?
- or might we need to support intra-system operations that do include refuted or inactive items?
- case: pt reports allergy, records it. Provider determines it's an intolerance, may give anyway.
- question of use of refuted: open.
- one option: if it's FHIR refuted, it doesn't go in CCDA. Or entered-in-error.
- and it likely won't be sent in FHIR.
- one option: if it's FHIR refuted, it doesn't go in CCDA. Or entered-in-error.
- current scope: CCDA to FHIR only, to start?
- Lisa moves, Ken seconds: we're starting with CCDA to FHIR in this iteration and we'll return to address FHIR-to-C-CDA (5-0-0)
- George: family history. CCDA uses normal observation negation, with related subject in organizer.
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items |
© 2012 Health Level Seven® International. All rights reserved.