Stream: implementers
Topic: Messaging,Operations andSubscription
Jayashree Surnar (Jun 20 2017 at 05:13):
hello all, as of now we used restful calls. But in fhir we have Operations,Messaging,Subscription. i'm not understanding in which scenarios use what? so please any suggestions?
Thank you.
René Spronk (Jun 20 2017 at 09:40):
See http://build.fhir.org/foundation-module.html#uses
Jayashree Surnar (Jul 07 2017 at 05:04):
Thank you @Rene Spronk, here they have not given much info, i'm not understanding the real time scenarios, in which situation what we use?
Lloyd McKenzie (Jul 07 2017 at 14:58):
Messaging works well for asynchronous communication and for indirect/routed communication. It also works well when you have a request/response behavior and want to communicate in a single (potentially large) burst rather than a bunch of small transmissions. Documents work when you care about strict control of human-readability, authentication and what data gets persisted (and you don't have any behavior such as "please do this"). Services work well for decision support where you're doing something not covered by a RESTful operation. Subscription isn't really a paradigm for exchange, it's just an alternate mechanism for getting query results that avoids repeatedly polling. Keep in mind that both messaging and operations are going to require more discussion between the communicating parties as they need a lot more definition than simple REST does
Jayashree Surnar (Jul 11 2017 at 11:52):
tnq @Lloyd McKenzie
Ken Melms (Jul 11 2017 at 18:56):
When implementing messaging via subscription (PUSH messages) - even though it's not a strict pattern to follow, I'm still getting hung up on which resources would be involved. MessageHeader or MessageDefinition? Is there a reason to choose one over the other?
Lloyd McKenzie (Jul 11 2017 at 19:49):
See my response on the ADT thread
Last updated: Apr 12 2022 at 19:14 UTC
