Skip to content
Back to blog

ABDM in 2026: what a small clinic actually has to do

M1, M2, M3, HFR, HPR — the acronyms hide a short list of real tasks. Most of them belong to your software vendor, not to you.

Qlinio
3 min read

Ayushman Bharat Digital Mission has stopped being a pilot. As of March 2026, roughly 86.6 crore ABHA accounts have been created, and the number of health records linked to them crossed 100 crore — doubling from 50 crore in February 2025 in about fifteen months.

But roughly 2.57 lakh facilities are actively using ABDM-enabled software. Against a private sector that accounts for about 62% of India's health infrastructure, that is a small fraction. The gap is not enthusiasm. It is that most clinic owners cannot tell which parts of ABDM are their job.

Here is the honest division of labour.

The three milestones, in plain terms

ABDM certification is organised into milestones. You will see them written as M1, M2 and M3.

  • M1 — ABHA creation and verification. Your registration desk can create or verify a patient's 14-digit ABHA number. This is the identity layer: one patient, one number, across every facility they ever visit.
  • M2 — linking records as a Health Information Provider. Records generated at your clinic — prescriptions, diagnoses, lab reports — can be linked to the patient's ABHA so they follow the patient.
  • M3 — fetching records as a Health Information User. Your doctor can request and view records created elsewhere, with the patient's consent.

They are sequential. You cannot hold M2 without M1, or M3 without M2. That ordering matters when a vendor tells you they are "ABDM compliant" — compliant to which milestone is the only version of that question worth asking.

The part that is your vendor's job

Certification is per-software, not per-facility. Your clinic does not get certified. Your software does.

The vendor integrates against the official ABDM sandbox, passes functional testing for each milestone, and only then receives production access. That is engineering work measured in weeks, and it happens once for the product, not once per clinic.

So when you are evaluating clinic software, the questions are:

  • Which milestones are certified today — not "on the roadmap"?
  • Is the integration in production, or still sandbox?
  • When a patient's ABHA fails to verify at the desk, what does the receptionist see?

That last one decides whether ABDM actually gets used. A flow that dead-ends on an error is a flow your staff will start skipping by week two.

The part that is genuinely yours

Three things, and none of them are technical.

Register the facility on the Health Facility Registry. You submit the clinic's name, type, location, contact details and services, and receive a unique HFR ID. Around 4.17 lakh facilities were registered as of mid-2025. Your software links to this ID, so it has to exist before the linking works.

Get your practitioners onto the Health Professional Registry. Doctors register individually against their medical council registration.

Decide your front-desk policy. Who asks for ABHA, at what point in registration, and what happens when the patient does not have one or does not want to share it. ABHA is voluntary for the patient. A clinic that treats it as mandatory will create friction it does not need.

A sensible order of operations

  1. Register on HFR and get the facility ID. It is free and independent of your software choice.
  2. Get practitioners onto HPR.
  3. Confirm your software's actual certified milestones.
  4. Turn on M1 at registration and leave it there for a few weeks. Let the desk get fluent with one new step before adding another.
  5. Enable record linking once ABHA capture is routine.

What it buys you

The honest answer for a single-doctor clinic today is: not much, immediately. The patient still walks in, still gets seen, still pays.

The value accrues on a longer horizon. A patient arriving with three years of linked history is a better consultation than one arriving with a plastic bag of paper. Referrals to a hospital stop losing context. And the direction of travel is not ambiguous — the registries, the identity layer and the consent framework are all built and running at national scale.

The clinics that will find this easy in two years are the ones that made ABHA capture a boring, thirty-second habit this year.

Bringing your clinic online?

See how Qlinikit and the Qlinio platform fit your workflow — book a short walkthrough.