ABDM Overview - NHA-ABDM/ABDM-wrapper GitHub Wiki

Stakeholders in ABDM

1. Patients

  • ADBM will enable patients to be able to register rapidly during their health visit, collect their health records across any health facility, book appointments with doctors and share their health information with consent.
  • Patients will need to get an ABHA address as their identifier in ABDM.

2. Health professionals

  • Health Professionals (Doctors, Nurses, Lab Technincans, .. ) need to register themselves in the Health Professional Registry (HPR) and get themsevles a HPR ID to participate in ABDM.
  • This will also enable them to be discovered as a verfied professional in the ecosystem

3. Health Facilities

  • Health Facilities (Hospitals, Nursing Homes, Clinics, Labs, Pharmacies .. ) will need to register themselves in the Health Facility Registry (HFR) and get themselves a HFR ID.
  • They will also need to use a ABDM compliant software for generating ABHA linked health records.

4. Digital Solution Companies

  • DSCs are organizations that provide software to patients or health facilities. DSCs are expected to integrate their software solution with the ABDM building blocks and get their solution certified to participate in the ecosystem.
  • DSCs are the primary users of the ABDM sandbox.
  • They sign up to the sandbox and validate their application before seeking certification.

What role do they get in ABDM ecosystem?

All roles in ABDM ecosystem are mapped to the client ID and secret which is provided on sandbox registration

1. Health Facilities

  • HIPs (Health Information Providers) or HIUs (Health Information Users)

2. Health Professionals

  • HIUs (Health Information Users, as per use case to provide better diagnosis)

3. Digital Solution Companies

  • HRPs (Healthcare repository providers, in case of multiple facilities) or HIPs (Health Information Providers, in case of single facility).
  • They provide solutions to health facilities, such that they can digitise their workflows.

4. Consumer Apps

  • PHR (Personal Health Repository) - to be used by patients to view their details, access healthcare services and manage their health records
  • HIPs (Healthcare Information Providers) if they want to provide option to the user to upload health records or manage them for insights.
  • HIUs (Healthcare Information Users) if they want to provide option to the user to fetch health records from ABDM ecosystem on their application

How does ABDM work in action?

1. Patient Registration -> This is to ensure the DSC in their application workflow is able to create or verify ABHA.

ABHA workflow

2. Record Linking (HIP) -> The application is supposed to notify ABDM. The application is supposed to share data in FHIR format only if a HIU (patient app or any other application) asks for the data with patients consent. Patient can also fetch the records from an app of their choice.

HIP initiated linking

3. Record Fetch (HIU) -> The application raises a consent on a user's (doctor or healthworker or patient) behalf, which is then approved by the patient on a PHR app. The application (HIU) then gets the data from the HIP in FHIR format. They are then supposed to show the data to the user for the time duration that the health data is requested, as specified in the consent

Consent Framework