FHIR Chat · Operations with no 'out' parameters

Stream: implementers

Topic: Operations with no 'out' parameters

Michele Mottini (Sep 26 2019 at 13:19):

eg not returning anything - what's the correct behavior on success? return nothing with a 204 (no content) status code? (http://hl7.org/fhir/operations.html#response does not say)

Michele Mottini (Sep 26 2019 at 13:55):

(FHIR .NET library accepts only 200 OK: https://github.com/FirelyTeam/fhir-net-api/blob/develop-stu3/src/Hl7.Fhir.Core/Rest/FhirClient.cs#L869)

Yunwei Wang (Sep 26 2019 at 14:12):

$export return 202 if success.

Michele Mottini (Sep 26 2019 at 14:13):

Yes, but that's for async - I am talking about normal sync execution

Brian Postlethwaite (Sep 27 2019 at 07:09):

Can you log that as an issue with the fhir client. Can't believe I have come across that one yet.

Brian Postlethwaite (Sep 27 2019 at 07:12):

There are many results that could be appropriate depending on the operation.
For the patient merge there are a handful of values that could come back.
We're trying to document all of them, and the return results.

Brian Postlethwaite (Sep 27 2019 at 07:18):

I would expect that could have:
201 Accepted
200 Ok
204 No content
And probably others.
Maybe we should list on the operations page in the core spec and the http summary table the complete set, which is only saying 200.