This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Health Condition List"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* Standard representation of sub-concerns | * Standard representation of sub-concerns | ||
* Standard representation of common attributes about a problem (eg clinical status, problem severity, etc) | * Standard representation of common attributes about a problem (eg clinical status, problem severity, etc) | ||
| − | * Methods for | + | * Methods for adding diagnosis specific attributes (eg Cancer Stage, CHF Class,...) |
| + | * Correct representation of problem modifiers and negation. (eg rule out MI, or history of MI vs AMI) | ||
| + | * List maintenance issues in messaging. (eg send full list including history, send full list, but no history, only send updates for a concern) | ||
== Artifacts and related modeling == | == Artifacts and related modeling == | ||
Revision as of 21:39, 15 January 2008
Contents
Project Summary
Concern Tracking and Care statements provide a framework for tracking and managing health concerns, however there are many undefined relationships and representations that remain to be defined. Issues identified include.
- Standard representation of how observations should be characterized (eg diagnosis vs problem)
- Standard representation of distinction and linkage between provider roles in problem lists (eg nursing problems vs physician problems).
- Standard representation of sub-concerns
- Standard representation of common attributes about a problem (eg clinical status, problem severity, etc)
- Methods for adding diagnosis specific attributes (eg Cancer Stage, CHF Class,...)
- Correct representation of problem modifiers and negation. (eg rule out MI, or history of MI vs AMI)
- List maintenance issues in messaging. (eg send full list including history, send full list, but no history, only send updates for a concern)
todo: ISO 18104, ISO 22789, ISO 13940, CCD
