USCT-01-Data-Verification-And-Validation

Owned by Damian Borowiecki
Last updated: Oct 30, 2023 by Ingmar Vali
10 min read

 

Use Case Step

USE CASE: Unconditional Social Cash Transfer

STEP: Data Validation

TYPE: Manual data verification and validation

https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/YLLEfCKTnmzAMDSDzJJH/readme/inst-1-unconditional-social-cash-transfer

Preconditions

(list of conditions that MUST be met in order to be able to successfully execute this process)

  1. Records of potential beneficiaries stored and accessible by the Social Welfare Ministry managers.

  2. Social Welfare Ministry managers are authenticated users and have rights to access digital registries entries.

  3. All necessary building blocks and workflows have been set up.

  4. Potential Beneficiaries are registered in the USCT programme.

  5. Potential Beneficiaries have consented to be processes in the USCT programme.

  6. The rules by which the potential beneficiaries will be validated against are already properly described

  7. The data analysis model is ready and integrated with the Data Analysis Building Block [not yet implemented].

Data inputs

Beneficiary 

  • First Name 

  • Second Name 

  • DOB 

  • National ID Number 

  • Place of residence

  • Contact info:

    • Email 

    • Phone Number 

    • Address

  • Eligibility criteria [Data required for making decisions on enrollment, e.g. with using Proxy Means Test, can vary between countries]

    • number of children

    • marital status

    • type of settlement [town, village, etc.]

    • employment status

Workflow Process

  • Name

  • Type

  • Version

  • Description

  • Process Body

    • Implementation

Actors

(the people, organization, computer systems - hardware and software, and building blocks that participate in the activity)

System

  • Consent Management BB

  • Information Mediator BB

  • Identity BB

  • Digital Registries BB

  • Client Case Management BB [not yet defined].

  • Identification and Authentication BB [not yet defined].

  • Analytics and Business BB [not yet defined].

  • Artificial Inteligence BB [not yet defined].

  • Reporting and Dashboards BB [not yet defined].

External system

  • SRIS

Human

  • Central level Social Welfare Ministry managers

  • Beneficiary

Normal Course (what happens if the event is triggered and the preconditions have been met)

Description

Central level Social Welfare Ministry managers verify if the data provided in the Registration Step USCT-01-Registration is elligible for the program and cross examine it using external systems, like governmental DBs, and fill in all the missing gaps.

Provided that

The central level Social Welfare Ministry managers have access SRIS and are able to retrieve data of potential beneficiaries from the Digital Registries BB in order to validate and verify data.

Step 1: Social Welfare Ministry Manager accesses beneficiary records

Description: Social Welfare Ministry manager can access the Social Registry Information System (SRIS) to retrieve in bulk identification records and eligibility information of potential beneficiaries that registered and consented to the given Social Programme (in this case Unconditional Social Cash Transfer).

Feature: Access to Registry Records Scenario: Retrieve beneficiary records from Digital Registry BB via SRIS Given that the Social Welfare Ministry manager is authenticated in the Identity BB When Social Welfare Ministry manager requests access to potential beneficiaries data from Digital Registires BB through SRIS And the potential beneficiaries have signed a consent agreement to be notified Then the identification records and eligibility information of potential beneficiaries are retrieved

Relevant Identity BB endpoints:

  • /authorize

    • Authorizes managers in designated platform

Relevant Digital Registries BB endpoints:

  • /data/{registryname}/{versionnumber}

    • Access the list of beneficiaries for data validation

Relevant Consent BB endpoints:

  • /service/agreement/{agreementId}/

    • Confirm that potential beneficiary has signed the agreement and can be notified about the program

 

Step 2: Social Welfare Ministry Manager reviews records

Based on the data retrieved in Step 2, managers can review entries. The question remains should it be done in SRIS app or on downloaded dataset .

Step 2.1 Prepare verification workflow

Description: Social worker creates new workflow, that use validation rules for detecting invalid/unverified records.

