Health data (ePA, FHIR)

Connecting health data: ePA, FHIR, and the telematics infrastructure

Health software has to write patient data securely into the electronic patient record (ePA), exchange it over FHIR, and sign users in through the GesundheitsID. appDev handles exactly that integration. We work as an integration and implementation partner on the approved telematics infrastructure, with a team that has already taken ePA applications for the German market into production.

Discuss your integration See the fixed-price pilot

01

What we connect

We connect your product to the services that are mandatory in the German healthcare system, and map the data cleanly onto your existing data model.

ePA integration. Write and read documents and structured data to and from the electronic patient record, with access control and consent.
FHIR integration. FHIR resources and profiles, mapping onto your data structures, interfaces to hospital (KIS), practice (PVS), and specialist systems.
GesundheitsID and identities. Sign-in and authentication via the GesundheitsID, connecting to the sectoral identity provider (sekIDP).
DiGA integration with the TI. The TI interfaces a DiGA needs, cleanly implemented and documented for operations.
TI specialist services. Connecting to the e-prescription (E-Rezept) and other specialist services, as far as your product needs them.

02

Our role: integration on approved infrastructure

The telematics infrastructure is approved and certified. We build on top of it. appDev delivers the integration of your product with this existing infrastructure. gematik distinguishes between manufacturers of approved components and providers that run solutions on top of them. We work on the provider and integration side. For you, that means less effort on your own side for the TI integration and a faster path into operations.

03

Experience from real ePA projects

Several of our engineering teams have years of hands-on ePA experience. That is rare in the market, and it is why this integration runs quickly and safely with us.

We helped build the application that manages the electronic patient record for a large statutory health insurer, in a tightly controlled telematics environment. What we implemented there:

FHIR data models and the integration with the TI specialist services.
Access control and consent management for accessing patient data.
Sign-in via the sectoral identity provider (sekIDP) and integration of further modules such as e-prescription (E-Rezept) and emergency data.
End-to-end auditability and documentation designed for the gematik audit.

04

The fixed-price entry point: FHIR/ePA Connect

You don't have to hand over the whole product to get started. FHIR/ePA Connect is a self-contained fixed-price building block for exactly one integration, built by us and handed over to your team. You get the full source code and can keep developing it yourself.

Discovery, €1,900 one-off. We scope your use case, clarify the interfaces, and deliver a solid effort and architecture assessment. The amount is credited toward the pilot.
Pilot, from €39,000. A working integration in six to eight weeks, with EU hosting and a full source-code hand-over.
Operations, from €1,900 per month. Maintenance, updates, and further development of the integration, if you'd like to hand it to us.

FHIR/ePA Connect is an integration building block for your product. It is a bespoke integration that we build for you.

Discuss your integration How the fixed-price pilot works

05

Who it's for

FHIR/ePA Connect is the best fit when you have your own product that needs to connect to the telematics infrastructure and you want to get into operation quickly.

Health SaaS providers, that want to exchange patient data over FHIR and connect to the ePA.
DiGA and DiPA providers, that need the TI integration for approval and operations.
Medtech manufacturers, connecting their device or companion software to ePA, FHIR, and the GesundheitsID.
Hospital and practice IT, looking to connect existing systems such as KIS or PVS to ePA, FHIR, and TI specialist services.

Reference

From our projects

Health and telematics large

Electronic patient record for a large statutory health insurer

Native Android app in the German telematics infrastructure

A new interface on an existing white-label base, FHIR data models, sign-in via the sectoral identity provider, consent management, connection of further specialist services such as e-prescription and emergency data. Complete traceability and documentation designed for the Gematik audit.

Passed the Gematik audit and in regular operation.

View project

Health and telematics medium

Document-to-FHIR extraction for lab and billing data

Structuring unstructured health data into FHIR

Extraction, mapping to FHIR profiles, validation and handover to the target system. A review step with expert sign-off.

Documents become checked FHIR resources for further processing.

View project

All references Get in touch

EU hosting

Processing and storage within the EU.

Data protection from the start

Data minimization and access control, built in from the very first design.

On approved telematics infrastructure

We connect your product to the approved TI components.

Frequently asked questions

What does an ePA or FHIR integration cost?

You start with a Discovery for €1,900, which we credit toward the pilot. The pilot starts at €39,000 and delivers a working integration in six to eight weeks. Ongoing operations start at €1,900 per month if you hand them to us.

Does appDev need its own gematik approval to connect our product?

We work on the already-approved telematics infrastructure and connect your product to the approved components. Approval of those components lies with their manufacturers. appDev is your integration and implementation partner on this infrastructure.

What's the difference between a manufacturer and a provider in the TI?

gematik approves individual components and services, such as record systems and identity providers. Their manufacturers hold the approval. Providers and integrators build solutions on this approved base. appDev works on the provider and integration side and connects your product to the existing services.

How quickly is a first working integration ready?

Usually in six to eight weeks. In week one we scope the use case, then we build, and testing and hand-over come at the end.

Do you support the GesundheitsID?

Yes. We connect sign-in via the GesundheitsID and the sectoral identity provider (sekIDP), just as we have already implemented it in production ePA applications.

What happens to the source code?

You get the full source code and documentation. Your team can run and develop the integration itself. We take over ongoing operations on request.

Get in touch

Discuss your integration. Reply the same business day.

Tell us about your use case. In the Discovery we clarify interfaces, effort, and architecture before you commit to the pilot.

Pick an open slot in the calendar directly. Free and without obligation.

Book a call online

Scheduling is provided by Zeeg (zeeg.me, servers in the EU). Loading it opens a connection to Zeeg and cookies may be set. More on this in the privacy policy.