-
Type:
Bug
-
Resolution: Done
-
Priority:
Blocker
-
None
-
Affects Version/s: None
-
AMRIT Sprint 44
-
HWC Mobile App
-
UAT
shashank.k@piramalswasthya.org karyamsetty.grace@piramalswasthya.org
Earlier API were responding with -
API Details -
https://uatamrit.piramalswasthya.org/fhir-api/careContext/generateOTPForCareContext
Request -
{"healthID":"91713747173076@sbx","healthIdNumber":"91-7137-4717-3076","abdmFacilityId":"PIRSWASTH_953256","abdmFacilityName":"Piramal Swasthya"}
Response -
{"data":{},"statusCode":200,"errorMessage":"Success","status":"Success"}
Note - In response - "data" should be bringing "txnId", but it is not present.
And API was taking 30 sec -
<-- 200 https://uatamrit.piramalswasthya.org/fhir-api/careContext/generateOTPForCareContext (30785ms)
Same issue is in web also, I am attaching screenshots
Now I checked, same API is responding -

<-- 200 https://uatamrit.piramalswasthya.org/fhir-api/careContext/generateOTPForCareContext (3316ms)
- blocks
-
MHWC-83 Integrate ABDM M2 Functionality into the AAM Mobile App
-
- Closed
-