You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it should be possible to cascade delete resources. For example, at our test environment we have a need to cascade delete a device, including all related/linked observations. I'm aware about the ENFORCE_REFERENTIAL_INTEGRITY environment variable, however it should do more than that - remove all linked resources whenever needed.
In order to support the cascade devete, the FHIR server should be configured accordingly, user have to have sufficient permissions and _delete=cascade query parameter should be set or, alternativelly, the HTTP header: 'X-Cascade': 'delete' should be set.
First, the Cascading Deletes Enabled setting must be enabled on the FHIR Storage module.
Then, the user performing the operation must have the FHIR_DELETE_CASCADE_ALLOWED permission, as well as a specific permission allowing the child resource to be deleted. For example, you might grant the user the FHIR_DELETE_CASCADE_ALLOWED and FHIR_ALL_DELETE permissions.
DELETE /Patient/123?_cascade=delete or HTTP header set: DELETE /Patient/123 X-Cascade: delete
The text was updated successfully, but these errors were encountered:
Hi Sem, thanks for your issue. We decently will do more work regarding deletion and also #399. Did you especially refer to the way SmileCDR does Cascading Deletes?
it should be possible to cascade delete resources. For example, at our test environment we have a need to cascade delete a device, including all related/linked observations. I'm aware about the
ENFORCE_REFERENTIAL_INTEGRITY
environment variable, however it should do more than that - remove all linked resources whenever needed.In order to support the cascade devete, the FHIR server should be configured accordingly, user have to have sufficient permissions and _delete=cascade query parameter should be set or, alternativelly, the HTTP header: 'X-Cascade': 'delete' should be set.
DELETE /Patient/123?_cascade=delete
or HTTP header set:DELETE /Patient/123 X-Cascade: delete
The text was updated successfully, but these errors were encountered: