Stream: implementers
Topic: Asynchronous RESTful Use Pattern
Ken Sinn (Apr 24 2019 at 14:40):
Hi everyone,
Looking over https://www.hl7.org/fhir/async.html, it's not exactly clear how the Async RESTful interaction works. For example, a Create Patient call would return the location of the Patient ID, along with any OperationOutcomes in case of warnings and errors (after the Create Patient has been processed). What happens in an Asynch RESTful call, since the Patient ID is not yet available, nor the OperationOutcomes?
FHIR Async Messaging addresses this by allowing the client to call the server to check for responses. Is there something similar designed for Async RESTful?
Yunwei Wang (Apr 24 2019 at 14:58):
https://www.hl7.org/fhir/async.html#3.1.6.4 talks about Bulk Data status check
Ken Sinn (Apr 24 2019 at 15:08):
Thanks Yunwei. It wasn't clear if the Bulk Data sections (3.1.6.3, 3.1.6.4) was specific to the Bulk Data IG operations ($export), or if it applied to all RESTful interfaces running in Async mode. An async RESTful interaction doesn't necessarily have to be "Bulk Data", it could just be a single Create interaction, so that was confusing. Can someone confirm that the Bulk Data sections apply equally to all RESTful interactions in Async mode?
Yunwei Wang (Apr 24 2019 at 17:43):
The whole page is still under construction. It has mixed content from Async and Bulk data. Bulk data is under May's ballots. This page may get reorganized after that.
Grahame Grieve (Apr 24 2019 at 21:24):
the async pattern can apply to any request, though it doesn't really make sense to apply to simple Get requests. But it can apply to a Create Patient interaction. And I don't understand the question - the async operation redirects to a new location where the client queries until it gets the response it would have go in the first place
Grahame Grieve (Apr 24 2019 at 21:24):
bulk data uses the async pattern but they are not one and the same
Last updated: Apr 12 2022 at 19:14 UTC
