This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Negation Requirements"

From HL7Wiki
Jump to navigation Jump to search
Line 39: Line 39:
==Project Documents==
==Project Documents==
* [[Negation Requirements Statement]]
* [[Negation Requirements Statement]] page
* [[Media: NegationUseCases.xlsx | Use Cases]]
* [[Media: NegationUseCases.xlsx | Use Cases]]
* [[Negation Principles]]
* [[Negation Principles]]

Revision as of 13:20, 6 March 2017

Return to Patient Care

Return to Vocabulary

Project Information

Scope Statement

Scope: Provide a set of classified requirements for the representation of negated clinical data, which standards developers can use to confirm coverage of requirements, demonstrate recommended patterns, and identify out-of-specification patterns.

Need: The ways current interoperability standards handle negation, or propose to do so,

  • are inconsistent & may not support transformations among different standards
  • may not support representation requirements
  • may not support computation requirements

Having a consistently articulated set of clinical requirements will allow standards designers to confirm support for these requirements and to provide clear guidance on recommended and prohibited patterns.

Meeting Information


  • Collect examples - complete
  • Classify examples - complete
  • Identify other requirements
    • Query requirements in process
  • Review requirements with design teams
    • Draft for review in January
  • Assemble results

Issues/Hot Topics

  1. TermInfo currently responding to FHIR request regarding PC requirement for "no known allergies" in Allergy resource.
  2. CIMI on threshold of addressing a pattern for absent findings, other 'negation' topics.
    1. Pattern follows SCT: evaluations of observables may have negative results; Assertions may have 'absent' context values

Project Documents