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

district admin can't mark a Shifting Patient status as complete #5373

Closed
nihal467 opened this issue Apr 23, 2023 · 4 comments · Fixed by ohcnetwork/care#1268
Closed

district admin can't mark a Shifting Patient status as complete #5373

nihal467 opened this issue Apr 23, 2023 · 4 comments · Fixed by ohcnetwork/care#1268
Assignees
Labels
P1 breaking issue or vital feature urgent

Comments

@nihal467
Copy link
Member

Describe the bug

Currently, an origin facility staff can only mark a shifting patient status to complete, if the destination hospital is a facility already registered in care and no other user type is having the access to do it (District admin and above)

Note: If we are sending a patient to a facility outside care, the bug won't happen to the district admin and above

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

image

@aparnacoronasafe
Copy link
Member

aparnacoronasafe commented Apr 24, 2023

This is a Bug.

The preferred behavior is,

  1. WHEN DESTINATION hospital is in CARE
    Here the staff of the destination and origin facility must be able to complete a shift.

  2. WHEN DESTINATION hospital is OUTSIDE CARE
    the staff from the origin facility MUST be able to mark a shift as complete

The district admin and above should have access to do all the above.

Please make the necessary changes

@nihal467 nihal467 removed the blocked label Apr 24, 2023
@nihal467 nihal467 added urgent P1 breaking issue or vital feature labels Apr 24, 2023
@github-actions
Copy link

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.

@aparnacoronasafe
Copy link
Member

@cp-Coder please note that I have changed the issue to have both user linked to of the destination and origin facility move shifting to complete for shifts with destination facility in CARE.

@aparnacoronasafe
Copy link
Member

Issue overlapping with #5385 and #5389

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 urgent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants