Further question based off discussion in this question.
And, now for the whole package. The model that I took the question from is attached to this email. Here's the explanation (question) I've been working through.
The modeler is working on a patient flow model (as attached), where they'd like patients to be transferred between units based on their acuity level and bed availability. Ideally, they would like patients to come to Step 50, and select a unit to go to based on global tables. Then, Step 51 will assign a LOS based on a "T_LOS" table. Step 60 will determine if the patient will leave the system (Step 70) or to be transferred to a new unit based on a newly assigned acuity level (Loop back to Step 50).
Everything works fine until the patient is transferred to a new unit. It seems like the patient gets stuck after being looped back to Step 50, and won't be able to pick up the new assigned LOS in Step 51.
I suggested looping back to Activity 51 instead of 50 for the same reason you suggested. Their response was, "The reason I have to send it to Activity 50 is I need to determine where the patient will go based on their new acuity and location availability. One example could be the patient might downgrade from an ICU unit to a PCU unit, so an available PCU unit would have to be assigned based on room availability in Activity 50. In this case, I am afraid my logic won't work if I loop the patient back to Activity 51.
In the case where I found the patient got stuck, the patient was told to move from L_9MIC to L_9MPC, which is a different unit with enough capacity. The interesting thing is the patient was moved over to L_9MPC (Fulfilled by Activity 50), but a new LOS was never assigned which is supposed to happen in Activity 51. Any thoughts on the potential reasons? capacity-planning3.fsm
