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



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

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