Oracle Cloud Infrastructure Documentation

Service Request

Options to work with FHIR R4 Service Request resources.

The following example shows one possible ServiceRequest workflow. The requester and performer are optional. When present, the requester is not necessarily a provider. A request can be rejected, revoked, or otherwise end without fulfillment. A fulfilled request can lead to different clinical or administrative results.

[Request Created]
        |
        v
[ServiceRequest Resource Created]
        |
        v
[Optional requester and performer references]
        |
        v
[Request status progresses]
  +-----+-----------------------------+
  |                                   |
[Fulfilled]               [Ends without fulfillment]
  |
  v
[Optional resulting resource]

Primitive extension support

ServiceRequest supports primitive companion elements in underscore form for selected fields:

_asNeededBoolean, _authoredOn, _doNotPerform, _implicitRules, _instantiatesCanonical, _instantiatesUri, _intent, _language, _occurrenceDateTime, _patientInstruction, _priority, _status.

For JSON usage patterns, see FHIR primitive extensions in JSON.

Successful HTTP Responses

This table lists successful HTTP responses for this resource.

EndpointMethodSuccessful status code
/api/fhir/r4/ServiceRequest GET 200
/api/fhir/r4/ServiceRequest POST 201
/api/fhir/r4/ServiceRequest/$purgeDeleted POST 200
/api/fhir/r4/ServiceRequest/{rid} DELETE 204
/api/fhir/r4/ServiceRequest/{rid} GET 200
/api/fhir/r4/ServiceRequest/{rid} PUT 200
/api/fhir/r4/ServiceRequest/{rid}/$hardDelete POST 200
/api/fhir/r4/ServiceRequest/{rid}/_history/{vid} GET 200

For cross-resource interaction summaries, see FHIR status codes.

See also

For permanent deletion guidance, see Data deletion and purge operations.