This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Observation FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 12: Line 12:
  
  
=putProposedResourceNameHere=
+
=Observation=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 32: Line 32:
 
==Interested Work Groups==
 
==Interested Work Groups==
  
* Anatomic Pathology
+
* All
* Clinical Genomics
 
* Imaging Integration
 
* Public Health and Emergency Response
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
Line 54: Line 51:
 
  -->
 
  -->
  
DEFINITION (SPECIMEN):
+
DEFINITION (OBSERVATION):
Any material sample taken from a biological entity, including a sample obtained from a  living organism or taken from the biological object after halting of all its  life functions. Biospecimen can contain one or more components including but not limited to cellular molecules, cells, tissues, organs, body fluids, embryos, and  body excretory products (source: NCIt, modified).
 
  
The specimen resource covers substances used for diagnostic and environmental testingThis includes all types of living and non-living subjects where a subject is defined as the host from which the specimen was obtained.
+
The observation resource covers simple assertions and measurements made about a patient, device or other subject.
 +
   
 +
The resource name as it appears in a RESTful URL is /observation/
  
 
==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. -->
*Role: Specimen (RoleClass=SPM)
+
*ACT: Observation (ClassCode=OBS and descendants)
**Entity (player): Material (EntityClass="MAT")
+
*ACT: Observation (Code=ObservationType)
**Entity (scoper): Choice - Person, Non-Human Living Subject, Material)
 
*Entity: Place (EntityClass="PLC")
 
  
 
==Resource appropriateness==
 
==Resource appropriateness==
 
Simple assertions and measurements made about a patient, device or other subject.
 
 
The resource name as it appears in a RESTful URL is /observation/
 
  
 
Observations are a central element in healthcare, used to support diagnosis, monitor progress, determine baselines and patterns and even capture demographic characteristics. Fundamentally, observations are simple name/value pair assertions with little structure, though there are several resources such as DiagnosticReport to manage and represent rich aggregation patterns for observations. Expected uses for this resource include:
 
Observations are a central element in healthcare, used to support diagnosis, monitor progress, determine baselines and patterns and even capture demographic characteristics. Fundamentally, observations are simple name/value pair assertions with little structure, though there are several resources such as DiagnosticReport to manage and represent rich aggregation patterns for observations. Expected uses for this resource include:
•Vital signs: temperature, blood pressure, respiration rate
+
*Vital signs: temperature, blood pressure, respiration rate
•Laboratory Data and other Diagnostic Measures
+
*Laboratory Data and other Diagnostic Measures
•Measurements emitted by Devices
+
*Measurements emitted by Devices
•Clinical assessments such as APGAR
+
*Clinical assessments such as APGAR
•Personal characteristics: height, weight, eye-color
+
*Personal characteristics: height, weight, eye-color
•Diagnoses (Note: track-able conditions, allergies, adverse reactions and more complex structures are handled elsewhere)
+
*Diagnoses (Note: track-able conditions, allergies, adverse reactions and more complex structures are handled elsewhere)
•Social history: tobacco use, family supports, cognitive status
+
*Social history: tobacco use, family supports, cognitive status
•Core characteristics: pregnancy status, death assertion
+
*Core characteristics: pregnancy status, death assertion
  
 
==Expected implementations==
 
==Expected implementations==

Revision as of 18:44, 1 April 2013



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 assertions and measurements made about a patient, device or other subject.

The resource name as it appears in a RESTful URL is /observation/

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. Fundamentally, observations are simple name/value pair assertions with little structure, though there are several resources such as DiagnosticReport to manage and represent rich 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

Expected implementations

??

Content sources

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

Resource Relationships

  • Order
  • OrderResponse ?
  • DiagnosticReport
  • ImagingStudy ?
  • Problem

Timelines

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

gForge Users

  • Lorraine Constable
  • Patrick Loyd