Stream: social
Topic: New to FHIR
pallavi talekar (Feb 26 2019 at 20:41):
I want to understand from infrastructure perspective, what is needed to make a communication between two entities FHIR enabled. Those two entities (or providers) will be exchanging documents and messages using FHIR. So for someone who does not understand FHIR at all, how can you explain the steps to take to enable FHIR based transactions?
For example, Provider A needs to follow this implementation guide and build resources, or FHIR server, somebody needs to create or connect with SMART on FHIR etc. Appreciate your guidance.
Michele Mottini (Feb 26 2019 at 20:58):
I'd start from what the two entities need / want to communicate
Lloyd McKenzie (Feb 26 2019 at 22:50):
Also, consider whether you really want messages. Most FHIR implementation is via REST and that will typically be easier.
Yohannes Tecle (Dec 22 2019 at 03:03):
Hi All, I am new to FHIR, either a documentation will help me install and set up FHIR ?
Lloyd McKenzie (Dec 22 2019 at 04:24):
FHIR is a specification, not a product. It's also a specification that can be used to do a wide variety of different things. Can you share more about what you're hoping to accomplish with FHIR?
Yohannes Tecle (Dec 23 2019 at 15:57):
Thank you Lloyd for the reply, I am working to develop a bi-directional data exchange with eClinical Works (eCW)
Lloyd McKenzie (Dec 23 2019 at 17:08):
Do you know what sort of FHIR interface eCW has? (FHIR version, REST vs. Messaging, what resources, etc.). Youll have to write code to map between your internal interface and FHIR. You might look at using one of the reference implementations handle parsing, serialization and some of the other non-app-specific bits
Yohannes Tecle (Dec 23 2019 at 18:16):
Thank you so much Llory for the reply, I truly appreciate for your input, it is REST API for FHIR that I have to develop.
Last updated: Apr 12 2022 at 19:14 UTC
