This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Observation FHIR Resource Proposal"
Jump to navigation
Jump to search
m (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| 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> | ||
| Line 29: | Line 28: | ||
==Owning committee name== | ==Owning committee name== | ||
| − | + | [[Orders & Observations WG]] | |
| − | [[ | ||
==Interested Work Groups== | ==Interested Work Groups== | ||
| − | + | * Anatomic Pathology | |
| − | * | + | * Clinical Genomics |
| − | * | + | * Imaging Integration |
| − | * | + | * Public Health and Emergency Response |
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| − | + | 952 | |
==Scope of coverage== | ==Scope of coverage== | ||
| Line 55: | Line 53: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | DEFINITION (SPECIMEN): | ||
| + | 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 testing. This includes all types of living and non-living subjects where a subject is defined as the host from which the specimen was obtained. | ||
==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) | ||
| + | **Entity (player): Material (EntityClass="MAT") | ||
| + | **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: | |
| − | + | •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== | ==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) --> | ||
| + | ?? | ||
==Content sources== | ==Content sources== | ||
| Line 84: | Line 93: | ||
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 v3 Other? | ||
| + | *HL7 v2.x | ||
| + | *HL7 OO Specimen DAM Project | ||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 95: | Line 109: | ||
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 | ||
| + | *OrderResponse ? | ||
| + | *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 | ||
Revision as of 18:37, 1 April 2013
This page documents a Pending FHIR Resource Proposal
Contents
putProposedResourceNameHere
Owning committee name
Interested Work Groups
- Anatomic Pathology
- Clinical Genomics
- Imaging Integration
- Public Health and Emergency Response
FHIR Resource Development Project Insight ID
952
Scope of coverage
DEFINITION (SPECIMEN): 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 testing. This includes all types of living and non-living subjects where a subject is defined as the host from which the specimen was obtained.
RIM scope
- Role: Specimen (RoleClass=SPM)
- Entity (player): Material (EntityClass="MAT")
- Entity (scoper): Choice - Person, Non-Human Living Subject, Material)
- Entity: Place (EntityClass="PLC")
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: •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
