Challenge
Milestone certification blocks production launch
Agnotic approach
We treat certification as a planned track, building against the milestones and validating in sandbox before we claim done.
ABDM / India
ABDM Integration (India)
We integrate India's Ayushman Bharat Digital Mission health stack (ABHA number and address, the HFR and HPR registries, consent-managed data exchange, and ABDM milestone certification) into your product.
ABHAHFR / HPRConsent ManagerFHIR R4
Trusted by global innovators
What ABDM integration actually involves
The Ayushman Bharat Digital Mission (ABDM) is India's national digital health stack. It gives every citizen an ABHA number and address, maintains the Health Facility Registry (HFR) and Healthcare Professionals Registry (HPR), and moves records through a consent manager: a Health Information User requests data and a Health Information Provider releases it only under a granted consent artefact.
Building on ABDM means implementing gateway callbacks, the consent request and grant flow, ABHA creation and linking, and HIP/HIU roles, with records exchanged as ABDM-profiled FHIR bundles. It also means passing milestone certification in the sandbox, which we shepherd alongside the build.
Architecture
See how we design ABHA linking, consent-managed exchange, and HIP/HIU flows on the ABDM gateway.
Common failure modes
ABDM pitfalls and how we handle them
Challenge
Gateway callback contracts are misimplemented
Agnotic approach
We implement the async callback flows exactly to spec with retries and idempotency, tested against the sandbox.
Challenge
Consent artefacts are not enforced end to end
Agnotic approach
We wire consent grants into every data request so records only move with a valid artefact, fully audited.
Challenge
FHIR bundles fail ABDM profile validation
Agnotic approach
We build to the ABDM FHIR profiles per record type and validate bundles before exchange.
ABDM Capabilities We Work With
The exact India health-stack surface behind consent-managed digital health.
ABHA identity
ABHA number and ABHA address creation, verification, and linking of health records to a patient's health ID.
HFR & HPR registries
Health Facility Registry and Healthcare Professionals Registry lookup and registration for facilities and clinicians.
Consent manager & gateway
Consent request, grant, and revocation flows with HIP and HIU roles over the ABDM gateway callbacks.
FHIR record exchange
ABDM-profiled FHIR R4 bundles for diagnostic reports, prescriptions, discharge summaries, and OP consult notes.
Where it runs
ABDM workflows we build
ABHA onboarding
Create or link a patient's ABHA at registration in your app.
Record sharing
Share diagnostic reports and prescriptions with patient consent.
HIP enablement
Turn a hospital or clinic into a Health Information Provider.
HIU workflows
Fetch a patient's linked records as a Health Information User.
Facility onboarding
Register facilities and professionals in HFR and HPR.
ABDM go-live means passing certification
ABDM is a consent-managed stack with a certification gate. We build to the spec and shepherd the milestones.
ABHA
Health ID creation & linking
2 to 4 mo
Typical build to certification
FHIR R4
ABDM-profiled record exchange
Compliance-First Healthcare App Development Services Backed by Global Standards
15-Minute Scoping Call01
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
02
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
03
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
04
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
05
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
06
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
07
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
08
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
09
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
Standards we build against
ABDM standards
ABHAHFRHPRConsentFHIRDPDP
Our Process
How we deliver ABDM integration
Consent architecture and milestone certification treated as first-class delivery work.
1.
Discovery & role scope
We define whether you act as HIP, HIU, or both, which ABDM milestones apply, and the record types in scope.
Role-scoped
2.
Sandbox & registration
We register on the ABDM sandbox, obtain credentials, and implement the gateway callbacks and ABHA flows.
Sandbox-first
3.
Build & certify
We build consent, linking, and FHIR exchange, then pass ABDM milestone certification in sandbox.
Milestone-certified
4.
Go-live & monitoring
Production access with consent audit trails, callback monitoring, and record-exchange health tracking.
Audited
Build, SDK or buy
Should you build ABDM integration directly, use an SDK or buy an integrated system?
Build directly on the ABDM APIs when ABDM is core to your product, use an SDK for a head start, or buy an integrated system if you run a clinic. Either way you own consent and record sharing, so we scope that first.
| Path | What your team still owns | Dependency risk | Certification work that remains | When it fits |
|---|---|---|---|---|
| Build directly on the ABDM APIs | Everything: gateway callbacks, consent artefact handling, FHIR bundle generation to the ABDM profiles, the HIP data push and the audit trail. | Lowest outside dependency, but your team must track every ABDM API and profile change itself. | All milestones for your HIP or HIU role, tested in the sandbox by your own team. | A new product where ABDM exchange is part of what you sell to many facilities. |
| Use an ABDM SDK or integration library | Your data model, the mapping of your records into FHIR bundles, consent decisions in your workflow and the audit trail. | You wait on the SDK maintainer when ABDM changes an API, and you inherit any gap in what the SDK covers. | The same milestones still apply to your application; the SDK does not certify it for you. | An existing HMIS or EHR that needs ABDM added without rebuilding its core. |
| Buy a system that is already integrated | Configuration, facility and professional registration, staff training and checking that records flow as expected. | You depend on the vendor's roadmap for new milestones, record types and fixes. | Usually the vendor's, but confirm what your facility must still complete before go-live. | A single clinic or small hospital that runs software rather than building it. |
Before choosing, check the current milestone list and sandbox steps on the ABDM sandbox site, because they change. Ask any SDK or vendor which record types and ABDM API versions they support today, and who fixes a failed consent or data push in production.
Featured case study
Read Case StudyLera Health: compliant women's health platform
Lera Health is related proof of compliant, integration-heavy delivery: a privacy-first platform built end to end. ABDM work draws on the same strengths: consent-driven data flows, FHIR modelling, and disciplined handling of sensitive health records.
Why Partner With Us
15-Minute Scoping CallWhy teams trust us with ABDM
Real health-stack integration, including certification.
Compliance-first
Consent-artefact enforcement, data-privacy alignment, and audit trails built to ABDM's model.
Health-stack depth
We work fluently in ABHA, HFR/HPR, the consent manager, and HIP/HIU gateway flows.
Certification-focused
We shepherd ABDM milestone certification so production access is not a surprise blocker.
FHIR fluency
ABDM-profiled FHIR R4 bundles built correctly for each supported record type.
Frequently Asked Questions
A build to milestone certification typically runs 2 to 4 months, depending on whether you act as HIP, HIU, or both and how many record types you support. Sandbox registration and passing the ABDM milestones run alongside engineering and usually set the pace to production access.
Cost scales with your HIP/HIU role, the number of supported record types, and how deep the consent and registry integration goes. A focused ABHA-linking and record-sharing integration is modest, while a full HIP or HIU implementation with certification is a larger engagement. We scope against your role and use cases.
Yes. ABDM requires passing milestone certification in the sandbox before you receive production access, and your facility and professionals are registered in HFR and HPR. We build against the milestones and shepherd the certification so production access is a planned outcome, not a surprise.
Yes. We link wearable, RPM, and telehealth data to a patient's ABHA and exchange it as ABDM-profiled FHIR under a valid consent artefact, so remote-monitoring and virtual-care records become part of the patient's national health record.
Yes. We implement the full consent request, grant, and revocation flow with HIP and HIU roles, enforcing the consent artefact on every data request so records only move when the patient has explicitly authorized it, with complete audit trails.
Ready to connect to India's health stack?
Tell us your HIP/HIU role and record types. We will return a realistic build-and-certification plan.
contact@agnotic.com
Partnerships
contact@agnotic.com