Skip to content

Commit a686823

Browse files
Merge pull request #284117 from EXPEkesheth/patch-177
Update fhir-bulk-delete-operation.md
2 parents 31300ee + d3506b5 commit a686823

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

articles/healthcare-apis/includes/fhir-bulk-delete-operation.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,14 @@ Here's a list of error messages that might occur if the `$bulk-delete` operation
111111
112112
## FAQ
113113
114+
- I have soft deleted resources, what are the steps I can take to hard delete the resources?<br/><br> To hard delete, soft deleted resources use operation $bulk-delete-soft-deleted.
115+
Sample request
116+
request:
117+
118+
```
119+
{{fhir_url}}/<resource type>/$bulk-delete-soft-deleted
120+
```
121+
114122
- My `$bulk-delete` job seems to be stuck. What are the steps for resolution?<br/><br/> To check if a `$bulk-delete` job is stuck, run a FHIR search with the same parameters as the bulk delete job and _summary=count. If the count of resources is going down, the job is working. You can also cancel the `$bulk-delete` job and try again.
115123
116124
- Do API interactions see any latency impact when a `$bulk-delete` operation job is executed concurrently?<br/><br/>When you run a `$bulk-delete` operation, you might see increased latency on concurrent calls to the service. To avoid a latency increase, we recommend that you cancel the `$bulk-delete` job, and then rerun it during a period of lower traffic.

0 commit comments

Comments
 (0)