question

Hi @Amy, if I am understanding what you mean by transferring patients, I think you'll want to utilize independent staff tasks. However, instead of a Maintenance Task or using an Inter-Arrival Source (for something like phone calls) like in the tutorial, you can create tokens based on the staff that you want to use as the transfer staff. That way, a token will represent a staff member being used for the transfers, and you can use a General Process Flow (like in the phone call section of the tutorial) to direct those transfer staff members.

I would also suggest learning about Lists if you do now know about them yet. Here is an overview of Lists and here is a tutorial that introduces Lists. But you can add patients to a global list when they are ready to be transferred and pull from that list in the general process flow when telling the transfer staff what patients need to be transferred. You can even use fields in the list for things like origin, destination, transfer time, transportation, etc.

I am including a very simple example model (Healthcare_TransferPatients_Examples_22.1.fsm) for how you might do the very basics of this type of logic. There are two patients flows that are doing the same thing - processing patients, then pushing them to a Global List (different lists being used in each patient flow). And then there are two General Process Flows (named Transfer Patients and Transfer Patients2) that pull from those lists to tell the different transfer staff groups how to handle patients needing to be transferred.

In the Transfer Patients flow, it is just telling each member of the TransferStaff group to transfer one patient at a time. But the Transfer Patients2 flow has the TransferStaff2 group transferring multiple patients at the same time.