Compliance & Access
Understand what ABDM expects of a hospital, and see how the ABDM add-on module is designed to support ABHA-linked registration and consent-based record sharing.
In short
The Ayushman Bharat Digital Mission (ABDM) is India's national digital health framework, built around the ABHA number, consent-based record exchange and registries of facilities and professionals. DevOrbital's ABDM Module is an ABDM-ready add-on designed to support ABHA-linked registration and consent-based sharing of records from the hospital's own system. Participation remains the hospital's choice, and scope is confirmed during onboarding.
The problem
ABHA, M1, M2, M3, HIP, HIU, HFR and HPR arrive together, and hospital teams struggle to tell which apply to them and in what order.
Names, ages and phone numbers are typed differently at each visit, so linking records to a single national identity is hard without a structured registration step.
Discharge summaries, prescriptions and reports kept on paper or in scattered files cannot be shared digitally, even when the patient asks.
When a patient's records are shared, the hospital needs to show that the patient agreed. Informal permission is not a record.
How it works
The hospital is listed in the Health Facility Registry and its doctors in the Healthcare Professionals Registry.
At registration, the patient shares their ABHA number, or one is created with their consent.
The OPD or IPD episode is documented in the hospital system.
The visit is linked to the patient's ABHA as a care context.
Another provider or the patient requests access, and the patient approves or declines.
Only after consent is the record shared in the agreed format.
What's included
Use it on its own — or connected
The ABDM Module is an add-on to DevOrbital HMS, so it works with the registration, OPD, IPD and records already running in the hospital. Because it builds on the patient record rather than duplicating it, a hospital can adopt it when it is ready to take part in ABDM without changing its other workflows.
Pairs naturally with:
Who it's for
Illustrative scenario · not a customer story
A returning patient registers with ABHA
Front-desk supervisor
A patient arrives for an OPD visit and says she has an ABHA number. The front-desk supervisor enters it at registration, and it is attached to her existing UHID. After the consultation, the doctor's notes and prescription are saved in the hospital system. Later, the patient visits a specialist elsewhere, who asks to see her earlier records. She approves the request on her phone, and only then is the relevant record shared. The hospital can show that consent was given. (Illustrative scenario.)
The Ayushman Bharat Digital Mission (ABDM), run by the National Health Authority, is India's national framework for digital health. Its aim is a connected ecosystem in which a person's health records can be linked to a single identity and shared between providers, with the person's consent. ABDM was launched nationwide in September 2021.
For a hospital, ABDM is mostly about three things: identifying patients with a national ID, making records available in a standard digital form, and sharing them only when the patient agrees. Participation is voluntary for patients and hospitals alike, and requirements are published by the NHA, so always check the latest guidance on abdm.gov.in. Our ABDM and ABHA guide for hospitals explains the mission in more depth, and the glossary covers ABDM and ABHA.
ABHA (Ayushman Bharat Health Account) is a 14-digit number that identifies a person in ABDM. People can create it using Aadhaar or a mobile number, among other routes, and creation is voluntary and not a condition for receiving care. People can also choose an ABHA address, a readable username such as name@abdm.
The Health Facility Registry (HFR) is the registry of healthcare facilities, and the Healthcare Professionals Registry (HPR) is the registry of doctors and other professionals. A hospital that wants to take part registers its facility, and its clinicians register as professionals. See the glossary entries for HFR and HPR.
These registries matter because other participants need to find and trust the facility and the professional behind a record.
ABDM groups its software integration into milestones. M1 is about creating and verifying ABHA numbers, so a hospital can identify patients through ABHA. M2 is about the hospital acting as a health information provider (HIP): linking a patient's visits (care contexts) to their ABHA and sharing records when consent is given. M3 is about the hospital acting as a health information user (HIU): requesting records from other providers, again with consent.
The consent manager sits in the middle. It makes sure that health data moves only when the patient approves, for a stated purpose and period. Records are exchanged in standard formats such as FHIR.
These are ABDM's own terms, and its sandbox and review process define what each milestone requires. DevOrbital's module is an ABDM-ready add-on designed to support these concepts, and the milestones relevant to your facility are confirmed during onboarding. We make no claim of certification here.
The most visible change is at registration, where staff capture or create an ABHA number and attach it to the patient's UHID. Another is Scan and Share: facilities display a QR code, patients scan it with a supported app, and their basic details arrive in the hospital's system to speed up OPD registration. Our token management and QR registration add-ons work in the same area of the patient journey.
Behind the scenes, the more important change is record quality. For records to be shared, they must exist digitally, be tied to the right patient and be reasonably complete. That is why ABDM readiness is as much about the clinical and records modules as about any one add-on. Read how this connects in ABDM and NABH readiness.
FAQ
It is an ABDM-ready add-on to DevOrbital HMS, designed to support ABHA-linked registration and consent-based sharing of health records from the hospital's own system. It builds on the OPD, IPD and records already running, and the scope for each hospital is agreed during onboarding.
They are ABDM's integration milestones. M1 covers creating and verifying ABHA numbers, M2 covers acting as a health information provider by linking and sharing records with consent, and M3 covers acting as a health information user by requesting records from others with consent.
A health information provider (HIP) holds and shares health records, such as a hospital or laboratory. A health information user (HIU) requests and views records with the patient's consent, such as another hospital or a doctor. One facility can act as both.
No. As of 2026, ABDM describes ABHA creation as voluntary, and patients can receive care without it. Hospitals that take part simply give patients the option to link their records, so registration should work with or without an ABHA number.
We do not claim any ABDM milestone certification on this page. The ABDM Module is described as an ABDM-ready add-on, designed to support ABHA-linked registration and consent-based sharing. Ask about the current status and scope for your facility during onboarding.
Taking part in ABDM generally involves registering the facility in the Health Facility Registry and its professionals in the Healthcare Professionals Registry. Check the current requirements on abdm.gov.in, since processes can change over time. DevOrbital can walk you through this during onboarding.
That is the core ABDM principle. Records move only after the patient approves a consent request, for a stated purpose and period, through the consent manager. A hospital taking part should also keep its own records of consent and access.
Keep exploring
Compliance
ABDM and ABHA Guide for Hospitals: What to Do in 2026
● DevOrbital HMS
Compliance · 9 min read
A plain-English guide to ABDM for Indian hospitals: ABHA, HFR, HPR, M1/M2/M3 milestones, Scan and Share, consent, FHIR and a practical readiness checklist.
Read this guideCompliance
NABH and Hospital Software: What an HMS Can and Cannot Do
● DevOrbital HMS
Compliance · 6 min read
How hospital software supports NABH accreditation: medical records, medication safety, access control and audit trails mapped to the 6th edition chapters.
Read this guideCompliance
DPDP Act for Hospitals: Patient Data Obligations Explained
● DevOrbital HMS
Compliance · 7 min read
What India's DPDP Act 2023 and 2025 Rules mean for hospitals: patient consent, breach notice, security safeguards, children's data and a checklist.
Read this guideTell us about your facility and we will walk you through the modules that fit — one department or the whole hospital.
