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.
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.
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.
Every self-respecting student of programming has already needed to use libraries (the famous โlibโ) in the development of their applications. Examples include the Axios and Fetch libs, which are widely used on the front-end and back-end to consume external APIs.
Recently, Node.JS v17.5 underwent two changes that divided opinions, so let’s explain how these changes impact the issues of effectiveness and agility in code production. Additionally, I will also discuss the pros and cons of this update.
You love frontend JavaScript frameworks, but your client wants a WordPress website… Donโt worry, you can do both! Let’s build a custom backend and API with WordPress!
WordPress provides an out-of-the-box CMS solution that can be customized very easily to fit many different types of projects. Youโre not just stuck with blog posts and web pages, either.
In this post, Iโm going to show you how you can use a very popular plugin called Advanced Custom Fields (ACF) plus some custom code to create your own content and API endpoints for your fancy new frontend to consume while allowing your client to keep using what they love.