1 of 9

Manika Jain

Mentors: Atul Kumar, Madhuram Jajoo and Anchita Goel

CODE4GovTech 2023

Midpoint Demo Showcase

ABDM: Discovery and Linking

Workflows

2 of 9

OUTLINE

Introduction to Problem Statement and Motivation
Understanding ABDM
Project Goals and Impact
Live Demonstration
Milestones covered and Future work
Learning Outcomes

3 of 9

INTRODUCTION TO PROBLEM STATEMENT

BACKGROUND

When a gateway calls the HIP system to request a specific patient's records, the HIP health repository responds with a set of care context labels in a masked form. To establish the link between the patient's care context and their Consent Manager's User ID, the HIP system provides a link reference number and authentication type, along with its associated parameters.

AUTHENTICATION AND LINKING

The HIP system sends a (OTP) to the patient's phone number for verification.

Upon receiving the OTP, the patient uses their patient app to submit the OTP within a specified time frame. If the patient successfully passes the authentication process as determined by the HIP system, the linking of the care context to the patient's Consent Manager's User ID is considered complete.

Make them understand problem statement and motivation behind choosing it

Why do we need to discover and link workflows

Now coming on to understanding the problem statement, my project is focused in the area of discovery of new patients and linking their information in the Health Repository Portal fo ABDM. In the context of a Healthcare Information Provider (HIP) system, the process of authenticating patients and linking their care context to their Consent Manager's User ID involves several steps. The goal of this problem statement is to optimize and enhance the efficiency and security of the patient authentication and information linking process in the HIP system.

When the gateway calls an HIP system and requests for a particular patient’s records with a set of verifiable Ids, the process of information discovery begins. The HIP system sends an OTP to the patient’s phone number. Note, the phone number for OTP communication from HIP may be the same as verified by the CM or maybe a different number that the patient has chosen as preferred mode of communication with HIP - meaning it's up to the HIP to choose the phone number it sends OTP to. The patient, via patient app, submits the OTP received from the HIP system within the stipulated time. If the patient is successfully authenticated by the HIP, the linking is now complete.

Motivation behind choosing this project: Patient data in healthcare is highly sensitive and confidential. With the increasing use of digital systems, ensuring robust security measures becomes extremely important. So I wanted to work in the lines of healthcare and security while at the same time work on a new stack to enhance my skill set.

4 of 9

WHAT IS ABDM?

ABDM (Ayushman Bharat Digital Mission) is a pioneering initiative undertaken by the Government of India to establish a robust digital health infrastructure that supports an integrated healthcare ecosystem. This mission aims to bridge existing gaps among various stakeholders in the healthcare sector by establishing digital highways, enabling seamless connectivity and efficient information exchange.
In my project “Discovery and Linking Workflows”, the primary objective is to ensure that patients are easily discoverable within the ABDM ecosystem using their unique ABHA number.

5 of 9

PROJECT MILESTONES

& IMPACT

4th

Sending a consent request and importing data from other applications in the ecosystem.

3rd

Linking and Exporting Health Data: Create a care context associated with the patient post consultation and ensure it can support sharing of all five major types of reports: Diagnostic reports, Discharge summaries, OPD notes, Prescription report, Immunization Record.

2nd

ABHA ID Creation, Verification and Generating the Link access

This milestone allows the user to access the health records mapped to their respective ABHA ID and a specific Link token for the same.

1st

Understanding the problem statement of ABDM - Discovery and Linking Workflows and familiarizing with the tech stack (Spring Boot, Java, NoSQL). Understand the design flow of ADBM Wrapper that abstracts the HRP(HIU/HIP) complexities for developers.

Talk about milestones covered and impact of the project

So broadly following are the project milestones :

Thoroughly understanding the design flow of ABDM Discovery and Linking and more importantly of the ABDM Wrapper. Basically ABDM SDK Wrapper shall abstract HRP(HIU/HIP) complexities for developers. Majority of ABDM use cases involve asynchronous API calls, implementation of which is turning out to be a challenge for developers.The use-cases are very complex and involve multiple steps which in turn is difficult to implement. So we will be simplifying the process.
ABHA ID creation using the ABHA SBX Application, creation of ABHA address, verification of the ids using ABDM Sandbox APIS and generating token access to invoke external ABDM APIs - the work is almost completed for this one where I have created the controllers, service layers and the testing methods. Once we are thorough with the ABDM Sandbox access, we will be able to test it out on the local enviornment too
Linking records for the existing patients and share different types of health records
Ability to import data from other applications in the environment

