Clinical
- Electronic Medical Records (EMR)
- ICU
- Emergency Department (ED)
- Outpatient & Inpatient
- Pharmacy
- Laboratory
- Radiology
- Surgery
- Maternity & NICU
A complete guide to the hospital information system (HMS) — meaning, functions, modules, mandatory integrations, and compliance. Neutral and educational, with links to an in-depth discussion of each topic.
Definition
An HMS is software that manages every hospital process in an integrated way — from clinical services (medical records, pharmacy, laboratory) and finance through to administration and reporting. The goal: one consistent source of data, with no duplicate entry across units.
In Indonesia, a modern HMS is also the backbone of compliance: running EMR (Permenkes 24/2022), submitting data to SATUSEHAT, BPJS claims, and SIRS Online reporting.
For specific segment needs, see the HMS for clinics & small hospitals and the HMS for maternity hospitals.
Core modules
A complete HMS spans three major groups. Adievia provides 49 modules across all three.
Compliance
In Indonesia, an HMS is bound by a number of regulations: EMR (Permenkes 24/2022), SATUSEHAT interoperability (reinforced by Permenkes 6/2026), data protection (UU 27/2022 on Personal Data Protection, PDP), and accreditation (MRMIK). Learn about each obligation:
Choosing an HMS
There is no single answer. An open source HMS is free and useful, but compliance & maintenance become the hospital's responsibility; a paid vendor adds accountability & hands-on support. What matters is transparency on compliance, the right to exit with your data, and honest pricing.
FAQ
HMS stands for hospital information system (known in Indonesia as SIMRS — Sistem Informasi Manajemen Rumah Sakit) — software that manages every hospital process in an integrated way: clinical services (medical records, pharmacy, laboratory), finance (billing, accounting), and administration, through to reporting and interoperability with national systems such as BPJS and SATUSEHAT.
It unifies data so there is no duplicate entry across units, speeds up services, streamlines BPJS claims, meets regulatory obligations (EMR under Permenkes 24/2022, SATUSEHAT data submission, SIRS reporting), and safeguards the security and traceability of patient data.
An open source HMS is generally free and useful, but compliance, security, and maintenance become the hospital's responsibility. A paid HMS from a vendor adds accountability and hands-on support. What decides it is not the label but transparency on compliance, the right to exit with your data, and honest pricing.
Typically: electronic medical records, registration, outpatient & inpatient, pharmacy, laboratory, billing, plus the mandatory BPJS and SATUSEHAT integrations. Actual needs depend on the type and scale of the hospital.