Stream: implementers
Topic: Integration Patterns
nicola (RIO/SS) (Nov 24 2016 at 19:00):
Just idea to map FHIR interop paradigms to http://www.enterpriseintegrationpatterns.com/patterns/messaging/toc.html
Grahame Grieve (Nov 24 2016 at 19:01):
would it be any different to any other RESTful spec?
Grahame Grieve (Nov 24 2016 at 19:01):
btw, we should call you our "RIO" Random Ideas Officer
nicola (RIO/SS) (Nov 24 2016 at 19:02):
I will print it on my next t-shirt :)
nicola (RIO/SS) (Nov 24 2016 at 19:03):
It's mostly about messaging, i hope, may be useful for subscriptions direction
nicola (RIO/SS) (Nov 24 2016 at 19:04):
Ideas not so random, i've just tried to generalize and align with industry paradigms slide for training
Kevin Mayfield (Nov 25 2016 at 07:00):
Is it the correct 'Martin Fowler Series' Book? Adding FHIR to messaging arena isn't difficult but getting (integration/hl7) staff to think about service design patterns and/or enterprise application architecture patterns is lengthy. Noticed at HL7 UK roadshows, people who don't understand gaps where FHIR fits mostly work with EIP patterns and not these others.
Rémy DIAS (Nov 25 2016 at 14:42):
Hi everybody,
I'm wondering how the applications will deal with FHIR Server.
With Several FHIR-compatible applications, do we have one FHIR instance server which is data master and will be requested by all the applications (with references) or do we have several instance which are responsible of their own data because they know how to deal with it ? If I receive a device measurement, do i have to request the patient repository AND the device repository etc ... ?
What do you think about that ?
Thx
Last updated: Apr 12 2022 at 19:14 UTC