6 of 9

LIVE

DEMONSTRATION

In the demo, I will be showcasing the following features:

Postman API Testing: ABHA ID Creation, Verification and Generating the Link access
Invoking the Discovery and Linking APIs in Postman and fetching data
Understanding the codebase for invoking ABDM APIs (Controllers, Unit test cases, etc)

Things to be covered:

ABDM Sandbox - Showcase the APIs that you are working on
Postman - since ours is a heavily backend project,
Show the user authentication first - how to get access token
API Testing - Discover and Consent Request INIT - there has been some blocker from the ABDM Side to provide the user access which doesn’t let us fetch the data, currently working on that

3. Understanding the codebase -

Discovery Controller which is the receiving stage for the Discovery API Endpoints and calls the ABDM layer
DiscoveryService Client - The logic behind invoking the API that makes a call to the ABDM
DiscoveryCOntrollerTest - covers the unit test cases for the discovery controller comprising of mainly JUnit and Mockito test cases

This is the entire flow of the project so far now, and I am currently working alongside my mentor to get the ABDM access so I can test out the APIs for which the code is already ready. Although the access posed to be a challenge, but in the meantime I devoted my time to create the code piece for invoking APIs in my local machine along with completing the unit test cases for the same so as when we get the access, the time is only spent on testing and moving forward on milestone 3.

7 of 9

GOALS COVERED

FUTURE WORK

Developed a high-level architecture design document for my backend implementation of HIP Facade.
Gained proficiency in working with the ABDM Sandbox environment by setting it up locally on my machine.
Implemented the ABDM APIs specific to my use case and handle the output data based on the application needs.
Implemented the service layer for the HRP (Health Repository Provider). This layer plays a pivotal role in making calls to the Wrapper and ABDM to retrieve and invoke patient data and information.
ABHA ID Creation, Verification and Generating the Link access completed.
Completed the ABDM APIs in Postman and fetching data in Spring boot (Controllers, Unit test cases using JUnit and Mockito, etc).
Milestone 1 and Milestone 2 completed

Going forward, major focus will be on completing some requisites left for Milestone 2 and completing Milestone 3.
Testing the APIs after receiving access from ABDM Sandbox.
Working on User Authentication via different channels of OTP, Demographics, etc.
Create a care context associated with the patient post consultation and ensure it can support sharing of all five major types of reports: Diagnostic reports, Discharge summaries, OPD notes, Prescription report, Immunization Record.

Sending a consent request and importing data from other applications in the ecosystem.
Documentation of the work

Coming onto now the work that has been accomplished:

Development of a high-level architecture design of HRP is completed where HRP is our main interface for interacting with ABDM. To call external apis, the request is sent to HRP Facade which fetched the data from ABDM and calls it on local host. A multi modular project has been set up for the same and the interface is almost completed.
Implemented the ABDM APIs specific to my use case of Discovery, Authentication and Linking on my local machine and handle the output data based on the application needs.
Completed the ABDM APIs in Postman and fetching data in Spring boot (Controllers, Unit test cases using JUnit and Mockito, etc). - Covering MIlestone 1 and Milestone 2

Future Work:

Getting access and testing out APIs to be completed
Working on User Authentication via different channels of OTP, Demographics, etc.
Linking of the workflows after discovery is completed
Documentation of the work done

8 of 9

LEARNING OUTCOMES

1

Implemented the ABDM APIs specific to my use case and handle the output data based on the application needs.

3

Learned and implemented unit testing frameworks like JUnit and Mockito which helped me ensure the correctness of my code and its individual components.

5

Client and server side communication,Long polling and Short Polling, Synchronous and Asynchronous API.

2

Gained in-depth knowledge and hands-on experience with the backend tech stack, particularly Spring boot

4

Rest Templates and WebClient, tools that are important for invoking an API in Spring boot and worked on creating them for calling external mock APIs.

9 of 9

By: Manika Jain

LinkedIn: https://www.linkedin.com/in/manika-jain/

GitHub: https://github.com/manikajain11

Email: manikajain11@gmail.com

THANK YOU!

ABDM: Discovery and Linking

Workflows