Stream: implementers
Topic: What is FHIR?
Lucky Luo (Jun 25 2019 at 21:01):
hello everyone, I am new here and I would like to know how to start to use FHIR in our application. Is it just some API calls
to get patient data?
Jean Duteau (Jun 25 2019 at 21:09):
hello everyone, I am new here and I would like to know how to start to use FHIR in our application. Is it just some API calls
to get patient data?
No, it is definitely not that. It is an entire specification. Have you been to the FHIR website: http://hl7.org/implement/standards/fhir/ I suggest you go there and look at the various introductions. That should give you a good idea of what FHIR is. As to using it in your application, you'll want to explore how best to use it, i.e. what your application does. And you'll want to know what FHIR servers you'll be accessing so you can know exactly how to work with them.
Lucky Luo (Jun 25 2019 at 21:38):
hello everyone, I am new here and I would like to know how to start to use FHIR in our application. Is it just some API calls
to get patient data?No, it is definitely not that. It is an entire specification. Have you been to the FHIR website: http://hl7.org/implement/standards/fhir/ I suggest you go there and look at the various introductions. That should give you a good idea of what FHIR is. As to using it in your application, you'll want to explore how best to use it, i.e. what your application does. And you'll want to know what FHIR servers you'll be accessing so you can know exactly how to work with them.
Thank you. I will check it and get more info from there.
Jason Walonoski (Jun 25 2019 at 22:58):
Another way to answer that question, is "yeah, it basically is just an API to get patient health data." Everything else is just the complexity of healthcare and technology, which is why there is an enormous specification for you to read... and don't forget the safety checklist: https://www.hl7.org/fhir/safety.html
Lucky Luo (Jun 26 2019 at 00:10):
Thank you all for the help. Also, does FHIR provide any e-prescription feature/service?
Lloyd McKenzie (Jun 26 2019 at 00:43):
Yes - take a look at the Medication module. Depending on what you're trying to do, you might also need the workflow module
Lucky Luo (Jun 26 2019 at 23:56):
Does FHIR provide the service to connect to a doctor's system? like can we send an e-prescription to a doctor by using FHIR? If so, how can we receive it from a doctor?
Michele Mottini (Jun 27 2019 at 00:04):
The specifications probably cover that - ie it is possible to write FHIR-compliant system doing that, but to the best of my knowledge none actually implemented it (to date). So: in theory yes, in practice no.
Brendan Keeler (Jun 27 2019 at 00:37):
If it's the US, you'll still be using NCPDP
Lloyd McKenzie (Jun 27 2019 at 20:17):
Are you at the stage where you're trying to design FHIR-based solutions for use in an interoperability community? If so, then yes, you could design such a solution using FHIR. If instead you're an implementer who's just wondering what's going to be available in other systems, you should check to see what implementation guides your communication partners support/intend to support. That will tell you what interfaces might exist - and what architectural approaches have been landed on.
Ken Sinn (Jun 27 2019 at 20:25):
Canada is rolling out the PrescribeIT solution based on the FHIR standard. https://prescribeit.ca/ So yes, your use case could be implemented using the FHIR standard to transmit e-prescriptions from doctors to pharmacies, but FHIR is just the standard -- you need to still design and build the system, workflows, etc to enable your use case.
Lloyd McKenzie (Jun 27 2019 at 20:27):
And it'll be driven by your architecture - are you looking for direct delivery or is there an intermediary? Who "owns" the prescription once it's been delivered? Can it be updated/suspended/cancelled? Do you need to capture "refusal to fill"? Does the pharmacy push back information about dispenses? Will both parties have RESTful interfaces? Will there be support for subscriptions? Do you have registries that give you common identifiers for patients, prescribers, pharmacies, etc?
ankur chauhan (Jul 06 2021 at 13:13):
hello i am new to fhir Can anyone explain to me in layman terms
Yannick Börner (Jul 06 2021 at 13:43):
ankur chauhan said:
hello i am new to fhir Can anyone explain to me in layman terms
Hi there, FHIR is a standard for health care data exchange. It captures all health care data via 'Resources' such as Patient, Observation etc. I'd suggest to take a first look into the summary if you don't know what it is about yet: http://hl7.org/fhir/summary.html
ankur chauhan (Jul 06 2021 at 13:48):
How it works so as here it is mentioned its's a standard for data exchange so what does it mean like if i am creating any appliation so my api design should follow that convention mentioned in the document or is it a kind of api that i have to hit to get the data
Vassil Peytchev (Jul 06 2021 at 15:11):
Without knowing any details of what you might be creating, I would say both - your api design should follow the FHIR conventions, and you can use the FHIR API to get data form external sources.
Lloyd McKenzie (Jul 06 2021 at 15:32):
FHIR defines a variety of architectural approaches to data exchange - REST, messaging, documents and a few others - with variations in approach between those. Because of that flexibility, there are often implementation guides that further constrain how FHIR data structures should be used to support interoperability for particular use cases and/or in particular jurisdictions. In some cases, there may be regulations that mandate the use of FHIR in particular ways - so it may be helpful to look for implementation guides relevant to your particular area(s) of healthcare and/or jurisdictions of implementation.
Mark Iantorno (Jul 06 2021 at 15:44):
@ankur chauhan https://www.youtube.com/watch?v=YbQcJj1GqH0
Last updated: Apr 12 2022 at 19:14 UTC
