Stream: implementers
Topic: Issue type for HTTP 412 Precondition Failed
Lee Surprenant (Feb 25 2020 at 19:35):
Assuming folks are returning an OperationOutcome in cases where you return an HTTP 412 Precondition Failed (e.g. based on https://www.hl7.org/fhir/http.html#concurrency), what issue type from https://www.hl7.org/fhir/valueset-issue-type.html are you using?
Lee Surprenant (Feb 25 2020 at 19:36):
would it make sense to introduce a new issue type code under processing specifically for this case?
Grahame Grieve (Feb 25 2020 at 19:38):
This would also be conflict
Lee Surprenant (Feb 25 2020 at 19:39):
yeah, thats what we're using now. but the description explicitly mentions HTTP 409
Paul Church (Feb 25 2020 at 19:40):
+1 for conflict
Lee Surprenant (Feb 25 2020 at 19:40):
my pipe dream is to be able to map the issue type to the HTTP response code so that my persistence layer doesn't need to know which HTTP status code is most appropriate
Lee Surprenant (Feb 25 2020 at 19:40):
i think this is the one case where I can't do that
Lee Surprenant (Feb 25 2020 at 19:41):
(could be 409, could be 412, depends on context)
Grahame Grieve (Feb 25 2020 at 19:48):
you could make a task to mention 412 in the desc - I think that's something I missed. But I think that you're hoping for too much from the issue type.
Lee Surprenant (Feb 25 2020 at 19:48):
like i said, just a dream :-)
Lee Surprenant (Feb 25 2020 at 19:49):
i ran a little experiment and consolidated the HTTP status codes in our system into a single spot (an IssueType-to-HttpStatus Mapper), leaving just the issue types, and this is the only issue i hit
Lee Surprenant (Feb 25 2020 at 19:49):
so i think its close
Lee Surprenant (Feb 25 2020 at 19:49):
but yeah, perhaps there's more lurking there than I realize
Last updated: Apr 12 2022 at 19:14 UTC
