Stream: implementers
Topic: Why is my R4 Azure API for FHIR picky w/ processing Bundle
Michael Cox (Jun 11 2020 at 13:19):
Hi All,
I just wanted to stop by and ask for some advice related to the Azure API for FHIR service, specifically related to sending a POST to the Base URL of the server with a Bundle resource in the body...
Even more specifically, this question is related to the processing of the "request" fields for each item in "entry[]"
When I send a Bundle resource with the Bundle.type value == "transaction", the queries detailed to be completed by the server do not seem to be actually fire that query. BUT, when I send a POST with the same Bundle resource albeit with Bundle.type == "batch", to the same Base URL, it DOES indeed send the respective queries in each entry[] item's request field.
Any idea why this is? I am under the impression that the transaction field would also have those requests completed however as one "atomic" command. So says the documentation here, as I am understanding it: https://www.hl7.org/fhir/valueset-bundle-type.html#expansion
I would love to know what I am missing or why this discrepancy may occur. Thanks as always for everyone's guidance.
Michele Mottini (Jun 11 2020 at 13:40):
Maybe transactions are not implemented? (The fact that are in the specs does not mean that all server implement them) @Michael Hansen
Michael Hansen (Jun 11 2020 at 14:29):
In the managed service and in the OSS version based on Cosmos DB, only “batch” is supported. The OSS version based on SQL supports transaction as well. And transaction will be coming to the managed service, but I don’t have a date at the moment.
Michael Cox (Jun 11 2020 at 14:33):
@Michele Mottini Yeah, thanks for mentioning this, I checked the Azure documentation for it and it does not offer transaction bundles on the "PaaS" version .
@Michael Hansen Thanks a lot for the helpful feedback.
Last updated: Apr 12 2022 at 19:14 UTC
