DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

5.26 Resource OrderResponse - Content

This resource is marked as a draft.

Orders and Observations Work GroupMaturity Level: 0Compartments: Device, Patient, Practitioner

A response to an order.

5.26.1 Scope and Usage

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 its outcome.

5.26.2 Background and Context

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.

5.26.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. OrderResponse ΣDomainResourceA response to an order
... identifier Σ0..*IdentifierIdentifiers assigned to this order by the orderer or by the receiver
... request Σ1..1Reference(Order)The order that this is a response to
... date Σ0..1dateTimeWhen the response was made
... who Σ0..1Reference(Practitioner | Organization | Device)Who made the response
... orderStatus ?! Σ1..1codepending | review | rejected | error | accepted | cancelled | replaced | aborted | completed
OrderStatus (Required)
... description Σ0..1stringAdditional description of the response
... fulfillment Σ0..*Reference(Any)Details of the outcome of performing the order

doco Documentation for this format

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. OrderResponse ΣDomainResourceA response to an order
... identifier Σ0..*IdentifierIdentifiers assigned to this order by the orderer or by the receiver
... request Σ1..1Reference(Order)The order that this is a response to
... date Σ0..1dateTimeWhen the response was made
... who Σ0..1Reference(Practitioner | Organization | Device)Who made the response
... orderStatus ?! Σ1..1codepending | review | rejected | error | accepted | cancelled | replaced | aborted | completed
OrderStatus (Required)
... description Σ0..1stringAdditional description of the response
... fulfillment Σ0..*Reference(Any)Details of the outcome of performing the order

doco Documentation for this format

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

5.26.3.1 Terminology Bindings

PathDefinitionTypeReference
OrderResponse.orderStatus The status of the response to an order.RequiredOrderStatus

5.26.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
codetokenpending | review | rejected | error | accepted | cancelled | replaced | aborted | completedOrderResponse.orderStatus
datedateWhen the response was madeOrderResponse.date
fulfillmentreferenceDetails of the outcome of performing the orderOrderResponse.fulfillment
(Any)
identifiertokenIdentifiers assigned to this order by the orderer or by the receiverOrderResponse.identifier
requestreferenceThe order that this is a response toOrderResponse.request
(Order)
whoreferenceWho made the responseOrderResponse.who
(Device, Organization, Practitioner)