WHERE THE WORLD
CONNECTS FOR HEALTH
Let’s talk about why FHIR is great, what isn’t so good and what the standard is not built to do.
Here is what you get with FHIR:
Here are the reasons I love FHIR and why I see much use in it as a standard:
FHIR is the real deal that can be applied to solve different clinical, administrative and business problems. It’s a tool that can create miracles in the hands of multidisciplinary teams of engineers and healthcare innovators.
Here are a few challenges I found when working with FHIR:
FHIR is supported by all major EHR vendors and some of them even offer FHIR marketplaces. But some vendor marketplaces are quite expensive. They also tend to not have friendly intellectual property terms, so the FHIR API is currently limited in its usability and lagging behind the FHIR adoption curve across the industry.
There are many benefits of FHIR, but like any standard it comes with limitations. FHIR was not built to take care of certain technical requirements (though that might change in the future). This is why a company leveraging the FHIR specification for their enterprise solutions need to compliment it with additional features to meet comprehensive technical needs of a solution.
Here’s what FHIR is not built to do:
FHIR is designed to do great things for health IT. Despite a few limitations around the standard, the benefits it brings will make it a standard that is here to stay. As long as you are aware of what FHIR is built to do and what it isn’t built to do, you will be able to find solutions in the marketplace that compliment FHIR to meet your data and solution needs.
Experience up-and-coming digital health innovations at the HIMSS Interoperability Showcase™.