HealthID as query param in locker regustration endpoint

Health Locker
#1

Hi Team,
We want to get healthid as parameter in locker registration endpoint, e.g-
current registration endpoint - https://xxx.com/hl/register
we want to upgrade it to -
new registration endpoint - https://xxx.com/hl/register?healthId=:healthId
Please guide us if simply re-registering the endpoint can resolve the issue or else what needs to done, since, we want to auto populate user’s healthId when he lands on application page after selecting our locker from PHR app.

#2

Hey @pragati.varshney,

This won’t work for now, we will discuss this pointer with our team and will try to come up with some solution for this.

Thank You.

#3

Hi Shivanshu,

This won’t work for now, we will discuss this pointer with our team and will try to come up with some solution for this.

Could you please check once more since this is contradictory to what is happening on sandbox already i.e. locker redirection url on PHR app was
https://xxxxqa.dxxxxxxx.com/healthLocker/register?health-id=rishi.1dubey@sbx
while our locker service end point for Registration was -
https://xxxxqa.dxxxxxxx.com/hl/register
So we re-registered the updated endpoint and could successfully get Health ID in url itself.
Now can you please guide us how do we do the same for production environment?

#4

Hey @pragati.varshney,

Is it like you have successfully implemented this on sandbox and you want this change on prod as well?
For prod case, you can mail us your previous endpoint and new endpoint you wishing to move.

Thanks

#5

Hey @Shubhanshu_Shukla
Yeah sort of, so it was like we found that the previous endpoint was updated from PHR app itself that’s when we re-registered it with our locker service.

So, are you saying that we can mail the registration end point for prod if its successfully working on sandbox?