Common Exception Handling

Exception-handling procedures have been set up to address some potential issues that may arise.



Applicant does not have an ID

In a situation where an applicant wants to apply for the SP-MIS scheme but lacks any identification document, the SP-MIS can still process the request by collecting alternative data that uniquely identify the beneficiary such as the applicant's demographic information, as their full name, date of birth, place of birth, mother's and father's names, or any other necessary details required for verification. This information will then be sent to the respective system(s) to conduct a search. The system(s) may request further details to confirm the person's identity after reviewing the search results.

As a result, this process might generate multiple matching records, and the SP-MIS will need to perform additional validation to verify the applicant's identity against the data received from the respective system(s).


Applicant's Record not found in respective system


Applicant's record incomplete in one system

If the applicant's record is received from the registry systems using a Foundational ID or a registry systems-issued certification but contains incomplete or inaccurate information (such as missing date of birth, sex, or inaccurately recorded name), SP-MIS can further cross-reference the applicant ID with other ID systems maintained by the country. These systems, including the Foundational ID system, population registers, social registries, or other trustworthy sources maintained by the country, can offer the required information to complete and verify the applicant's details.


Lack of connecitivity

To proactively react to a lack of connectivity the following measures are proposed:

  • System Redundancy: Implement redundancy measures in the system to ensure uninterrupted service even if the systems experiences downtime. This could involve having backup servers, data replication, or alternative data sources to retrieve essential information.

  • Offline Mode: Develop an offline mode of functionality within the system to allow basic functionalities to continue even without real-time access to registry systems. This may include capturing data locally and syncing with registry systems once it is back online.

  • Manual Verification: Establish a manual verification process as a fallback option when the system is inaccessible. This could involve verifying documents, barcodes, and records manually until the system services are restored.

  • System Monitoring: Implement robust monitoring mechanisms to promptly detect any systematic system issues or downtime.

Last updated