We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Describe the bug When attempting to DELETE a search parameter, for example
{ "resourceType": "SearchParameter", "id": "8055acd7-051e-4982-b99e-13ecb7bafc44", "meta": { "versionId": "1", "lastUpdated": "2023-11-07T13:02:52.296+00:00" }, "url": "https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/how-to-do-custom-search#create-new-search-parameter-for-resource-attributes-with-reference-type", "version": "1.0", "name": "CompositionSearchParameter", "status": "active", "description": "Search parameter for Composition by focus", "code": "focus", "base": [ "Composition" ], "type": "reference", "expression": "Composition.section.focus", "target": [ "Resource" ] }, "search": { "mode": "match" } }
DELETE 'http://localhost:8080/SearchParameter/8055acd7-051e-4982-b99e-13ecb7bafc44'
The response is
{ "resourceType": "OperationOutcome", "id": "e1b7f977-4b0d-4437-bb0d-46bd725bd077", "meta": { "lastUpdated": "2023-11-15T17:17:46.9870796+00:00" }, "issue": [ { "severity": "error", "code": "unknown", "diagnostics": "" } ] }
FHIR Version? R4
Data provider? SQL Server
The text was updated successfully, but these errors were encountered:
Also experiencing some weird issues with SearchParameter deletion.
Specifically when i DELETE a resource and then execute a PUT request afterwards (#3608)
Sorry, something went wrong.
#113078- internal reference id
No branches or pull requests
Describe the bug
When attempting to DELETE a search parameter, for example
DELETE 'http://localhost:8080/SearchParameter/8055acd7-051e-4982-b99e-13ecb7bafc44'
The response is
FHIR Version?
R4
Data provider?
SQL Server
The text was updated successfully, but these errors were encountered: