Authors:<\/strong><\/p>\n Alexandra Heuel, Project <\/strong>Manager at BAYOOMED<\/p>\n Julia Schliesch, Marketing <\/strong>Generalist at BAYOOMED<\/p>\n<\/div> Effective July 1, 2026,<\/strong> new requirements apply to permanently listed digital health applications (DiGA) as part of the application-accompanying effectiveness measurement (AbEM)<\/strong>. This means manufacturers will face additional DiGA requirements<\/strong> that go far beyond mere documentation obligations.<\/p>\n While the focus has primarily been on demonstrating a positive impact on care, the actual use of digital health applications in everyday clinical practice will also become increasingly important in the future.<\/p>\n Manufacturers must be able to provide verifiable evidence of how their DiGA is used and must collect, analyze, and submit the necessary data to the Federal Institute for Drugs and Medical Devices (BfArM) in a manner that complies with regulatory requirements. These requirements therefore apply not only to regulatory processes but also to technical implementation, reporting, and, in the long term, the economic evaluation of a DiGA.<\/p>\n Measuring success throughout the course of use thus becomes an integral part of a DiGA\u2019s product life cycle\u2014with implications for development, operation, and, in the future, reimbursement as well.<\/p>\n<\/div><\/div><\/div><\/div><\/div> Through the post-implementation effectiveness assessment (AbEM), lawmakers aim to understand how digital health applications are actually used in everyday healthcare practice following their regulation. At the same time, the goal is to align reimbursement for digital health applications more closely with their actual use and to allocate statutory health insurance funds in a more targeted manner.<\/p>\n Among other things, the focus is on the following questions:<\/p>\n<\/div> Is a DiGA actually used after it has been prescribed?<\/p>\n<\/div><\/li> How often is the application used?<\/p>\n<\/div><\/li> Is it used regularly, or is it discontinued prematurely?<\/p>\n<\/div><\/li> How does usage change over the entire period covered by the regulation?<\/p>\n<\/div><\/li><\/ul> In the future, the data collected will be used in both the regulatory and economic evaluation of a DiGA. Starting in 2027, the results of the AbEM may affect up to 20% of the reimbursement for a permanently listed DiGA.<\/strong><\/p>\n<\/div><\/div><\/div><\/div><\/div> The introduction of real-world outcome measurement presents DiGA developers with new professional, technical, and regulatory challenges. Unlike with retrospective data analysis, the requirements of real-world outcome measurement must be taken into account as early as the design and development phases of a DiGA.<\/p>\n Among the most important challenges are:<\/p>\n<\/div> Development of a technical framework<\/strong> for measuring success throughout the application process and for selecting appropriate performance metrics.<\/p>\n<\/div><\/li> Taking regulatory requirements into account<\/strong> as early as the planning phase to ensure that data collection and reporting comply with the provisions of the DiGAV.<\/p>\n<\/div><\/li> Integration of appropriate analytics solutions<\/strong> that automatically and transparently collect usage data within the DiGA.<\/p>\n<\/div><\/li> Preparation of a standardized reporting system<\/strong> for the regular submission of the required data to the BfArM.<\/p>\n<\/div><\/li> Close collaboration among various departments<\/strong>, such as Product Management, software engineering, Regulatory Affairs, and Quality Management.<\/p>\n<\/div><\/li><\/ul> Those who do not take these requirements into account until shortly before implementation often have to expect additional development work, adjustments to the software architecture, and delays in the project schedule.<\/p>\n<\/div><\/div><\/div><\/div><\/div> Under the first phase of the AbEM<\/strong>, which has been in effect since July 1, 2026<\/strong>, objectively measurable usage data will initially be collected. The goal is to be able to track how a DiGA is actually used in everyday healthcare practice following its regulation.<\/p>\n The data currently being collected includes, among other things:<\/p>\n<\/div> Filled prescriptions and follow-up prescriptions<\/p>\n<\/div><\/li> Scope of Use<\/p>\n<\/div><\/li> Frequency of use<\/p>\n<\/div><\/li> Defined termination criteria<\/p>\n<\/div><\/li> Key Performance Indicators<\/p>\n<\/div><\/li><\/ul> Data collection takes place directly within the DiGA<\/strong>. External data collection methods such as email, text messages, or push notifications are not provided for under the AbEM. At the same time, data collection is limited to the information defined by regulations\u2014comprehensive user tracking is expressly not the goal of the AbEM.<\/p>\n Participation in the surveys for later phases of the program is voluntary for insured individuals. If users decide not to participate, they will not face any disadvantages as a result, and they are not required to explain their decision.<\/p>\n The collected data is recorded automatically, standardized, and then submitted quarterly to the Federal Institute for Drugs and Medical Devices (BfArM)<\/strong> as part of a report.<\/p>\n Plans are already in place to gradually expand the measurement of outcomes during treatment. While the first phase of expansion focuses on objective usage data, subsequent phases will also collect patient-reported information such as the Patient Global Impression of Change (PGI-C)<\/strong>, patient satisfaction<\/strong>, and indication-specific Patient-Reported Outcome Measures (PROMs)<\/strong>.<\/p>\n<\/div><\/div><\/div><\/div><\/div> The technical implementation of performance measurement within applications goes far beyond simply collecting usage data. The goal is to integrate the necessary analytics mechanisms into existing applications in such a way that data collection is automated, reliable, and compliant with regulatory requirements.<\/p>\n The new features must be seamlessly integrated into the existing system architecture without compromising the user experience. At the same time, aspects such as data quality, traceability, and the standardized processing of the collected information for reporting to the BfArM must be taken into account.<\/p>\n Those who take these requirements into account early on in the design and development of a DiGA lay the groundwork for efficient implementation and significantly reduce the effort required for later adjustments.<\/p>\n<\/div><\/div><\/div><\/div><\/div> BAYOOMED has already implemented the first phase of its in-use effectiveness measurement for a digital health application.<\/p>\n Analytics solutions<\/strong> were implemented in accordance with current best practices<\/strong> to automatically and reliably collect the usage data required by regulators. Particular attention was paid to seamless integration into the existing application and to establishing a robust foundation for future reporting to the BfArM.<\/p>\n<\/div><\/div><\/div><\/div><\/div> Measuring success throughout the use of a digital health application is much more than just a new regulatory requirement. It is bringing about lasting changes to the types of data that digital health applications will need to collect in the future and to how manufacturers develop, operate, and improve their products.<\/p>\n With AbEM, usage data becomes an integral part of the DiGA lifecycle. At the same time, it is becoming increasingly important not only for regulatory purposes but also for the economic evaluation of an application.<\/p>\n For manufacturers, this means that those who integrate these requirements early on in the design, development, and operation phases lay the groundwork for efficient implementation, reduce the need for later adjustments, and are best prepared for future regulatory developments.<\/p>\n<\/div><\/div><\/div><\/div><\/div> Measuring success during use is just one component of a DiGA\u2019s lifecycle. From the initial idea through development and approval to operation, further development, and regulatory requirements, we support manufacturers throughout the entire product lifecycle. Learn how BAYOOMED supports you throughout the entire DiGA lifecycle<\/a>.<\/p>\n<\/div><\/div><\/div><\/div><\/div>The requirements for DiGA manufacturers are changing<\/h2><\/h2><\/div>
Why was the program-based performance measurement introduced?<\/h2><\/h2><\/div>
What challenges does AbEM present?<\/h2><\/h2><\/div>
What data is currently being collected?<\/h2><\/h2><\/div>
What does this mean in terms of technical implementation?<\/h2><\/h2><\/div>
How BAYOOMED Supports Manufacturers<\/h2><\/h2><\/div>
Conclusion<\/h2><\/h2><\/div>
Further information<\/h2><\/h2><\/div>