Ayushman Bharat Digital Mission

ABDM-integrated hospital management system

Swastik HMS is integrated with ABDM for milestone M1 (ABHA) and milestone M2 (Health Information Provider). Patients create or use their ABHA at registration, link their hospital records, and share them securely with any doctor they choose.

What ABDM integration means for your hospital

An ABDM-integrated hospital management system connects your hospital to the Ayushman Bharat Digital Mission, India’s national digital health ecosystem run by the National Health Authority. Patients get an ABHA (Ayushman Bharat Health Account) at your registration counter, and the records your hospital creates can be linked to it and shared with the patient’s consent.

Swastik HMS is integrated for milestone M1 (ABHA) and milestone M2 (Health Information Provider), and with the Health Professional and Health Facility Registries. New to ABDM? Read our plain-language ABDM integration guide.

What is integrated

ABDM capabilities in Swastik HMS

Each ABDM milestone and registry integration, and what HMS does for it.

M1

ABHA at the counter

Create and verify ABHA numbers, log patients in with ABHA, and register them with Scan & Share.

  • ABHA creation with Aadhaar OTP, biometrics or driving licence
  • ABHA address suggestions and selection
  • Mobile and email verification, and child ABHA
  • Login with ABHA number, mobile or ABHA address and OTP
  • ABHA profile, ABHA card download and QR code
  • Benefit linking, delinking and search
  • Scan & Share registration that issues a token number
M2

Health Information Provider

Visits, admissions and reports become records patients link to their ABHA and share with consent.

  • Care contexts created automatically for OPD visits, IPD admissions, lab reports and radiology reports
  • Care-context discovery, patient-initiated linking with OTP, and hospital-initiated linking
  • Consent notifications stored as consent artefacts
  • Sharing limited to the consented care contexts, record types and date range
  • FHIR records: OP consultation, discharge summary, diagnostic report and prescription
  • Encrypted with X25519 key agreement and AES-256-GCM, delivered in the background with retries
HPR · HFR

Health registries

Doctors linked to the Health Professional Registry and the facility to the Health Facility Registry.

  • Search the Health Professional Registry (HPR) and link doctors to their HPR ID
  • Search, register and sync the facility with the Health Facility Registry (HFR)
+

Need more?

Health Information User (M3) capability, or ABDM integration for software you already run, can be built by our team.

Hospital software development
Record flow

How a hospital record reaches a patient’s phone

  1. Patient visits

    The patient registers at the counter with their ABHA, or by scanning the hospital’s Scan & Share QR code.

  2. Care context created

    Saving an OPD visit, admission, lab report or radiology report creates a care context automatically.

  3. Records linked

    The patient discovers and links records from their PHR app with an OTP, or the hospital links them.

  4. Consent granted

    A doctor or the patient requests records, and the patient approves exactly what can be shared.

  5. FHIR record built

    HMS builds FHIR records for only the consented care contexts, record types and dates.

  6. Encrypted delivery

    Records are encrypted and delivered in the background, with retries if the receiver is unavailable.

Consent

Only what the patient agreed to, and nothing more

Every request for records is checked against the patient’s consent before anything is built or sent.

Going live with ABDM: each hospital registers its facility in the Health Facility Registry, its doctors in the Health Professional Registry, and links as a Health Information Provider. ABHA creation works from day one; our team helps with the rest of the onboarding.

Which records

Only the care contexts (visits, admissions, reports) the patient selected.

Which kinds of record

Only the approved record types: OP consultation, discharge summary, diagnostic report or prescription.

Which dates

Only records inside the date range in the consent.

Encrypted in transit

X25519 key agreement and AES-256-GCM, delivered in the background with retries.

Also included

Built to be operated

v0.5 and v3 APIs

Handles callbacks from both ABDM API versions.

Callback log

Every gateway callback is logged for troubleshooting and audit.

Staff console

A console for staff to run ABHA and linking flows.

SMS providers

Patient SMS notifications through a configurable SMS provider.

Learn more

ABDM guides for hospitals

Explore more

ABDM-ready modules

OPD Management

Registration, daily tokens, room rotation and waiting-hall displays.

FAQ

ABDM integration questions

What does ABDM integration mean for a hospital?

It lets the registration counter create and verify ABHA numbers, and lets the hospital share the records it creates, such as OPD visits, admissions and lab and radiology reports, with patients and their chosen doctors through ABDM, with consent.

Which ABDM milestones does Swastik HMS support?

Milestone M1 (ABHA creation, verification, login and Scan & Share) and milestone M2 (Health Information Provider: care contexts, linking, consent and encrypted FHIR record sharing), plus HPR and HFR registry integration.

Does Swastik HMS support M3 (Health Information User)?

Not in the standard product. HIU capability, to fetch records from other facilities, can be built by our development team.

What does our hospital need to do to go live with ABDM?

Register the facility in the Health Facility Registry, register doctors in the Health Professional Registry and link the facility as a Health Information Provider. ABHA creation works from day one, and our team helps with the onboarding.

Can you add ABDM integration to software we already use?

Yes. We can add ABHA (M1) and Health Information Provider (M2) capability to an existing HMS, LIS or EMR after reviewing your system.

How is patient data protected when records are shared?

Records are shared only within the patient’s consent (the selected care contexts, record types and date range) and are encrypted with X25519 key agreement and AES-256-GCM.

Planning your ABDM rollout?

Talk to us about ABHA at your registration counters, HIP onboarding, or ABDM integration for your existing software.

Request a demo WhatsApp us