This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Condition FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 79: Line 79:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
Prolems are a common activity within medical practice and recorded by most EMR systems.  
+
 
 +
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==
 
==Expected implementations==
  

Revision as of 21:14, 3 June 2013



Problem

Owning committee name

Patient Care

(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

Content sources

CCDA, openEHR, existing systems

Example Scenarios

Resource Relationships

Timelines

gForge Users