Difference between revisions of "Negation Requirements"

From HL7Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 27: Line 27:
  
 
==Plan==
 
==Plan==
# Planning:
+
# Collect content representation requirements (examples) - Done
## choose meeting times for Fall 17
+
# Classify content representation examples - Done
## plan tasks, roles.
+
# Collect consumption requirements - Done
# Complete collection of content requirements (examples) - Done
+
# Revise [[Negation project ballot outline | outline]]
# Classify content examples - in process
+
# Draft - Done
# Collect consumption requirements - in process
+
# Review
## UI
+
# Revision
## Query
+
# Presentation to sponsor WGs
## CDS
+
# Ballot submission
# Classify consumption requirements - 
 
# Collect compatibility requirements
 
## V2, RIM, FHIR, CIMI, DL
 
# Identify other requirements
 
# Create [[Negation project ballot outline | outline]]
 
# Draft guidelines
 
## Review requirements & guidelines with design teams
 
# Draft document 
 
# Revise document
 
  
 
==Issues/Hot Topics==
 
==Issues/Hot Topics==
Line 53: Line 44:
 
==Project Documents==
 
==Project Documents==
 
* [[Media: NegationDocument18.docx | 2018 Draft]]
 
* [[Media: NegationDocument18.docx | 2018 Draft]]
* [[Media: NegationDocument.docx | 2017 Document for ballot]]
+
* May 2017
* [[Media: HL7_XPARADIGM_NEGATION_R1_I1_2017MAY_Consolidated.xlsx | May ballot commments]]
+
** [[Media: NegationDocument.docx | 2017 Document for ballot]]
 +
** [[Media: HL7_XPARADIGM_NEGATION_R1_I1_2017MAY_Consolidated.xlsx | May 2017 ballot commments]]
 
* [[Negation Requirements Statement]] page
 
* [[Negation Requirements Statement]] page
 
* [[Media: NegationUseCases.xlsx | Use Cases]]
 
* [[Media: NegationUseCases.xlsx | Use Cases]]

Latest revision as of 15:38, 7 November 2018


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

Plan

  1. Collect content representation requirements (examples) - Done
  2. Classify content representation examples - Done
  3. Collect consumption requirements - Done
  4. Revise outline
  5. Draft - Done
  6. Review
  7. Revision
  8. Presentation to sponsor WGs
  9. Ballot submission

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]]