Feature: Create new workflow Scenario: Create workflow that verifies resources using Digital Registry BB data Given Social Worker can create workflows And Workflow is connected to the Digital Registry BB And rule engine/model to verify potential beneficiaries is ready When Social Worker creates new workflow Then New workflow is created And Potential beneficiaries data can be verified And Potential beneficiaries whose data is invalid or unverified can be identified And Social Welfare Manager is sent a message about the results

Relevant Digital Registries BB endpoints:

  • /data/{registryname}/{versionnumber}

    • Access the list of individuals for scoring.

Relevant Workflow BB endpoints:

  • /processes (post)

    • Create new workflow

Relevant Scheduler BB endpoints:

  • /message/new

    • A message about finished workflow and its results is send

Step 2.2 A Trigger automatic data verification and authentication

This step could use Business Data Analysis BB and AI BB, however at the moment’s they’re not defined. It is assumed that the logic used for data verification was implemented in the workflow.

Description: Social Welfare manager triggers workflow created in previous step.

Feature: Automatic potential beneficiary data validation and verification Scenario: Social Welfare Manager executes workflow for validating and verifing data Given that a workflow for data validation has ben created And Social Welfare Manager can trigger the workflow And Social Welfare has a defined list of the beneficiaries When Social Welfare Manager executes workflow for the beneficiaries on the list And potential beneficiaries signed consent Then every beneficiary data is validated and verified And beneficiaries that didn't pass the validation/verification are flagged And Social Welfare Manager is sent a message with the results

Relevant Workflow BB endpoints:

  • /processes/{processId}/start

    • Trigger Data Validation Process

Relevant Digital Registries BB endpoints:

  • /data/{registryname}/{versionnumber}/update

    • Flag beneficiaries as requiring data update

Relevant Scheduler BB endpoints:

  • /message/new

    • A message about finished workflow and its results is send

Step 2.2 B Manual Cross-Reference and Verify Records

Description: This is an alternative version of the previous step where no automation was added and Social Welfare Manager cross-references the records with multiple registry sources. Looks for gaps or overlaps in the data, comparing information such as names, addresses, identification numbers, etc.

Relevant Digital Registries BB endpoints:

  • /data/{registryname}/{versionnumber}

    • Access multiple registries to gather data about beneficiaries.

  • /data/{registryname}/{versionnumber}/update

    • Flag beneficiaries as requiring data update

 

Step 3: Social Welfare Ministry Manager fills in the missing gaps

Description: For the potential beneficiaries that were flagged for not passing the validation, managers fill in missing gaps in the records. This could involve contacting potential beneficiaries for further information or accessing other sources of data. Updated data is stored back in the SRIS via Digital Registries BB.

Relevant Digital Registries BB endpoints

  • /data/{registryname}/{versionnumber}/update

    • Used to update data flagged as not validated / verified

 

Step 4: Social Welfare Ministry Manager validates collected information

Description: We’re once again checking if issues with beneficiary data are resolved and reiterate if necessary. Once all records are verified, validated, and authenticated, the managers confirm the completion of the process. This could involve:

  • Updating a status in the Digital Registry BB

  • Sending a notification to other actors

  • other activities.

This step can be executed using Workflow BB, social worker can use existing workflow to once again validate data.

Relevant Workflow BB endpoints:

  • /processes/{processId}/start

    • Trigger step completion workflow

  • /instances/{instanceId}

    • Confirm that process was done successfully

 

Alternative Course

(links to other use cases in case there are different ways how to solve the same use case)

[TBA]

Data output

  1. Report of data quality and completeness (Analytics and BI BB / Reporting and Dashboards) [not yet defined BBs].

  2. Identified discrepancies and gaps in the data (Digital Registries BB).

  3. Updated and validated SRIS data (Digital Registries BB).

