Hard Delete Medication

Hard Delete Medication using FHIR R4 4.0.1.

Resource category: Medication.

Endpoint

MethodEndpoint
POST/api/fhir/r4/Medication/{rid}/$hardDelete

Use the R4 base URL from your DDFS instance. Send Authorization: Bearer <access-token> and accept application/fhir+json.

Parameters

ParameterLocationRequiredTypeDescription
ridPathYesFHIR logical IDThe logical ID of the Medication resource.

Authorization

ContextResource scope
Resource-server definition / issued tokensystem/Medication.d
Client grant / token requestddfssystem/Medication.d
Additional custom scopehttps://docs.oracle.com/iaas/device-data-fhir/scopes/hard-delete

Resource constraints still apply. Use the least privilege needed for this operation; see authentication and scope configuration.

Configure the Custom Hard-Delete Scope and follow the permanent-deletion policy.

Behavior

Permanently remove one already soft-deleted Medication resource and its history. A live resource must be soft-deleted first; attempting to hard-delete a live resource returns 409. Do not send a resource body.

Example Request

Replace the example logical IDs, version IDs and connection values with values for your workflow.

POST /api/fhir/r4/Medication/{rid}/$hardDelete

Responses

Successful statusMeaning
200An OperationOutcome describing the permanent-deletion result.

For common error statuses and FHIR-formatted error bodies, see OperationOutcome errors. Authentication/authorization responses follow the shared policy; a protected resource can be concealed as 404. See also interaction responses.