ABDM for a clinic is five steps. None of them involve writing code.

What ABDM actually asks a clinic to do.

The Ayushman Bharat Digital Mission (ABDM), run by the National Health Authority, is the national framework for digital health records in India. It gives each patient a health ID (the ABHA), registers facilities and professionals, and defines how records move between them with the patient's consent.

For a clinic, the practical scope is narrower than the mission statement. You need to be able to create or verify a patient's ABHA at the desk, link the records you generate to that ABHA, and, when the patient consents, share those records or receive records from elsewhere.

Almost everything else is the software's job. Your clinic does not write code. It chooses an ABDM-integrated EMR and changes a few front-desk habits.

The building blocks, in plain language.

• ABHA (Ayushman Bharat Health Account): the patient's 14-digit health ID, plus an ABHA address (of the form name@abdm) used to link and share records.
• HFR (Health Facility Registry): the registry your clinic is listed in. Registration gives your clinic an ID that ABDM uses to identify it as a source of records.
• HPR (Healthcare Professionals Registry): the registry for doctors and other professionals.
• HIP (Health Information Provider): any facility that generates records and can link them to an ABHA. Your clinic is a HIP.
• HIU (Health Information User): any facility that requests records with consent. A clinic receiving a referral is acting as a HIU.
• Consent artefact: the digitally signed record of what the patient agreed to share, with whom, for what purpose and for how long.
• FHIR: the format (HL7 FHIR) in which records are packaged and exchanged.

Step 1. Register the facility and the doctors.

Facility registration on the HFR is done online by the clinic owner with basic details: name, address, type, ownership and services offered. Doctor registration on the HPR is done by each doctor with their council registration details. Both are done directly on the government portals.

Do this before you switch on the integration in your EMR. The facility ID and the doctors' HPR IDs are what the EMR uses to identify the source of every record it pushes.

Step 2. Choose how the EMR connects.

An EMR can integrate with ABDM in two ways: build against the ABDM APIs and go through the sandbox and approval process itself, or use an integration that has already been approved. As a clinic you only need to care about whether your vendor has done the work. Ask three questions.

1. 1Which ABDM milestones has the vendor completed? Milestone 1 covers ABHA creation and verification. Milestone 2 covers linking records as a HIP. Milestone 3 covers fetching records as a HIU.
2. 2Whose facility ID appears on the records, the vendor's or yours? Your clinic should be the HIP.
3. 3What happens to the consent artefact? It should be stored against the patient in your EMR, visible to staff.

Saaro Health integrates directly with ABDM. ABHA creation and verification, HIP linking with FHIR record push and consent artefact storage are part of the product, and the details are on our ABDM compliance page.

Step 3. Change the front-desk flow.

This is where most integrations stall. The software works; the desk does not use it. The fix is a script and a habit, not a feature.

At registration.

• Ask: 'Do you have an ABHA?' If yes, verify with the ABHA number or address and an OTP on the patient's phone.
• If no, offer to create one. Creation uses Aadhaar or mobile OTP on the patient's phone; the clinic does not need to store the Aadhaar number.
• The ABHA is written into the patient record. The EMR should do this automatically once verified.

After the consult.

• The prescription, diagnosis and any reports generated at your clinic are linked to the ABHA as a care context.
• The patient sees a notification in their ABHA app asking them to approve the link. That is the consent step for linking.

Train the desk with a script and give them a target, such as offering an ABHA to every new patient in the first month. Do not set a percentage you cannot yet measure. Get the habit first, then measure.

Step 4. Consent and record exchange.

When your doctor wants to see a patient's records from another facility, the EMR raises a consent request. The patient approves it in their ABHA or PHR app, choosing what to share and for how long. That approval is the consent artefact. Only then can your EMR fetch the records, as FHIR bundles, and display them.

Two points matter for the DPDP Act here. The consent artefact is purpose-bound and time-bound, and the patient can revoke it. Your EMR should honour both, and keep the artefact for your own audit.

Step 5. Go live and keep it running.

• Run a week in which every new patient is offered an ABHA. Review what the desk found hard.
• Check the ABDM link status inside the record for a sample of visits.
• Confirm the doctors' HPR IDs are attached to their profiles in the EMR.
• Keep the consent artefacts visible. Auditors and patients will ask.

Once the habit settles, ABDM stops being a project. Records link as a side effect of writing a prescription, and the patient has their history on their phone.

Common mistakes.

• Registering the facility under the vendor's name instead of the clinic's.
• Treating the ABHA field as optional, so the desk skips it when the queue is long.
• Storing Aadhaar numbers 'just in case'.
• Assuming consent for linking is consent for sharing. They are separate steps.
• Choosing an EMR whose ABDM integration is 'coming soon'.

What changes for the doctor.

Very little, if the EMR is doing its job. The ABHA sits on the patient header. Outside records, once consented, appear as a timeline next to your own notes. The prescription you dictate is pushed as a FHIR bundle without a separate step.

The benefit shows up on the second visit and the referral: the history is there, and the patient did not have to carry a file.