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

[Visit Scheduling] Do not schedule visits from exited programs #1481

Open
Tracked by #1649
mahalakshme opened this issue Aug 26, 2024 · 0 comments
Open
Tracked by #1649

[Visit Scheduling] Do not schedule visits from exited programs #1481

mahalakshme opened this issue Aug 26, 2024 · 0 comments

Comments

@mahalakshme
Copy link
Contributor

mahalakshme commented Aug 26, 2024

Need:

Frequently in 'Visit schedule rule' of cancellation forms we check, if the program is not exited before scheduling.

AC:

  • Should not schedule encounters from an exited program or when an individual is voided.
  • The above case need to be handled when filling any form in both DEA and mobile app
  • Add a point about the above in readme here

Old: ignore

Hence if we auto-cancel the visits, there will be no need for manual visit cancellation as well as checking if program exited in visit schedule rules of cancel forms.

AC:

  • Cancel all the scheduled visits on program exit
  • On undo exit, un-cancel the auto-cancelled visits alone.
  • Manually cancelled visits should not get un-cancelled on undo exit.

Technical:

  • In db, in program_encounter table have a column called auto_cancelled (inline with auto_approved in the entity_approval_status table)
  • Default value for the column need to be false.
  • Update it as true when auto-cancelled because of program exit
  • Update to false on undo exit.

Old: ignore:

  • Approach 1. Do not schedule visits when program exited.

  • Approach 2: cancel all the pending visits - cant do

usecases:

    1. undo exit
    1. cancel all the visist
    1. exited - complete the encounters scheduled

inputs:

autocancelled - uncancelled when unexited
store the what autocancelled

person 1: collected data - register
person 2: exited program filled some info - dead
person 1: want to enter data

find root cause - research -


  • school, phulwari, - bulk exit - 1000 visits - autocancel
  • program exited - schedule an encounter on individual
  • exit, planned visits complete - not required so far - unlikely but possible
    • person 1 - register - enter those data -
    • person 2 - exit - undo - might want to fill the visits
  • sewa rural - want to undo enrolment - continue the visits

Question:

  • How do we distinguish such visits - have a column called auto-cancel(with true and false as values)?
  • from product perspective there is a need to distinguish to be able to write reports as we want
  • may be question to implementation team.

Inputs:

Undo exit.
Single place - edit, cancel, do

@mahalakshme mahalakshme changed the title [Visit Scheduling] Cancel the uncompleted planned visits on program exit [Visit Scheduling] Do not schedule new visits from a exited program Sep 4, 2024
@mahalakshme mahalakshme changed the title [Visit Scheduling] Do not schedule new visits from a exited program [Visit Scheduling] Cancel visits on program exit Sep 20, 2024
@mahalakshme mahalakshme changed the title [Visit Scheduling] Cancel visits on program exit [Visit Scheduling] Do not schedule visits from exited programs Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready
Development

No branches or pull requests

1 participant