Hard Delete DocumentReference

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

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.

Permanently remove one already soft-deleted DocumentReference 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.

• Permanent deletion: shared operation semantics.
• DocumentReference resource guidance: resource-specific requirements and restrictions.
• R4 CapabilityStatement and R4 metadata: supported capabilities.

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

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

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.

FHIR R4 definition: https://hl7.org/fhir/R4/documentreference.html. Canonical profile URI: http://hl7.org/fhir/StructureDefinition/DocumentReference.

This is a DDFS custom operation. Definition: ddfs-r4-hardDelete.json.

• Search DocumentReference
• Read DocumentReference
• Read DocumentReference Version
• Create DocumentReference
• Update DocumentReference
• Delete DocumentReference
• Purge Deleted DocumentReference