Stream: implementers
Topic: FHIR Architecture
sucharitha manyala (Nov 11 2018 at 01:30):
Hello,
Could someone please provide link to FHIR architecture diagram?
Thanks,
Suchi
Lloyd McKenzie (Nov 11 2018 at 02:52):
What sort of diagram are you looking for? FHIR supports a wide variety of archiectural approaches, so there wouldn't be just one possible diagram...
sucharitha manyala (Nov 11 2018 at 13:36):
I am looking for a diagram that shows where FHIR stands in the picture of interoperability between various healthcare systems and how the components of FHIR interact. I understand this can be achieved in various ways so any diagram showing interfacing between two clinical systems (or a patient requesting for his reports through an app) using FHIR and mainly showing how components within FHIR interact to exchange data between these two systems will be good. Please let me know if there is any such architectural diagram.
Thanks,
Suchi
Lloyd McKenzie (Nov 11 2018 at 14:27):
FHIR can be used with REST (with intermediaries or not), with messaging, with document repositories and a number of other ways. SMART and CDS Hooks provide additional mechanisms for using FHIR interfaces. This deck has a few slides describing some of the different architectural approaches at a high level which might be helpful.
sucharitha manyala (Nov 11 2018 at 16:06):
Thank you! This is exactly what I needed.
Keerthivasan Ramanathan (May 19 2020 at 07:28):
we don't have a FHIR respository in our system. we have clinical data at rest that we transform to FHIR resources on the fly.
Keerthivasan Ramanathan (May 19 2020 at 07:28):
how do we approach it generally?
Michele Mottini (May 19 2020 at 13:08):
You;ll have to write mapping code between your internal data and FHIR, for the REST interface you can use one of the available servers (HAPI, Vonk) usually have a definable backing store - or write your own (the mapping is the most difficult part in my experience)
Last updated: Apr 12 2022 at 19:14 UTC
