This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Negation Requirements Project Minutes 15 August 2018"
Jump to navigation
Jump to search
| Line 115: | Line 115: | ||
<!-- **** Delete instructions and fill in minutes ON NEXT LINES ******--> | <!-- **** Delete instructions and fill in minutes ON NEXT LINES ******--> | ||
| − | + | # family history updated (George) | |
| − | + | ## typically family history straightforward member and condition; no negations | |
| − | typically family history straightforward member and condition; no negations | + | ### CCDA: example is fine, but it's pretty rare to negate family history |
| − | + | ### breast cancer example of a condition where you might need a negation | |
| − | + | ### even breast cancer negation would tend to be in a progress note | |
| − | + | ### Issue of boundary between capture of data for human use and for automated processing | |
| − | + | ## no issues with CCDA example | |
| − | CCDA: example is fine, but it's pretty rare to negate family history | + | ## Issue: FHIR has two ways to go |
| − | + | ### precoordinated code or List with empty reason | |
| − | no issues with CCDA example | + | ### no example to instruct us which way to go |
| − | + | ### ask for one | |
| − | Issue: FHIR has two ways to go | + | ## clinical need: to negate a specific condition for a specific relation; not, typically "no known problems" |
| − | + | ### [track down fhir extension - allergyintolerance-substanceExposureRisk] | |
| − | no example to instruct us which way to go | + | ## List solution only addresses generic statement, not specific negation |
| − | ask for one | + | ### Also, Mappings that have already been done in CCDA on FHIR IG |
| − | + | #### CCDA set of conditions -> fhir conditions, not a List | |
| − | clinical need: to negate a specific condition for a specific relation | + | #### Implementer community seems to prefer not to use list |
| − | + | ## if precoordinated code exists 'no history of cancer' | |
| − | [track down fhir extension - allergyintolerance-substanceExposureRisk] | + | ### but none for a second disorder; use an expression? |
| − | List solution only addresses generic statement, not specific negation | + | ### burden on terminology |
| − | + | ## option: like Procedure, have a concrete tightly scoped property for presence/absence | |
| − | Mappings that have already been done in CCDA on FHIR IG | + | ### note: keep distinct from absence of data |
| − | + | ## proposition: CDA negation and FHIR 'no known' mean the same thing for all practical purposes. | |
| − | Implementer community seems to prefer not to use list | + | ### no dissent |
| − | + | ## Potential Rationale for when to use a list: to represent RIM Organizer | |
| − | if precoordinated code exists 'no history of cancer' | ||
| − | |||
| − | |||
| − | option: like Procedure, have a concrete tightly scoped property for presence/absence | ||
| − | |||
| − | |||
| − | proposition: CDA negation and FHIR 'no known' mean the same thing for all practical purposes. | ||
| − | |||
| − | |||
| − | Potential Rationale for when to use a list | ||
| − | |||
===Meeting Outcomes=== | ===Meeting Outcomes=== | ||
Revision as of 21:25, 15 August 2018
Back to Negation Minutes
Minutes
Meeting Information
| HL7 PC-CIMI-POC Meeting Minutes Location: PC call line |
Date: 2018-08-15 Time: 4:00-5:00 PM ET | ||
| Facilitator | Jay Lyle | Note taker(s) | Jay Lyle |
| Attendee | Name | Affiliation
| |
| y | Jay Lyle | JP Systems | |
| Yanyan Hu | Joint Commission | ||
| y | Senthil Nachimuthu | 3M | |
| y | Ken Lord | VA | |
| y | Rob Hausam | IMO | |
| Ben Hamlin | NCQA | ||
| y | Lisa Nelson | ||
| Emma Jones | Allscripts | ||
| y | George Dixon | Allscripts | |
| Michelle Miller | Cerner | ||
| y | Michael Padula | Cerner | |
| y | Stephen Chu | Joint Commission | |
Agenda
Agenda Topics
- review
- family history generic, including no history of x: George
Minutes
- family history updated (George)
- typically family history straightforward member and condition; no negations
- CCDA: example is fine, but it's pretty rare to negate family history
- breast cancer example of a condition where you might need a negation
- even breast cancer negation would tend to be in a progress note
- Issue of boundary between capture of data for human use and for automated processing
- no issues with CCDA example
- Issue: FHIR has two ways to go
- precoordinated code or List with empty reason
- no example to instruct us which way to go
- ask for one
- clinical need: to negate a specific condition for a specific relation; not, typically "no known problems"
- [track down fhir extension - allergyintolerance-substanceExposureRisk]
- List solution only addresses generic statement, not specific negation
- Also, Mappings that have already been done in CCDA on FHIR IG
- CCDA set of conditions -> fhir conditions, not a List
- Implementer community seems to prefer not to use list
- Also, Mappings that have already been done in CCDA on FHIR IG
- if precoordinated code exists 'no history of cancer'
- but none for a second disorder; use an expression?
- burden on terminology
- option: like Procedure, have a concrete tightly scoped property for presence/absence
- note: keep distinct from absence of data
- proposition: CDA negation and FHIR 'no known' mean the same thing for all practical purposes.
- no dissent
- Potential Rationale for when to use a list: to represent RIM Organizer
- typically family history straightforward member and condition; no negations
Meeting Outcomes
Actions
|
| Next Meeting/Preliminary Agenda Items Agenda for 8/1:
|
© 2012 Health Level Seven® International. All rights reserved.
