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

Beds can have conflicting records across patients #6161

Closed
Ashesh3 opened this issue Aug 25, 2023 · 2 comments · Fixed by coronasafe/care#1577
Closed

Beds can have conflicting records across patients #6161

Ashesh3 opened this issue Aug 25, 2023 · 2 comments · Fixed by coronasafe/care#1577
Assignees
Labels
P1 breaking issue or vital feature stale

Comments

@Ashesh3
Copy link
Member

Ashesh3 commented Aug 25, 2023

Describe the bug
When a bed is assigned to a patient for a duration of time, it is considered in-use by that patient for that amount of time. The issue is that the same bed can be assigned to another patient in between the time it was assigned to the previous patient. Suppose you assign BED1 to Patient1 from 1pm to 3pm. You are also able to assign the same BED1 to another patient, say, Paitent2 for a conflicting time range, say 2pm to 2:30pm.

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://care.coronasafe.in/patients?facility=10c66ed2-5b95-4649-bd2f-f5766334e1cd&page=1&limit=12&emergency_phone_number=
  2. Click on the first patient
  3. Assign a bed to that patient
  4. Wait 10 minutes
  5. Unassign the bed from the patient (by assigning a new bed to that patient)
  6. Click on the second patient
  7. Assign the bed which was assigned previously to the first patient with a start time which falls in between the time range between when the bed was in use already.
  8. It allows us to create the conflicting record

Screenshots
Patient 1:
image

Patient 2:
image

Expected behavior
It should show an error and disallow such conflicting entries to be created.

@nihal467 nihal467 added the P1 breaking issue or vital feature label Aug 29, 2023
@github-actions
Copy link

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.
@sainak kindly acknowledge this message by commenting 'Acknowledged' below.

@github-actions
Copy link

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 breaking issue or vital feature stale
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants