Purge Deleted AllergyIntolerance

Purge Deleted AllergyIntolerance using FHIR R4 4.0.1.

Resource category: AllergyIntolerance.

Endpoint

MethodEndpoint
POST/api/fhir/r4/AllergyIntolerance/$purgeDeleted

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

Send Content-Type: application/fhir+json.

Parameters

ParameterLocationRequiredTypeDescription
beforeFHIR Parameters bodyYesdateTimeRequired FHIR dateTime cutoff supplied as Parameters.parameter.valueDateTime; deleted resources before this instant are purged.
limitFHIR Parameters bodyNointegerOptional maximum supplied as Parameters.parameter.valueInteger. The route accepts values from 1 through 50.

Authorization

ContextResource scope
Resource-server definition / issued tokensystem/AllergyIntolerance.d
Client grant / token requestddfssystem/AllergyIntolerance.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.

Example Request

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

POST /api/fhir/r4/AllergyIntolerance/$purgeDeleted
Content-Type: application/fhir+json

{
  "resourceType": "Parameters",
  "parameter": [
    {
      "name": "before",
      "valueDateTime": "2026-01-01T00:00:00Z"
    },
    {
      "name": "limit",
      "valueInteger": 10
    }
  ]
}

Responses

Successful statusMeaning
200An OperationOutcome describing the purge 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.