Stream: implementers
Topic: batch responses
Jens Villadsen (Oct 02 2020 at 14:08):
Hi all -
I have a case where I'm in need of implementing Bundle batch processing. Due to the nature of batch processing, some of the requests within the batch bundle may fail - some may succeed. Looking at https://www.hl7.org/fhir/stu3/bundle.html#transaction-response, I don't see any examples of how errors for some of the requests within the bundle should look like. I also seem to lack the understanding of how a response can refer to the requests within the origin batch bundle (I suspect a fullUrl reference would be proper). Guidance to this matter is highly appreciated.
René Spronk (Oct 02 2020 at 14:28):
A transaction either fails (one or more of its contents could not be processed), or succeeds (all of the contents are succesfully processsed). By definition a transaction response won't ever be a mixture of successfully and non-sucessfully processed transaction contents.
In Batches, partial failure could happen. Entry x in the Bundle (the x-th entry) has a corresponding entry x in the Responde Bundle.
Jens Villadsen (Oct 02 2020 at 15:06):
Yes i know - but I dont see any example of this in the spec
Jens Villadsen (Oct 02 2020 at 15:07):
The link holds the text "Transaction/batch Response"
Jens Villadsen (Oct 02 2020 at 15:08):
I would like to see a batch response where the content has partially failed
Jens Villadsen (Oct 02 2020 at 15:08):
And the originating request
Jens Villadsen (Oct 02 2020 at 15:10):
And i would like such example to be part of the specification @René Spronk
Yunwei Wang (Oct 02 2020 at 15:13):
The response entry does not link to the request entry but the response entries has the same order as the request entries. The section states "... contains one entry for each entry in the request, in the same order, with the outcome of processing the entry"
Jens Villadsen (Oct 02 2020 at 15:23):
Good point @Yunwei Wang - I guess order really matters on this point
Jens Villadsen (Oct 02 2020 at 15:25):
But why wouldnt a reference to the entry's fullUrl in the request be sufficient?
Jens Villadsen (Oct 02 2020 at 15:39):
I mean that in theory, that is
Yunwei Wang (Oct 02 2020 at 15:52):
entry.fullUrl is optional. Especially when batch several independent requests, requester may not bother to create a fullUrl for each entry.
Last updated: Apr 12 2022 at 19:14 UTC