The FHIR server is where you will initiate your API calls to begin the exchange of data. You might think of it as the repository of the resource data accessed via the APIs you create. Many of the FHIR servers are built on Java but other languages exist. There are a number of test FHIR servers on the web and many others that you can download and use as models. The HL7 application programming interface (HAPI) FHIR server is one of them:

Figure 6.3 – The HAPI FHIR server can be used for testing APIs

In this chapter, we will be running tests on a HAPI FHIR server that is prepopulated with test resources. You can access the HAPI FHIR test server at this URL:

http://hapi.fhir.org

Before you start developing your first FHIR API, it will be beneficial to understand the motivation of using API Connect to implement your RESTful FHIR APIs.

Government-mandated FHIR interfaces

As mentioned in the chapter introduction, CMS has mandated payers (insurance companies) to implement a Patient Access API and a Provider Directory API for consumption by third-party entities using the FHIR standard. While the implementation date was moved from January 1, 2021, to July 1, 2021, nevertheless, payers will need to comply.

The benefits proposed by these two requirements are as follows:

• Patient Access: This is the government’s response to putting patients first, giving them access to their health information when they need it most, and in a way that they can best use it. During a pandemic such as COVID-19, this would be very beneficial.
• Provider Directory: The government is requiring an FHIR interface to a directory of a health insurer’s in-network providers and pharmacies for patients/consumers. Again, during a pandemic such as COVID-19, this would be very beneficial.

These two benefits to consumers are just what the doctor ordered. Having information readily available is critical to healthcare and patient care. Now that we will be learning how to create RESTful FHIR APIs, it is important to note the reasons why using API Connect is a good choice.

Figure 6.4 highlights reasons for building APIs, managing the FHIR API lifecycle, and maintaining the integrity of data:

Figure 6.4 – FHIR and API Connect synergy

You now have a good overview of FHIR and how CMS mandates implementing capabilities for the Patient Access and the Provider Directory using FHIR. It’s time to start playing with FHIR.

Creating a RESTful FHIR API

As you may recall, your APIs will be accessing an FHIR server that provides healthcare resources. Given that, when you create your FHIR RESTful API, you will need an endpoint. For the examples provided in this section, you will be referencing the online HAPI Test FHIR server that is at this location:

http://hapi.fhir.org/baseR4/swagger-ui/

You have learned to use the LTE and have been introduced to the API Manager Drafts Designer. You’ll be using the LTE initially and then switch to the API Manager so that you can learn the other capabilities of the API Manager.

If you haven’t already downloaded the chapter files from the URL mentioned in the Technical requirements section of this chapter, you should do that now and place them in a directory/folder on your local device.

Now that you have the files, you can log in and begin developing APIs.