Search loading...


Explore and Make use of Nationally Defined Messaging APIs


FHIR® library

There are benefits to using an existing FHIR® library

Using an existing FHIR® library

GP Connect strongly advises suppliers to use an existing FHIR library as it will reduce development time and result in more robust implementations of the GP Connect API. Benefits of using an existing FHIR library for the implementation of both the consumer and provider side of a GP Connect API are:

  • Reduced complexity - using a library can reduce the quantity of boilerplate code required to configure provider endpoints, structure a request and validate consumed resources. This will help keep the code base smaller, and make it easier to work on and maintain.
  • Quicker development - a library gives developers the standard FHIR data types, FHIR resources and some validation of the FHIR resources, allowing developers to focus on data transformation and business rules.
  • Solution resilience - using a tried and tested implementation of the FHIR resources and data types should result in the implementation being more resilient to receiving valid but unexpected elements within FHIR resources. Many libraries will also include some level of validation to aid in ensuring that only valid data enters the system.

What libraries to use?

There is an ever-increasing list of open source FHIR libraries appearing on the web, written for a wide variety of languages, such as Java, C#.NET, JavaScript and PHP. As a starting point, the Health Level Seven (HL7®) International standards body maintains a list of open source FHIR implementations on its Wiki page.

In addition to open source FHIR libraries, many widely used health software systems now support FHIR as a standard message type, which means some consumers and providers may be able to create a GP Connect interface with extensions available on their current system.

Please refer to the Spine Core FHIR API Framework for details of open source FHIR client libraries and open source FHIR reference servers available for use.

All content is available under the Open Government Licence v3.0, except where otherwise stated