About
An editorial project about process, not personalities
This independent publication tracks Malaysia's digital health transformation, with particular attention to hospital digitalisation, EMR strategy, interoperability, continuity of public digital assets, governance and value-for-money.
Purpose
Why this publication exists
This independent publication tracks Malaysia's digital health transformation, with particular attention to hospital digitalisation, EMR strategy, interoperability, continuity of public digital assets, governance and value-for-money. It exists to ask evidence-based questions, publish critical analysis, and document the evolution of healthcare digitisation in Malaysia over time.
It takes no position on which vendor, platform or architecture Malaysia should choose. It takes a position on disclosure: options analysis funded by public money should be visible to the public.
Any answer can be right. An unpublished answer cannot be checked.
Method
How this desk works
No invented facts
Nothing is asserted that cannot be traced to a citable document. Where analysis is inference, it is labelled as inference in the text.
Source types are labelled
Official material, hospital and state health department publications, tender notices, academic reports, media coverage and vendor claims are weighted differently and marked as such.
Conservative figures preferred
Where vendor claims exceed official reported figures, the conservative official figures are used in the site's own statements.
Process, never persons
This publication examines decisions, documents and disclosures. It does not publish allegations about individuals, and it does not treat officials as the story.
Right of reply
Any organisation named in reporting may respond. Sourced rebuttals are published in full alongside the original piece.
Corrections in the open
Errors are corrected on the page, with a note describing what changed and when. Upcoming articles are marked as unpublished and never presented as completed reporting.
Independence
Disclosure
All material is published under the Editorial Desk. This publication deliberately does not attach individual names, biographies, personal social accounts or personal contact details to its work: the evidence should carry the argument, and no contributor should become the subject of the story. Where a contact field is technically required, the generic placeholder editorial@example.com is used.
The publication is unaffiliated with any vendor, supplier or bidder in Malaysia's health technology market and accepts no advertising from parties with an interest in the outcome of the programmes it covers.
Why this matters
The stakes behind the reporting
Taxpayer value
Public money has already been committed to building, deploying and supporting an operational platform. Whether that investment is extended or written off should be a documented decision.
Continuity of patient data
Millions of registered patient records exist inside current systems. Their migration, integrity and accessibility are clinical safety issues, not just technical ones.
Institutional memory
Years of configuration, workflow knowledge and local adaptation live inside a deployed system and inside the teams that run it.
Avoiding duplicated capability
Procuring capability that already exists and functions is the most avoidable category of public IT waste.
Migration risk
Cutover in live hospitals carries operational and clinical risk that rarely appears in headline procurement pricing.
Total cost of ownership transparency
Subscription pricing, interfaces, training, change management and parallel running determine real lifecycle cost far more than licence headline figures.
Interoperability
Multiple procured EMRs must exchange data reliably, or the country replaces one generation of silos with another.
National digital sovereignty and capability
The ability to build, adapt and maintain public health systems domestically is a strategic capability, and it is easier to lose than to rebuild.
Accountability
Questions MOH should answer
On the record
- 1What MPIS modules are currently live, by hospital?
- 2Which hospitals are using MPIS comprehensively versus only registration or selected modules?
- 3What is the current technical architecture and lifecycle assessment of the platform?
- 4What functionality is missing against the future HIS/EMR specification?
- 5Was a formal fit-gap analysis performed before choosing the new procurement direction?
- 6What is the comparative 7–10 year total cost of ownership of enhancing MPIS versus subscribing to new systems?
- 7What is the coexistence and migration strategy for MPIS hospitals and their data?
- 8How will four EMRs avoid creating another generation of silos?
- 9What role will FHIR and common terminology / data models play?
- 10What is MPIS's intended role after the new national EMR procurements?
Read the flagship article, the timeline, or the source register.