API related to save and mapping HealthID To Beneficiary id is poor due to network latency

XMLWordPrintable

    • Type: Bug
    • Resolution: Done
    • Priority: Highest
    • 3.2.0
    • Affects Version/s: None
    • AMRIT Sprint 39, AMRIT Sprint 42
    • FLW Mobile App
    • Prod

      There is a ABHA count mismatch between ABDM dashboard and AMRIT report,
      Suspected reasons:
      ABHA is created using native ABDM APIs and after that ABHA is saved in the AMRIT by calling an AMRIT API, may be API poor performance due to network latency in the field sometimes or most of the times this AMRIT API might be failing.

      Steps to Reproduce:
      Open FLW App on mobile or Tab device .
      Login and navigate to "Create ABHA" screen
      Expected Result:
      User should able to Create ABHA and send ABHA to saved in the AMRIT
      Actual Result:
      Sometimes created ABHA numbers are Not saving in AMRIT
      Note:
      This is the API to link Beneficiary id with ABHA and save to AMRIT:
      fhirapi-v1.0/healthIDRecord/mapHealthIDToBeneficiary
      This API needs to be optimized to respond quickly in the poor network areas.

        1. mapHealthId Performace.png
          mapHealthId Performace.png
          107 kB
        2. Screenshot from 2025-06-19 22-41-08.png
          Screenshot from 2025-06-19 22-41-08.png
          278 kB
        3. Screenshot from 2025-06-19 22-44-27.png
          Screenshot from 2025-06-19 22-44-27.png
          254 kB

              Assignee:
              Nikhil Ananda Fegade
              Reporter:
              Madhava Ramu N
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: