This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Condition FHIR Resource Proposal"
Jump to navigation
Jump to search
| 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 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. | + | 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== | ==RIM scope== | ||
Revision as of 20:58, 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
Prolems are a common activity within medical practice and recorded by most EMR systems.
Expected implementations
Content sources
CCDA, openEHR, existing systems
