Project Name: ABDM - Sandbox

Integration
Module Name: ABHA Creation and
Verification
Release Version:

Session API https://dev.abdm.gov.in/api/hiecm/gatewa

S.No Function Applicable To Mandatory/ Optional

ABHA Creation Process

ABHA Creation Through

1 All
Aadhaar OTP

1.1 Mandatory

1.2 Mandatory
1.3 Optional

1.4 Mandatory

1.5 Mandatory

1.6 Mandatory

1.7 Mandatory

1.8 integrating entities Optional

have not
implemented API
for OTP not to be
sent in case
communication
mobile is same as
Aadhaar linked
mobile. In that case
the test scenario
detailed under sl.
No 1.8 will only be
 No 1.8 will only be
considered.
However, it is
recommended that
API =
checkAndGenerate
MobileOTP be
1.9 Mandatory
implemented. This
will reduce one step
of OTP verification
in case
communication
mobile is same as
the Aadhaar linked

Mandatory for Private

/Government (Optional for
integrated program using
1.1
demo auth as they have
default ABHA address
generated)

1.11 Mandatory

1.12 Mandatory for Private

 Either of the test cases
CRT_ABHA_114 or
CRT_ABHA_115 is
mandatory for
1.13
Governement

Optional for Private

ABHA Creation Through

2 All
Aadhaar Biometric

2.1 Optional

2.2 Optional

2.3 Optional

2.4 Optional

2.5 Optional

sent in case
communication
mobile is same as
Aadhaar linked
mobile. In that case
2.6 the test scenario Optional
detailed under sl.
No 2.6 will only be
considered.
However, it is
recommended that
API =
 API =
checkAndGenerate
MobileOTP be
2.7 Optional
implemented. This
will reduce one step
of OTP verification
2.8 Optional

2.9 Mandatory for Private

Either of the test cases

CRT_ABHA_209 or
CRT_ABHA_210 is
mandatory for
2.1
Governement

Optional for Private

ABHA Creation Through

