Digital Health Applications (DiGA)

The digitalisation of healthcare is picking up speed

For a successful DiGA approval, however, a large number of data protection and information security requirements must be considered early and implemented "by design".

What is a digital health application (DiGA)?

A DiGA is an app, or more generally an IT application, that medical staff can prescribe. Colloquially, these applications are therefore often called "apps on prescription". Unlike simple "health apps", which have been available in large numbers in app stores for years, DiGA have been through an extensive official approval process and are consequently listed in the statutory health insurance (GKV) benefits catalogue as low-risk medical devices (class 1 or 2a under the European Medical Device Regulation, MDR). The advantage for patients is therefore that the applications can be prescribed by medical staff (like medicines) and the resulting costs are covered in full by the statutory health insurance funds. For an overview, all prescribable apps can also be found in the so-called DiGA directory, available online on the website of the Federal Institute for Drugs and Medical Devices (BfArM).

Smartphone with a medical cross next to a health record: digital health application

A key difference between digital health applications classified as medical devices and simple health or wellness apps is the evidence-based standard that the BfArM applies to DiGA. Within 12 months of the provisional approval of their app, DiGA manufacturers must use studies and verifiable data to show that their app brings about a so-called "positive healthcare effect" and thus a measurable benefit for patient health and/or the healthcare system as a whole. In other words, DiGA either have a clear medical benefit or they bring about measurable improvements in processes and structures that are relevant to patients.

The fast-track approval process

A manufacturer's route into the BfArM's DiGA directory as a verified, reimbursable application depends on successfully completing the so-called "fast-track" procedure. For this, manufacturers submit an application in which they must provide information on meeting various DiGA requirements. In addition to details of any positive healthcare effects already demonstrated, these include requirements on safety, functionality and quality, but also on interoperability, data protection and information security.

Hospital and smartphone with a medical cross

Data protection and information security in particular take up a great deal of space in the approval of a DiGA (DiGA Ordinance, Annexes I and II), and comprehensive compliance ("by design" and "by default") largely determines the long-term success or failure of a DiGA. Because the personal data involved is often highly sensitive within the meaning of Art. 9 GDPR, patients' acceptance of a DiGA ultimately stands and falls with data subjects' trust in the application's "confidentiality". The reason is simple: DiGA take over some tasks that until now were carried out exclusively by people, and patients' expectations regarding the confidentiality of their data are now transferred from medical staff to the DiGA.

Circular arrows around a grid with ticks: continuous review

Adaptability is required

Approving a digital health application is a complex major project that many manufacturers underestimate, because the people and departments that necessarily have to be involved range from data protection and information security officers to software developers and UX testers, as well as cloud providers, lawyers and project managers. Given the strong software component of such a project, it is also essential to engage with agile structures or project management methods such as Scrum, Kanban or Design Thinking, and to keep the iteration cycles within the project much shorter than in traditional project management.

Involving SDG

Annexes I and II of the so-called DiGA Ordinance (DiGAV) contain more than 80 items or statements on data protection and security-related questions in total, all of which must be answered when the application is submitted. Data protection experts are already familiar with the topics from the GDPR or from ISO standards: they cover the usual principles, legal bases and information obligations of the GDPR as well as questions on system hardening, access control and the implementation of an information security management system (ISMS). Important points include:

  • An ISMS under BSI 200-2 or alternatively under ISO 27001 has been mandatory for DiGA approval since 2 January 2022!
  • DiGA approval imposes much more restrictive data protection requirements than a look at the GDPR alone would suggest. In the case of third-country transfers, for example, the use of Art. 46 and 47 GDPR (standard contractual clauses and binding corporate rules) is completely excluded. Since there has also been no adequacy decision under Art. 45 for the USA since mid-2020, personal data in connection with a DiGA may under no circumstances be processed by companies based there or by their EU subsidiaries.
  • Because health data is personal data of a special category under Art. 9 GDPR, DiGA manufacturers must analyse, assess, reduce or even eliminate the risks associated with processing this data by means of a so-called data protection impact assessment (DPIA) under Art. 35 GDPR.
Logo of Süddeutsche Datenschutzgesellschaft (sdg)

Quality management, risk management, technical feasibility and a pragmatic view of the data protection framework: the number of points to consider is large and can feel overwhelming. Here we help you with interdisciplinary knowledge of technology and data protection and an unbiased outside view. As an external adviser, we are not "blind to the company's own shortcomings", and through years of supporting many companies from different sectors and industries we can offer extremely broad, practical expertise tailored precisely to your company, to make the approval of your DiGA a lasting success story.