This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Negation Requirements"
Jump to navigation
Jump to search
Remember
(→Plan) |
|||
| 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 | + | # Draft document |
| − | # Revise document | + | # Revise document |
==Issues/Hot Topics== | ==Issues/Hot Topics== | ||
Revision as of 13:42, 22 September 2017
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 2017)
- Link to call: Fall 2017 planning in process
- Minutes
Plan
- Planning:
- choose meeting times for Fall 17
- plan tasks, roles.
- Complete collection of content requirements (examples) - Done
- 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
- Create outline
- Draft guidelines
- Review requirements & guidelines with design teams
- Draft document
- Revise document
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
- Document for ballot
- May ballot commments
- Negation Requirements Statement page
- Use Cases
- Negation Principles
- Negation Glossary
- Negation Sources
- Negation Outreach
- DAM
Categorization
[[Category:Active_Projects]]
