Stream: implementers
Topic: HTTP Status for updating a FHIR resource without any changes
Ron Shapiro (May 04 2019 at 16:30):
A question has come up on the Patient Track at the Montreal FHIR Connectathon 21 about how to handle an update operation that doesn't really update the FHIR resource. If no content in the updated FHIR resource has changed, would it be appropriate to return an HTTP 304 Not Modified response?
Currently, FHIR specifies 200 Ok and 201 Created as the only valid responses, but if the server detects that there is nothing to update and no new version is generated, it seems reasonable to communicate that to the client. Additionally, since no new version is generated, a version read would therefore not include an additional entry.
Grahame Grieve (May 04 2019 at 16:51):
I think it would be a policy choice whether to make the record of change or not, but it should be allowed to return 304
Lloyd McKenzie (May 04 2019 at 17:35):
@Ron Shapiro Can you guide your commenter through process of registering on gForge and submitting a change request to allow 304?
Ron Shapiro (May 05 2019 at 17:56):
GF#21258 has been logged.
Last updated: Apr 12 2022 at 19:14 UTC
