SIMRS Implementation Costs: A Complete Breakdown and How to Save Budget

On average, type C hospitals in Indonesia spend Rp 250–400 million for SIMRS licenses, then are surprised when the first-year bill swells by 60–80% because of line items not included in the RAB: SatuSehat bridging, legacy medical record migration, backup servers, night-shift training, and maintenance contracts. As an Operations Manager supporting SIMRS and SIM Klinik implementations in Yogyakarta, DIY, and Magelang, I often see RABs prepared only from vendor quotations — without a five-year TCO (total cost of ownership). As a result, projects stop midway, pharmacy and support modules remain inactive, and staff return to Excel. This article breaks down the details of SIMRS implementation costs with concrete figures per component, a TCO calculation example, and ways to save budget without cutting what is truly critical.

Details of SIMRS Implementation Cost Components

SIMRS costs are divided into two: CAPEX (licenses, servers, initial implementation) and OPEX (maintenance, cloud, support, retraining). For a 100-bed hospital with 8–12 core modules (registration, outpatient, inpatient, pharmacy, laboratory, radiology, billing, claims), a perpetual license is generally Rp 150–350 million; a subscription model is Rp 8–20 million/month. A primary clinic with 2–5 polyclinics is much cheaper: SIM Klinik is Rp 15–60 million one-time or Rp 1.5–5 million/month. Those prices usually do not include bridging and customization.

Infrastructure: a decent on-premise server (Xeon Silver, 64 GB RAM, SSD RAID-1) plus UPS and NAS backup falls in the Rp 35–70 million range, plus Windows Server/Database licenses of Rp 15–25 million if not using an open-source stack. A managed cloud VPS alternative is Rp 1.5–4 million/month for a clinic, or Rp 4–12 million/month for a hospital with 150+ concurrent users. Dual-server redundancy for high availability adds 60–80% to the cost of a single server.

Implementation and configuration are the most often underestimated cost items: 20–35% of the license value, or Rp 30–90 million. This includes business process analysis, master data preparation (ICD-10, formulary, INA-CBG tariffs, polyclinic–doctor–payer mapping), role-based access rights configuration, and UAT. Historical data migration adds Rp 10–40 million: cleaning duplicate patients, normalizing date formats, and mapping lab results from the old LIS are manual tasks that can rarely be fully automated.

External integration is now a mandatory cost. BPJS bridging (VClaim, Antrean Online, iCare) is Rp 15–40 million, SatuSehat integration with FHIR R4 standards is Rp 20–50 million, and INA-CBG e-Klaim is Rp 10–25 million, depending on vendor API readiness. For each FHIR resource — Patient, Encounter, Condition, Observation — field mapping, terminology validation, and testing in the Kemenkes sandbox are required; the test cycle is usually 3–8 weeks. Add training of Rp 10–30 million and annual maintenance of 15–22% of the license value.

Calculating 5-Year TCO with a Real Example

Take the case of a 120-bed private hospital in DIY that chose a vendor with a license of Rp 240 million and maintenance at 18%/year. The initially approved RAB was Rp 420 million; the five-year realization was Rp 1.05 billion. The difference came from SatuSehat bridging, which only became mandatory in year two, the addition of a radiology module, server upgrades, and two rounds of retraining due to staff turnover.

The following Python 3.11 script summarizes the TCO calculation from the components above. Run it with python hitung_tco_simrs.py, then replace the figures according to your vendor quotation.

# hitung_tco_simrs.py — Python 3.11
komponen = {
    'lisensi': 240_000_000,
    'implementasi': 60_000_000,
    'server_dan_backup': 55_000_000,
    'bridging_bpjs_satusehat': 55_000_000,
    'pelatihan': 20_000_000,
}
maintenance_rate, tahun = 0.18, 5
capex = sum(komponen.values())
opex = komponen['lisensi'] * maintenance_rate * tahun
print(f'TCO {tahun} tahun: Rp {capex + opex:,.0f}'.replace(',', '.'))

