Claims & Coding

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

During the INA-CBGs-to-iDRG transition, hospitals should anchor both workflows in one complete, specific clinical record. Casemix teams can keep current grouping and submission separate from iDRG training and validation, so each grouper's results remain traceable.

Reviewed documentation for the claim team

Care Workspace’s reviewed clinical context can give authorized coding and claim teams a traceable documentation starting point. Claim Readiness focuses on source completeness and human review, not automated submission or payer approval.

Read the full explanation
Discuss this step for your team

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. From the Claim Readiness payer-workflow perspective, the upstream discipline begins with purpose-limited, institution-approved patient context and clinician-reviewed documentation. Completeness checks and coding suggestions can support authorized review under either grouper, but the institution's clinicians, coders, and casemix staff own coding and submission, while the payer system owns adjudication. Clinical judgment stays with clinicians; the AI does not diagnose or sign.

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.