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 outside the district #1091

Closed
aparnacoronasafe opened this issue May 16, 2021 · 3 comments
Closed

Shifting outside the district #1091

aparnacoronasafe opened this issue May 16, 2021 · 3 comments
Assignees
Labels

Comments

@aparnacoronasafe
Copy link
Member

aparnacoronasafe commented May 16, 2021

Problem Statement

  • MOVING TO FACILITY OUTSIDE CARE NETWORK: We have a lot of patients moving out of the district. the operational process right now is, in the shifting request form, the shifting team will simply mark an INVALID FACILITY as the destination and process the shift. The issue is, the patient stays in the live list of the origin facility since no one pulled the card out. Also, currently, we have no data on how many such patients have chosen to move out of the district.
  • MOVING TO FACILITY IN CARE NETWORK: In certain cases, the shift will be done to a facility outside the district/state, to a facility registered in CARE. Eg: in the case of Lakshadweep moving patients from their hospital to a hospital in Ernakulam. In this case, also, these shifts must be recognised separately so that the district administration can know how many such shifts have happed over time

Proposed solution
The shifting form should have separate flags for INTER-DISTRICT and INTER-STATE shifting. When this Is flagged, the destination field must be made non-mandatory.

Also, in cases where the destination is not mentioned (where the shift happens to a hospital outside the CARE network), once the shift completes, the patient's card must automatically move to the discharge list of the facility.

@stale
Copy link

stale bot commented Oct 12, 2022

Hi, This pr/issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs for 7 more days. Thank you for your contributions.

@nihal467
Copy link
Member

nihal467 commented Aug 2, 2023

@aparnacoronasafe is this issue still relevant

@sainak
Copy link
Member

sainak commented Oct 3, 2023

This will be handled by ohcnetwork/care#895

@sainak sainak closed this as not planned Won't fix, can't repro, duplicate, stale Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

6 participants