This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Observation FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
m (Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
 
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
 
<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 a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
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:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  
Line 13: Line 12:
  
  
−
=putProposedResourceNameHere=
+
=Observation=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 29: Line 28:
 
==Owning committee name==
 
==Owning committee name==
  
−
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
+
[[Orders & Observations WG]]
−
[[YourCommitteeName]]
 
  
 
==Interested Work Groups==
 
==Interested Work Groups==
  
−
<!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) -->
+
* All
−
* Work Group Name
 
−
* 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 -->
+
952
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 55: Line 50:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
 +
DEFINITION (OBSERVATION):
 +
 +
The observation resource covers simple as well as complex assertions and measurements made about a patient, specimen, device or other subject.
 +
 +
Fundamentally, observations can be as simple as name/value pair assertions with little structure, as well as observations nested within other observations to represent a rich and complex observation, although there are several resources such as DiagnosticReport to manage and represent aggregation patterns for observations. Expected uses for this resource include:
 +
*Vital signs: temperature, blood pressure, respiration rate
 +
*Laboratory Data and other Diagnostic Measures
 +
*Measurements emitted by Devices
 +
*Clinical assessments such as APGAR
 +
*Personal characteristics: height, weight, eye-color
 +
*Diagnoses (Note: track-able conditions, allergies, adverse reactions and more complex structures are handled elsewhere)
 +
*Social history: tobacco use, family supports, cognitive status
 +
*Core characteristics: pregnancy status, death assertion
  
 
==RIM scope==
 
==RIM scope==
  
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 +
*ACT: Observation (ClassCode=OBS and descendants)
 +
*ACT: Observation (Code=ObservationType)
  
 
==Resource appropriateness==
 
==Resource appropriateness==
  
−
<!-- Does the resource meet the following characteristics?
+
Observations are a central element in healthcare, used to support diagnosis, monitor progress, determine baselines and patterns and even capture demographic characteristics.
−
 
 
−
Must
 
−
* Represents a well understood, "important" concept in the business of healthcare
 
−
* Represents a concept expected to be tracked with distinct, reliable, unique ids
 
−
* Reasonable for the resource to be independently created, queried and maintained
 
−
 
 
−
Should
 
−
* Declared interest in need for standardization of data exchange</span>
 
−
* Resource is expected to contain an appropriate number of "core" (non-extension) data elements (in most cases, somewhere in the range of 20-50)
 
−
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document
 
−
-->
 
  
 
==Expected implementations==
 
==Expected implementations==
  
 
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource.  (Should ideally have multiple independent implementations) -->
 
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource.  (Should ideally have multiple independent implementations) -->
 +
Required for CCDA.  Referenced as part of DiagnosticReport.
  
 
==Content sources==
 
==Content sources==
Line 84: Line 85:
  
 
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? -->
 +
 +
*HL7 v3 Laboratory Standard - Normative
 +
*HL7 v2.x
 +
*HL7 OO Specimen DAM Project
 +
 +
==Example Scenarios==
 +
 +
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 95: Line 104:
 
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)
 
  -->
 
  -->
 +
*Order
 +
*DiagnosticOrder
 +
*DiagnosticReport
 +
*ImagingStudy
 +
*Problem
  
 
==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 -->
 +
 +
*Vote by WG (Ready for ballot): July 2013
 +
*Ballot: 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.) -->
 +
*Lorraine Constable
 +
*Patrick Loyd
 +
 +
==Issues==
 +
# Need to explicitly define the difference between this and: Alert, AllergyIntolerance, AdverseReaction, Condition, DeviceObservation, OperationOutcome and Questionaire
 +
# Need the RIM scope to exclude the content for Alert, AllergyIntolerance, etc.
 +
# Should be looking at OpenEHR too.  National projects?
 +
# Need to provide a description for all "related" resources - related how?
 +
# Need to add example scenarios

Latest revision as of 05:44, 22 May 2014

OpenHotTopic.GIF

This page documents an Approved FHIR Resource Proposal



Observation

Owning committee name

Orders & Observations WG

Interested Work Groups

  • All

FHIR Resource Development Project Insight ID

952

Scope of coverage

DEFINITION (OBSERVATION):

The observation resource covers simple as well as complex assertions and measurements made about a patient, specimen, device or other subject.

Fundamentally, observations can be as simple as name/value pair assertions with little structure, as well as observations nested within other observations to represent a rich and complex observation, although there are several resources such as DiagnosticReport to manage and represent aggregation patterns for observations. Expected uses for this resource include:

  • Vital signs: temperature, blood pressure, respiration rate
  • Laboratory Data and other Diagnostic Measures
  • Measurements emitted by Devices
  • Clinical assessments such as APGAR
  • Personal characteristics: height, weight, eye-color
  • Diagnoses (Note: track-able conditions, allergies, adverse reactions and more complex structures are handled elsewhere)
  • Social history: tobacco use, family supports, cognitive status
  • Core characteristics: pregnancy status, death assertion

RIM scope

  • ACT: Observation (ClassCode=OBS and descendants)
  • ACT: Observation (Code=ObservationType)

Resource appropriateness

Observations are a central element in healthcare, used to support diagnosis, monitor progress, determine baselines and patterns and even capture demographic characteristics.

Expected implementations

Required for CCDA. Referenced as part of DiagnosticReport.

Content sources

  • HL7 v3 Laboratory Standard - Normative
  • HL7 v2.x
  • HL7 OO Specimen DAM Project

Example Scenarios

Resource Relationships

  • Order
  • DiagnosticOrder
  • DiagnosticReport
  • ImagingStudy
  • Problem

Timelines

  • Vote by WG (Ready for ballot): July 2013
  • Ballot: September 2013

gForge Users

  • Lorraine Constable
  • Patrick Loyd

Issues

  1. Need to explicitly define the difference between this and: Alert, AllergyIntolerance, AdverseReaction, Condition, DeviceObservation, OperationOutcome and Questionaire
  2. Need the RIM scope to exclude the content for Alert, AllergyIntolerance, etc.
  3. Should be looking at OpenEHR too. National projects?
  4. Need to provide a description for all "related" resources - related how?
  5. Need to add example scenarios
Retrieved from "https://wiki.hl7.org/w/index.php?title=Observation_FHIR_Resource_Proposal&oldid=86957"