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 38: Line 38:
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
* Work Group Name
+
None
* or link
 
* or "None"
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 +
 +
Pending
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 58: Line 58:
 
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.
  
 
==RIM scope==
 
==RIM scope==
Line 77: Line 78:
 
* 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.
 
==Expected implementations==
 
==Expected implementations==
  
Line 87: Line 88:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
CCDA, openEHR, existing systems
  
 
==Example Scenarios==
 
==Example Scenarios==

Revision as of 19:07, 3 June 2013



Problem

Owning committee name

YourCommitteeName 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.

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

Example Scenarios

Resource Relationships

Timelines

gForge Users