HMS / HIS integration

Curably exposes a machine-to-machine B2B API for HMS, HIS, EHR, HMO, and pharmacy systems. Partners exchange beneficiary data under roster enrollment, consent, and payer contracts — not consumer self-service.

The live contract is served from the API itself. Use it as the source of truth for paths, auth, and modules:

• GET /api/v1/openapi — OpenAPI 3.1
• GET /api/v1/integrations/catalog — public module catalog
• GET /api/v1/integrations/capabilities — org-enabled modules (auth required)

curl -s https://api.letscura.com/api/v1/openapi | jq '.info,.paths | keys'

1. Request sandbox access via Contact (HMS / hospital / HMO).
2. Receive client_id / client_secret (or an org API key).
3. Exchange credentials at POST /api/v1/oauth/token with grant_type=client_credentials.
4. Call org-scoped endpoints with Authorization: Bearer <token>.

Use Idempotency-Key on claim submit and roster sync POSTs.

1. Eligibility — GET /api/v1/beneficiaries?cura_id=… or NHIA-style GET /api/v1/nhia/eligibility
2. Encounter — capture consent / visit in Curably or push records under consent
3. Claim — POST /api/v1/claims from the network provider org to the HMO
4. Events — subscribe to claim.submitted, roster, and consent webhooks

Also see EHR / FHIR R4 for hospital SMART sync, and REST API & webhooks for headers and error shapes (application/problem+json).

For national / social health insurance style exchange, use the NHIA adapter endpoints documented in NHIA-style adapter. These sit on the same B2B rails — they are not a separate national switch.

• GET /api/v1/webhooks/events — event catalog
• Deliveries include X-Cura-Signature: sha256=…
• Key events: claim.submitted, roster.member.added, consent.granted

• Sandbox org + OAuth client provisioned
• HMS can call OpenAPI + eligibility + claim submit against sandbox
• Webhook endpoint returns 2xx within 10s
• Optional: FHIR Observation write / Patient read for clinical sync
• Run smoke: pnpm test:smoke-api-v1