Duplicate residents are one of the most hardest thing to manage in BeGIn. Since there are different of data endpoint (web registration, barangay enumerators and vaccination hub), where residents are encoded, it is no surprise that there will be duplicates among your records.

To minimize this impact, the resident entry from will now enforce duplicate checking for the first name, last name, birth date and gender of the current item being recorded before it is committed to the database.

Let's take a look at an example. Here you see an existing resident with the following details:
First name = Joselito
Last name = Manuel
Birth Date = 5/8/1990
Gender = Male

If we try to encode a resident with the exact same details:

You will get the following error:

You will need to do a thorough search in to verify the already recorded entry. To do this you can simple type in the details into the filter bar:


Now you can simply edit the resident and change the necessary information.

Happy coding!