Stream: implementers
Topic: FHIR Community moving towards event driven architetures
Ross Powell (Feb 10 2022 at 20:04):
Hi Implementers,
I'm relatively new to FHIR and have a more broad question about what architecture pattern (Event-driven or Request-driven) the FHIR Community recommends as best-practice for our FHIR server. Generally our team has been moving towards an event-driven architecture, but considering the FHIR spec supports both patterns we wanted to reach out to clarify if there is a recommended one.
Thank you for your time in advance!
Grahame Grieve (Feb 10 2022 at 20:15):
we generally recommend that you adopt the patterns that work for you
Grahame Grieve (Feb 10 2022 at 20:17):
in general, FHIR has nothing to say about that choice, but the community desire has very much been that there's no need to come to consensus about the choices you make in your event drive architecture, because these aren't usually the basis for interoperability - except for messaging. So the specification is strongly dominated by the request pattern, though there is a little about messaging
Notification Bot (Feb 10 2022 at 21:14):
Ross Powell has marked this topic as resolved.
Notification Bot (Feb 10 2022 at 21:14):
Lloyd McKenzie has marked this topic as unresolved.
Lloyd McKenzie (Feb 10 2022 at 21:15):
There's actually an extensive set of documentation about the different mechanisms of sharing information in FHIR and the trade-offs between them here
Ross Powell (Feb 11 2022 at 16:20):
Thank you both! I'll take these responses/document back to our team to help decide the high level pattern we'll use for our use cases.
Last updated: Apr 12 2022 at 19:14 UTC
