This repository has been archived by the owner on Jan 5, 2025. It is now read-only.
fix: use Fhir Http client to hard delete patients #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liammoat
requested review from
johncollinson2001 and
gaurarpit
and removed request for
gaurarpit and
johncollinson2001
|
@johncollinson2001, might be worth capturing a PBI to update the |
gaurarpit
reviewed
Apr 16, 2024
gaurarpit
approved these changes
Apr 16, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PdsServiceTestshas a method which deletesPatientresources from the Fhir Service. By default, this operation is a soft delete.The remaining "soft" copy of the resource prevents subsequent tests from running successfully - due to the 410 GONE Http result.
This PR updates the
CleanFhirStoreto "hard" delete the resource, using thehardDeletequery parameters:Patient/9000000025?hardDelete=trueSubsequent requests for "9000000025" will now result in a 404: