Difference between revisions of "Condition FHIR Resource Proposal"
| Line 124: | Line 124: | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| − | + | Expected to be balloted DSTU in September 2013 | |
==gForge Users== | ==gForge Users== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| + | david_hay | ||
Revision as of 21:32, 3 June 2013
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Problem
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
Problem
Owning committee name
(Temporarily managed by FHIR Core with review from Patient care)
Contributing or Reviewing Work Groups
None
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
Used to record detailed information about problems or diagnoses recognised by a clinician. There are many uses including: recording a Diagnosis during an Visit; populating a Problem List or a Summary Statement, such as a Discharge Summary. It excludes conditions for which there are more specific resources - such as allergies, procedures or immunizations.
RIM scope
Resource appropriateness
The recording of a patients problems and diagnoses are a common activity within medical practice. Exmaples of their use include:
- Most clinical encounters are assigned to a problem or problems.
- An up to date problem list is one of the cornerstones of clinical practice, are are implemented by most, if not all EMR systems.
- Problems (active and inactive) are a part of most CDA documents
Expected implementations
Most clinical systems and communications between clinical systems
Content sources
CCDA, openEHR, existing systems
Example Scenarios
Resource Relationships
The problem resource is linked to:
- Patient resource as the subject
- Visit resource to indicate the visit where the problem was first asserted
- Practitioner & Patient resource to indicated who is asserting this problem
Plus links as appropriate to any other resource for assessment of stage, evidence for the problem and related items
Timelines
Expected to be balloted DSTU in September 2013
gForge Users
david_hay
