-
Notifications
You must be signed in to change notification settings - Fork 299
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
Fix op number constraint for readmitted patients #2147
Conversation
@skks1212 add test for the cases mentioned in the issue |
@skks1212 the PR is not working as expected Test Case Status : failed
Bug
|
PR was incomplete, forgot to label as wip 😅. Fixing now |
@skks1212 the PR is still having bugs, I can create multiple consultation with same IP number for a single patient within a facility |
As per the issue , we are removing Data validation on the OP No. field. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when a patient is discharged, and we reuse the same IP for next patient, it is being accept
Note: When a patient is live, and we try to reuse the IP for a new patient, this error is thrown properly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test case required
…care into op-number-constraint
…onasafe/care into op-number-constraint" This reverts commit cfe9962, reversing changes made to 4e80be9.
…care into op-number-constraint
LGTM |
I still think we need a unique validator across patients, as in two live patients cannot have the same IP/OP number |
Proposed Changes
Merge Checklist
/docs
Only PR's with test cases included and passing lint and test pipelines will be reviewed
@coronasafe/care-backend-maintainers @coronasafe/care-backend-admins