User profile detail

Consent Manager and Gateway
#1

Hi @IntegrationSupport @SARCH1

As you are aware, at DRiefcase, we have been doing a lot of work on the Scan & Share. In our experience, we have seen that patients typically prefer mobile based registration (ABHA Address) and avoid giving Aadhaar.

The same behaviour is seen in smaller hospitals and clinics. So typically ABHA Address get created first and then it can be verified using Aadhaar later.

An issue we have seen come up is that once the KYC verification is done the profile details of the patient are overwritten with Aadhaar data. However the same is not communicated to the HIPs where the ABHA Address was verified pre-KYC. This results in failure of the demo-mode linking of health records.

Can we look at a scenario wherein ABDM gateway informs HIPs (where ABHA Address has been verified) about the new demographic details once the KYC has got done. The HIP can then decide to handle it the way it wants.

Thanks

#2

@Hemant
Hi, as discussed on our telecon, we will revert to you on this.

Please note that ABHA number and ABHA address have been de-coupled and ABHA address is being created using mobile number where the user may identify himself/herself with another name. Hence, it is recommended that EKYC be done and ABHA number be created. User can then proceed to link the abha address with abha number.