NDHM Apis not working after 6 pm

General Query
#1

I am integrating NDHM HIP and HIU Apis in our existing HMIS. But some Important Apis like sending otp sms, Linking patient to hmis, sending consent request doesnt work after 6 pm everyday. Call back hit on our HRP apis from Gateway doesnt occur after this time. Can you please resolve this problem . we get very limited time till 6 pm to integrate and test our integration with NDHM Apis.

#2

I am facing same issue Today. Most of the time I get “Timed out When calling target system” error

#3

Hi @ravish1kazi,

Do you also get the same problem as mentioned by @bhaskar.dabhi? We don’t have anything which should start stopping the requests after 6 PM.

#4

Yes. Same error after 4-5 pm

#5

Please send us the corresponding request id so we can check. Also for how long you have been experiencing this issue.

#6

Currently at this time , on sending consent request “https://dev.ndhm.gov.in/gateway/v0.5/consent-requests/init” we are not getting expected response from ndhm gateway on our hip server link “v0.5/consent-requests/on-init”

Request_id : d744a984-5466-4db1-8dad-af71b1f21b3c

#7

Hi @ravish1kazi,

There is an error in the consent-request call. We will check why you are not receiving any callback.

error=Error(code=UNKNOWN_ERROR_OCCURRED, message=consent.permission.dataEraseAt: Permission expiry must be in future.

#8

Hi @ravish1kazi,

We see our logs and we can see there was a call made to this URL:

https://verratonhealth.com/apisNDHM/v0.5/consent-requests/on-init

At February 17th 2021, 17:42:39.689. Could you please check logs on your side and confirm there was no call at that time.

#9

No record was found in our logs. callback from ndhm gateway got stopped from 5pm onwards

#10

HI @ravish1kazi,

We don’t have any such settings to stop the calls after 5. We tested by calling webhook URLs which is on public internet and we were able to call them y’day night.

#11

Even now at this time, callback https://verratonhealth.com/apisNDHM/v0.5/consent-requests/on-init not getting hit by ndhm gateway

request_id : e3fe3e20-de91-48b2-b79e-be3fcbc14cdb

#12

Hi @ravish1kazi,

Was the above requested accepted by gateway. Did you not receive a 429 with Too many requests found.

This happens when you are sending a old timestamp or a reused request-id. Could you please verify this.

Thanks

#13

Yes using old timestamp. now resolved thanks for help

1 Like