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

Difference between revisions of "Order FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
<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 19: Line 19:
 
<!-- 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. -->
 
[[FHIR Core Team]]
 
[[FHIR Core Team]]
 +
But: OO will have eventual responsibility and has filled out the paperwork
  
 
==Interested Work Groups==
 
==Interested Work Groups==
Line 31: Line 32:
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
−
<not sure - this is a core team resource - what is the project insight ID for that?>
+
Pending
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 46: Line 47:
 
  -->
 
  -->
  
−
An order resource describes an order for an action be performed. An order is expected to lead to one or more responses that describe the outcome of processing/handling the order. The order resource is focused on the process of actually requesting an action be performed; the actual action to be performed is detailed in a separate resource that contains the details. Note that orders are often called "requests", but this name is not used here since the word "request" is used differently elsewhere in this specification.
+
An order resource describes a request for an action be performed. An order is expected to lead to one or more responses that describe the outcome of processing/handling the order. The order resource is focused on the process of actually requesting an action be performed; the actual action to be performed is detailed in a separate resource that contains the details. Note that orders are often called "requests", but this name is not used here since the word "request" is used differently elsewhere in this specification.
  
 
Note that there are a variety of processes associated with making and processing orders. Some orders may be handled immediately by automated systems but most require real world actions by one or more humans. Some orders can only be processed when other real world actions happen, such as a patient actually presenting themselves so that the action to be performed. Often these real world dependencies are only implicit in the order details.
 
Note that there are a variety of processes associated with making and processing orders. Some orders may be handled immediately by automated systems but most require real world actions by one or more humans. Some orders can only be processed when other real world actions happen, such as a patient actually presenting themselves so that the action to be performed. Often these real world dependencies are only implicit in the order details.
 +
 +
Several resources including CarePlan, DiagnosticOrder and MedicationPrescription represent requests, intentions or authorizations for some sort of activity to occur.  However, these resources don't specifically direct the fulfilment of the order.  I.e. they indicate what the clinician intends to happen, but don't actually initiate the workflow.  The Order resource is used to initiate and manage the workflow.
  
 
==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
+
Act (classCode=ACTN, moodCode=RQO)
−
MoodCode = RQO
 
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 71: Line 73:
 
  -->
 
  -->
  
−
Diagnostic orders are central to the business of healthcare.
+
Workflow is key to real-world processes, including in healthcare. While simple workflows can be handled via messaging events, more sophisticated workflows, particularly those requiring human action need to be persisted as resources.
−
The basic process of healthcare is the diagnosis and treatment of patients. The diagnostic order is the primary means of allowing providers to request diagnostic services, in domains such as laboratory, radiology, pathology, etc.
+
 
 +
==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.) -->
  
 
==Expected implementations==
 
==Expected implementations==
Line 87: Line 92:
  
  
−
*HL7 v3 Laboratory Standard - Normative
+
*HL7 v3 ControlAct wrapper
−
*HL7 v2.x
+
*HL7 v2.x EVN/ORC
−
*HL7 Radiology Report standards (for instance the DR Structured Report in C-CDA)
 
−
*HL7 Nutrition Order v3 Standard
 
−
*HL7 Laboratory Order Domain Analysis Model
 
  
  
Line 123: Line 125:
 
*Patrick Loyd
 
*Patrick Loyd
 
*Lorraine Constable
 
*Lorraine Constable
 +
 +
 +
==Issues==
 +
* Added to the scope.  Make sure you're comfortable with the changes
 +
* Revamped RIM mapping - make sure you're ok with that too
 +
* Fixed copy paste in resource appropriateness
 +
* Need to add in example scenarios.  Probably one for a fulfillment request on an order, one to stop an order, one for a query, etc.
 +
* Changed content sources (presume fixing a copy/paste)
 +
* Need to indicate how the different resources are related.

Latest revision as of 05:45, 22 May 2014

OpenHotTopic.GIF

This page documents an Approved FHIR Resource Proposal



Order

Owning committee name

FHIR Core Team But: OO will have eventual responsibility and has filled out the paperwork

Interested Work Groups

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

FHIR Resource Development Project Insight ID

Pending

Scope of coverage

An order resource describes a request for an action be performed. An order is expected to lead to one or more responses that describe the outcome of processing/handling the order. The order resource is focused on the process of actually requesting an action be performed; the actual action to be performed is detailed in a separate resource that contains the details. Note that orders are often called "requests", but this name is not used here since the word "request" is used differently elsewhere in this specification.

Note that there are a variety of processes associated with making and processing orders. Some orders may be handled immediately by automated systems but most require real world actions by one or more humans. Some orders can only be processed when other real world actions happen, such as a patient actually presenting themselves so that the action to be performed. Often these real world dependencies are only implicit in the order details.

Several resources including CarePlan, DiagnosticOrder and MedicationPrescription represent requests, intentions or authorizations for some sort of activity to occur. However, these resources don't specifically direct the fulfilment of the order. I.e. they indicate what the clinician intends to happen, but don't actually initiate the workflow. The Order resource is used to initiate and manage the workflow.

RIM scope

Act (classCode=ACTN, moodCode=RQO)

Resource appropriateness

Workflow is key to real-world processes, including in healthcare. While simple workflows can be handled via messaging events, more sophisticated workflows, particularly those requiring human action need to be persisted as resources.

Example Scenarios

Expected implementations

TBD

Content sources

  • HL7 v3 ControlAct wrapper
  • HL7 v2.x EVN/ORC


Resource Relationships

  • OrderResponse
  • DiagnosticOrder
  • Specimen
  • Substance
  • Supply
  • ImagingStudy

Timelines

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

gForge Users

  • Patrick Loyd
  • Lorraine Constable


Issues

  • Added to the scope. Make sure you're comfortable with the changes
  • Revamped RIM mapping - make sure you're ok with that too
  • Fixed copy paste in resource appropriateness
  • Need to add in example scenarios. Probably one for a fulfillment request on an order, one to stop an order, one for a query, etc.
  • Changed content sources (presume fixing a copy/paste)
  • Need to indicate how the different resources are related.
Retrieved from "https://wiki.hl7.org/w/index.php?title=Order_FHIR_Resource_Proposal&oldid=86959"