KEMBAR78
ABDM Functionality Checklist - M2 | PDF | Cyberspace | Internet
0% found this document useful (0 votes)
31 views3 pages

ABDM Functionality Checklist - M2

The document outlines the testing requirements for the ABHA functionality in the ABDM system, focusing on health record creation, linking, and notification processes. It details the expected outcomes for both HIP-initiated and user-initiated health record linking, including the need for demographic details and successful OTP verification. Additionally, it emphasizes the importance of FHIR format for health records and their visibility in the sandbox PHR app.

Uploaded by

6hlh0led8l
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
0% found this document useful (0 votes)
31 views3 pages

ABDM Functionality Checklist - M2

The document outlines the testing requirements for the ABHA functionality in the ABDM system, focusing on health record creation, linking, and notification processes. It details the expected outcomes for both HIP-initiated and user-initiated health record linking, including the need for demographic details and successful OTP verification. Additionally, it emphasizes the importance of FHIR format for health records and their visibility in the sandbox PHR app.

Uploaded by

6hlh0led8l
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/ 3

Note : The ABDM SERVER URL SHOULD NOT BE CALLED FROM UI.

Client Name
Date
Test Case
ABHA Functionality (to be checked during functional testing)
Milestone - 2 Sumasoft
Status Remarks
Health Record Creation ABDM mandates only the sharing of digital health record in
FHIR format. Expected result is generation of digital health
record.
From the below HI types, all 8 of health records should be
created by health facility:
https://sandbox.abdm.gov.in/sandbox/v3/new-documentation?
doc=HealthRecordFormats
HIP Initiated Health Record In the application the Health records generation functionality
Linking Using Demographic Auth should present.
The UI should present for the Health records creation in the
Application
In the application, the application user should able to create all
eight types of health records from the below health record types
OF Consultation, Prescription, DischargeSummary,
DiagnosticReport,
ImmunizationRecord, HealthDocumentRecord, WellnessRecord,
Invioice Record
Demographic details of the patient should be reflected while you
link the patient (Name,ABha Address,Abha Number,Dob,
Gender,Mobile Number)
The new health records should be linked to the ABHA of patient.
The successfully
linked health records should be visible in the sandbox phr app.
The time visibled on the HMIS should me matched with the time
displayed in PHR and attachment
The care context linked and data linked to ABHA notifications
should received in Sandbox PHR app.
Sending Notification for deep link If the health record is created for non abha patient then HIP
workflow should notify HIE-CM .
Patient will receive an SMS from ABDM on mobile number
which is registered in health facility
User Initiated Health Record The discovery and linking flow should work in sandbox PHR app
Linking When patient searches the name of HIP in the linked facility
section in the sandbox PHR
app the HIP should be visible in the list
After selecting the HIP name and clicking on the fetch records
button the unlinked
records should be visible in the sandbox PHR app
After selecting the records from the list the user will clicks on link
selected button the
OTP screen should visible and here the patient should receive
the OTP via SMS from
the HIP
On the Otp screen patients registered mobile number should be
visible
If patient will enters valid OTP the success message will show in
the sandbox PHR app,
Records linked successfully. The successfully linked records
should be visible under the
HIP name's linked facility section in sandbox PHR app.
If patient will enters invalid OTP the invalid OTP message will
show in the sandbox PHR
app, The records should not linked to patient abha. The records
should not be visible
under the HIP name's linked facility section in sandbox PHR
app.
The care context linked and data linked to ABHA notifications
should received in Sandbox PHR app.
After pulling the records, The records should be visible in the
structured format.
After being linked, the record must be visible in their HIMS
along with the ABHA Address and ABHA Number.
Data transfer and visible in The health facility will transfer health records in FHIR
sandbox PHR app format(Structured and Unstructured). The transferred
health records in FHIR format should be visible in the
sandbox PHR app
After successful linking please display the list of linked &
unlinked records in the aplication
The data visibled in PHR should be in strctured as well as
unstrcutured format
On the attachment(report) all the demographics details should
be visible along with ABHA number, ABHA address

1. All the paramters available on nrces website for respective


Note: bundles should be visibled in PHR as per your business usecase

You might also like