Difference between revisions of "DiagnosticReport FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
 
(18 intermediate revisions by 4 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=
+
=DiagnosticReport=
  
<!-- Resource names should meet the following characteristics:
 
* Lower camel case
 
* U.S. English
 
* Domain-friendly
 
* Short
 
* Clear
 
* Unique
 
* Avoid non-universal abbreviations (e.g. URL would be ok)
 
* Be expressed as a noun
 
* Be consistent with other similar resources
 
-->
 
  
 
==Owning committee name==
 
==Owning committee name==
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
[[YourCommitteeName]]
+
[[Orders & Observations WG]]
  
 
==Interested Work Groups==
 
==Interested Work Groups==
  
 
<!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) -->
 
<!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) -->
* Work Group Name
+
 
* or link
+
* Anatomic Pathology
* or "None"
+
* Clinical Genomics
 +
* Imaging Integration
 +
* Public Health and Emergency Response
  
 
==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 45:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
 +
The findings and interpretation of diagnostic tests performed on patients and/or specimens. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretation, and formatted representation of diagnostic reports.
 +
 +
Note the use of the Observation resource to represent the actual result. There are many circumstances where the use of the Observation resource alone is sufficient to record clinical information, such as clinical observations made directly by a clinician or patient.
  
 
==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. -->
 +
ActClass = OBS and children
 +
MoodCode = EVN
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 74: Line 70:
 
* 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  
 
  -->
 
  -->
 +
 +
Diagnostic reporting is central to the business of healthcare.
 +
The basic process of healthcare is the diagnosis and treatment of patients. The diagnostic report is the primary means of communicating diagnostic results to providers, particularly in domains such as laboratory, radiology, pathology, etc.
  
 
==Expected implementations==
 
==Expected implementations==
 +
 +
Can be expected to be implemented by Diagnostic Laboratories, Radiology systems and specialist Investigation services (eg endoscopy services),  and to be consumed by EHR/PHR/EMR systems. 
  
 
<!-- 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) -->
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 Radiology Report standards (for instance the DR Structured Report in C-CDA)
 +
*OpenEHR?
 +
 +
 +
==Example Scenarios==
 +
* A report from a Laboratory after a blood test was ordered. May exist in multiple versions reflecting an interim report first, followed by a final report
 +
* A report from a Radiology service on Xrays taken after an injury
 +
* A pathologists report
 +
* A psychiatric assessment
 +
* A veterinary outbreak assessment
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 95: Line 110:
 
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
 +
*DiagnosticOrder
 +
*Observation
 +
*Specimen
 +
*Substance
 +
*Supply
 +
*ImagingStudy
  
 
==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.) -->
 +
*Patrick Loyd
 +
*Lorraine Constable
 +
 +
==Issues==
 +
* need to refine RIM definition to differentiate from observations
 +
* Does scope include things like psychiatric reports, reports on outbreaks, etc.?
 +
* What's the boundary between a diagnostic report and a Document containing observations?
 +
* Need to explain details about the relationships to other resources are

Latest revision as of 05:39, 22 May 2014



DiagnosticReport

Owning committee name

Orders & Observations WG

Interested Work Groups

  • Anatomic Pathology
  • Clinical Genomics
  • Imaging Integration
  • Public Health and Emergency Response

FHIR Resource Development Project Insight ID

952

Scope of coverage

The findings and interpretation of diagnostic tests performed on patients and/or specimens. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretation, and formatted representation of diagnostic reports.

Note the use of the Observation resource to represent the actual result. There are many circumstances where the use of the Observation resource alone is sufficient to record clinical information, such as clinical observations made directly by a clinician or patient.

RIM scope

ActClass = OBS and children MoodCode = EVN

Resource appropriateness

Diagnostic reporting is central to the business of healthcare. The basic process of healthcare is the diagnosis and treatment of patients. The diagnostic report is the primary means of communicating diagnostic results to providers, particularly in domains such as laboratory, radiology, pathology, etc.

Expected implementations

Can be expected to be implemented by Diagnostic Laboratories, Radiology systems and specialist Investigation services (eg endoscopy services), and to be consumed by EHR/PHR/EMR systems.


Content sources

  • HL7 v3 Laboratory Standard - Normative
  • HL7 v2.x
  • HL7 Radiology Report standards (for instance the DR Structured Report in C-CDA)
  • OpenEHR?


Example Scenarios

  • A report from a Laboratory after a blood test was ordered. May exist in multiple versions reflecting an interim report first, followed by a final report
  • A report from a Radiology service on Xrays taken after an injury
  • A pathologists report
  • A psychiatric assessment
  • A veterinary outbreak assessment

Resource Relationships

  • Order
  • OrderResponse
  • DiagnosticOrder
  • Observation
  • Specimen
  • Substance
  • Supply
  • ImagingStudy

Timelines

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

gForge Users

  • Patrick Loyd
  • Lorraine Constable

Issues

  • need to refine RIM definition to differentiate from observations
  • Does scope include things like psychiatric reports, reports on outbreaks, etc.?
  • What's the boundary between a diagnostic report and a Document containing observations?
  • Need to explain details about the relationships to other resources are