ClaimGuard
ENID
API · v1

ClaimGuard API

Find missing or inconsistent clinical documentation before a BPJS claim is submitted, at every stage of the clinical pathway. Each finding comes with a ready-to-copy fix for the doctor or nurse.

Get started →Download Postman collection

How it works

🏥
Your SIMRSsends one visit's documents
→
⇢
POST /checksone endpoint, pick a stage
→
🛡️
ClaimGuardclaim rules + clinical AI
→
🩺
Your screenstatus + fixes per section

Example simulation

A mock EMR screen with ClaimGuard integrated. Pick a preset, press Simpan, and watch the Catatan Verifikasi card fill in. Everything runs in your browser with synthetic data; no API is called.

🏥 EMR · Asesmen Awal Dokter IGDdr. Demo (Dokter)
Simulation preset

Press "Simpan" to save the form and run ClaimGuard for every section.

1. Data Pasien
2. Anamnesa
3. TTV & Keadaan Umum
4. Pemeriksaan Fisik
5. Pemeriksaan Lab & Penunjang
6. Coding ICD-10 & Diagnosa
  1. Doctor presses Simpan in the EMR
  2. EMR sends POST /checks
  3. Card shows loading
  4. Card shows status + fixes per section
Show API request & response
POST /checks


200





Clinical pathway coverage
Call the stage that matches the document being written. Each stage is independent, so you can start with one.


🚑 Emergency → Inpatient
IGD initial assessmentigd_asesmen_awalAvailable
→
Inpatient CPPT / early warningranap_cpptAvailable
→
Discharge summaryranap_resumeAvailable


🩺 Outpatient clinic
Outpatient SOAPrajal_soapAvailable


Casemix overviewbefore INA-CBG submissionComing soon


Which input format should I use?


Does your SIMRS already send data to SATUSEHAT?



 
Yes
①FHIR (default)Reuse your SATUSEHAT resources in one Bundle

 
No
②SimpleSend your form sections as they are




③Custom / on-premiseSpecial format or on your own server? We build the adapter.


All three give the same result for the same clinical content.

NextQuickstart →