Getting Success message instead of OTP Screen in PHR Mobile APP

HIP Implementation
#1

In Discovery flow after discover care-contexts when i click on Link Selected I am getting message saying ‘Success’. But where the user will enter OTP in PHR application, I am not able to find any screen there. links/link/on-init API is returning 202 status code but PHR apps show message saying ‘Success’.

init Request :
{“requestId”:“41d09654-1cad-41d0-a47a-80b514a719cc”,“timestamp”:“2022-08-24T04:23:03.015537”,“transactionId”:“12058989-9015-41ee-877e-7437cd7f2dde”,“patient”:{“id”:“91735176185842@sbx”,“referenceNumber”:“91735176185842@sbx”,“careContexts”:[]}}

on-init call back Response:
{“requestId”:“fb05f461-6282-4314-b75d-225f816f7830”,“timestamp”:“2022-08-24T04:22:19.19”,“transactionId”:“12058989-9015-41ee-877e-7437cd7f2dde”,“link”:{“referenceNumber”:“91735176185842@sbx”,“authenticationType”:“DIRECT”,“meta”:{“communicationMedium”:“MOBILE”,“communicationHint”:“91735176185842@sbx”,“communicationExpiry”:“2022-08-24T04:32:19.19”}},“error”:{“code”:“1000”,“message”:“Success”},“resp”:{“requestId”:“41d09654-1cad-41d0-a47a-80b514a719cc”}}

image
image351×715 49.5 KB

image
image359×720 37.5 KB

image
image352×723 38.3 KB

#2

@pramodk Please see this video and share short video of this process.

https://lntinfotech-my.sharepoint.com/:v:/r/personal/atik_lntinfotech_com/Documents/Microsoft%20Teams%20Chat%20Files/video-20220824-110420-82ba2fda.mov?csf=1&web=1&e=ZPcF5w

#3

Please find the below video link of the process

#4

Hi @Sravani1
I did debug this issue in Sandbox PHR App. Following API success response have a parameter value is null that parameter should not be null in the case of success response.

That particular parameter key and value is “careContexts”:null

**API Request : ** GET https://dev.ndhm.gov.in/cm/patients/links

Response : {“patient”:{“id”:“ganapathyp85@sbx”,“links”:[{“hip”:{“id”:“DigiLocker_HIP”,“name”:“DigiLocker”,“type”:“HIP”},“referenceNumber”:null,“display”:null,“careContexts”:null}]}}

Please contact (HIECM) Backend API team for this issue.

Thanks

#5

Hey @pramodk,

As discussed, wrong response for API links/link/init was being provided at your end which is diagnosed and closed at the same time.

Thanks