Skip to content
#software testing Open access

Digitalization of the Mandatory Notifications System for Infectious Diseases in Germany: Implementation of DEMIS (the German Electronic Reporting and Information System)

Sep 2026 · JMIR Medical Informatics · Vol 14 · 0 citations · 24 references
Medicine

TL;DR

The implementation of DEMIS is described from conceptualization to deployment and evaluation as well as the associated challenges, which enable secure data exchange across many stakeholders and interoperable data processing across different software systems.

Abstract

Abstract Background Mandatory notifications of infectious diseases in Germany were paper based until the implementation of DEMIS (Deutsches Elektronisches Melde- und Informationssystem für den Infektionsschutz; German Electronic Reporting and Information System) in 2020. DEMIS provides technical infrastructure for electronic reporting of infectious diseases to public health authorities, with the goal of streamlining processes through automation and reducing the burden of manual data entry. Objective DEMIS provides Fast Healthcare Interoperability Resources (FHIR)–based interfaces for mandatory notification systems that can be accessed by multiple authentication methods for different user groups, such as laboratories, hospitals, and public health authorities. In this paper, we describe the implementation of DEMIS from conceptualization to deployment and evaluation as well as the associated challenges. Methods Conceptualization of DEMIS was initiated in 2012 by the Robert Koch Institute, Fraunhofer FOKUS, and the German Federal Ministry of Health. The implementation was accelerated during the COVID-19 pandemic in 2020 with support from gematik, Germany’s national digital health agency. DEMIS uses FHIR interfaces and standardized terminologies, such as LOINC (Logical Observation Identifiers Names and Codes) and SNOMED CT (Systematized Nomenclature of Medicine–Clinical Terms), to digitally submit basic information on notifiers and patients along with specific diagnostics, clinical data, and epidemiological information from physicians and laboratories to public health authorities. The use of FHIR should ensure interoperability with other surveillance systems. DEMIS provides access either directly via an FHIR-based API or through a web portal. Then, DEMIS notifications will be integrated into the recipient’s specialized software. The deployment of FHIR packages in DEMIS will be published on simplifier.net. Finally, the notification data coming via DEMIS will be monitored and evaluated thoroughly. The whole process from implementation to deployment should be supported with active communication between stakeholders. Implementation (Results) The first surveillance module was deployed for SARS-CoV-2 notifications during the COVID-19 pandemic in 2020. Since then, DEMIS availability has been over 95% per month, and usually above 99%. As of August 2025, there were 697 laboratories, 1670 hospitals, and 870 other institutions such as private test centers, pharmacies, and general practitioners in Germany that have accessed DEMIS via the API. DEMIS has handled roughly 50 million pathogen notifications and 500,000 disease notifications to date, routed to all 376 local public health authorities. For notifiable pathogens, data quality has been routinely assessed and reported back to the laboratories. On average, 92% (92,378/100,579) of the notifications included a LOINC code. Conclusions DEMIS plays a key role in digitizing health care. It enables secure data exchange across many stakeholders and interoperable data processing across different software systems. Operations have functioned reliably since rollout. Ongoing routine data quality assessment could further enhance DEMIS performance. As DEMIS expands to other surveillance systems, continued discussion on semantic interoperability is necessary.

Read PDF

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.