Stream: implementers
Topic: Implementer Question
Grahame Grieve (Jan 09 2017 at 22:06):
I've been askd this:
If you had an application that currently does not have HL7 interfaces, and you want to interface using FHIR, would you create a new database to publish the FHIR resources too or would you map to the existing schema? What are the advantages and disadvantages to each?
Of course, I have my own opinions, but interested in anyone else's comments...
Bryn Rhodes (Jan 10 2017 at 02:35):
I would typically lean towards mapping to the existing schema. Of course, there are run-time computational costs, but for specific use cases those typically aren't too high. Mapping to existing lends itself more to an incremental approach, I think.
Brian Postlethwaite (Jan 10 2017 at 03:42):
I presented on this at HL7 NZ in June Last year, just posted to Slideshare for others
http://www.slideshare.net/BrianPostlethwaite1/fhir-server-design-review
Jenni Syed (Jan 12 2017 at 19:42):
+1 to mapping to existing schema. If you used a new database, you would need to keep the old and new in synch, which raises a bunch of other questions/complications. They're solvable, but not without some extra infrastructure that you may not want to add
Jenni Syed (Jan 12 2017 at 19:43):
Unless you don't need interop at all between the "legacy" and new
Grahame Grieve (Jan 12 2017 at 20:46):
typically, it's if you want bidirectional data flow that mapping to existing schema becomes really compelling. Otherwise, there's pro's and con's either way
Grahame Grieve (Jan 12 2017 at 20:47):
thanks all for input
Igor Sirkovich (Jan 12 2017 at 21:07):
I think that if the intent is to keep using the existing application then it would be better to map to the existing schema. However, if the intent is to eventually replace the existing legacy application with a new one, creating a new database would make sense.
Grahame Grieve (May 17 2019 at 01:33):
Someone has just written to me with this:
I want to get a better idea of all the capabilities of FHIR and get a better understanding of how it plays into an IT infrastructure with KAFKA, Hadoop, Spark, and OT protocols like MQTT, AMQP, and DDS
They're asking for a phone call. I hadn't even heard of those OT protocols before, so I'm not sure I'm the best person to talk to. Has anyone got any perspectives to offer?
Vadim Peretokin (May 17 2019 at 08:52):
@nicola (RIO/SS) ?
nicola (RIO/SS) (May 17 2019 at 09:25):
Yes, i can participate in call and share my thoughts
Roel Barelds (Nov 17 2021 at 20:13):
What was the outcome of the call. We are using AMQP and MQTT as internal standards. But we we just want to use FHIR over our API gateway. Is there any knowledge over mapping AMQP to FHIR?
Joel Schneider (Nov 17 2021 at 20:45):
For asynchronous messaging, FHIR messaging may be pertinent (but also "some assembly required"):
http://hl7.org/fhir/messaging.html
Josh Mandel (Nov 17 2021 at 21:50):
Which call today? Worth evaluating whether Subscriptions revamp (since 2019) addresses any of this but if don't have context on the question(s) @Roel Barelds
Roel Barelds (Jan 17 2022 at 10:28):
@Josh Mandel Hi josh,
I'm not sure if I understand you correctly. Are you saying that a mapping can be done through subscriptions from AMQP/MQTT to FHIR
Gino Canessa (Jan 18 2022 at 16:16):
Roel, I think what Josh is referring to is that the changes for Subscriptions (R5, with a backport to R4B once that is published) include the ability to define custom channels for communication.
It should be fairly straightforward to define a channel type for any of those protocols, but it would not be something in the core spec.
John (Mar 10 2022 at 17:16):
Hi guys, I am wondering how can I install / Use an Implementation Guide. Unfortunately I couldn't find much documentation how to use them. Thanks
Lloyd McKenzie (Mar 10 2022 at 17:40):
What do you mean by "install"? Typically there's no automatic mechanism to point a server at an IG and have the software magically support it. Implementing an IG typically will involve writing code to enforce the rules of the IG and/or add new capabilities to the system.
Last updated: Apr 12 2022 at 19:14 UTC
