Explainer
MPIS, explained from the public record
The Medical Programme Information System grew out of a pandemic-era platform and became an operational hospital information system deployed across scores of Malaysian government hospitals. Here is what public material says, and where it stops.
Scale
What has been reported, and by whom
Deployment figures come from ministry presentation material and an academic visit report. Each carries a source marker.
~80S8
Hospitals using MPIS fully or modularly
By August 2024, according to the UGM visit report; 13 described as comprehensive.
Figures refer to varying levels and modules of MPIS deployment and should not be interpreted as 74–80 fully paperless hospitals.
Origins
Not simply a COVID system
MPIS has roots in the CPRC Hospital platform developed during the COVID-19 pandemic, but it did not stay there. Patient-management functionality was introduced in February 2021. In 2022 the system was implemented at Hospital Tanjong Karang, covering 114 beds within two weeks, and 17 hospitals had implemented the Patient Management component by the end of that year. In February 2023, approval was obtained for further expansion and CPRC Hospital was rebranded as MPIS.S1
Hospital-level and state health department publications from Perak, Penang and Melaka show implementation briefings, facility implementation committees and use across rehabilitation, dietetics, medical records and revenue or registration functions — evidence that adoption reached routine operational life inside facilities.S5S6S7
A platform that reached scores of hospitals is an installed base, not a pilot. Whatever happens next, its future should be stated.
Architecture
It was designed to be expanded
How public material describes the platform's structure — and the limits of what that description proves.
Web-based and cloud-native
Described in public material as a cloud-native, government-hosted platform rather than a per-hospital installed product.
Multi-tenant
One platform serving many facilities, which is the structural precondition for national scale-up without duplicating deployments.
Modular
Facilities can adopt components progressively, which explains why hospital counts differ depending on which module is being measured.
Designed for phased deployment
Public descriptions emphasise progressive implementation rather than single big-bang cutover.
Cross-facility information sharing
Public presentation material references tracing records from other hospitals and '1 Patient 1 ID' concepts.
Presented as cost-effective
Cost-effectiveness is asserted in public presentation material; this publication treats that as a claim awaiting a published lifecycle comparison.
Areas that may still require enhancement
Direction
Where the public conversation has moved
Public statements in 2025 described a shift towards off-the-shelf cloud EMR products on a subscription model, national scale-up across four zones, and emphasis on FHIR and HIMSS maturity frameworks.
Existing MPIS footprint
- · Operational platform
- · Modular
- · Cloud-native
- · Multi-tenant
- · Deployed across many hospitals at varying levels
- · Supports clinical and non-clinical functions
- · Already supported by public investment
New EMR direction
- · Off-the-shelf products
- · Subscription-based cloud model
- · National scale-up
- · Four zones / four EMRs publicly discussed in 2025
- · FHIR / interoperability emphasis
- · HIMSS maturity frameworks
This comparison describes strategic direction as reflected in public material. It is not a conclusion that MPIS is automatically superior to a procured commercial system, nor that the new direction is wrong. It is a statement of what exists today alongside what is being planned.S2S3
Still live
MPIS has not disappeared
On 19 May 2026, the Ministry of Health advertised Tender No. 85/2026 for technical support and maintenance covering MPIS hardware, software and applications; it closed on 12 June 2026. The ministry is therefore still maintaining and supporting the platform while pursuing a broader new digitalisation direction.S4
What a reader should still want to know
- Which modules are live in which hospitals today?
- How is the platform positioned in the national EMR roadmap after new procurements?
- Was a fit-gap analysis performed, and can it be published?
Continue to the functionality breakdown, the timeline, or the source register.