-
Type:
Bug
-
Resolution: Done
-
Priority:
Low
-
None
-
Affects Version/s: None
-
AMRIT Sprint 33, AMRIT Sprint 34, AMRIT Sprint 35, AMRIT Sprint 42
-
FLW Mobile App
-
Prod
Expected Behavior- One ABHA ID should be linked to one beneficiary
Current Behavior - In some cases one beneficiary has 2 different ABHA IDs (refer to attached screenshot).
- ABHA ID duplicate issue in the db. Sharing one beneficiaryregid=9078453 for reference.
- For saving the ABHA ID under t_healthid table, providerservicemapid=34 is same for all
- relates to
-
AMM-1609 API related to save and mapping HealthID To Beneficiary id is poor due to network latency
-
- Closed
-
-
AMM-1610 Single ABHA linking with Multiple Beneficiaries
-
- Closed
-
-
AMM-1636 Niramay-II Wrong Providerservicemapid under ABHA table
-
- Closed
-
-
AMM-1637 Niramay-II Beneficiary RegistrationID null under m_benhealthidmapping
-
- Closed
-