Post-Conditions (the success criteria)

  1. The information of potential beneficiaries in the SRIS are verified and validated.

  2. All records in the SRIS are validated and approved by managers

  3. A detailed report is available for stakeholders, documenting the process and its results. [Require Analytics and Reporting]

Exceptions

(error situations)

  1. SRIS is not accessible, the process cannot be executed.

  2. No consent from beneficiaries

  3. Beneficiaries who cannot be contacted or reached for data updates

  4. Errors in workflow process

Related BBs

(working groups related to this implementation example)

Digital Registries BB

Workflow BB

Information Mediator BB

Registration BB

Sequence Diagram

sequenceDiagram

participant SWM as Social Welfare Ministry Manager

participant IDBB as Identity BB

participant SRIS as SRIS

participant DRBB as Digital Registries BB

participant CBB as Consent BB

participant WBB as Workflow BB

participant SBB as Scheduler BB

participant BF as Potential Beneficiary

Note over SWM: Step 1: Access to beneficiary records

activate SWM

SWM->>SRIS: Enter authentication data

activate SRIS

SRIS->>IDBB: Send authentication data

activate IDBB

IDBB->>SRIS:Return Auth Token and Functional ID

deactivate IDBB

SRIS->>SWM: Authenticate user in the app

SWM->>SRIS: Request a list of all potential beneficiaries

SRIS->>DRBB: Send request to access all beneficiaries data

activate DRBB

loop for each beneficiary

DRBB->>CBB: Check consent agreement

activate CBB

CBB-->>DRBB: Confirm consent agreement

end

deactivate CBB

DRBB-->>SRIS: Return beneficiaries list

deactivate DRBB

SRIS->>SWM: Access potential beneficiaries list with all their data

deactivate SRIS

deactivate SWM

Note over SWM: Step 2: Review beneficiary records

Note right of SWM: Step 2.1: Create validation workflow

opt Data Validation workflow doesn't exist

activate SWM

SWM->>WBB: Create data validation workflow for beneficiaries

activate WBB

WBB-->>DRBB: Validate Digital Registry BB connection

activate DRBB

deactivate DRBB

Note over WBB: Apply a rule engine for data verification

WBB->>SWM: Confirm new workflow created

deactivate WBB

end

SWM->>WBB: Trigger data validation process

deactivate SWM

activate WBB

loop Each potential beneficiary

WBB->>DRBB: Validate and verify beneficiary data

activate DRBB

alt Data Invalid

WBB->>DRBB: Flag data as requiring update

end

deactivate DRBB

end

WBB->>SBB: Trigger new message about finished verification

activate SBB

deactivate WBB

SBB->>SWM: Message is sent with verification results

activate SWM

deactivate SBB

deactivate SWM

Note right of SWM: Step 2.2: Trigger automatic workflow or cross-referance manually

alt Automatic workflow is implemented

SWM->>WBB: Trigger automatic workflow

activate SWM

activate WBB

SBB->>SWM: Message with the results is send

deactivate WBB

deactivate SWM

else Manual cross-reference is implemented

SWM->>DRBB: Request potential beneficiaries records

activate SWM

activate DRBB

DRBB-->>SWM: Return aggregated beneficiary data

SWM->>DRBB: Cross-reference beneficiary data

DRBB->>SWM: Show which beneficiares were validated successfully and which not

deactivate DRBB

deactivate SWM

end

Note over SWM: Step 3: Fill in the missing gaps for potential beneficiaries

opt Get missing information from beneficiary

SWM->>BF: Get missing information

activate SWM

activate BF

BF-->>SWM: Return missing information

deactivate BF

SWM->>DRBB: Update missing information

activate DRBB

DRBB->>SRIS: Show updated information

activate SRIS

end

Note over SWM: Step 4: Validate updated information

SWM->>DRBB: Request updated potential beneficiaries records

DRBB-->>SWM: Return updated potential beneficiaries records

SWM->>DRBB: Confirm data update for each record

deactivate DRBB

deactivate SWM

 

 

Links to Code