"Connected to SATUSEHAT" does not mean claims-ready

Ask “is your hospital integrated with SATUSEHAT?” and many hospitals today can answer yes. Many are reportedly connected to the platform — and that is a real achievement. But there is a second question that matters more and more: is the data you submit complete and consistent?

Update, 3 September 2026 — now there are numbers. At the launch of the SATUSEHAT EMR Viewer on 1 September 2026, the Health Minister said that of roughly 100,000 health facilities, about 60,000 are connected (CNBC Indonesia). Earlier, KPK recorded that as of May 2026 some 2,400 hospitals had submitted six EMR service types to SATUSEHAT (Liputan6, 31 July 2026).

Note what both figures actually count: connection and submission, not completeness. Neither answers the second question above. And since 1 September, that second question is no longer judged only by a claims verifier — it is also visible to patients. SATUSEHAT Mobile users whose profile has been verified can now open their own medical summary (Health Ministry, 1 September 2026).

Connected ≠ complete

“Connected” means credentials are active and the system can send data. “Complete” means the FHIR resources you submit genuinely cover the care chain — registration, diagnoses, procedures, medications, ancillary results — with correct terminology, consistently over time. The two get conflated, because compliance dashboards display connection status, not content quality. The Health Minister stressed the same point at the launch: make sure facilities are not just connected and not just sending data, but sending complete data, from diagnoses and lab results to medications and radiology (detikHealth, 1 September 2026).

As long as SATUSEHAT submission was only a reporting obligation, that gap went unnoticed. The JKN electronic-claims direction (the 30 July 2026 joint circular) changes it: SATUSEHAT-integrated EMR is being steered into the data source for claims. Holes in the data — encounters without structured diagnoses, medications without KFA mapping, unlinked NIKs — are no longer just red marks on a report; they can become obstacles to claims verification. SATUSEHAT’s documentation for the BPJS Kesehatan claims module, still in development, describes E-Klaim validating a claim by Encounter ID (SATUSEHAT documentation). A visit that never reached SATUSEHAT has nothing to be checked against.

Update, 8 November 2026. The deadline now has a date. On 6 November 2026 the Director General of Advanced Health said all JKN claims must be based on SATUSEHAT-integrated EMR from June 2027 (CNN Indonesia, 7 November 2026). The gap between connected and complete now has a time limit.

Three questions to test your hospital

1. Where does your SATUSEHAT data come from? If it is entered manually, separately from the EMR used in daily care, completeness depends on double-entry discipline — and double entry always loses to a busy shift.
2. Which resources are actually submitted? A serious vendor can name the list, not just claim “100% integrated”.
3. Who knows when a submission fails? Silent failures are the most common source of data holes. There must be a queue, automatic retries, and monitoring.

Where we stand

Adievia builds its SATUSEHAT bridging with the EMR as the single source (no double entry), direct FHIR R4 resource mapping from care data, and a submission queue that retries automatically on failure. Since October 2026 Adievia HMS has been listed in SATUSEHAT’s directory of EMR system providers. We remain honest about the limits: production submission uses each hospital’s own SATUSEHAT organization and credentials, and the technical rules for electronic claims still await the circular’s implementing guidance.

More: Adievia’s SATUSEHAT integration and the JKN electronic claims guide.