Demo Auth/ Offline Mode
3 (Available Only for trusted Government
entities. All government
Entities are eligible.

3.1 Mandatory

3.2 Mandatory

3.3 Optional
3.4 Mandatory

3.5 Mandatory

3.6 Mandatory

3.7 Mandatory
3.8 Mandatory for Private

Either of the test cases

CRT_ABHA_308 or
CRT_ABHA_309 is
mandatory for
3.9
Governement

Optional for Private

Optional for Private

ABHA Creation Through
4
Driving License / PAN Mandatory for
Government

4.1 Optional

4.2 Optional

4.3 Optional

4.4 Optional

4.5 Optional

4.6 Optional

4.7 Optional

4.8 Optional
 4.9 Optional

4.1 Optional

ABHA Verification Process

5 ABHA Verification All

5.1 Mandatory

5.2 Mandatory

6 ABHA Verification All

 Mandatory

6.1 Mandatory

7 ABHA Verification All

7.1

Mandatory

7.2

Mandatory
7.3

Mandatory

7.4

Mandatory
7.5

Mandatory
Fetching ABHA details
8 using Aadhaar Number All

8.1
Mandatory

Mandatory
8.2

Mandatory

8.3

Mandatory

8.4
Mandatory

ABHA Verification
9 (Applicable for Government All
Entites)

9.1 Optional
9.2 Optional

Reading ABHA Info using

10 All
ABHA QR Code

10.1 Optional

11 Profile Update All

11.1 Optional

11.2 Optional

11.3 Optional

11.4 Optional

11.5 Optional

Verify one ABHA Number is

16 linked to the unique patient All
ID in HIMS

16

Mandatory

17 Share Profile PHR app Mandatory

17.1 Mandatory
 Test Designed by:

Test Designed date:

Test Executed by:

Test Execution date:
Application/ System Name:

https://dev.abdm.gov.in/api/hiecm/gateway/v3/sessions

Test Case ID Functionality

CRT_ABHA_101 Create ABHA Option

CRT_ABHA_102 Consent collection

CRT_ABHA_103 Suggestions:-
Consent collection should be multilingual

CRT_ABHA_104 Aadhaar collection and Error Message

CRT_ABHA_105 Aadhaar OTP Collection

CRT_ABHA_106 Resend OTP

CRT_ABHA_107 OTP based Aadhaar Authentication

CRT_ABHA_108 Communication Mobile Number verification-I

CRT_ABHA_109 Communication Mobile Number verification-II

CRT_ABHA_112 Suggested ABHA Address

CRT_ABHA_113 Display of ABHA Number

View and Download ABHA details.

CRT_ABHA_114
(If integrators is generating ABHA card)
 View and Download ABHA details.
CRT_ABHA_115
(If integrators is not generating ABHA card)

Create ABHA
CRT_ABHA_201
Option

CRT_ABHA_202 Consent collection

Suggestions:-
CRT_ABHA_203
Consent collection should be multilingual

CRT_ABHA_204 Aadhaar collection and Error Message

CRT_ABHA_205 Biometric based Aadhaar Authentication

CRT_ABHA_206 Communication Mobile Number verification-I

CRT_ABHA_207 Communication Mobile Number verification-II

CRT_ABHA_208 Display of ABHA Number

View and Download ABHA details.

CRT_ABHA_209
(If integrators is generating ABHA card)

View and Download ABHA details.

CRT_ABHA_210
(If integrators is not generating ABHA card)

Create ABHA
CRT_ABHA_301
Option

CRT_ABHA_302 Consent collection

Suggestions:-
CRT_ABHA_303
Consent collection should be multilingual
CRT_ABHA_304 Aadhaar collection and Error Message

CRT_ABHA_305 Demographic Information based authentication

CRT_ABHA_306 Profile Completion

CRT_ABHA_307 Display of ABHA Number

 View and Download ABHA details.
CRT_ABHA_308
(If integrators is generating ABHA card)

View and Download ABHA details.

CRT_ABHA_309
(If integrators is not generating ABHA card)

CRT_ABHA_401 Create ABHA Option

CRT_ABHA_402 Consent Collection

CRT_ABHA_403 Communication Mobile Number

CRT_ABHA_404 Mobile Number Verification

CRT_ABHA_405 Document Verification

CRT_ABHA_406 Document Upload

CRT_ABHA_407 Manual Verification and ABHA Creation

CRT_ABHA_408 Display of ABHA Number

 View and Download ABHA details.
CRT_ABHA_410
(If integrators is generating ABHA card)

View and Download ABHA details.

CRT_ABHA_411
(If integrators is not generating ABHA card)

VRFY_ABHA_101 ABHA Number Verification using Aadhaar OTP

VRFY_ABHA_102 ABHA Address Verification using Aadhaar OTP

 ABHA Number verification using mobile OTP(ABHA
VRFY_ABHA_201
Linked Mobile Number )

ABHA Address verification using mobile OTP(ABHA

VRFY_ABHA_202
Linked Mobile Number )

VRFY_ABHA _301 Fetch ABHA details using Mobile

(communication)authentication .
Multi authentication feature also need to be
implemented like Captcha preferred
VRFY_ABHA _302
VRFY_ABHA _303

VRFY_ABHA _304

VRFY_ABHA _305

Fetch ABHA details using Aadhaar Number

VRFY_ABHA_401

VRFY_ABHA_402

VRFY_ABHA_403

VRFY_ABHA_404

VRFY_ABHA_405

ABHA Number verification using Aadhaar Biometric -

VRFY_ABHA_501
Fingerprint
 ABHA Address verification using Aadhaar Biometric -
VRFY_ABHA_502
Fingerprint

VRFY_ABHA_501 Reading ABHA Profile Info using ABHA QR Code

PROF_ABHA_601 Mobile Update

PROF_ABHA_602 Photo Update

PROF_ABHA_603 Email Update

PROF_ABHA_604 Re-KYC

PROF_ABHA_605 Delete ABHA

TAGGING_UNIQUEPATIENTI Verify one ABHA Number is linked to the unique

D_UNIQUEABHANUMBER patient ID in HIMS
SHARE
Share Patient Profile
_PATIENT_PROFILE_701
NHA

Test Case
(to be checked during functional testing)

The system must provide an option to create ABHA through Aadhaar OTP

The system must display the consent language/ disclaimer language and
collect user's consent as per the ABDM published consent.
Refer Cell No-: M14
 The system should be able to provide the consent in languages other
than English also

System must allow the user to enter Aadhaar Number and the system
will display an error message for invalid Aadhaar Number

User receives Aadhaar OTP and System must allow the user to enter
Aadhaar OTP.

System may activate the Resend OTP button maximum 2 times after 60
seconds

System must verify the OTP

1. If communication mobile number is same as Aadhaar linked mobile

number then it should directly go to ABHA creation screen .

2. Alternatively , Integrators may also prompt for OTP again from the
user and then post verification of OTP user can go to ABHA creation
screen.
If communication mobile number is not same as Aadhaar linked mobile
number then system must ask for the OTP to verify comuncation mobile
number.

1. The system should allow the user to select the ABHA address giving
atleast 3 available suggestions

2. Otherwise the system should have a provision to create a ABHA

address with ABHA address Policy and validation rule should be print
beside the field where ABHA Address is entered.

Validation rules on ABHA Address to be set at the API level:

1. Minimum length - 8 characters
2. Maximum length - 18 characters
3. Special characters allowed - 1 dot (.) and/or 1 underscore (_)
4. Special character dot and underscore should be in between. Special
characters cannot be in the beginning or at the end
5. Alphanumeric - only numbers, only letters or any combination of
numbers and letters is allowed.

System must display the created ABHA Number

System must have a provision to View / Download ABHA card

System must have a provision to View details like ABHA number and
ABHA address in the card (either ABHA card or any card being generated
for their program/scheme/entity)

The system must provide an option to create ABHA through Aadhaar

Biometric

The system must display the consent language/ disclaimer language and
collect user's consent as per the ABDM published consent.

Refer Cell No-: M14

The system should be able to provide the consent in languages other

than English also

System must allow the user to enter Aadhaar Number and the system
will display an error message for invalid Aadhaar Number

System must verify the biometrics (fingerprint or face) of the user

1. If communication mobile number is same as Aadhaar linked mobile

number then it should directly go to ABHA creation screen .

2. Alternatively , Integrators may also prompt for OTP again from the
user and then post verification of OTP user can go to ABHA creation
screen.
If communication mobile number is not same as Aadhaar linked mobile
number then system must ask for the OTP to verify comuncation mobile
number.

System must display the created ABHA Number

System must have a provision to View / Download ABHA card

System must have a provision to View details like ABHA number and
ABHA address in the card (either ABHA card or any card being generated
for their program/scheme/entity)

The system must provide an option to create ABHA through Aadhaar

Demographic/ Offline Mode

The system must display the consent language/ disclaimer language and
collect user's consent as per the ABDM published consent.

Refer Cell No-: M14

The system should be able to provide the consent in languages other

than English also
System must allow the user to enter Aadhaar Number and the system
will display an error message for invalid Aadhaar Number

System must verify the demographic information of the user against

their Aadhaar

System should accepts user's profile information -

System must display the created ABHA Number

System must have a provision to View / Download ABHA card

System must have a provision to View details like ABHA number and
ABHA address in the card (either ABHA card or any card being generated
for their program/scheme/entity)

The system must provide an option to create ABHA through Driving License / PAN

The System must display the consent/ disclaimer language and collect user's
consent

System must collect the communication mobile number

System must verify the provided mobile number

System must verify the provided document - Driving License / PAN

System must allow upload of front and back page of the Driving licence/ PAN

System Operator / healthcare worker must manually check the documents - Driving
License / PAN

System should display the created ABHA Number

System must have a provision to View / Download ABHA card

If Integrator is not generating ABHA card.

System must allow ABHA Number verification using Aadhaar OTP

System must allow ABHA Address verification using Aadhaar OTP

System must allow ABHA Number verification using
mobile OTP(ABHA Linked Mobile Number )

System must allow ABHA Address verification using

mobile OTP(ABHA Linked Mobile Number )

System must allow ABHA retrieval using communication mobile OTP

ABHA Details not exists to communicated Mobile Number

ABHA Details exists to communicated Mobile Number.

Incorrect OTP

Resend OTP Functionality

System must allow ABHA retrieval using Aadhaar Number

Incorrect OTP
ABHA Details not exists to Aadhaar Number

ABHA Details exists to Aadhaar Number

Resend OTP Functionality

System must allow ABHA Number verification using Biometric scan

System must allow ABHA Address verification using Biometric scan

System must allow scanning of ABHA QR code to read the ABHA

information

System must allow the user to update their Mobile number

System must allow the user to update their Photo

System must allow the user to update their Email

System must allow the user to perform re-KYC

System must allow the user to Delete/ Deactivate ABHA

Intergrator's HIMS System should allow tagging of one ABHA Number

with unique patient Id.
User will scan the QR code which is placed the facility premises
 Steps To Be Executed
(By User or Functional Tester)

1. Read consent language

2. Agree to the consent language (through 'I agree' checkbox or any other form of signature)
1. Read consent language
2. Agree to the consent language (through 'I agree' checkbox or any other form of signature)

1. Enter Aadhaar number

1. Receive OTP on mobile number registered with Aadhaar

2. Enter Aadhaar OTP

1. Click on Resend OTP Button

2. Receive OTP on mobile

Click on verify button (For Resend and Send)

It is recommended that verify button be auto enabled

This is applicable for testcase cell no -G20 , point no-1

1. System will check entered mobile is same as Aadhaar linked mobile number. If returns true then user will dire
to ABHA creation screen.

2. For point number 2 step are already mentioned in test case cell no- G20 , point no-2
1. System must verify the mobile number.
1. System must send OTP on mobile number
2. User enters the OTP and clicks on verify
3. In case of incorrect OTP, the system displays an error
4. In case of correct OTP, the system allows the user to proceed

1. Governemnt integrator may use the option for creating default ABHA address. However, it is recommended t
user-defined or system suggested ABHA address be used
2. System should have a provision for private integrators to proceed with the suggested ABHA address.
3. If beneficary use the existing ABHA address then system displays the "ABHA Address is already exist".

1. System shows the 14-digit ABHA number and ABHA address generated

1. System should show the user their ABHA Card

2. ABHA Card should be generated by API and should contain -
a. ABHA Number (Mandatory)
b. User Photo-Optional
c. ABHA QR code
d. date of birth and gender
e. ABHA Address
1. If Integrator is not generating ABHA card then They print the mentioned information on their program/scheme
any other card
a. ABHA Number (Mandatory)
b. ABHA Address

1. Read consent language

2. Agree to the consent language (through 'I agree' checkbox or any other form of signature)

1. Read consent language

2. Agree to the consent language (through 'I agree' checkbox or any other form of signature)

1. Enter Aadhaar number

1. Scan biometrics (Fingerprint)

2. Click on verify button

This is applicable for testcase cell no -G20 , point no-1

1. System will check entered mobile is same as Aadhaar linked mobile number. If returns true then user will dire
to ABHA creation screen.

2. For point number 2 step are already mentioned in test case cell no- G20 , point no-2
1. System must verify the mobile number.
1. System must send OTP on mobile number
2. User enters the OTP and clicks on verify
3. In case of incorrect OTP, the system displays an error
4. In case of correct OTP, the system allows the user to proceed
1. System shows the 14-digit ABHA number and ABHA address generated

1. System should show the user their ABHA Card

2. ABHA Card should be generated by API and should contain -
a. ABHA Number (Mandatory)
b. User Photo-Optional
c. ABHA QR code
d. date of birth and gender
e. ABHA Address

1. If Integrator is not generating ABHA card then They print the mentioned information on their program/scheme
any other card
a. ABHA Number (Mandatory)
b. ABHA Address

1. Read consent language

2. Agree to the consent language (through 'I agree' checkbox or any other form of signature)

1. Read consent language

2. Agree to the consent language (through 'I agree' checkbox or any other form of signature)
1. Enter Aadhaar number

1. Enter beneficiary's name, date of birth, gender, Aadhaar Number, Mobile Number, Address, State name, and
district name in accordance with the details on their Aadhaar card.
2. Case 1:If the beneficiary has an existing ABHA address, it should be displayed on both the ABHA card and the
ABHA profile.
OR
Case 2: If beneficary want to create a customize ABHA address then same ABHA address should be displayed
both the ABHA card and the ABHA profile.
3 : Case 3 : If the beneficiary have no ABHA address then system will create a Default ABHA Address ( ABHA Nu
@sbx) and same ABHA address should be displayed on both the ABHA card and the ABHA profile. (Mandatory )

4. If a beneficiary's deatils are matched with Aadhaaar information then system will not allow to create ABHA.
5. If If a beneficiary's deatils are matched with Aadhaaar information then system will allow to create ABHA .

1. System auto-populates beneficiary's name, date of birth, gender, Aadhaar number, mobile number, address,
name, district name
and ABHA Number.
2.The fields for name, date of birth, and gender are set as non-editable, while the remaining fields can be open
editing.

1. The system displays the 14-digit ABHA number and generates the corresponding ABHA Address, adhering to t
implementation chosen by integrators, either as a default setting or a customized one.
1. System should show the user their ABHA Card
2. ABHA Card should be generated by API and should contain -
a. ABHA Number (Mandatory)
b. ABHA QR code
c. Name, date of birth and gender
d. ABHA Address

1. If Integrator is not generating ABHA card then They print the mentioned information on their program/scheme
any other card with the beneficiary's demographic details.
a. ABHA Number (Mandatory)
b. ABHA Address

1. Read the consent language

2. Agree to the consent language (through 'I agree' checkbox or any other form of signature)

1. Enters a valid mobile number for communication purpose

1. Receive OTP on mobile number
2. Enter the OTP and clicks on verify
1. Enter the Driving License / PAN number
2. Enter name, date of birth and gender as per the document.
3. successfully verification will generate enrollment number
4. With this enrollment number patient/ user will approach with any ABDM facilty for creation of ABHA number .
1. Upload the front and back page of the document i.e Driving License / PAN.

1. A healthcare worker/ system operator manually verifies the Driving License / PAN

1. Show the 14-digit ABHA number generated

2. Show ABHA Number instead of Health ID
1. System should show the user their ABHA Card
2. ABHA Card should be generated by API and should contain -
a. ABHA Number (Mandatory)
b. User Photo-Optional
c. ABHA QR code
d. date of birth and gender
e. ABHA Address
1. If Integrator is not generating ABHA card then They print the mentioned information on their own card.
a. ABHA Number (Mandatory)
b. ABHA Address

1. Share ABHA Number or ABHA Address

2. Receive OTP on the Aadhaar linked mobile number
3. Enter the OTP.
4. System may activate the Resend OTP button maximum 2 times after 60 seconds in the OTP not received.
5. If beneficiary updates their mobile number in the HIMS system and It is advisable to provide users with the op
to update their mobile number in the ABHA profile with (Yes/No) using the profile API you should be able to upda
the details.

1. Share ABHA Number or ABHA Address.

2. Receive OTP on the Aadhaar linked mobile number.
3. Enter the OTP.
4. System may activate the Resend OTP button maximum 2 times after 60 seconds in the OTP not received.
5. If beneficiary updates their mobile number in the HIMS system and It is advisable to provide users with the op
to update their mobile number in the ABHA profile with (Yes/No) using the profile API you should be able to upda
the details.
1. Share ABHA Number or ABHA Address
2. Receive OTP on the Communication mobile number
3. Enter the OTP.
4. System may activate the Resend OTP button maximum 2 times after 60 seconds in the OTP not received.
5. If beneficiary updates their mobile number in the HIMS system and It is advisable to provide users with the op
to update their mobile number in the ABHA profile with (Yes/No) using the profile API you should be able to upda
the details.

1. Share ABHA Number or ABHA Address

2. Receive OTP on the Communication mobile number
3. Enter the OTP.
4. System may activate the Resend OTP button maximum 2 times after 60 seconds in the OTP not received.
5. If beneficiary updates their mobile number in the HIMS system and It is advisable to provide users with the op
to update their mobile number in the ABHA profile with (Yes/No) using the profile API you should be able to upda
the details.

1. If the user enters a in-valid mobile number(communication) then system will display an error message " Plea
enter a valid mobile number".

1. Incase ABHA Details not exists to communicated Mobile Number in ABHA system.
1. Incase ABHA Details exists to communicated Mobile Number.
1.1. If ABHA Details exists to comunication mobile number exists in ABHA system , In case ' Yes' then syste
will display a message "ABHA Exists to communication Mobile" and user will receive the OTP i.e "OTP sent to AB
linked mobile number ending with ******XXXX" and then Upon verification completion, the system will display a
of ABHA numbers linked to the mobile number, including the following details: Name, ABHA Number, ABHA Addr
and the beneficiary's photograph. When the user attempts to link selected ABHA details, the system will verify i
selected record is present in the HIMS system. If so, it will display a message indicating that the record is alread
linked in the HIMS with the HIMS beneficiary's ID.
1.2 If the selected ABHA Profile is not present in HIMS, the system will allow it to be Register and linked in t
HIMS beneficary's ID or proceed as per bussiness requirement OR benefciary can download the ABHA card (Opti

1. In case of incorrect OTP, the verification fails and display the relevant message.

1. System may activate the Resend OTP button maximum 2 times after 60 seconds in the OTP not received.

1.If the user enters wrong Aadhaar Number then system will display an error message "Invalid LoginId" or som
relevant message i.e "Aadhaar Number is not valid".

1. In case of incorrect OTP, the verification fails and display the relevant message.
1. Beneficary enter Aadhaar Number .
2. Beneficary will receive the OTP i.e "OTP sent to Aadhaar linked mobile number ending with ******XXXX"
3. After OTP verfication then system will display "NO ABHA user registered with this Aadhaar Number".
4. The system should have a provision to create ABHA.

1. Enter Aadhaar Number.

2. Beneficary will receive the OTP i.e "OTP sent to Aadhaar linked mobile number ending with ******XXXX" .
3. After the OTP verfication. If ABHA Number exists then system will display Beneficary ABHA profile details and
can download the ABHA card.
4. If ABHA Profile is not present in HIMS, the system will allow it to be Register and linked in their HIMS benefic
ID or proceed as per bussiness requirement .

1. System may activate the Resend OTP button maximum 2 times after 60 seconds in the OTP not received.

1. Share ABHA Number or ABHA Address

2. Scan fingerprint or face
1. Share ABHA Number or ABHA Address
2. Scan fingerprint or face

1. EMR/HMIS scans the user's ABHA QR code

1. Enter new mobile number

2. Enter OTP
3. Enter Password/ OTP on old mobile number
1. Click on Edit Photo
2. Upload new photo
1. Enter new Email ID
2. Enter OTP
1. Click on re-KYC option
2. Enter OTP received on Aadhaar linked mobile numer

1. Click on Delete/ Deactivate ABHA

2. Enter OTP received on mobile number to confirm deletion/ deactivation
3. Try to login again using the same ABHA

ABHA Number should be validated in the database if already exists before creating a new patient id to avoid tag
of multiple patient id with same ABHA Number.
Kindly Note: This test scenario is applicable for both new and existing beneficiaries and linking will be happens
ABHA creation and verification flow.
1. Log into PHR app.
2. User will scan the QR code which is placed at the facility premises/registration desk.
3. Post scanning, patient profile details are displayed including ABHA number, ABHA address, Name, Gender, DoB, Mobile No
Address. Below this consent language is displayed - "Your consent to the above information to be shared with <HIP Name>. Th
can use this information for your registration and linking your health records" and both "Cancel" / "Share" buttons are provide
4.Check that after clicking on "Share" button, user profile is successfully shared with the HIP and if user click on "Cancel" butto
then user profile is not shared with the HIP.
5. User clicks on share and gets a token number.
6. User clicks on ok and gets token number with validity of 30 minutes.
 Expected Result

User will have an option to create ABHA

User provides consent for sharing of Aadhaar details and creation of ABHA.

System records user consent for compliance with Health Data Management
Policy.
User provides consent for sharing of Aadhaar details and creation of ABHA.

System records user consent for compliance with Health Data Management
Policy.

User is prompted to enter correct Aadhaar Number

In case user enters an invalid Aadhaar number (A valid Aadhaar is a 12-digit

number), the system shows an error message "Aadhaar Number is not valid".

User will be able to enter a valid Aadhaar OTP (A valid Aadhaar OTP is a 6-
digit number).
Example -
Modified text for the "Please enter 6 -digit OTP sent to Aadhaar linked mobile
number " step during the ABHA Creation workflow with “We just sent an OTP
on the Mobile Number *******XXXX linked with Aadhaar. Enter the OTP
below to proceed with ABHA creation".

User will able to send OTP again and verify it

System authenticates the user's Aadhaar through OTP

In case of incorrect OTP, the system displays an error

In case of correct OTP, the system allows the user to proceed
Redirect to the ABHA creation screen.
System verifies the communication mobile number

System should prompt / display the available or suggested ABHA addresses.

System should allow the user to proceed with the enterered ABHA Address.
In case, entered ABHA address is already in use then system should allow the
user to input and proceed with any one of the suggested ABHA address.

User should be able to view the generated ABHA Number and linked ABHA
address

User should be able to view their ABHA Card with all the demographc details
as mentioned in cell H26
User should be able to view card with ABHA number and ABHA address and
the details should be saved in HIMS system and linked with the HIMS unique
beneficary 's ID.g or as per their business requirement.

User will have a choice to create ABHA using Aadhaar Biometrics

User provides consent for sharing of Aadhaar details and creation of ABHA.

System records user consent for compliance with Health Data Management
Policy.

User provides consent for sharing of Aadhaar details and creation of ABHA.

System records user consent for compliance with Health Data Management
Policy.

User is prompted to enter correct Aadhaar Number

In case user enters an invalid Aadhaar number (A valid Aadhaar is a 12-digit

number), the system shows an error message "Aadhaar Number is not
valid".
System authenticates the user's Aadhaar though user's biometrics
In case of incorrect biometrics, the system displays an error
In case of correct biometrics, the system allows the user to proceed

Redirect to the ABHA creation screen.

System verifies the communication mobile number

User should be able to view the generated ABHA Number

User should be able to view their ABHA Card

User should be able to view card with ABHA number and ABHA address and
the details should be saved in HIMS system and linked with the HIMS unique
beneficary 's ID.g or as per their business requirement.

User provides consent for sharing of Aadhaar details and creation of ABHA.

System records user consent for compliance with Health Data Management
Policy.

User provides consent for sharing of Aadhaar details and creation of ABHA.

System records user consent for compliance with Health Data Management
Policy.
User is prompted to enter correct Aadhaar Number

In case user enters an invalid Aadhaar number (A valid Aadhaar is a 12-digit

number), the system shows an error message "Aadhaar Number is not
valid".

1. System authenticates the user's Aadhaar though user's demographic data.

2.The fields for name, date of birth, and gender are set as non-editable, while
the remaining fields can be open for editing i.e (Address, Email , Mobile
Number, State, district , City e.t.c)

User should be able to view the generated ABHA Number

User should be able to view their ABHA Card

User should be able to view card with ABHA number and ABHA address.and
the details should be saved in HIMS system and linked with the HIMS unique
beneficary 's ID.g or as per their business requirement.

User will have a choice to create ABHA using Aadhaar Biometrics

User provides consent for sharing of Aadhaar details and creation of ABHA.

System records user consent for compliance with Health Data Management Policy.

User will be able to enter their Mobile Number

In case of incorrect OTP, the system displays an error
In case of correct OTP, the system allows the user to proceed

System validates user's Driving License / PAN

Document photos are uploaded in the system

Documents are manually verified.

In case the document is valid, the operator approves ABHA creation.

In case the document is invalid, the operator rejects the ABHA creation.

User should be able to view the generated ABHA Number

User should be able to view their ABHA Card and the details should be saved
in HIMS system and linked with the HIMS unique beneficary 's ID.g or as per
their business requirement.

User should be able to view card with ABHA number and ABHA address.

1. In case of correct OTP, the verification is complete and the System can
fetch user's ABHA profile - name, date of birth, gender, mobile number, photo
and address, ABHA Number , ABHA Address and other details from the APIs.
2. In case of incorrect OTP, the verification fails.

3. The fields for name, date of birth, and gender are set as non-editable,
while the remaining fields can be open for editing i.e (Address, Email , Mobile
Number, State, district , City e.t.c)

4. After verification , the details should be saved in HIMS system and linked
with the HIMS unique beneficary 's ID.g or as per their business requirement.

1. In case of correct OTP, the verification is complete and the System can
fetch user's ABHA profile - name, date of birth, gender, mobile number, photo
and address, , state,district, ABHA Number , ABHA Address and other details
from the APIs.

2. In case of incorrect OTP, the verification fails.

3. The fields for name, date of birth, and gender are set as non-editable,
while the remaining fields can be open for editing i.e (Address, Email , Mobile
Number, State, district , City e.t.c)

4. After verification , the details should be saved in HIMS system and linked
with the HIMS unique beneficary 's ID.g or as per their business requirement.
1. In case of correct OTP, the verification is complete and the System can
fetch user's ABHA profile - name, date of birth, gender, mobile number, photo
and address, , state,district,ABHA Number , ABHA Address and other details
from the APIs.
2.In case of incorrect OTP, the verification fails.

2. The fields for name, date of birth, and gender are set as non-editable,
while the remaining fields can be open for editing i.e (Address, Email , Mobile
Number, State, district , City e.t.c)

4. After verification , the details should be saved in HIMS system and linked
with the HIMS unique beneficary 's ID.

1. In case of correct OTP, the verification is complete and the System can
fetch user's ABHA profile - name, date of birth, gender, mobile number, photo
and address,, state,district, ABHA Number , ABHA Address and other details
from the APIs.

2. In case of incorrect OTP, the verification fails.

3. The fields for name, date of birth, and gender are set as non-editable,
while the remaining fields can be open for editing i.e (Address, Email , Mobile
Number, State, district , City e.t.c)

4. After verification , the details should be saved in HIMS system and linked
with the HIMS unique beneficary 's ID.g or as per their business requirement.

Display relevant error messgae.

System will display an error message i.e.

" ABHA Number not found
We did not find any ABHA number linked to this mobile number.
Please use ABHA linked mobile number"
Kindly Note: System should allow to create ABHA option should be
open.
1. Fetching ABHA Details.
2. Register and Linked in their HIMS OR OR benefciary can download the
ABHA card.

Display relevant error messgae.

Display relevant error messgae.

Display relevant error messgae.

Display relevant error messgae.

1. Display ABHA Profile details.

2. Download ABHA Card.
3. Register and linked in their HIMS beneficary's ID or proceed as per
bussiness requirement .

Display relevant error messgae.

In case the biometrics match, the verification is complete and the System
can fetch user's ABHA profile - name, date of birth, gender, mobile number,
photo and address, ABHA Number , ABHA Address and other details from the
APIs.

In case the biometrics do not match, the verification fails.

In case the biometrics match, the verification is complete and the System
can fetch user's ABHA profile - name, date of birth, gender, mobile number,
photo and address, ABHA Number , ABHA Address and other details from the
APIs.

In case the biometrics do not match, the verification fails.

System reads the user information from the ABHA QR code - name, date of
birth, gender, mobile and other details into the system for registration.

Mobile number on ABHA profile is updated

Photo on ABHA profile is updated

Email ID on ABHA profile is updated

KYC details on ABHA profile are updated

ABHA Number should be deleted.

The system should not allow login through the same ABHA

HIMS is able to tag Patient ID with ABHA number.

1. Log into PHR app.
2. User will scan the QR code which is placed at the facility premises/registration desk.
3. Post scanning, patient profile details are displayed including ABHA number, ABHA
address, Name, Gender, DoB, Mobile No and Address. Below this consent language is
displayed - "Your consent to the above information to be shared with <HIP Name>.
They can use this information for your registration and linking your health records" and
both "Cancel" / "Share" buttons are provided.
4.Check that after clicking on "Share" button, user profile is successfully shared with
the HIP and if user click on "Cancel" button then user profile is not shared with the HIP.
5. User clicks on share and gets a token number.
6. User clicks on ok and gets token number with validity of 30 minutes.
 Suggestions for the Functional Tester

Please refer the approved consent language.

Please refer the approved consent language.
Please refer the approved consent language.
Please refer the approved consent language.
Status Remark
 V3 APIs

https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/byAadhaar
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/auth/byAbdm
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/suggestion
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/abha-address
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/byAadhaar
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/auth/byAbdm
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/suggestion
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/abha-address
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/byAadhaar
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3enrollment/auth/byAbdm
https://abhasbx.abdm.gov.in/abha/api/v3/enrollment/enrol/byDocument
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/verify
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card

https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/abha/search
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/abha/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/abha/verify
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/profile/abha-profile
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/profile/abha/phr-card
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/verify
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card

https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/abha/search
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/abha/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/abha/verify
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/profile/abha-profile
https://abhasbx.abdm.gov.in/abha/api/v3/phr/web/login/profile/abha/phr-card

https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/verify
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/verify/user
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/verify
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card

https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/verify
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/abha-card
No API

No APIs

https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/verify

https://abhasbx.abdm.gov.in/abha/api/v3/profile/account
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/verify
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/verify

Delete using Aadhaar OTP OR ABDM OTP

https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/verify

Deactivate using Aadhaar OTP OR ABDM OTP

https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/account/verify

Re-activate using Aadhaar OTP OR ABDM OTP

https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/request/otp
https://abhasbx.abdm.gov.in/abha/api/v3/profile/login/verify/user

NO APIs
https://dev.abdm.gov.in/api/hiecm/patient-share/v3/on-share