Before Malaysia Buys the Next EMR, What Happened to MPIS?

Malaysia needs to digitalise its public hospitals. On that point, there should be little disagreement.

The Ministry of Health has acknowledged that electronic medical records are not comprehensively deployed and that greater interoperability is required across the health system. The current Digital Health Division has therefore articulated an ambitious direction: accelerate hospital digitalisation, move towards cloud-based systems, adopt international interoperability standards, and create a model in which a person's health information can follow the patient across the healthcare system.S2S3

These are worthy objectives.

But before Malaysia commits itself to another generation of EMR and Hospital Information System procurement, there is an important question that deserves much more attention.

More importantly:

MPIS is not simply a COVID system

MPIS has roots in the CPRC Hospital platform developed during the COVID-19 pandemic, but the platform subsequently evolved considerably.S1

Public MOH and MyGovCloud material states that patient-management functionality was introduced in February 2021. In 2022, MPIS was implemented at Hospital Tanjong Karang, covering 114 beds within two weeks, and by the end of that year 17 hospitals had implemented the Patient Management component. In February 2023, approval was obtained for further expansion and CPRC Hospital was rebranded as MPIS.S1

By the first quarter of 2024, public MOH material reported more than 2.5 million registered patients, more than 39,000 users, 74 hospitals using Patient Management, eight hospitals with comprehensive implementation, 66 undergoing progressive implementation, and seven operating MPIS together with legacy systems.S1

A subsequent August 2024 report by UGM Health Policy and Management, following a visit to MOH, described around 80 hospitals as using MPIS either fully or modularly, with 13 using it comprehensively at that stage, and described a wider 149-hospital implementation ambition.S8

What does MPIS actually do?

Public materials — ministry presentation decks, hospital and state health department bulletins, and operational training sites — show functionality far broader than a simple data-collection system. Across published sources, MPIS is described as covering inpatient and outpatient patient management, clinical orders and ancillary services, medical records management, programme and hospital management, asset management, clinical surveillance, workforce management, billing and revenue, helpdesk and operational support, and reporting and business intelligence.S1S9S7S5S6

The full module-by-module breakdown, with the source behind each group, is set out on this site's MPIS functionality page. It is deliberately presented as a description of what public material claims the platform covers, not as an independent audit of how well each function performs in practice.

Vendor claim: MHNexus publicly describes MPIS as a 24-module cloud-native enterprise solution integrated with LIS, RIS/GEPACS and SMRP, and states deployment across 152 MOH hospitals. That is reproduced here as a vendor claim, not as independently verified fact. This publication continues to use the more conservative 74 and approximately 80 hospital figures for actual usage at the cited dates.S10

It was designed to be expanded

Public descriptions present MPIS as web-based, cloud-native, government-hosted, multi-tenant and modular; designed for phased deployment; capable of sharing health information across facilities; and cost-effective relative to alternatives.S1S8

Modular architecture does not prove suitability for every tertiary-hospital requirement. Large referral hospitals impose demands — depth of clinical documentation, complex medication workflows, high availability, integration breadth — that a platform grown from district-level deployment may not yet meet. That is precisely why a fit-gap analysis is essential before replacement, rather than after it.

Areas that may still require enhancement, and which any honest assessment should test, include the following.

• Advanced medication management
• Specialised clinical workflows
• Clinical decision support
• Interoperability with national and third-party systems
• Cybersecurity posture
• Usability for high-volume clinical settings
• High availability and resilience
• Analytics and reporting depth
• Integration breadth across ancillary systems
• Mature tertiary-hospital requirements

Yet the current public digitalisation narrative focuses on another EMR future

Public statements in 2025 by the Digital Health Division director, Dr Mahesh Appannan, as reported by CodeBlue and Healthcare IT News, described a clear strategic direction: transition to off-the-shelf cloud EMR systems; a subscription model rather than building internally; a view that internally developed systems were reaching end-of-lifecycle and that the ministry lacked capacity to maintain the pace of technology change; the One Record, One Citizen direction; four zones using four EMRs; a first procurement covering 16 hospitals; and FHIR together with HIMSS EMRAM as important frameworks.S2S3

The editorial observation is narrow and should be read precisely: in these major public explanations of the future architecture, MPIS is not prominently presented as the existing platform to be evaluated first for expansion. That is an observation about the public strategy statements reviewed for this article. It is not a claim that MOH has never mentioned MPIS anywhere, nor that officials hold no internal view of its future.S2S3

MPIS has not actually disappeared

On 19 May 2026, the Ministry of Health advertised Tender No. 85/2026 for technical support and maintenance services covering MPIS hardware, software and applications. The tender closed on 12 June 2026.S4

That matters for a simple reason: the ministry is still maintaining and supporting MPIS while simultaneously pursuing a broader new digitalisation direction. A platform that is being funded for continued support is, by definition, still part of the operating estate — which strengthens rather than weakens the case for stating publicly what its long-term role is.S4

This should not become old team versus new team

Public digital assets should survive leadership and organisational transitions. Systems built with public funds are government assets, not the property of a particular departmental generation, vendor relationship or era of policy enthusiasm.

Framing this as a contest between the people who built one thing and the people now planning another would be both unfair and unproductive. The subject here is institutional continuity and taxpayer value — how a country carries forward what it has already paid for, and documents the reasoning when it decides not to.

The correct question is not MPIS versus innovation

This article does not argue that MPIS must be retained forever, and it does not rely on sunk-cost logic. Money already spent is not, by itself, a reason to keep spending. If a transparent technical, clinical and financial assessment concludes that replacement delivers better outcomes and better lifecycle value, replacement may well be justified.

What is missing from the public record is the assessment itself. The remedy is straightforward: an MPIS fit-gap and total cost of ownership assessment, published in a form outside experts can examine.

Reuse, improve, integrate — then replace where necessary

A defensible sequence for any national health platform decision is not complicated, and it is applied routinely in comparable public technology programmes.

1. 1Reuse what works.
2. 2Develop what can be improved.
3. 3Integrate what provides additional value.
4. 4Replace only where the existing platform demonstrably cannot meet requirements, or where replacement offers superior lifecycle value.

That is not resistance to innovation. It is responsible digital governance.