Stream: implementers
Topic: FHIR Task
Kesara Liyanage (Apr 02 2019 at 13:05):
Can the FHIR Task resource be used instead of FHIR message header?? Or are their purposes different?
Lloyd McKenzie (Apr 02 2019 at 15:23):
Their purposes are slightly different. MessageHeader is used for messaging - when you package up a whole bunch of resources with an event code that drives the behavior of the recipient. With Task, you post the Task to a server and systems then update the Task and query to find related resources.
Kesara Liyanage (Apr 03 2019 at 18:40):
Is the task resource sent as part of a FHIR message payload? or independently communicated?
Lloyd McKenzie (Apr 03 2019 at 18:44):
Task could be communicated in a message, but it would typically be sent independently. There's a whole section that talks about workflow that shows some of the different architectures in which Task can be used and the pros and cons of each. It also talks about the pros and cons of using messaging. http://build.fhir.org/workflow-communications.html
Last updated: Apr 12 2022 at 19:14 UTC
