Stream: implementers
Topic: Asynch Messaging Response Payload
Ken Sinn (Aug 28 2020 at 14:43):
Regarding https://www.hl7.org/fhir/messaging.html#rest, the guidance is that "The receiver works through the response, processing each message. As each message is processed, the receiver creates a response message, reversing the source and destination, and posts it back to the server."
There's no requirement that the same payload (or any payload for that matter, ie MessageHeader.focus and Bundle.entry[1].resource) is posted back to the server for an asynchronous response Message Bundle, correct?
Grahame Grieve (Aug 28 2020 at 22:16):
I'm not sure what 'posted back to the server' means in this context?
Vassil Peytchev (Aug 28 2020 at 23:18):
Since this is a response message, it needs to be a FHIR Message (a FHIR Bundle of type message with the first Bundle.entry containing a MessageHeader). Ther is a requirement that MessageHeader.response is populated with the id of the original message. Everything else depends on the agreement/implementation guide that would define what is in the response message.
Ken Sinn (Sep 30 2020 at 18:56):
Is there any requirement to always provide an acknowledgement of receipt? Or is that up to implementers to decide?
That is, we're looking to implement Async Messaging, and proposing to only acknowledge successful processing receipt from the recipient only. (any failures will just be left unresolved).
Ken Sinn (Sep 30 2020 at 19:26):
Additionally, there doesn't seem to be any native FHIR way for a recipient to query "Give me all Async Messages that have not been processed yet".
Last updated: Apr 12 2022 at 19:14 UTC
