Custom HL7 FHIR integration development
HL7 FHIR is HL7's standard for exchanging healthcare data, built on web technology that developers already know. In the Netherlands, MedMij, maternity care and eOverdracht (electronic patient handover) all use it, and many new information standards are being developed in FHIR. If your own software needs to offer or retrieve healthcare data as FHIR, following the profiles published by Nictiz, you need an integration that does this correctly. Appfront builds that integration.
What is an HL7 FHIR integration?
An HL7 FHIR integration enables your software to offer or retrieve healthcare data in the form FHIR prescribes. FHIR consists of resources: individual building blocks for concepts such as patient, healthcare professional, organisation, measurement, problem or medication. They are exchanged via a REST interface in JSON or XML, as a message or as a document. According to Nictiz, FHIR combines the best features of HL7 version 2, HL7 version 3 and CDA with modern web standards such as HTTP and OAuth. In the Netherlands, FHIR is used by MedMij, in maternity care and for eOverdracht, and many new information standards are being developed with it.
The base FHIR resources are deliberately generic. Agreements for a country or use case are recorded in profiles, with extensions and linked terminology. Nictiz works in layers: profiles that follow a zib (healthcare information building block) from the 2020 or 2024 release, above them the nl-core profiles intended for implementations, and profiles per information standard. FHIR R4 (version 4.0.1) is a mixed standard, with normative parts that remain stable and parts at Trial Use level. There is now an R5, but at Nictiz's request HL7 Netherlands has advised combining zib2024 with FHIR R4 and skipping R5. For an integration in Dutch healthcare, R4 is therefore the starting point.
We build custom because the data in your system rarely maps one-to-one onto a profile. For each resource, the integration defines where every element comes from, fills in the codes from the right code systems and validates every response against the profiles before it leaves the building. A CapabilityStatement describes which resources and searches your server supports, so another party knows what to expect. If your system needs to be qualified for an information standard, we prepare the integration for qualification with Nictiz. We establish with you in the first step which information standard and which profiles apply to you.
Resources
Your data as FHIR.
Profiles
According to nl-core and zibs.
Validated
Checked before sending.
How we build your HL7 FHIR integration
We start with your application: which data you want to provide or retrieve, with whom, and for which information standard. Then, for each resource, we create a mapping from the profiles to the fields in your system, which your functional administrator can review. We first build one resource completely, including search, validation and error handling, and test it with example messages from the profiles. The remaining resources, the CapabilityStatement and the security follow. When a new version of the profiles is released, we update the integration.
Data, partners, standard.
Profiles mapped to your fields.
Fully built and tested.
Remaining resources, and maintenance for new profiles.
What an HL7 FHIR integration actually does
The components below appear in almost every FHIR integration. Which ones you need depends on whether your system provides data, retrieves it, or both.
FHIR server
Resources provided via REST.
FHIR client
Retrieve data from others.
Mapping
Every element traced to its source.
Validation
Checked against the profiles.
Terminology
Codes from the right systems.
Log
Every request traceable.
Who we build an HL7 FHIR integration for
The integration is intended for organisations that build or maintain their own software and want to provide or use FHIR in it, whether for a national information standard or for their own data exchange.
Healthcare organisations
Your own systems on FHIR.
Software builders
FHIR in your healthcare software package.
Healthcare apps
Data from the source system.
Partnerships
Regional data exchange.
Technology and integrations
This page is about the FHIR interface itself: resources, profiles and validation. If you want to make data available to patients' personal health environments, see the MedMij integration. If the data in your system first needs to align with the healthcare information building blocks, read about the zibs integration, and for the minimum dataset for handover, the BgZ integration. If your hospital works with HiX, also see the ChipSoft integration. You can read about our approach at building software.
Why choose Appfront for your HL7 FHIR integration?
A FHIR interface that seems to work but doesn't conform to the profile, codes that don't come from the prescribed code systems, or an integration that breaks as soon as the profiles are updated: each of these costs you time with every new partner. That's what we build against: a mapping you can review, validation on every response, and an integration that keeps pace with new versions.
Traceable
Every element traced to its source.
Validated
Against the current profiles.
Kept up to date
New versions handled.
Security and privacy in an HL7 FHIR integration
A FHIR integration gives access to patients' health data. The integration supplies only the resources and elements the application needs, checks on every request who is making it and with which permissions, and logs every request with time, user and result. FHIR also has its own resources for this, such as AuditEvent and Provenance, which we can use if that suits your environment.
The integration runs in a European data centre or in your own environment, with encrypted connections and storage. Keys and certificates for connecting to other parties are kept secure and are not visible to staff. We agree with you in advance who may read or write which resources.
Frequently asked questions about an HL7 FHIR integration
Questions that information managers, architects and healthcare software vendors ask before starting with FHIR.
FHIR, Fast Healthcare Interoperability Resources, is an HL7 standard for exchanging healthcare data. Data is divided into resources, such as patient, observation or medication, which are exchanged in JSON or XML through a REST interface.
In Dutch healthcare, FHIR R4 is the starting point. At Nictiz's request, HL7 Netherlands has advised combining zib2024 with FHIR R4 and skipping R5. Which version an information standard prescribes is stated in that standard's specification.
Profiles that constrain and extend the general FHIR resources for the Dutch context. Nictiz builds them on the zib profiles and intends them as the layer for implementations. Information standards add their own profiles on top of these.
MedMij is a framework of agreements for exchange with patients' personal health environments, with its own requirements for participation, authorisation and login. The data services within it use FHIR. A FHIR integration is about the interface itself and can also serve other applications.
That depends on the information standard. Nictiz awards an XIS qualification when an information system complies with the information standard, and requires requalification when there is a new version of the standard or a major change. We prepare the integration for this.
Yes. Many hospital systems still exchange HL7 v2 messages internally. HL7 has an implementation guide that translates v2 messages, segments and data types to FHIR R4. An integration can serve both sides.
For organisations with their own software or data from multiple sources, and for vendors who want to include FHIR in their product. If your off-the-shelf package already offers a qualified FHIR interface for your application, a custom integration is usually not needed.
Want to provide or retrieve your data as FHIR?
Tell us which data you want to exchange and with whom. We'll show you how a FHIR integration handles that according to the Dutch profiles.