Functionality
Eleven functional groups and 85 documented functions, compiled from ministry presentation material, hospital and state health department publications, and operational training sites. This is a description of what published sources claim the platform covers — not an independent audit of how well each function performs.
How to read this page
Each group lists the source material behind it. Where a function appears only in vendor material, it is marked as such rather than folded into the official picture.
Admission-to-discharge workflows for ward-based care.
Registration, clinics, allied health and emergency department flows.
Ordering and the ancillary systems that fulfil those orders.
The record layer: storage, retrieval, classification and identity.
Facility-level and programme-level operational management.
Equipment planning, procurement support and multi-level approval.
Registration, verification and mortality-related surveillance.
Clinical workforce administration, training and supervision.
Charging, deposits and revenue workflows at facility level.
Support tooling around the platform itself.
Facility and national reporting and analytics layers.
Attribution
Vendor claim — not independently verified
The vendor MHNexus publicly describes MPIS as a 24-module cloud-native enterprise solution integrated with LIS, RIS/GEPACS and SMRP, and states that it has been deployed across 152 MOH hospitals. This publication reproduces that as a vendor claim, not as independently verified fact. The deployment figures used elsewhere on this site remain the more conservative 74 and approximately 80 hospital figures reported for actual usage at the cited dates.S10
Next step
Documented functionality is only half the exercise. The other half is the published requirement set it should be measured against.
Five questions
Read the argument in full in the flagship article, or check the references.