Services Done for you
We integrate your hospital with ABDM, end to end
The connector is built for teams that integrate it themselves in a few days. Not every hospital has that team, and not every software vendor has the hands free this quarter. So we also do it for you: our engineers connect the software you already run to ABDM, register the facility and its doctors, take the setup through certification, train the front desk and stay on after go-live.
01 Who this is for
Three situations we see every week
A hospital with no developer
You run an HMIS a vendor installed years ago, the vendor is slow or gone, and the incentive scheme or a scheme requirement now needs ABDM. We integrate what you have, or set up the registration desk in our portal where the HMIS cannot be touched.
A software company short of hands
You sell an HMIS, EMR or lab system to dozens of sites and every customer is asking for ABDM. We build the integration into your product once, on your codebase or against your API, and hand it back documented. Your customers stay yours.
A group rolling out many facilities
Eleven hospitals, three lab chains, one deadline. We register each facility in HFR, link every site, onboard each desk and report progress per site until the last one is live.
02 What is included
End to end means end to end
Every engagement covers the same list. What changes between them is how much of your own team is involved and how many sites there are.
- Scope
- A short call and a look at your software: which records it holds, how they can be read, which milestones you need, and which facilities are in scope.
- Build
- Our engineers connect your HMIS, EMR or LIS to the connector’s API: ABHA at registration, care-context linking on discharge or report sign-off, consent and record fetching where you need them, webhooks into your system.
- FHIR
- Your prescriptions, discharge summaries and lab reports mapped to the NDHM FHIR profiles the network expects, with the coding gaps in your master data named and closed.
- Registries
- The facility registered in HFR with the facility manager’s HPR ID, address proof and photos; each doctor and nurse registered in HPR with the right category and course codes; bridge linkage done and confirmed by ABDM, not just declared.
- Certify
- NHA’s test cases run against the sandbox with the evidence kept; the exit form, the agency’s functional testing and the security audit supported until credentials are issued.
- Go live
- Production configuration, the first live ABHA and first linked visit done with your desk, and a short written procedure for the staff who will do it every day.
- Support
- A support period included in every engagement; monitoring of callbacks and failed links; NHA’s changes absorbed by the connector so nothing is rebuilt on your side.
- Handover
- Documentation, credentials in your name, and every configuration in your account. Nothing depends on us that you cannot see.
03 How it runs
Four steps, two to six weeks for one hospital
The range depends on how your software exposes its records. A system with an API or a readable database is at the short end; one that needs a new export is at the long end. Groups run sites in parallel after the first.
Scope and quote
A thirty-minute call, access to a test copy of your software, and a written scope with a fixed price or a monthly rate within two working days.
Build on the sandbox
Integration and FHIR mapping against ABDM’s sandbox in your own account, with weekly demonstrations of real flows: ABHA created, visit linked, consent granted, records received.
Register and certify
HFR and HPR registrations completed, bridge linkage confirmed, NHA’s test cases run and evidenced, and the certification file prepared with you.
Go live and hand over
Production credentials configured, the first live patient done together, the desk trained, documentation handed over, and a support window that starts the same day.
04 Engagement models
Pick the shape that fits
The service is priced separately from the connector subscription, which stays at its listed per-hospital price. Quotes follow the scoping call; there is no list price because no two systems expose their records the same way.
Fixed scopeOne integration, one price
A defined integration of one product or one hospital, priced once, delivered to a written scope. The usual choice for a single hospital or a vendor adding ABDM to a product.
Dedicated developerAn engineer on your team, by the month
One of our engineers works inside your team for as many months as the rollout needs, on your codebase and your priorities, with the connector’s own engineers behind them.
Managed onboardingPer facility, for groups
For groups and chains: a per-facility fee covers registering, linking, onboarding and training each site, with a progress report across the estate until every site is live.
05 Why us
The people who built the connector do the integration
We spend every day against NHA’s sandbox and its registries, which is why the connector knows that a degree is a course code, that a bridge answers success inside an error, and that a facility declared as linked is not linked. That knowledge is what an integration project is mostly made of, and it comes with the engineers rather than with a document.
FAQ Common questions
Frequently asked questions
Do I need a developer to use the Swastik ABDM Connector?
What does an end-to-end integration include?
How long does it take?
How is the service priced?
Can you work with our HMIS vendor?
Next Keep reading
Related reading
What ABDM integration really costs, and why a connector is the cheaper way
Three ways to get a hospital onto ABDM: build it in-house, replace the HMIS with an ABDM-ready one, or connect what you run today. What each costs, how long it takes, who carries the next NHA change, and how the Swastik connector at Rs 2,999 per hospital compares.
Priced per hospital, not per patient
One ABDM integration, billed per hospital per month. Free sandbox with no card. ABHA, HIP linking, HIU consent, FHIR and the HFR/HPR registries on every paid plan.
ABDM compliance for hospitals, on the systems you run
What ABDM means for a hospital: an HFR identity per site, ABHA at the registration desk, discharge summaries and lab reports in patients' PHR apps, and consented history for clinicians — and how to get there without replacing your HMS or LIS.
ABDM for HMIS vendors, built once for every customer
For companies that sell hospital information systems: add ABHA, HIP record sharing, HIU consent and HFR onboarding to your HMIS once, then roll it out to every hospital you serve, with a facility per site and every record attributed to it.
Tell us what you run
Name your software and how many facilities, and an engineer will come back within a working day with questions or a scope.