EUVIMEDEUVIMED entdecken
Open Access · CC BY-NC 4.0

Transferable Migration Framework Derived from a Large-scale Tertiary Hospital EHR System

Hojun Yu, Keehyuck Lee, Sangbeob Lee, Yongchul Kim

Healthcare Informatics Research · 30.04.2026 · 32 (2) · 145-155

DOI: 10.4258/hir.2026.32.2.145 ↗

Kurz gefasst

Fachartikel in der Zeitschrift Healthcare Informatics Research, erschienen am 30.04.2026. Verfasst von Hojun Yu und 3 weiteren Autor:innen. Beteiligte Einrichtung: Office of Hospital Information, Seoul National University Hospital, Seoul, Korea. Die Arbeit nennt 16 Literaturangaben. Der Volltext ist frei zugänglich (Open Access, CC BY-NC 4.0).

AbstractSchlagwörterBibliografische AngabenZitierenVerwandte Studien

Abstract (Originalsprache)

Objectives

Migrating legacy on-premise electronic health record (EHR) systems in tertiary hospitals to modern cloud-native platforms presents technical and strategic challenges. We aimed to establish an optimized roadmap for transitioning legacy monolithic systems to a microservice architecture-based cloud-native EHR (MCEHR).

Methods

We conducted a 3-month strategic assessment and case study based on the modernization requirements of a global healthcare provider. The methodology incorporated semi-structured interviews with key stakeholders, including clinical informatics officers and system architects, to identify critical pain points such as .NET 4.0 end-of-support risks and performance bottlenecks during peak clinical hours. Phased hybrid migration was adopted, analyzing over 20 TB of Oracle-based legacy data and evaluating the technical feasibility of transitioning to .NET 9 and RESTful APIs. To ensure clinical safety, a proof-of-concept (PoC) environment was developed to simulate high-concurrency clinical workloads, emphasizing system resilience and transaction integrity during intensive order-entry periods.

Results

The transition to .NET 9 and MCEHR demonstrated 100% transaction integrity across 1,012 complex clinical test cases. Frontend and backend modernization showed high feasibility; however, migration of business logic embedded within legacy Oracle views represented a primary technical bottleneck, necessitating targeted decoupling. The PoC confirmed that RESTful API-based services maintained stable throughput under heavy concurrent loads, significantly reducing the risk of system-induced delays in clinical workflows.

Conclusions

Transitioning to an MCEHR architecture is complex but strategically essential. The proposed task force team roadmap outlines staged upgrades incorporating core technology modernization (.NET 9 and RESTful APIs), selective business component migration, and parallel DevOps adoption.

Schlagwörter

Stichwörter der Autor:innen

Cloud ComputingElectronic Health RecordHealth Information SystemsSoftware DesignSystems Integration

Autor:innen und Institutionen

  • Office of Hospital Information, Seoul National University Hospital, Seoul, Korea.
  • Interdisciplinary Program in Medical Informatics, Seoul National University College of Medicine, Seoul, Korea.
  • Business Division, ezCaretech Inc., Seoul, Korea. chrisruga@snubh.org.
  • Department of Family Medicine, Seoul National University Bundang Hospital, Seongnam, Korea. chrisruga@snubh.org.
  • Technology Division, ezCaretech Inc., Seoul, Korea.
  • Division of Nephrology, Department of Internal Medicine, Seoul National University Hospital, Seoul, Korea.

Zitieren

APA

Yu, H., Lee, K., Lee, S., & Kim, Y. (2026). Transferable Migration Framework Derived from a Large-scale Tertiary Hospital EHR System. Healthcare Informatics Research, 32(2), 145-155. https://doi.org/10.4258/hir.2026.32.2.145

Vancouver

Yu H, Lee K, Lee S, Kim Y. Transferable Migration Framework Derived from a Large-scale Tertiary Hospital EHR System. Healthcare Informatics Research. 2026;32(2):145-155. doi:10.4258/hir.2026.32.2.145

BibTeX
@article{Yu2026,
  author = {Yu, Hojun and Lee, Keehyuck and Lee, Sangbeob and Kim, Yongchul},
  title = {Transferable Migration Framework Derived from a Large-scale Tertiary Hospital EHR System},
  journal = {Healthcare Informatics Research},
  year = {2026},
  volume = {32},
  number = {2},
  pages = {145--155},
  doi = {10.4258/hir.2026.32.2.145}
}
Kostenlos starten →