[01]
Claims source: from PDF to EMR data
JKN claims shift from scanned (PDF) documents to electronic claims sourced directly from Electronic Medical Record data — complete with a digital audit trail.
[Regulatory Guide] JKN Electronic Claims
JKN claims move to the EMR.
A five-agency joint circular (30 July 2026) pushes JKN claims onto SATUSEHAT-integrated EMR — pilots from August 2026, full enforcement targeted for 2027. This is no longer about compliance; it is about your hospital's BPJS cashflow.
Background
From compliance to cashflow survival.
EMR and SATUSEHAT obligations have long been read as a compliance matter. The 30 July 2026 joint circular — signed by BPJS Kesehatan, the Health Ministry, the Home Affairs Ministry, KPK, and BSSN — changes the calculus: electronic medical records are set to become the data source for JKN claims. A hospital whose electronic documentation is not claims-grade faces a direct risk to its revenue, not just an administrative warning.
An honest note: this page is built from official press coverage and the Health Ministry's industry-forum presentation (August 2026). The circular is numbered HK.02.02/D/2431/2026, 400.5/8030/Dukcapil, No. 01 of 2026, and No. 43 of 2026; detailed technical guidance for all hospitals is still being rolled out alongside pilots at ministry-designated hospitals. We will update this page as soon as the technical rules are published, and we do not invent details that do not yet exist.
What changes
Four key shifts.
The essence: claims are no longer judged from stacks of scanned documents, but from a complete, auditable chain of electronic data.
[02]
NIK as the single connector
NIK-based EMR links patient identity, diagnoses, procedures, medications, clinicians, service timestamps, and supporting documents into one auditable data chain.
[03]
Electronic signatures
Electronic signatures become part of the claims flow — the clinical documents backing a claim need to be signed electronically, not merely scanned.
[04]
SATUSEHAT as the data path
The SATUSEHAT platform becomes the integrated data basis for claims management — the completeness and quality of a hospital's FHIR submissions directly affect how smoothly claims flow.
Timeline (as reported & per the Ministry's presentation)
Pilot first, full enforcement later.
30 Jul 2026
Joint circular signed
Five agencies: BPJS Kesehatan, the Health Ministry, the Home Affairs Ministry, KPK, and BSSN — on accelerating SATUSEHAT-integrated EMR in JKN claims management.
Aug 2026 — Now
Transition & pilot period
System adjustments, data-submission trials, e-signature adoption, and electronic-claims simulations — reportedly without disrupting payment continuity. First pilots run at ministry-designated hospitals.
1 Jul 2027 — Mandatory target
"No RME, No Claim" in full
Per the Health Ministry's presentation: all hospitals targeted to run RME-based JKN claims in full production. Hospitals that get their documentation claims-grade early will not have to sprint at the deadline.
- Make the EMR the true source of structured clinical documentation — not paper scanned after the fact
- Clean up NIK-based patient identity data (duplicates, missing/incorrect NIK) — NIK becomes the primary connector of the claims chain
- Prepare an electronic-signature flow for claim-supporting clinical documents (medical resumes, certificates)
- Ensure your SATUSEHAT bridging submits complete, consistent data — not just "connected"
- Build a routine audit of claims-documentation completeness so gaps surface before the verifier finds them
Adievia's role: a structured EMR as the documentation source, SATUSEHAT FHIR R4 bridging, BPJS VClaim and E-Klaim integration with a fault-tolerant queue, plus a BSrE integration module for certified e-signatures (the certificate is a separate subscription from the provider). Because the technical guidance is not yet out, we do not sell a "100% circular-compliant" claim — we guarantee the foundation and adapt as soon as the technical rules are final.
FAQ
Questions about JKN electronic claims.
On 30 July 2026, BPJS Kesehatan together with the Health Ministry, Home Affairs Ministry, the Corruption Eradication Commission (KPK), and the National Cyber and Crypto Agency (BSSN) signed a Joint Circular on Accelerating the Implementation of SATUSEHAT-Integrated Electronic Medical Records in JKN Claims Management (No. HK.02.02/D/2431/2026, No. 400.5/8030/Dukcapil, No. 01 of 2026, No. 43 of 2026). The direction: electronic medical records become the data source for JKN claims, replacing scanned documents, for transparency and fraud prevention. All hospitals are targeted to run EMR-based JKN claims in full production in 2027 — the exact enforcement date awaits the implementing guidance.
August 2026 is a transition and pilot period: system adjustments, data-submission trials, electronic-signature adoption, and claims simulations — reportedly without disrupting the continuity of payments. First pilots run at ministry-designated hospitals for the August 2026 service month, and full enforcement is targeted for 2027 (the exact date awaits the implementing guidance). Technical guidance for all hospitals is being rolled out in stages, so specifics (which claim types go first, the e-signature standard, facility scope) follow the implementing guidance.
The things that hold up whatever the guidance says: a structured EMR as the documentation source (not scans), clean NIK-based patient data, electronic-signature readiness, complete and consistent SATUSEHAT submissions, and a routine audit of claims-documentation completeness. Hospitals that prepare early will not have to sprint when full enforcement arrives.
In the Health Ministry's presentation (August 2026), SATUSEHAT Klaim is described as a cross-payer claims and membership data-exchange platform — BPJS Kesehatan, private insurers, and TPAs — unified with the SATUSEHAT Platform: one connection links a hospital to many payers. E-Klaim remains in use for grouping, while BPJS verification is steered onto SATUSEHAT EMR data. In other words, SATUSEHAT integration done properly stands to serve every payer, not just BPJS.
The foundation this policy direction demands is what we build: a structured EMR as the single documentation source, SATUSEHAT FHIR R4 bridging, BPJS (VClaim/SEP) and E-Klaim integration with a fault-tolerant queue, and a BSrE integration module for certified electronic signatures (the certificate itself is a separate subscription from the provider). We are honest: because the circular's technical guidance has not been published, we do not claim to "already meet every requirement" — what we guarantee is that the foundation is ready, and we will adapt as soon as the technical rules are final.
Next step