2023-12-12 Developers Deep Dive - CORE-MIS

• Overview

• Minutes

• Questions

• Action items

• Additional Resources

Overview

Date: 2023-12-12

Objective: CORE-MIS requirements initial review

Participants:

• @Artur Lebiedziński

• @Damian Borowiecki

• @Andrea

• @malike

Minutes

1. List of the requirementshttps://docs.google.com/spreadsheets/d/1sEJ2QBiPEO7MX9EnblBM0Cplq9L6mtOv/edit#gid=417237253

2. Example of the epic is created. It will help us to track the features gather under certain module https://openimis.atlassian.net/browse/CM-349

3. Duplicate Flagging:

   1. Backend Definition: Specify in the backend whether a column can be unique or not, considering schema flexibility from the benefit plan program.

   2. Detection Criteria: If a column in the schema is marked as unique, the detection of duplicates involves marking both records if a non-unique value is found.

   3. Deduplication Process: Searches for new and existing records and identifies potential duplicates based on specified criteria.

4. Anonymization of Data:

   1. Masking on Frontend: Select fields to be masked with asterisks on the frontend level for data privacy.

   2. Permission-Based Access: Users with higher permissions can view unmasked data, possibly with confirmation.

   3. Backend Data Storage: Data remains in plain text at the database level.

5. Medium - Recommendation

   1. Referral to Other Programs: Recommends existing individuals who might benefit from other programs.

   2. Program Transfer: Allows individuals to be moved into another program.

   3. Multi-Programming: Supports participation in multiple programs simultaneously.

   4. List of Potentials: Shows a list of potential candidates for recommended programs.

6. Medium - Assessment (Similar to Recommendation):

   1. Application of Changes: Implements changes based on the flagged recommendations from above (flagged individuals) and specified criteria.

   2. Custom Filters: Utilizes a custom filters mechanism for assessment and targeting purposes.

   3. Both 5 and 6 can work in simillar way as is should be in targeting modules (that will be developed in this new phase)

7. Historical Searches for Individuals:

   1. Key Individual in a Group: Identifies a main individual within a group who will receive funds.

8. Person Eligible to Receive Money:

9. Bank Account Provider: Specifies the person providing the bank account and account number. This person might differ from the main individual and should be tagged as special (primary or alternate). Avoids confusion with group status (main household person, etc.). The primary is beneficiary. The different mechanism can be configured. The default primary for groups - it depends. need to be determined.

Action items

• @Piotr Kabelis to verify if there is a maker-checker logic introduced for the inidividual data update

• @Andrea to create list of possible roles within terminology individuals/groups/beneficiaery

See link: https://openimis.atlassian.net/wiki/spaces/coremis/pages/3667361862

Additional resources