The script output above is Rp 646,000,000 — a figure far more realistic to present to the board of directors than the license price alone. This figure also becomes a negotiation basis: when a vendor offers a license of Rp 180 million, you can ask how much SatuSehat bridging costs, whether first-year maintenance is included, and whether API documentation is handed over. Such questions usually cut 10–20% off the contract value because vendors avoid hidden costs.

How to Save Budget Without Sacrificing Quality

First, apply a phased rollout: activate registration, cashier, and pharmacy in phase 1; laboratory and claims in phase 2. This spreads spending across two budget years, reduces the change burden, and provides room for evaluation before committing to the next modules. Many hospitals force a go-live of 12 modules at once and then lose momentum in the third month.

Second, consider open source such as SIMRS Khanza or a Laravel/PostgreSQL stack for non-critical modules. The license becomes zero, but honestly calculate the internal cost: one full-time PHP/Laravel developer is equivalent to Rp 90–150 million/year, and bridging still costs money. Open source is superior if your IT team has maintenance capacity; if not, a vendor subscription is cheaper than one vacant position.

Third, negotiate maintenance as a fixed percentage with clear SLAs, not a per-ticket cost, plus a maximum escalation clause of 5%/year. Fourth, run migration and training using a train-the-trainer pattern: train 5 internal super users, then they train 100+ staff — a realistic saving of Rp 15–25 million per cycle.

Fifth, choose an implementation partner that is geographically close. For hospitals and clinics in Yogyakarta, DIY, and Magelang, working with a local IT consultant cuts travel costs, accommodation, and onsite response time from days to hours. IT consulting and application development services (SIMRS, SIM Klinik, ERP, POS, website) based in this region generally offer more competitive rates without lowering technical standards, because their teams understand the regulatory context and work flows of local healthcare facilities.

Best Practices

1. Draft a 5-year TCO before signing the contract, not just the first-year license price.
2. Lock the bridging scope (BPJS VClaim, SatuSehat FHIR R4, e-Klaim) with measurable completion definitions.
3. Implement phased rollout and go-live per module with written UAT criteria.
4. Require API documentation, database schema, and admin guide as contract deliverables.
5. Budget a 10% contingency and review maintenance costs annually against actual ticket volume.

FAQ

How much does SIMRS implementation cost for a 100-bed hospital?

A reasonable range is IDR 400 million–1 billion for a five-year period, covering licenses, servers and backup, implementation, BPJS and SatuSehat bridging, training, and maintenance. Below IDR 350 million there are usually items not yet accounted for, typically integration and data migration.

Is open-source SIMRS really free?

The license is zero, but implementation, bridging, server, and maintenance staff costs remain. Calculate the need for at least one full-time developer plus integration testing costs; if internal capacity is unavailable, the subscription model is actually cheaper.

Must SatuSehat bridging be budgeted from the start?

Yes. SatuSehat integration with FHIR R4 is mandatory for healthcare facility reporting, so the costs of resource mapping, terminology validation, and sandbox testing must be included in the initial budget, not submitted as a change request mid-project.

How long does SIMRS implementation take until go-live?

Small clinics 4–8 weeks; medium hospitals 3–6 months for the first phase. The largest time is spent on data migration and UAT, not application installation, so both activities need to be scheduled with a buffer.

Calculating SIMRS costs is not about finding the cheapest vendor, but ensuring every rupiah produces accurate data and faster work flows. Start with a five-year TCO, lock the integration scope, and break implementation into measurable phases. If you are preparing a budget for SIMRS, SIM Klinik, ERP, or POS and need a second opinion, the Nugroho Setiawan team is ready to help — IT consulting and application development for Yogyakarta, DIY, and Magelang, from TCO preparation to go-live and post-implementation assistance.

This article is part of the knowledge base of Nugroho Setiawan, an IT consultant in Jogja (Yogyakarta). Related solutions: SIMRS (Hospital Information System) BPJS & SatuSehat Integration. Need a free consultation?