This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Negation Requirements"
Jump to navigation
Jump to search
(→Plan) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
Return to [[Vocabulary]] | Return to [[Vocabulary]] | ||
| − | |||
==Project Information== | ==Project Information== | ||
| Line 28: | Line 27: | ||
==Plan== | ==Plan== | ||
| − | # | + | # Collect content representation requirements (examples) - Done |
| − | + | # Classify content representation examples - Done | |
| − | + | # Collect consumption requirements - Done | |
| − | + | # Revise [[Negation project ballot outline | outline]] | |
| − | # Classify content examples - | + | # Draft - Done |
| − | # Collect consumption requirements - | + | # Review |
| − | # | + | # Revision |
| − | + | # Presentation to sponsor WGs | |
| − | + | # Ballot submission | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | # Draft | ||
| − | ## | ||
| − | # | ||
| − | # | ||
==Issues/Hot Topics== | ==Issues/Hot Topics== | ||
| Line 54: | 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: 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
- Link to call project meeting schedule (Summer 2018)
- Link to call: Fall 2017 planning in process
- Minutes
Plan
- Collect content representation requirements (examples) - Done
- Classify content representation examples - Done
- Collect consumption requirements - Done
- Revise outline
- Draft - Done
- Review
- Revision
- Presentation to sponsor WGs
- Ballot submission
Issues/Hot Topics
- TermInfo currently responding to FHIR request regarding PC requirement for "no known allergies" in Allergy resource.
- CIMI on threshold of addressing a pattern for absent findings, other 'negation' topics.
- Pattern follows SCT: evaluations of observables may have negative results; Assertions may have 'absent' context values
Project Documents
- 2018 Draft
- May 2017
- Negation Requirements Statement page
- Use Cases
- Negation Principles
- Negation Glossary
- Negation Sources
- Negation Outreach
- DAM
- Negation transform examples
Categorization
[[Category:Active_Projects]]
