Difference between revisions of "Negation Requirements"

From HL7Wiki
Jump to navigation Jump to search
Line 28: Line 28:
  
 
==Plan==
 
==Plan==
 +
# Planning:
 +
## choose meeting times for Fall 17
 +
## plan tasks, roles.
 
# Complete collection of content requirements (examples) - Done
 
# Complete collection of content requirements (examples) - Done
 
# Classify content examples - in process
 
# Classify content examples - in process
Line 41: Line 44:
 
# Draft guidelines
 
# Draft guidelines
 
## Review requirements & guidelines with design teams
 
## Review requirements & guidelines with design teams
# Draft document - First draft by September WG; identify roles for review & revision
+
# Draft document
# Revise document - submit NIB in October
+
# Revise document
  
 
==Issues/Hot Topics==
 
==Issues/Hot Topics==

Revision as of 13:42, 22 September 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

  1. Planning:
    1. choose meeting times for Fall 17
    2. plan tasks, roles.
  2. Complete collection of content requirements (examples) - Done
  3. Classify content examples - in process
  4. Collect consumption requirements - in process
    1. UI
    2. Query
    3. CDS
  5. Classify consumption requirements -
  6. Collect compatibility requirements
    1. V2, RIM, FHIR, CIMI, DL
  7. Identify other requirements
  8. Create outline
  9. Draft guidelines
    1. Review requirements & guidelines with design teams
  10. Draft document
  11. 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]]