[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 moveto the EMR
A five-agency joint circular (30 July 2026) pushes JKN claims onto SATUSEHAT-integrated EMR — a transition from August 2026, and per the Health Ministry all JKN claims must be EMR-based from June 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). According to that presentation, the circular is numbered HK.02.02/D/2431/2026, 400.5/8030/Dukcapil, No. 01 of 2026, and No. 43 of 2026 — the official Health Ministry and BPJS releases do not state the numbers, and the full text is not yet published; 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. As of 11 October 2026 we have still not found that guidance published. What is new: BPJS Kesehatan's briefing on the 2026 hospital (FKRTL) credentialing and recredentialing forms (6 October 2026) — according to Legawa's summary — also scores the EMR and certified e-signatures (at least for attending physicians). We have not seen the official form; check with your BPJS Kesehatan branch office.
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.
June 2027 — All JKN claims
"No RME, No Claim" in full
When the circular was signed, KPK described full enforcement in 2027 as conditional on a review finding national readiness. A presentation by the Director General of Advanced Health on 6 November 2026 said all JKN claim submissions must be based on SATUSEHAT-integrated EMR from June 2027, without that condition (CNN Indonesia, 7 November 2026). We have not found an official text fixing the month, so plan on June 2027. 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 (Adievia HMS has been listed in SATUSEHAT's directory of EMR system providers since October 2026), BPJS VClaim and E-Klaim integration with a fault-tolerant queue, plus electronic signing in the EMR flow (uncertified today; certified e-signature integration through BSrE or a non-agency PSrE is being prepared with the first partner hospital). 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 (numbers per the Health Ministry's August 2026 presentation: HK.02.02/D/2431/2026, 400.5/8030/Dukcapil, No. 01 of 2026, No. 43 of 2026 — the circular's text has not been published on an official site). 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. According to press coverage, a presentation by the Director General of Advanced Health on 6 November 2026 said all JKN claim submissions must be based on SATUSEHAT-integrated EMR from June 2027; follow-up implementing guidance has not been published.
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 according to the Ministry's 6 November 2026 presentation, all JKN claims must be based on SATUSEHAT-integrated EMR from June 2027 (follow-up implementing guidance has not been published). 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 electronic signing in the EMR flow — today an uncertified electronic signature; certified e-signature integration through BSrE (government hospitals) or a non-agency PSrE (private hospitals) is being prepared together with the first partner hospital. 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