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

Difference between revisions of "Negation Requirements Project Minutes 6 April 2016"

From HL7Wiki
Jump to navigation Jump to search
 
Line 98: Line 98:
 
'''Minutes/Conclusions Reached:'''<br/>
 
'''Minutes/Conclusions Reached:'''<br/>
  
# Add link to PSS: it's on project wiki. Perhaps this referred to the TermInfo wiki.
+
# PSS status: still pending Vocab approval
## PSS status: still pending Vocab approval
+
# Reviewed FHIR/Allergy discussion on patterns. Use to confirm requirements can help make these decisions.
# Provenance
+
## single field, renamed from 'substance' to 'code' to accommodate negatives
## Provenance may affect interpretation of a negated fact, e.g., patient asserts no allergies. If there is a record of an reaction, this is reason to doubt such an assertion. However, positive assertions are also subject to trust and validation. Provenance is important, and may be a requirement for displaying allergy negation, but it's not specific to negation. This topic remains out of scope for this project.
+
## dual field: present things and absent things
# Use cases introduced by quality measure use case: need to identify actions not taken for cause.
+
## dual field: thing and presence vs absence value
## This information should not be specifically created for the measure calculation: if it's important enough for the measure, it should be in the record. Persistence is necessary to support cases such as "discontinued medication," which would presumably influence future opportunities for administration.
+
# Patterns
## QDM models a property, "negation rationale," for recording such causes.
+
## Pattern documentation does seem to make assumptions, not about information model solution but about terminology semantics
## Whether such a note automatically excludes a patient from the denominator depends on the design of the rule -- for some rules, there are value sets of valid exclusion kinds.
+
## Separation of the "absent" assertion from the thing that is absent seems clear, as well as possible context
## These reasons are not limited to contraindications; they may include patient refusal.
+
### though context of thing (patient, family) may be different from context of absence (today, historical)
## Note that the reason is distinct from the assertion that the act was not performed.
+
## The thing itself seems to align with the SCT idea of an observable; i.e., not a finding or anatomical entity. This may mean requesting new SCT concepts.
## There was some discussion of identifying whether an act is not done# "intentionally." The "reason" property seems to at least offer the ability to identify intentionally omitted acts, and possibly some unintentional. All unintentionally omitted acts would be an infinite set, so we are not concerned with modeling it.
+
### SCT is not the only target terminology solution, but it seems to be the richest, so we anticipate solutions that accommodate it will fit simpler ones, too
## Current systems handle this case in a variety of ways.
+
### If "spleen size" is one possible observable (values PQ, or ordinal small medium large), can "absent" describe an observable "spleen", or do we need a "spleen presence" observable?
### Reason may annotate the order.
 
### It may not be saved in a predictable place.
 
### CDA template design: _act.negation, entryRel.reason: observation reason.
 
## VA is considering ways to handle this issue.
 
## CQL logical design under discussion.
 
# New examples: see items 73 - 86 in spreadsheet.
 
# Examples other than observations
 
## Procedures & substance administrations pretty well covered above
 
## Encounter: follow-up not needed; patient did not show up
 
## Supply: did not provide electric wheelchair; did not use antithrombotic device on legs (as a supply item within a larger order or without order)
 
  
 
===Meeting Outcomes===
 
===Meeting Outcomes===

Latest revision as of 16:54, 6 April 2016


Back to Negation Minutes

Minutes

Meeting Information

HL7 PC-CIMI-POC Meeting Minutes

Location: PC call line

Date: 2016-03-30
Time: 11:00-12:00 ET
Facilitator Jay Lyle Note taker(s) Jay Lyle
Attendee Name Affiliation


Jay Lyle JP Systems
Serafina Versaggi
Lisa Nelson
Rob Hausam
Carmela Couderc

Agenda

Agenda Topics

  1. FHIR/allergy topic
  2. patterns

Minutes

Minutes/Conclusions Reached:

  1. PSS status: still pending Vocab approval
  2. Reviewed FHIR/Allergy discussion on patterns. Use to confirm requirements can help make these decisions.
    1. single field, renamed from 'substance' to 'code' to accommodate negatives
    2. dual field: present things and absent things
    3. dual field: thing and presence vs absence value
  3. Patterns
    1. Pattern documentation does seem to make assumptions, not about information model solution but about terminology semantics
    2. Separation of the "absent" assertion from the thing that is absent seems clear, as well as possible context
      1. though context of thing (patient, family) may be different from context of absence (today, historical)
    3. The thing itself seems to align with the SCT idea of an observable; i.e., not a finding or anatomical entity. This may mean requesting new SCT concepts.
      1. SCT is not the only target terminology solution, but it seems to be the richest, so we anticipate solutions that accommodate it will fit simpler ones, too
      2. If "spleen size" is one possible observable (values PQ, or ordinal small medium large), can "absent" describe an observable "spleen", or do we need a "spleen presence" observable?

Meeting Outcomes

Actions
  • review examples for completeness, classification for accuracy (all)
  • secure Vocabulary co-sponsorship (Rob H)
  • request involvement from SD & FHIR (Jay)
  • consolidate wiki pages (Jay)
Next Meeting/Preliminary Agenda Items
  • none identified

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