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

Difference between revisions of "Negation Requirements Project Minutes 22 June 2016"

From HL7Wiki
Jump to navigation Jump to search
Line 121: Line 121:
 
##. Solution pending: see [https://github.com/esacinc/cql-formatting-and-usage-wiki/wiki/negation-in-qdm github page]
 
##. Solution pending: see [https://github.com/esacinc/cql-formatting-and-usage-wiki/wiki/negation-in-qdm github page]
 
#. Case list completeness (see spreadsheet: Use Cases)
 
#. Case list completeness (see spreadsheet: Use Cases)
##.  
+
##. Group requested to review use case list, ensure it's complete & correctly classified
 
#. Completeness tactics
 
#. Completeness tactics
FHIM
+
##. In process
Work groups
+
#. Semantics
Ontology guru outreach
+
##. Observable or finding: can we articulate an operational criterion for when to use which and why?
 +
###. No spleen vs no rash: is the "normal vs abnormal" axis relevant?
 +
###. What's abnormal may be normal for a context -- rash may be a common question for a viral infection exam
  
 
===Meeting Outcomes===
 
===Meeting Outcomes===

Revision as of 18:36, 23 June 2016


Back to Negation Minutes

Minutes

Meeting Information

HL7 PC-CIMI-POC Meeting Minutes

Location: PC call line

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


y Jay Lyle JP Systems
y Richard Esmond PenRad
Gerard Freriks
y Rob Hausam
Serafina Versaggi
Cynthia Barton NLM
y Viet Nguyen
y Floyd Eisenberg
y Susan Barber

Agenda

Agenda Topics

  1. . PSS status
  2. . Case list completeness (see spreadsheet: Use Cases)
  3. . Completeness tactics
    1. FHIM
    2. Work groups
    3. Ontology guru outreach

Minutes

Minutes/Conclusions Reached:

  1. . PSS status: MnM approves; Jay to return to DESD
  2. . CQF update
    1. . Need to allow "not done reason" on procedures that end up getting done anyway
    2. . Design proposals to represent procedures not done either
      1. . require queries to filter negated records, or
      2. . cause combinatorial explosion by defining classes for every negated situation
    3. . Solution pending: see github page
  3. . Case list completeness (see spreadsheet: Use Cases)
    1. . Group requested to review use case list, ensure it's complete & correctly classified
  4. . Completeness tactics
    1. . In process
  5. . Semantics
    1. . Observable or finding: can we articulate an operational criterion for when to use which and why?
      1. . No spleen vs no rash: is the "normal vs abnormal" axis relevant?
      2. . What's abnormal may be normal for a context -- rash may be a common question for a viral infection exam

Meeting Outcomes

Actions
  • review Use Cases for completeness, classification for accuracy (all)


Next Meeting/Preliminary Agenda Items
  • Continue review of requirements

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