Attention: This article was published over 3 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.Navigating the world of software can be intricate, especially when aiming for growth and scalability. Join us as we delve deep with a top-tier …
Part 4: Creating an FHIR API – Wrapping Things Up
Welcome to the fourth and final installment of Creating an FHIR API with GCP. So far, weโve covered a lot!
We discussed the differences between Google and Azure, landing on GCP as the best option for FHIR in Part 1. We began our implementation in Part 2, creating both the BigQuery resources and your FHIR repository resources. And finally, in Part 3, we tackled authentication methods and populating data in our FHIR repository.
This time, weโll wrap everything up with a nice little bow. First, weโll finish our implementation, and then, Iโll share the limitation I found – for the sake of transparency. Letโs dive in.
Part 3: Creating an FHIR API – Implementation Part B
This is Part 3 of our series on creating an FHIR API using Google Cloudโs offering. In the last installment, we began implementing an FHIR using GCP. We covered creating both the BigQuery resources and your FHIR repository resources. if you missed Part 1 and Part 2, be sure you go back to read those – theyโre critical to understanding!
This time, weโre continuing the implementation. Iโll explain the authentication methods, and weโll also tackle populating data in our FHIR repository.
Part 2: Creating an FHIR API – Implementation Part A
Welcome back to our series, Creating an FHIR API. This is Part 2 in our 4-part series on standing up an FHIR using GCP. In Part 1, we talked through two of the offerings out there, Google and Azure, and based on the pros and cons, I decided to use GCP FHIR Cloud Healthcare API.
In this part, we’ll start in on our implementation. A forewarning: we won’t be able to finish it during this installment, so stay tuned for parts 3 and 4! Let’s dive in.
Part 1: Creating an FHIR API – Google or Azure?
Data interoperability is one of the hardest problems in Healthcare IT. The most popular approach is to exchange HL7v2 messages between systems. These pipe-delimited messages are difficult to read by a human and often need additional customizations between implementations.
The next major paradigm shift is towards FHIR (Fast Healthcare Interoperability Resources), a JSON-based standard that is evolving ahead of the needs of the industry. Cloud vendors like Microsoft, Amazon, and Google are trying to lay their claim to be the one-stop shop for healthcare on the cloud.
This blog is part of a 4 part series diving into an actual use case I recently encountered while working with a client. I had to stand up an FHIR repository/API for 2+ million patients that could be used by hundreds of users every day, as well as countless background processes.