[C4GT] - EPIC: ABDM Wrapper

[atulai-sg]

Project Description

The Ayushman Bharat Digital Mission (ABDM) aims to develop the backbone necessary to support the integrated digital health infrastructure of the country. It will bridge the existing gap amongst different stakeholders of the Healthcare ecosystem through digital highways.

Following are the components defined by ABDM which are essentially the building blocks for the ecosystem:

• ABHA Number
• Healthcare Professionals Registry (HPR)
• ABHA Mobile App (PHR)
• Health Facility Registry (HFR)
• Unified Health Interface (UHI)

ABDM Architecture:

Key components in the above diagram are:

• Health Information Providers (HIPs)
• Health Information Users (HIUs)
• Repositories (HRPs / Health Repository Providers)
• Consent Managers (CMs)
• Gateway
• Health Lockers
• Facilities (Hospitals / Labs / Clinics)

ABHA milestones

In order to make an application ABDM compliant, it has to go through 3 milestones:
Milestone 1: ABHA Id creation, verification and obtaining link token
Milestone 2: Linking and exporting health data
Milestone 3: Sending a consent request and importing data from other applications in the ecosystem

Current challenges

Currently, developers are facing challenges when building applications around the interfaces provided by NHA:

• Majority of ABDM use cases involve asynchronous API calls, implementation of which is turning out to be a challenge for developers.
• The 2-way Encryption and Decryption steps suggested by ABDM are quite complex. Developers have raised concerns regarding this.
• Developers have often pointed out that the API contract published on their Swagger is not up to date.
• The use-cases are very complex and involve multiple steps which in turn is difficult to implement.

Project Goals

• This project aims to build ABDM Wrapper (SDK) which abstracts HRP complexities for developers. This abstraction can be achieved at both HIP and HIU sides:
• Handles metadata storage such as consent artifacts, schemas, mappings, etc.
• Abstracts out ABDM version upgrades, contract changes, deprecation, etc by giving a constant workflow interface to developers
• Provides capabilities of both async and sync apis. Developers will have the option to opt according to their convenience.
• Handles encryption decryption
• Take care of security auditing and compliance
• Store audit logs for consent and data flows.
• Governance around data retention and policies.

Modules and Features

Discovery and Linking Workflows - Allow discovery of a patient’s managed by HIP in the ABDM network and allow linking of ABHA Id to the patient profile. #1

Consent Management - Manages lifecycle of consents granted by a patient to an HIP/HIU #2

Data Transfer - Allow consented medical data transfer to the ABDM network. #3

Subscription Management - Subscription management for continuously pulling the medical records for a patient from other HIPs. #4

[sharvarii11]

hello @atulai-sg , I'm interested in this project and want to contribute in it . I have some questions regrading to project . you have mentioned, currently, NHA has api system available , which is complex to use. Is that repository is available publically or not ?.. if it is available can u provide me link of it . That will help me to understand this project more precisely.

[atulai-sg]

hello @atulai-sg , I'm interested in this project and want to contribute in it . I have some questions regrading to project . you have mentioned, currently, NHA has api system available , which is complex to use. Is that repository is available publically or not ?.. if it is available can u provide me link of it . That will help me to understand this project more precisely.

The APIs documentations are available, like this one: https://sandbox.abdm.gov.in/swagger/ndhm-hip.yaml
You can go through the sandbox documentation on how to use them: https://sandbox.abdm.gov.in/docs/integration_and_exit_process

[Dhruv-Bar0t]

@atulai-sg : Currently, we are facing the same problem while integrating ABDM with our new product, And we wanted to simplify the integration process for that specific I am also trying to solve the same problem, that's why I would contribute to this project.

Looking forward to hearing from you and working on this project.