Scribd
Upload
154 views4 pages

(External) ABDM Wrapper Proposal

The document describes a proposal to build an ABDM Wrapper SDK that abstracts complexities of interacting with the Ayushman Bharat Digital Mission for developers. The SDK would handle tasks like consent management, data transfer, encryption/decryption, and abstract version upgrades to provide a simple interface for developers.

Uploaded by

chaks.gauty
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
154 views4 pages

(External) ABDM Wrapper Proposal

The document describes a proposal to build an ABDM Wrapper SDK that abstracts complexities of interacting with the Ayushman Bharat Digital Mission for developers. The SDK would handle tasks like consent management, data transfer, encryption/decryption, and abstract version upgrades to provide a simple interface for developers.

Uploaded by

chaks.gauty
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

[External] ABDM Wrapper proposal

Project Description & End-Use Case


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)

ABHA 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)

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

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.

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.

List of Features to be implemented


● 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.
● Consent Management - Manages lifecycle of consents granted by a patient to an
HIP/HIU

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

● Subscription Management - Subscription management for continuously pulling the


medical records for a patient from other HIPs.

Learning Path
Complexity

Medium

Required Skills

Java and SpringBoot to develop API services.

Project Size

8 weeks
Link to documentation for Product Set-Up
NA

Acceptance/Success Criteria for the pull requests


● Make sure code written is of production grade and follows best practices.
● Make sure code written follows open-source guidelines.
● All APIs should follow best practices and they should be tested locally by the reviewer
before merging it.
● Make sure all the use-cases and scenarios are backed by unit-test cases.
● Documentation should be up to the mark.

Milestones
● Understanding the project and requirements.
● Setup sandbox environment.
● Setting up a local dev environment.
● Define API contracts.
● Develop APIs required for discovery and linking workflows.
● Develop APIs required for consent management.
● Develop APIs required for data transfer.
● Develop APIs required for subscription management.
● Test end-to-end

You might also like