Skip to main page content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Access keys NCBI Homepage MyNCBI Homepage Main Content Main Navigation
. 2025 Mar 4:27:e68083.
doi: 10.2196/68083.

Empowering Health Care Actors to Contribute to the Implementation of Health Data Integration Platforms: Retrospective of the medEmotion Project

Affiliations

Empowering Health Care Actors to Contribute to the Implementation of Health Data Integration Platforms: Retrospective of the medEmotion Project

Marcel Parciak et al. J Med Internet Res. .

Abstract

Health data integration platforms are vital to drive collaborative, interdisciplinary medical research projects. Developing such a platform requires input from different stakeholders. Managing these stakeholders and steering platform development is challenging, and misaligning the platform to the partners' strategies might lead to a low acceptance of the final platform. We present the medEmotion project, a collaborative effort among 7 partners from health care, academia, and industry to develop a health data integration platform for the region of Limburg in Belgium. We focus on the development process and stakeholder engagement, aiming to give practical advice for similar future efforts based on our reflections on medEmotion. We introduce Personas to paraphrase different roles that stakeholders take and Demonstrators that summarize personas' requirements with respect to the platform. Both the personas and the demonstrators serve 2 purposes. First, they are used to define technical requirements for the medEmotion platform. Second, they represent a communication vehicle that simplifies discussions among all stakeholders. Based on the personas and demonstrators, we present the medEmotion platform based on components from the Microsoft Azure cloud. The demonstrators are based on real-world use cases and showcase the utility of the platform. We reflect on the development process of medEmotion and distill takeaway messages that will be helpful for future projects. Investing in community building, stakeholder engagement, and education is vital to building an ecosystem for a health data integration platform. Instead of academic-led projects, the health care providers themselves ideally drive collaboration among health care providers. The providers are best positioned to address hospital-specific requirements, while academics take a neutral mediator role. This also includes the ideation phase, where it is vital to ensure the involvement of all stakeholders. Finally, balancing innovation with implementation is key to developing an innovative yet sustainable health data integration platform.

Keywords: Belgium; Europe; collaborative; communication; data; data science; digital health; health care; health care providers; health data; health data integration; health data platform; hospital-specific requirements; integration platforms; personas; platform; real-world evidence.

PubMed Disclaimer

Conflict of interest statement

Conflicts of Interest: None declared.

Figures

Figure 1
Figure 1
Personas involved in the different demonstrators, with some of their focus points indicated. GDPR: General Data Protection Regulation.
Figure 2
Figure 2
A high-level overview of the medEmotion platform implementation. The figure shows components from 3 environments: On-premises (eg, a partner hospital), the Azure cloud, and External, which shows users outside the platform. Where applicable, we name the Microsoft Azure product used written in bold. The arrows indicate data flows, starting with the data sources on the left and flowing to the data users on the right. CDM: common data model; FHIR: Fast Healthcare Interoperability Resources; OHDSI: Observational Health Data Sciences and Informatics; OMOP: Observational Medical Outcomes Partnership.

References

    1. Martin-Sanchez FJ, Aguiar-Pulido V, Lopez-Campos GH, Peek N, Sacchi L. Secondary use and analysis of big data collected for patient care. Yearb Med Inform. 2017;26(01):28–37. doi: 10.1055/s-0037-1606529. - DOI - PMC - PubMed
    1. Peng C, Goswami P, Bai G. A literature review of current technologies on health data integration for patient-centered health management. Health Informatics J. 2020;26(3):1926–1951. doi: 10.1177/1460458219892387. - DOI - PubMed
    1. Zhang H, Lyu T, Yin P, Bost S, He X, Guo Y, Prosperi M, Hogan WR, Bian J. A scoping review of semantic integration of health data and information. Int J Med Inform. 2022;165:104834. doi: 10.1016/j.ijmedinf.2022.104834.S1386-5056(22)00148-4 - DOI - PubMed
    1. U.S. Food and Drug Administration U.S. food and drug administration. Framework for FDAs? Real-World Evidence Program. 2018. [2024-01-09]. https://www.fda.gov/media/120060/download?attachment .
    1. Ranchal R, Bastide P, Wang X, Gkoulalas-Divanis A, Mehra M, Bakthavachalam S, Lei H, Mohindra A. Disrupting healthcare silos: addressing data volume, velocity and variety with a cloud-native healthcare data ingestion service. IEEE J. Biomed. Health Inform. 2020;24(11):3182–3188. doi: 10.1109/jbhi.2020.3001518. - DOI - PubMed

LinkOut - more resources