BfArM Digitale Anwendungen
3.0.2-RC1 - draft
BfArM Digitale Anwendungen - Local Development build (v3.0.2-RC1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
This implementation guide documents the DiGA-API software interface for providing data from the DiGA directory, i.e. the directory of Digital Health Applications (DiGA) that have been assessed by the BfArM in accordance with § 139e of Book V of the German Social Code (SGB V).
Pursuant to § 21(2) and (3) of the Digital Health Applications Ordinance (Digitale-Gesundheitsanwendungen-Verordnung – DiGAV), the BfArM has been providing authorised users with the data published in the DiGA directory in machine-readable form upon request since 1 January 2021. These data are made available via a programming interface (DiGA-API) documented in this implementation guide. The guide also provides initial descriptions of use cases for the authorised user groups.
Pursuant to 21(2) DiGAV, third parties are authorised to use the DiGA-API where this is necessary for the use of electronic prescriptions for benefits under 21(2) DiGAV, third parties are authorised to use the DiGA-API where this is necessary for the use of electronic prescriptions for benefits under
In addition, pursuant to § 21(3) DiGAV, the following may apply for access to the DiGA-API:
The DiGA-API supports typical scenarios for working with Digital Health Applications. The following provides an overview of these.
Prescribing a DiGA
Physicians and psychotherapists can use their practice software to find out about DiGA available for their patients, select a suitable application and the appropriate prescription unit, and initiate the prescribing process (automated completion of the standard prescription form Muster 16). The completed prescription is handed over to the patient. The main actors involved, in addition to the treating professional and the patient, are vendors of practice software.
Billing by statutory health insurance funds
After a patient has submitted a prescription or application, the statutory health insurance fund checks the patient’s entitlement to the specific DiGA and, if entitled, sends an activation code to the patient. The DiGA manufacturer then bills the costs to the statutory health insurance fund by reference to the activation code.
Quality transparency
The DiGA directory enables transparency on the market and the quality of DiGA in line with a public reporting model. Data from the directory may be processed and published for end users by quality transparency initiatives, consumer protection organisations or other providers, possibly enriched with additional quality or rating data. This allows consumers to find out about the range and quality of Digital Health Applications.
To use the DiGA-API, you must be authorised under § 21(2) or (3) DiGAV and, as a first step, submit an application for use. The following steps are required until the DiGA-API is made available to you:
1. Create a user account
To submit an application to use the DiGA-API, you first need a user account for the electronic API application portal. You can create the account at antrag-api.bfarm.de.
2. Activate your user account
After creating your account, you will receive an email with a link to activate it. Opening the URL provided and setting a password activates your user account.
3. Submit your application for API use
Within the electronic API application portal, you can submit an application to use the DiGA-API under the “Anträge” (Applications) menu item. Your application will be reviewed by the BfArM after submission, and you will receive an email notification of its acceptance or rejection.
When your application to use the DiGA-API is accepted, you will receive a notification by email. From that point on, you have access to your individual API token (Bearer token) in the dashboard of the electronic API application portal. You must treat your token as confidential and must not pass it on under any circumstances.