ABDM Sandbox aligned · Trusted by integration teams
Wire your systems into Bharat's digital rails.
BharatConnector is the connector layer for India's public digital infrastructure — starting with ABDM and NHCX. Go live on ABHA, health records and insurance claims in days, not quarters, with the compliance handled for you.
Each connector is middleware that turns a national programme's tangle of APIs into a handful of simple calls — so your team ships the product instead of the plumbing.
Live
ABDM Connector
Ayushman Bharat Digital Mission
Everything a HIP or HIU needs to join the national health ecosystem — from creating an ABHA to sharing records under consent — behind clean REST endpoints and SDKs.
ABHA creation & verification
Care-context linking
Consent lifecycle
PHR & record sharing
FHIR R4 bundling
M1 / M2 / M3 milestones
Live
NHCX Connector
National Health Claims Exchange
Move claims off portals and PDFs. Exchange structured, FHIR-based claims between providers, payers and TPAs — with AB-PMJAY and private schemes on a single integration.
Pre-authorisation flow
Claim submission
Status & query callbacks
Payment-notice handling
Coding & claims bundles
Multi-payer onboarding
Three ways to connect
Pick the path that fits your timeline.
Go live this week on our certified endpoints, embed our hosted screens, or build and certify your own native integration — the same connector underneath, your choice of speed and control.
Fastest
Plug & play
~2–3 daysUse our certified endpoints
No certification needed
Call BharatConnector's existing, already-certified endpoints. You inherit our certification, so there is no sandbox or milestone process on your side.
Shared, already-certified endpoints
No M1 / M2 / M3 on your side
Minimal code — REST calls or SDK
Ideal for a fast pilot or go-live
Best for apps & vendors who want the shortest path to live.
Hosted UI
Front-end wrapper
~1–2 weeksEmbed our hosted screens
Certification handled for you
Embed our hosted, certified interface — ABHA creation, consent capture, claim submission — directly into your product, with little to no backend work.
Drop-in hosted screens
Consistent, compliant UX
Configurable & white-labelable
We keep the screens current
Best for teams without bandwidth to build ABDM/NHCX UI.
Full control
Native + certification
~6–8 weeksYour own certified build
Your own M1 / M2 / M3
Integrate directly against ABDM and NHCX with our SDKs and obtain your own certification, with our team guiding every milestone.
Direct API integration
Guided M1 / M2 / M3 certification
Runs in your own infrastructure
Maximum control & data residency
Best for enterprises that need full control and their own certification.
From kickoff to production
Four steps, one integration.
The order matters — each step feeds the next, and the connector carries the weight at every stage.
STEP 01
Connect
Point your HMIS, EMR or claims system at our REST endpoints or drop in an SDK. No changes to your core system.
Typically day 1
STEP 02
Map
Your data is transformed into ABDM and NHCX FHIR structures automatically — bundling, coding and validation included.
Automatic
STEP 03
Certify
Run every workflow in a sandbox that mirrors the national environment, then clear the milestones with our team alongside you.
Weeks 2–6 · native path
STEP 04
Go live
Flip to production. Spec changes are shipped to the connector centrally, so your integration keeps working.
Same day
Timelines shown are for the native, self-certified path. With plug-and-play you inherit our certification and skip step 3 — going live in days.
NHCX & AB-PMJAY
Faster claims for AB-PMJAY and every insurer.
The National Health Claims Exchange replaces email, portals and PDFs with structured, interoperable claims. The NHCX Connector maps your data to the exchange and runs the full lifecycle — pre-auth, claim, query and payment notice — so a single integration reaches many schemes at once.
No clinical data stored Payloads pass through encrypted channels; nothing is warehoused.
Answers
Questions teams ask us.
Basic workflows connect in a day. A typical hospital, lab or vendor goes from kickoff to a sandbox-certified integration in about six to eight weeks, because the connector already handles authentication, FHIR mapping, callbacks and the milestone workflows for you.
No. BharatConnector sits as a middleware layer between your system and the ABDM/NHCX networks. You call simple REST endpoints or an SDK; we handle data transformation, FHIR bundling and protocol details, so your core system stays exactly as it is.
The NHCX Connector maps your claims data into National Health Claims Exchange formats and routes pre-authorisation, claim, query and payment-notice workflows. One integration lets you onboard AB-PMJAY alongside private insurers and TPAs, instead of building a separate portal integration for each payer.
It isn't. Clinical and claims payloads pass through encrypted channels and are not retained. Data moves over TLS 1.3 with OAuth 2.0 and JWT authentication, and the platform follows ISO 27001 practices and is built to align with the DPDP Act, 2023.
Specification and milestone changes are tracked centrally and shipped to the connector, so your integration keeps working without your team re-reading the API documentation every release.
Only if you want it. With plug-and-play you use our already-certified endpoints and need no certification of your own; the front-end wrapper handles certification for you as well. If you prefer full ownership, the native path takes you through your own M1/M2/M3 certification, with our team guiding each milestone.
Hospitals and clinics, diagnostic labs, HMIS/EMR vendors, insurers and TPAs, and patient-facing healthcare apps. More connectors across Bharat's digital public infrastructure are on the roadmap.
Request an integration consult
Tell us what you're connecting.
We use a few cookies
Necessary cookies keep the site working. With your permission we also use analytics and marketing cookies to understand how the site is used. See our Cookie Policy.
Cookie preferences
Choose which cookies BharatConnector may use. You can change this anytime from “Cookie settings” in the footer.
Strictly necessaryRequired for the site to function. Always on.
AnalyticsHelps us understand which pages are useful.
MarketingUsed to measure campaigns and reach the right audiences.