Using an existing a FHIR library
GP Connect strongly advises suppliers to utilize 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 boiler plate code required to configuring provider endpoints, structuring a requests and validate consumed resources. This will help keep the code base smaller, 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?
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.
A short list of some open source FHIR clients
The following open source FHIR client libraries are available on GitHub:
A short list of some open source FHIR servers
The following open source FHIR server libraries are available on GitHub: