NHIA-style scheme adapter

Eligibility checks and claims/settlement exports for NHIA-style and government scheme partners — built on Curably’s B2B API, not a separate national switch.

Last updated September 2026

What this is

The NHIA-style adapter formats Curably enrollment and claims data for HMS, HMO, and government / NHIA-style agencies. It reuses the same OAuth / API-key auth and org isolation as the rest of /api/v1.

Not a national switch

These endpoints are Curably’s interoperability layer for scheme-style data exchange. Certified NHIA national message formats or gateway connectivity — if required — are scoped per engagement on top of this adapter.

Eligibility

GET/api/v1/nhia/eligibility

Check whether a Curably ID is enrolled / eligible under the caller’s organization contracts (roster, consent, or claims history).

Example

curl -s "https://api.letscura.com/api/v1/nhia/eligibility?cura_id=CURA-XXXX&org_id=ORG_UUID" \
  -H "Authorization: Bearer $TOKEN"

Response includes eligible, enrollment_status, sources, and human-readable notes. Requires the identity integration module.

Claims export

GET/api/v1/nhia/claims-export

Export claims as JSON (default) or CSV (?format=csv). Optional from / to (YYYY-MM-DD) filter on service date.

Payer / HMO / government orgs see claims where they are the hmo_org_id
Provider orgs see claims they submitted
Requires the billing module

Settlements export

GET/api/v1/nhia/settlements-export

Export paid settlement batches for a month (?month=YYYY-MM), JSON or format=csv. M2M equivalent of the HMO workspace NHIA CSV export.

Auth & modules

Same as HMS integration: OAuth client credentials or org API key. Capabilities are listed in GET /api/v1/openapi under the NHIA tag.

HMS pairing

Typical HMS pilot: eligibility at intake → encounter / consent → POST /api/v1/claims → periodic claims/settlements export for scheme reporting. See HMS / HIS integration and Billing & payers.