This wiki has undergone a migration to Confluence found Here

Difference between revisions of "OrderResponse FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "<div class="messagebox cleanup metadata"> <div style="float: left;">35px| </div> <div style="background:#F0F0F0"> This page documents a [[:category:Pen...")
 
Line 33: Line 33:
 
==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?>
 
<not sure - this is a core team resource - what is the project insight ID for that?>
 
+
952
 
==Scope of coverage==
 
==Scope of coverage==
  
Line 57: Line 57:
 
<!-- 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
 
ActClass = OBS and children
MoodCode = PRM
+
MoodCode = RQO and PRM
  
 
==Resource appropriateness==
 
==Resource appropriateness==

Revision as of 21:18, 22 May 2013



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

<not sure - this is a core team resource - what is the project insight ID for that?> 952

Scope of coverage

The response to an order indicates the outcome of processing the order itself - whether it was accepted or rejected, or is still in process. The order response resource does not itself convey or represent information that arises as a result of performing the actual order, but it may have references to other resources that do have this information, in order to link between the original order and it's outcome.

There may be multiple responses for a given order. For some requests, a responding system may issue a sequence of responses, where each response replaces previous responses as the original order is processed/performed. In these cases, each response should have the same logical identity, and the multiple responses are different versions of the same overall response.

If there are multiple systems responding to the request, or if there request may have multiple different responses, then the different logical responses should have different logical ids.

RIM scope

ActClass = OBS and children MoodCode = RQO and PRM

Resource appropriateness

<need text here >

Expected implementations

TBD

Content sources

  • HL7 v3 Laboratory Standard - Normative
  • HL7 v2.x
  • HL7 Radiology Report standards (for instance the DR Structured Report in C-CDA)
  • HL7 Laboratory Order Domain Analysis Model


Resource Relationships

  • Order
  • DiagnosticOrder
  • Specimen
  • Substance
  • Supply
  • ImagingStudy

Timelines

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

gForge Users

  • Patrick Loyd
  • Lorraine Constable