Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad Request error on PATCH operation for replace operatio #2516

Closed
LumiProj opened this issue Jul 4, 2023 · 1 comment
Closed

Bad Request error on PATCH operation for replace operatio #2516

LumiProj opened this issue Jul 4, 2023 · 1 comment

Comments

@LumiProj
Copy link

LumiProj commented Jul 4, 2023

Describe the bug
I am encountering an issue with the PATCH operation in the FHIR server. While the PATCH operation works fine for adding operations, I consistently receive a "Bad Request" error (HTTP 400) when attempting to perform a replace operation using PATCH. I am providing a sample JSON payload below to illustrate the problem:

To Reproduce
Steps to reproduce the behavior:

  1. Go to Postman
  2. { "resourceType": "Parameters", "parameter": [ { "name": "operation", "part": [ { "name": "type", "valueCode": "replace" }, { "name": "path", "valueString": "Patient.identifier.where(system='urn:oid:1.2.36.146.595.217.0.2')" }, { "name": "value", "valueIdentifier": { "use": "official", "type": { "coding": [ { "code": "MR", "display": "Medical record number" } ] }, "system": "urn:oid:1.2.36.146.595.217.0.2", "value": "0-95941-01" } } ] } ] }

Expected behavior
The PATCH operation with a "replace" type should execute successfully, updating the specified resource in accordance with the provided JSON payload.

Spark version

  • Version:1.5.17.0

Operating system + Database

  • OS: Linux Ubantu focal
  • Database: [MongoDB]
@mbaltus
Copy link
Member

mbaltus commented Jul 5, 2023

It looks like the request can be sent correctly, but that there is a problem on the server side that does not give you the response you were expecting. There is nothing we can do on this library to fix that. Please reach out to the server admins or developers to get assistance on the server's handling of the PATCH interaction.

@mbaltus mbaltus closed this as completed Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants