Request for auth token

Hello @mdubey, @sukreet,
Hope you all are doing well.

We have some query regarding Locker Implementation,

  1. In future also user can update locker subscription periods from PHR App.
  2. We observe that if we raise a request for Autherization then we need to raise request for subscription also.
    Can we send only autherization request.
    How CM will know which request is for Autherization and which is for Subscription.
    If user accept the request then Locker have two Subscription ID with valid time frame.

Thanks,

Hi @chitendra,

Could you please explain us a scenario for only auth requests.

Right now we have combination of Auth and Subscription which can be approved for a locker by a patient, as long as there is pair from the same locker.

Hello @mdubey,

The scenario is,
If user subscribe the locker for more than one year, after approval, locker receive token and that token is valid for only one year.
Then after expiry locker needs to raise separate request for token.

Thanks,

Hi @chitendra,

Even though subscription and auth requests are raised at the same time and treated in the combination on the app, from the construct design both are totally independent and do not share properties/attributes. The auth validity is decided by a config which will be set to a longer time for lockers irrespective of the subscription time.

Also in future the plan is to edit the existing auth-request/subscription-request for locker as a renew than providing a new subscription/auth. This is not implemented as of now and is in our backlog.

Let us know if there are more questions.

Thank you

Hai @chitendra please help on NDHM Related apis,
Even we don’t know how its calls

Please give me ur number sir