Difference between revisions of "Condition FHIR Resource Proposal"
| (6 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents | + | This page documents an [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 59: | Line 59: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| − | Used to record detailed information about | + | Used to record detailed information about a specific issue with the health state of a patient. It is intended for use for issues that have been identified as relevant for tracking and reporting purposes or where there's a need to capture a concrete diagnosis the gathering of data such as signs and symptoms. However, there are situations where the same information might appear as both an Observation as well as a Condition. For example, the appearance of a rash or an instance of a fever are signs and symptoms that would typically be captured using the Observation resource. However, a pattern of ongoing fevers or a persistent or severe rash requiring treatment might be captured as a Condition. The Condition resource specifically excludes AdverseReactions and AllergyIntolerances as those are handled with their own resources. |
| + | |||
| + | Conditions are frequently referenced by other resources as "reasons" for an action (Prescription, Procedure, DiagnosticOrder, etc.) | ||
==RIM scope== | ==RIM scope== | ||
| Line 89: | Line 91: | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | |||
| + | Most clinical systems and communications between clinical systems | ||
==Content sources== | ==Content sources== | ||
| Line 111: | Line 115: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | 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 indicate 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== | ==Timelines== | ||
<!-- 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 | ||
Latest revision as of 05:37, 22 May 2014
This page documents an Approved 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 a specific issue with the health state of a patient. It is intended for use for issues that have been identified as relevant for tracking and reporting purposes or where there's a need to capture a concrete diagnosis the gathering of data such as signs and symptoms. However, there are situations where the same information might appear as both an Observation as well as a Condition. For example, the appearance of a rash or an instance of a fever are signs and symptoms that would typically be captured using the Observation resource. However, a pattern of ongoing fevers or a persistent or severe rash requiring treatment might be captured as a Condition. The Condition resource specifically excludes AdverseReactions and AllergyIntolerances as those are handled with their own resources.
Conditions are frequently referenced by other resources as "reasons" for an action (Prescription, Procedure, DiagnosticOrder, etc.)
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 indicate 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
