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

Difference between revisions of "Negation Requirements"

From HL7Wiki
Jump to navigation Jump to search
Line 27: Line 27:
  
 
==Plan==
 
==Plan==
* Collect examples - complete
+
* Collect content requirements (examples) - in process
* Classify examples - complete
+
* Classify content examples - in process
 +
* Collect consumption requirements - in process
 +
** UI
 +
** Query
 +
** CDS
 +
* Classify consumption requirements - 
 +
* Collect compatibility requirements
 +
** V2, RIM, FHIR, CIMI, DL
 
* Identify other requirements
 
* Identify other requirements
** Query requirements in process
+
* Draft guidelines
* Review requirements with design teams
+
** Review requirements & guidelines with design teams
** Draft for review in January
+
* Draft document
* Assemble results
+
* Revise document
  
 
==Issues/Hot Topics==
 
==Issues/Hot Topics==

Revision as of 14:53, 21 June 2017


Return to Patient Care

Return to Vocabulary

Remember

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

Plan

  • Collect content requirements (examples) - in process
  • Classify content examples - in process
  • Collect consumption requirements - in process
    • UI
    • Query
    • CDS
  • Classify consumption requirements -
  • Collect compatibility requirements
    • V2, RIM, FHIR, CIMI, DL
  • Identify other requirements
  • Draft guidelines
    • Review requirements & guidelines with design teams
  • Draft document
  • Revise document

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


Categorization

[[Category:Active_Projects]]