White-Label PhilHealth Compliance API

PhilHealth eClaims & Konsulta, Solved via API.

Nucleus is the compliance engine behind the scenes — EMR and HIS vendors call one API, and Nucleus handles the PhilHealth XML generation, SOAP transmission, and Konsulta tranche submission logic underneath.

No SOAP, No XML, No Cipher Keys

Send structured JSON to a single REST endpoint. Nucleus owns the PhilHealth integration surface so your team never touches PECWS or the Konsulta DTD directly.

Request API Access View API Reference

RFC 7807 Error Responses

Facility-Scoped API Keys

submit-claim.sh

curl -X POST https://api.nucleus.dev/v1/claims/submit \
  -H "X-Nucleus-API-Key: nuc_live_..." \
  -H "Idempotency-Key: claim-88213" \
  -d { "patient": ..., "diagnosis": [...] }

// 200 OK

{ "status": "SUBMITTED", "transmittalNo": "TRK-2026-00931" }

Core Capabilities

One API, Full Compliance

Nucleus is the shared compliance layer behind PhilHealth eClaims and Konsulta — built so EMR vendors integrate once instead of maintaining SOAP/XML plumbing themselves.

eClaims Submission API

POST structured claim JSON to one endpoint. Nucleus builds the PhilHealth-compliant XML and handles transmission, so your team never writes SOAP integration code.

Konsulta Package Support

Masterlist sync, first/second tranche submissions, and live PNF medicine + ICD-10 library search — the full primary-care benefit workflow, exposed as JSON.

AI-Assisted Clinical Coding

Feed in clinical notes and get back suggested ICD-10 diagnosis and RVS procedure codes with confidence scores, ready for review before submission.

Partner & Facility-Scoped Keys

Every API key is tied to a partner, and can be scoped to a single clinic. Per-partner rate limits, idempotency keys, and RFC 7807 error responses come standard.

Integration Flow

Three Steps to Go Live

Get a Facility-Scoped API Key

We provision a partner account and an API key scoped to your clinic or facility. Keys are admin-issued and shown once at generation time.

Call the Nucleus API

Attach the key as an X-Nucleus-API-Key header and POST claim or Konsulta tranche data as JSON to the relevant /v1 endpoint.

Track Submission Status

Nucleus generates the compliant XML, submits it to PhilHealth, and returns a transmittal number you can poll for status.

Integrating an EMR with PhilHealth?

API access is issued per partner. Reach out and we'll set up your partner account, facility, and first API key.

Request API Access

Nucleus API: PhilHealth eClaims & Konsulta Compliance Engine