How to Register Your Clinic on ABDM as a Health Information Provider

If you run a clinic or hospital in India, you've probably been hearing more and more about ABDM — the Ayushman Bharat Digital Mission. Maybe a government circular mentioned it. Maybe a patient asked if you accept ABHA health IDs. Maybe you want PM-JAY empanelment and someone told you ABDM registration is a prerequisite.

Whatever brought you here, this guide walks you through the actual process of registering your facility as a Health Information Provider (HIP) on the ABDM network. No jargon walls. No 60-page policy documents. Just the steps, the gotchas, and practical advice from facilities that have done it.

What is a Health Information Provider (HIP)?

In ABDM terminology, a HIP is any healthcare facility that generates health records — prescriptions, lab reports, discharge summaries, imaging reports. That's you.

When you're registered as a HIP, you can:

• Link patient records to their ABHA (Ayushman Bharat Health Account) ID
• Push health documents to the ABDM network in FHIR R4 format
• Enable patients to access their records through ABDM-linked apps
• Participate in the national health data exchange with patient consent
• Apply for government scheme empanelment (PM-JAY, CGHS, ESI)

As of early 2026, over 55 crore ABHA IDs have been created. The network is growing fast, and facilities that register now will be ahead of the curve when ABDM integration becomes effectively mandatory for government scheme participation.

Prerequisites before you begin

Before starting the registration process, make sure you have:

1. Facility registration: Your clinic/hospital must be registered with the relevant state medical council or under the Clinical Establishments Act. You'll need the registration number.

2. Healthcare Professional Registry (HPR) IDs: At least one doctor at your facility should have an HPR ID. Doctors can register at hpr.nha.gov.in using their state medical council registration number.

3. Health Facility Registry (HFR) entry: Your facility must be listed on the Health Facility Registry. If it isn't, you'll register during the process (more on this below).

4. Technical readiness: You need software (an HMS or a dedicated ABDM integrator) that can generate health records in FHIR R4 format and communicate with the ABDM gateway. This is where your choice of HMS matters — more on this later.

5. Aadhaar-linked mobile number: The facility administrator's Aadhaar-linked mobile number for OTP verification.

Step-by-step registration process

Step 1: Register on the Health Facility Registry (HFR)

Go to facility.ndhm.gov.in and register your facility.

You'll need: - Facility name and type (clinic, hospital, lab, etc.) - Address with PIN code - State medical council registration number or Clinical Establishment Act registration - Contact details (phone, email) - Ownership type (individual, trust, corporate, government)

Tip: Make sure the facility name exactly matches your state registration certificate. Mismatches cause delays in verification.

After submission, the system assigns you a facility ID. This is your unique identifier on the ABDM network. Save it — you'll need it for every subsequent step.

Verification timeline: HFR verification typically takes 5-15 working days. Some states are faster than others. Kerala and Karnataka tend to verify within a week. UP and Bihar may take longer. Follow up if it exceeds 15 days.

Step 2: Obtain your HIP ID

Once your HFR registration is verified, you can register as a Health Information Provider.

Navigate to the ABDM sandbox portal at sandbox.abdm.gov.in (for testing) or abdm.gov.in (for production).

The HIP registration requires: - Your verified HFR facility ID - Technical endpoint URL (this is where your HMS/software will receive ABDM requests) - SSL certificate for the endpoint (HTTPS mandatory) - Callback URLs for consent notifications and data requests

Important: If you're using an HMS that handles ABDM integration (like MedOS), the HMS provider will supply the technical endpoints. You don't need to set up servers yourself.

Step 3: Set up ABHA linking at patient registration

This is where ABDM becomes part of your daily workflow. When a patient visits:

1. Ask if they have an ABHA ID (14-digit number or an @abdm address) 2. If yes, verify it using the ABDM API — the patient receives an OTP on their registered mobile 3. If no, help them create one using their Aadhaar (takes 2-3 minutes) 4. Link their ABHA to your facility's patient record

Practical reality: Not every patient will have or want an ABHA ID. Don't force it. Make it available, encourage it for government scheme patients, and train your reception staff to handle both scenarios smoothly. Over time, ABHA adoption will increase as patients see the benefit of portable records.

Step 4: Configure consent management

ABDM uses a consent-based model. Before you share any patient record on the network, the patient must grant explicit consent through the consent manager.

The flow works like this: 1. A Health Information User (another doctor or hospital) requests the patient's records 2. The patient receives a consent request on their ABDM-linked app 3. The patient approves or denies the request 4. If approved, your system (the HIP) pushes the requested records to the HIU

Your HMS needs to handle incoming consent notifications and respond with the appropriate records in FHIR R4 format. If your HMS doesn't support this natively, you'll need a middleware bridge — which adds complexity and cost.

Step 5: Start pushing health records

Once you're registered and consent management is configured, you can start pushing records to the ABDM network:

• **Prescriptions** — After each consultation, the e-prescription is formatted in FHIR R4 and linked to the patient's ABHA
• **Lab reports** — Test results pushed as DiagnosticReport resources
• **Discharge summaries** — For IPD patients, the discharge summary goes to ABDM
• **OPD records** — Visit notes and clinical observations

FHIR R4 formatting is the technical barrier most facilities struggle with. Unless you have a development team, you need an HMS that generates FHIR-compliant documents natively. Manual formatting is not realistic for a busy clinic.

Common pitfalls and how to avoid them

Pitfall 1: Facility name mismatch Your HFR facility name must match your state registration certificate exactly. "Dr. Sharma's Clinic" vs "Dr Sharma Clinic" — that small difference will delay verification. Double-check before submitting.

Pitfall 2: Trying to self-integrate without technical capacity ABDM integration involves REST APIs, FHIR R4 document generation, encryption (public key infrastructure), and webhook handling. If your clinic doesn't have a developer on staff — and 99% of clinics don't — use an HMS that handles this for you.

Pitfall 3: Ignoring the sandbox Don't go straight to production. Use the ABDM sandbox (sandbox.abdm.gov.in) to test your integration end-to-end. Create test ABHA IDs, simulate consent flows, and verify that your records are correctly formatted before going live.

Pitfall 4: Not training reception staff The reception desk is where ABDM lives or dies in daily practice. If your receptionist doesn't know how to ask for an ABHA ID, verify it, or help create one, the integration exists on paper only. Invest 30 minutes in training and create a simple cheat sheet for the front desk.

Pitfall 5: Treating ABDM as a one-time setup ABDM specifications evolve. NHA releases updates, new document types are added, and consent flows may change. Make sure your HMS vendor actively maintains ABDM compliance — not just a one-time integration that breaks when NHA updates the API.

How MedOS simplifies ABDM registration

MedOS is built as an ABDM-ready HMS, meaning ABDM isn't a bolt-on module — it's woven into the core patient registration and record-keeping workflow.

Here's what that means practically:

• **ABHA linking at registration:** Two-click flow — enter ABHA number, verify OTP, done. If the patient doesn't have one, create it from the same screen using Aadhaar
• **Automatic FHIR R4 conversion:** Every prescription, lab report, and discharge summary is auto-converted to FHIR R4 format and pushed to ABDM
• **Consent management built in:** Incoming consent requests appear in your dashboard. Approve, and the records are shared automatically
• **HIP registration support:** We handle the technical endpoint setup as part of onboarding

Get started with ABDM

Whether you use MedOS or another HMS, getting on the ABDM network is becoming essential for Indian healthcare facilities. Start the process now rather than waiting for it to become mandatory.

Try MedOS free for 14 days at [med-os.in](https://med-os.in) — ABDM-ready architecture included in Professional and Enterprise plans. No credit card required.