Medical Software and DiGA Development - Our Blog

On December 19, 2019, the Digital Supply Act (DVG) made it possible for doctors to be able to prescribe digital health applications (DiGA) to patients in a standardized way for the first time. Now a counterpart has also been created for nursing care: digital care...

The implementation of a digital health application (DiGA) involves effort and costs that should ultimately be worthwhile for your company. And indeed - many certified DiGAs that make it onto the market show extremely positive prescription and sales figures. Others, on...

The development of a digital health application (DiGA) costs time and money and involves many regulatory hurdles. As a manufacturer, you naturally have an interest in ensuring that this effort pays off in the end. You probably already know that even if your...

Here you will find the most important links to the Digital Healthcare Act (DVG) and the Digital Health Applications Ordinance (DiGAV). This list is intended to help you access the relevant documents more quickly for regular reference. This page also provides an...

We would like to quickly introduce the topic of interoperability in DiGA development with a small example: “Μια DiGA πρέπει να πληροί ορισμένες απαιτήσεις διαλειτουργικότητας.” Do you understand this sentence? Unless you speak Greek, probably not. You therefore need...

Having fulfilled all regulatory parameters and been entered in the central DiGA directory, have all hurdles been cleared and a successful market entry guaranteed? Unfortunately not quite. Contrary to some wishful thinking, entry in the central DiGA directory itself...

Although Switzerland is geographically located in the heart of the EU, it is not part of it. This also affects manufacturers of (software) medical devices. Is it possible for MDR medical devices to enter the Swiss market without further ado? How do Swiss manufacturers...

If you are developing software that qualifies as a medical device under the Medical Device Regulation (MDR), validation is one of the most critical issues. Successful validation of your software is an absolute prerequisite for bringing your medical device to market....

Anyone involved in the development of software medical devices is certainly no stranger to the term "Quality management system" (QMS). You may also have heard of ISO 13485 in this context. ISO 13485 is a standard that defines the requirements for a quality management...

Attention manufacturers of electronic aids, implants and DiGA! From mid-2024, a new legal requirement will apply to improve interoperability between medical devices and digital health applications (DiGA) approved by the BfArM: §374a SGB V Specifically, this involves...

"Clinical evaluation? No problem!" "A doctor was recently interviewed in the Süddeutsche Zeitung! She clearly stated that mindfulness apps help with depression. We can refer to that, can't we?" Unfortunately, it's not that simple. Of course, our exaggerated example...

 What is the point of a DiGA if it does not improve patients' lives? There is none! This is why DiGAs are only justified when their positive supply effect has been proven. Only then do you have a chance of being permanently included in the BfArM register. Ultimately,...

IEC 62304 specifies processes and activities that you must observe when developing software as a medical device. It places specific requirements on how you must develop and maintain your software. This applies both to stand-alone software (e.g. medical apps) and to...

A large number of electronic devices are used in medicine, and medical apps are now also increasingly being used. However, a major problem to date is that many of these devices cannot “talk” to each other: Exchanging data is often difficult or impossible. In this...