What to do with HTTP responses with codes other than 200 which have a body?

[pherk]

The FHIR standard precribes that an error resource with further informations (aka OperationOutcome) is returned in addition to the HTTP code.
AFAIS, Fore is ignoring the body, only returning the status and a message
regards
Peter

[JoernT]

if you help to provide a test case we could certainly think about implementation.

any information on how that body looks like exaclty (reference material) and ideally a page to test it with.

[pherk]

no complete test case, just an impression.
The FHIR standard demands that servers return an OperationOutcome resource as a lonely body or contained in other response resource on several circumstances (https://hl7.org/fhir/R4/operationoutcome.html).

Besides the HTTP header code > 400 the OO resource carries additional informations.
At the moment I can live with the HTTP code alone, since I only have failures from trying to get a resource by id.
For other operations the real thing can be much more complicated.
I'm presuming that a possible solution has to parse the body and has to load the data in an extra (error) instance named from fx-submission.

 <OperationOutcome xmlns="http://hl7.org/fhir">
        <issue>
            <severity value="fatal"/> <!-- mandatory -->
            <code value="{$code}"/>
            <diagnostics value="{$message}"/>
            <location value=""/>
           <expression value=""/>
        </issue>
</OperationOutcome>

[JoernT]

maybe getting this information from 'submit-error' details information would be possible too?

e.g.
so that error-outcome points to

or
{event('error-outcome}/diagnostics/@value}

let me know what you think @pherk

[pherk]

yes, if I can access the parsed body via an event it would be as nice as an additional instance arg (fx-submission) regards peter

…

On Tuesday, July 21, 2026 17:53 CEST, Joern Turner ***@***.***> wrote: maybe getting this information from 'submit-error' details information would be possible too? e.g. <fx-setvalue ref="error" value="event('error-outcome')"> so that error-outcome points to <OperationOutcome> or <fx-message ***@***.***}</fx-message> let me know what you think @pherk -- Reply to this email directly or view it on GitHub: #358 (reply in thread) You are receiving this because you were mentioned. Message ID: ***@***.***>