Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplication Solution - Duplicate Patient Registration Warning #1270

Open
Diama1 opened this issue Aug 7, 2024 · 2 comments
Open

Duplication Solution - Duplicate Patient Registration Warning #1270

Diama1 opened this issue Aug 7, 2024 · 2 comments
Assignees

Comments

@Diama1
Copy link
Collaborator

Diama1 commented Aug 7, 2024

Issue

When a user is registering a patient who has the same date of birth or ID number and resides in the same village as an existing patient, they should be alerted about the potential duplicate. The warning message will include the name and parent of the existing patient, along with the reason for the suspicion (matching date of birth or ID number and same village).

Screenshot from 2024-08-07 09-36-37

Todo

  • Create the screen as per designs.
  • Implement the logic for detecting potential duplicate patients.
@anvmn
Copy link
Collaborator

anvmn commented Dec 1, 2024

@Diama1

a patient who has the same date of birth or ID number and resides in the same village as an existing patient

Since national ID number is unique (it is, right?), I don't see the need to make a check for village. If we find existing patient with same national ID, we will present the warning.
Also, I don't really see how date of birth can be used here, since theoretically, there can be several patients from same village born on same day (twins, for example).

So, as I see it, only parameter checked here needs to be national ID.

@anvmn
Copy link
Collaborator

anvmn commented Dec 1, 2024

@adamhstewart

Implemented #1380 based on #1270 (comment).
Tell me if changes are required.

@anvmn anvmn moved this from In progress to Ready for Review in E-Heza Development Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Review
Development

No branches or pull requests

3 participants