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

Shifting Kanban- editing the process #5302

Closed
aparnacoronasafe opened this issue Apr 10, 2023 · 3 comments · Fixed by coronasafe/care#1263
Closed

Shifting Kanban- editing the process #5302

aparnacoronasafe opened this issue Apr 10, 2023 · 3 comments · Fixed by coronasafe/care#1263
Assignees
Labels
P1 breaking issue or vital feature shifting

Comments

@aparnacoronasafe
Copy link
Member

aparnacoronasafe commented Apr 10, 2023

Simplifying the shifting flow to have the following steps: These steps will reflect as lists in the Shifting Kanban Board.

  1. Shifting approval pending: List Only visible in "war-time configuration" Changes to shifting form #5300
  2. Patients to be shifted: All shifting requests in peacetime configuration will appear in this list. in war-time configuration only the shifting requests approved by the shifting approval facility will move from 'Shifting approval pending' into 'Patients to be shifted'
  3. Destination confirmed All shifting requests where the destination is confirmed will appear here. Any staff from the origin facility/ destination facility can approve the destination
  4. Transport arranged- any staff from the origin facility can mark this
  5. Patient in transit- any staff from the origin facility can mark this
  6. Transfer complete- Any staff from the destination facility can mark the shift as complete. Marking the shift as complete will automatically discharge the patient from the origin facility and move the card to the destination facility. At the origin facility, the discharge details will be auto-saved as a reason for discharge- referred, Date of discharge- present date. In case the destination hospital is one outside the CARE Network, the patient file gets discharged with the reason for discharge- referred, Date of discharge- present date.
  7. Shift request canceled- any staff from the origin facility can mark this
  8. Patient expired- any staff from the origin facility can mark this. Redirect to Discharge from CARE pop-up window, with the reason for discharge "death" must come auto-populated and must not be editable.

These steps must reflect in the lists in the shifting Kanban (https://care.coronasafe.in/shifting) as well as the Status dropdown in the update shifting request form (https://care.coronasafe.in/shifting/c10203c6-a382-4ffc-ab11-e416fb44c07e/update)

@gigincg to approve

@aparnacoronasafe aparnacoronasafe added P1 breaking issue or vital feature shifting labels Apr 10, 2023
@github-actions
Copy link

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

@gigincg
Copy link
Member

gigincg commented Apr 13, 2023

@aparnacoronasafe With all these changes, do you expect wartime approvals to work correctly too?

@aparnacoronasafe
Copy link
Member Author

Yes.

War- time will have only 2 difference from peace time configuration.

  1. 1 additional feature of shifting approval authority (control room) approval. Keeping that as the first steps further simplifies the flow. In peace-time configuration, the flow will start from step two.

  2. the destination approval can be done in peace mode by anyone. In war mode, it needs to be restricted to staff from destination hospital or shifting approval authority.

If we can have these two setting coded in such a way that is easily switchable, that would be ideal

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

Successfully merging a pull request may close this issue.

2 participants