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

Difference between revisions of "Negation Requirements Project Minutes 15 August 2018"

From HL7Wiki
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  ******-->
  
−
* Review of minutes from 7/25
+
* family history updated
−
# case 1 Clinical use. Specific. Intended time important for missed repeating dose.
+
 
−
## got 8:00 & 4:00 but not 12:00 dose.
+
typically family history straightforward member and condition; no negations
−
# case 2 quality measure
+
breast cancer example of a condition where you might need a negation
−
## Use encounter time (not given during encounter)?
+
 
−
## Or quality rule parameter (not given in accordance with rule; e.g., within 4 hours of presentation)
+
doc is old; xls is revised; added FHIR
−
## Quality team is looking for a reason. date and time not important to receiver
+
 
−
## some facilities will include even out-of-spec data, e.g., 5 hours
+
CCDA: example is fine, but it's pretty rare to negate family history
−
### some won't
+
even breast cancer negation would tend to be in a progress note
−
# case 3 timeframe of Reason?
+
no issues with CCDA example
−
## hearing screening not performed; patient in incubator
+
 
−
### does incubator time have to cover encounter time or rule-defined time?
+
Issue: FHIR has two ways to go
−
### probably an audit function; not main process
+
precoordinated code or List with empty reason
−
### Quality team: all data may be in QRDA, but if reason applies within timeframe, it's a pass
+
no example to instruct us which way to go
−
# case 4: Documentation time for statusReason?
+
ask for one
−
## hard to see a rationale. can be reconstructed from Resource.Meta.lastUpdated
+
 
−
# can we test these?
+
clinical need: to negate a specific condition for a specific relation
−
## i.e., put into the spreadsheet comparison format
+
not "no known problems"
−
## and then query live data? maybe Phase II.
+
[track down fhir extension - allergyintolerance-substanceExposureRisk]
−
# Out of time; will review 8/1 next week, then smoking status.
+
List solution only addresses generic statement, not specific negation
 +
 
 +
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
 +
 
 +
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
 +
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
  
 
===Meeting Outcomes===
 
===Meeting Outcomes===

Revision as of 21:21, 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

  1. review
    1. family history generic, including no history of x: George

Minutes

  • family history updated

typically family history straightforward member and condition; no negations breast cancer example of a condition where you might need a negation

doc is old; xls is revised; added FHIR

CCDA: example is fine, but it's pretty rare to negate family history even breast cancer negation would tend to be in a progress note 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 "no known problems" [track down fhir extension - allergyintolerance-substanceExposureRisk] List solution only addresses generic statement, not specific negation

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

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 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

Meeting Outcomes

Actions
  • stakeholders interested in completion, secure resources
  • review posted document draft, examples


Next Meeting/Preliminary Agenda Items

Agenda for 8/1:

  • tbd

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

Retrieved from "https://wiki.hl7.org/w/index.php?title=Negation_Requirements_Project_Minutes_15_August_2018&oldid=160020"