Indonesian hospitals face a unique challenge: they need clinical decision support, but most CDSS solutions are designed for Western healthcare systems. At MedMinutes, we're building tools specifically for Indonesia's healthcare ecosystem — and CDSS is one of our newest products.
Here's why this matters and what we've learned so far.
Why Indonesian Hospitals Need Their Own CDSS
Indonesia's national health insurance (BPJS Kesehatan) covers over 200 million people. Hospitals submit thousands of claims daily, and mistakes — wrong drug combinations, incorrect ICD-10 codes, missed diagnoses — lead to rejected claims and patient safety issues.
Off-the-shelf CDSS tools from the US or Europe don't work well here because they don't account for:
- Formularium Nasional (FORNAS) — Indonesia's national drug formulary that dictates what BPJS will reimburse
- INA-CBG coding — Indonesia's own case-based grouping system, different from standard DRG
- Local drug brands — Doctors prescribe by Indonesian brand names (Glucophage, Diafac, Eraphage), not just generic names
- Infrastructure reality — Many hospitals outside Java have unreliable internet connections
Our Approach: Browser Extension
Rather than asking hospitals to replace their existing systems, we built CDSS as a browser extension. It works on top of whatever Hospital Information System (HIS/SIMRS) the hospital already uses.
This was a practical decision. Indonesian hospitals use dozens of different HIS vendors. Building native integrations for each one would take forever. A browser extension that reads the screen and provides real-time alerts is much more realistic.
What the CDSS Actually Does
When a doctor is working in their HIS, our extension:
- Detects the diagnosis being entered and cross-checks it against clinical pathways
- Flags drug interactions — checking prescribed medications against known interactions, with attention to Indonesian brand names
- Validates ICD-10 codes — making sure the diagnosis codes match what BPJS expects for the treatment being given
- Suggests missing steps — like reminding a doctor that an HbA1c test is overdue for a diabetes patient
The goal isn't to replace clinical judgment. It's to catch the routine stuff that's easy to miss when you're seeing 40+ patients a day.
The Hard Part: Localization
The engineering isn't the hardest part. The real challenge is building an accurate knowledge base for Indonesia's specific context.
For example, mapping drug interactions requires knowing that "Metformin" might appear as "Glucophage", "Diafac", "Eraphage", or a dozen other brand names in different hospitals. This mapping work requires close collaboration with clinical pharmacists — it's not something you can just scrape from a database.
Similarly, Indonesia's clinical pathways (Panduan Praktik Klinis) are published by specialist associations like PAPDI, IDAI, and POGI. These aren't always digitized, and they get updated regularly. Keeping our rule database current is an ongoing effort.
What We've Learned Building Healthcare Tools
We've been in the Indonesian healthtech space for a while now. Our first product, BPJScan, helps hospitals audit their BPJS claims to catch errors before submission. A few lessons that carry over:
Hospitals buy compliance, not technology. The feature that convinces a hospital director to adopt a new tool is almost always "this will reduce your claim rejections" — not "this uses cutting-edge AI." We learned this with BPJScan and it applies equally to CDSS.
Start narrow, then expand. We focus on one hospital, one HIS vendor, one clinical specialty first. Get it working reliably. Then generalize. Trying to build for everyone at once is a recipe for building something that works for no one.
Internet reliability matters more than you think. We design everything to work offline-first. Clinical tools that break when the WiFi drops are not acceptable when patient care is involved.
Where We Are Now
CDSS is still early. We're piloting it alongside our existing products (BPJScan for claim auditing, RME for electronic medical records) in hospitals that already use our platform. The advantage is that hospitals using our RME get deeper CDSS integration — but the browser extension approach means any hospital can benefit.
If you're working on healthtech in Southeast Asia, or if you're a developer interested in healthcare challenges in emerging markets, I'd love to hear from you. The problems here are genuinely different from what you see in US/EU healthtech, and there's a lot of room for creative solutions.
Check out what we're building at MedMinutes.
This is part of a series on building healthtech infrastructure for emerging markets. Previously: How AI is Transforming Hospital Claim Auditing in Indonesia.
Top comments (0)