This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Order FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
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==

Revision as of 20:58, 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?>

Scope of coverage

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.

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.

RIM scope

ActClass = OBS and children MoodCode = RQO

Resource appropriateness

Diagnostic orders are central to the business of healthcare. 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.

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 Nutrition Order v3 Standard
  • HL7 Laboratory Order Domain Analysis Model


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