In Discovery and Link flow, is it mandatory to send otp to link the care contexts for pateint after discovery

Hi @IntegrationSupport,
In the discovery and link flow, after reading through the documentation and the worflows in youtube,
i got to know that in the link care context phase(after the discovery), HIP needs to send the OTP to the pateint directly( abdm wont send the otp in this case), and validate the otp from the HIP side itself.

Can you confirm that my understanding is correct and also can you help me weather there are any other alternate ways to autehnticate the patient (other than OTP).

And what is the reason to autheticate the patient here ?

@IntegrationSupport @IntegrationSupport @IntegrationSupport @IntegrationSupport can yuo respond here, we were blocked in our integration process here ?

@Phaneendhar123 For M2, HIP initiated linking flow - there are 3 linking and auth modes. Demographic auth, Mobile OTP, Aadhaar OTP. In M2, while linking care context you can implement any 2 of them. Demographic auth is mandate. You can implement mobile otp, when patient will receive OTP for authentication.

@IntegrationSupport, I’m not asking about the HIP initiated Linking, i’m asking about the Discovery and Link flow,

if you can see i’m asking about the Discovery flow, where we start the linking after the discovery, and then from the documentation i got to know that HIP will send the otp to the pateint not the ABDM

can you help us here.


you can see in the selected line, you are mentioning that HIP will send the OTP to the patient and validate that OTP,

@Phaneendhar123 This is a part of HIP initiated discovery and linking in M2 milestone.

@IntegrationSupport, yes, i’m asking about the same, does HIP needs to handle the otp sending and verifying here ?

@IntegrationSupport @IntegrationSupport, can you help us here ?