Stream: implementers
Topic: OperationOutcome in history bundles
James Jahns (Apr 28 2021 at 17:37):
Hello,
Say I'd like to return a non-fatal OperationOutcome in a history bundle (which has history entries present as well). I'm not sure how to do so while meeting the constraints of the Bundle resource ( https://www.hl7.org/fhir/bundle.html#invs ):
- Since
Bundle.type='history', by constraintbdl-2I can't haveentry.search.mode = 'outcome' - Since
Bundle.type='history', by constraintsbdl-3/bdl-4the OperationOutcome entry must haveentry.requestandentry.responseBackboneElements, neither of which seem to make sense for an OperationOutcome
What's the best way to format non-fatal OperationOutcomes in a history Bundle?
Lloyd McKenzie (Apr 28 2021 at 17:47):
Right now, the answer is "there isn't one" - can you submit a change request for us to address this in a future release?
James Jahns (Apr 28 2021 at 18:45):
Submitted change request: https://jira.hl7.org/browse/FHIR-32011
Rob Reynolds (Jun 24 2021 at 17:52):
Similar to this, I would like to include an informational OperationOutcome as the Paramater.resource alongside other Parameter objects in a Parameters object.
The other Parameter objects would be "expected results" for the operation and then there would be an "extra" Parameter object for this informational OperationOutcome (that describes why potential results weren't included as Parameter objects in the result).
I can't find anything that precludes this, other than the OUT Parameter is defined as:
Use=OUT
Name= return
Cardinality=0..*
Type=Bundle
and an OperationOutcome is not a Bundle.
Is there some provision for being able to sneak an OperationOutcome in there? Or does the OperationDefinition above preclude it?
Lloyd McKenzie (Jun 25 2021 at 16:10):
The OperationDefinition precludes it. In this case, the return would be a Bundle, not a Parameters instance, so there's no ability to send an OperationOutcome as well.
Last updated: Apr 12 2022 at 19:14 UTC
