MicromeetAI
Microware Group · HKEX: 1985
All answers
Claims & Coding

How do hospitals support both INA-CBGs and iDRG during the transition period?

By anchoring on the one asset both systems share: the clinical record. During Indonesia's casemix transition, a hospital may need to keep grouping and submitting claims under INA-CBGs (Indonesian Case Based Groups) while preparing coder training, data checks, and validation runs for iDRG (Indonesian Diagnosis Related Groups). Documentation that is complete and coded to full specificity groups correctly under either logic, so the most durable dual-running strategy is a documentation-completeness discipline — backed by a casemix team trained on both groupers and pending-claim tracking that keeps the two systems' results separate.

A workable transition plan has four parts. One, keep a single source of truth: the discharge summary (resume medis) and its supporting documentation, complete enough that either grouper can read the true complexity of the case — do not maintain one 'version' of an episode per system. Two, train the casemix team on both grouping logics, and follow the official BPJS Kesehatan and Ministry of Health (Kemenkes) channels for updates to E-Klaim and submission workflows rather than improvising ahead of the circulars. Three, run parallel validation on your highest-volume encounter types: group the same coded episodes under both logics and study where the results diverge, because those divergences show exactly where coding specificity or documentation is thin. Four, track pending and denial reasons per system, so a problem introduced by the transition is not misread as a documentation regression, and vice versa.

Notice that three of the four parts are really documentation work. That is the honest center of gravity: a grouper migration is disruptive at the coding desk, but the claims that survive verification under either system are the ones whose records were complete at the point of care. Micromeet's Claim Readiness is built for exactly that upstream layer — checking completeness, diagnosis-procedure consistency, and severity support, and suggesting ICD (International Classification of Diseases) codes the coder confirms — which is what makes it useful on both sides of the transition. This is governed healthcare AI: AI writes. Doctors decide.

Related questions

What should a casemix team do first to prepare for iDRG?+
Start with the encounter types that carry most of the hospital's claim value: re-validate how they group, audit whether current documentation supports the specificity DRG-style grouping rewards, and close the recurring gaps with clinicians. Grouper training matters, but it pays off only if the records feeding the grouper are complete.
Do hospitals need new software to support iDRG?+
Grouping and submission tooling arrives through the official Kemenkes and BPJS channel as the rollout proceeds, so hospitals should not need to buy a parallel claims stack. The work a hospital genuinely owns is readiness: complete documentation, retrained coders, and validated data — the inputs any grouper depends on.
Does running two groupers double the coding workload?+
It adds validation and training load, but not double coding: the episode is documented and coded once, from the same record. Hospitals that struggle in dual-running are usually paying for pre-existing documentation gaps twice — once per grouper — which is why completeness, not headcount, is the leverage point.

Micromeet — AI for governed healthcare. MCU CoPilot, AI Scribe (Voice-to-EMR), AI Front Desk, Care Loop, Claim Readiness and AI Care Command Center — every output doctor-reviewed. AI writes. Doctors decide. See the public benchmark →

See also

Talk to our team FAQ