This wiki has undergone a migration to Confluence found Here
Negation Requirements Project Minutes 2 August 2017
Jump to navigation
Jump to search
Back to Negation Minutes
Minutes
Meeting Information
HL7 PC-CIMI-POC Meeting Minutes Location: PC call line |
Date: 2017-08-02 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 | Rob Hausam | ||
y | Craig Newman | ||
Rita Pyle | |||
Richard Esmond | |||
Andrew Haslam | |||
Floyd Eisenberg | |||
Susan Barber | |||
Larry McKnight | |||
Galen Mulrooney | |||
Kurt Allen | |||
Jim Case | |||
Juliet Rubini | |||
Hank Mayers | |||
Agenda
Agenda Topics
- Agenda review
- Review of suggested quality measures (eCQI)
- Other usage cases
- Class coverage & definition
- Impact on problem statement
Minutes
Minutes/Conclusions Reached:
- Motivations for attending
- Craig: 5 years ago, OO discussion on how to record Salmonella not found in V2. For a Sal specific test, Negative works fine. For a general Micro ID test, Sal means Sal found. If you find E coli but no Sal, how do you say no Sal?
- Lisa
- How to harmonize CDA & FHIR so you can transform one into the other
- Ensure solution is comprehensible. And Document.
- Agree with position: "Negation" may be one problem for logicians, but the domain problems we face are different. Assuming it's one problem that can be solved with a common abstract design actually makes the problems worse.
- CDA examples task force is making decisions with minimal input; we need to check them out.
- E.g., prohibition on using "no known" concepts in value properties
- The idea that the CDA boat has sailed is not persuasive. There are many years left in its lifespan, and it should be fixed where broken.
- Input for 2.0 now, 2.1 in ballot. And FHIR.
- Who is target audience? Standards designers, not implementers. This needs to be clearer.
- ECQI input
- Negation is used in specifications and patterns
- See QRDA I guide for suggested mapping from CDA document artifacts to QRDA measure format. Also paragraphs on negation in Vol 1.
- Note that QRDA negated Observation may be based on a CDA procedure not done.
- Other uses
- Glimpse of VA project to identify SCT values with implicit negation
- Explicit negation (i.e., in Situation hierarchy) not a problem: this can be identified for special handling
- Implicitly negated values need to be flagged so that logical inference doesn't get tripped up
- Note that we're not trying to completely automate medicine & make people unnecessary
- But rules can support and assist clinical processes
- Role of project:
- Not to dictate to designers how to design
- but to dictate that designers explicitly address negative cases in their guidance to implementers. Perhaps a maturity checklist can address this.
- Glimpse of VA project to identify SCT values with implicit negation
- Next week: focus on picture. Some readers find pictures easier than words.
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.