First available location not reevaluated

Question

question

Dash Ballarta asked Oct 18 2016 at 4:37 PM Matthew Gillespie commented Oct 20 2016 at 4:51 PM

First available location not reevaluated

HI, just wondering if you could help me troubleshoot my clinic model.

I have three PCIs and they are supposed to go to a waiting area. They leave upon first availabilty of either exam tables or radiology tables.

Two of my PCIs are getting stuck in the waiting area and do no proceed further, although their activity should re-evaluate the availabiilty of tables.

Additionally, my wait times in my dashboard generate an error when i run them - however, this may be related to the above.

fsm is at the following link:

https://utexas.box.com/s/w04d80s2zr7j5pgejouxknekuzkax0gx

Thanks,

Dash

Software Version:

FlexSim HC 5.1.0

healthcare decision gridlock first available location reevaluate availability

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2016-10-18T18:44:25Z

Matthew Gillespie answered Oct 18 2016 at 6:44 PM Matthew Gillespie commented Oct 20 2016 at 4:51 PM

Dash,

There are a few issues here. I've attached a simplified version of your model to help point them out. When you run the model you'll see that the first set of three patients go through their activities correctly. However, when the next set of three arrive, two of them get stuck in the waiting room. This is because the decide activity starts the ToWaitingRoom activity on the patients if neither area is available at that time. The patients are then stuck forever trying to go to the waiting room because they're already there. Running the model some more shows the other issue. When the group of 5 shows up, 2 of them go to a bed and 2 of them go to a CT. However, they're gridlocked once they finish their processing time. The bed patients are waiting for the CT patients to leave and the CT patients are waiting for the bed patients to leave.

I've attached a modified version of that model that doesn't have these issues. In activity 20, I use the Based on Destination Status pickoption to send the patients to the first available location. The processing time uses the Based on patient's location pickoption so you can have different processing times based on the area. I added a Activity Finished trigger that sets the "nextArea" label on the patient to be the other area (whichever one the patient still needs to go to). Activity 40 then tells the patient to go to the area recorded on that "nextArea" label. Activity 30 is a decide that checks to see if the next area is available and starts activity 40 if it is, otherwise it starts activity 31 that sends the patient to the waiting room and then activity 40 will start.

stuckpatients.fsm (119.0 KiB)

stuckpatientssolution.fsm (125.1 KiB)

· 5

Dash Ballarta commented · Oct 19 2016 at 7:47 PM

Matt,

Thanks for this, I wouldn't have thought to structure the logic this way. It works great the way you demonstrated.

As I iterate this model, I do notice that as my queue grows, patients are evaluated on a "last in, first out" basis (e.g., ID8 will end up waiting all day, while ID23 will come in and get throughput). Is there something I can do to have these patients evaluated by priority (that being wait time?).

Dash

0 ·

Matthew Gillespie ♦♦ Dash Ballarta commented · Oct 19 2016 at 9:03 PM

This behavior is determined by the Entrance Criteria of the object. The default entrance criteria sorts the patients first by acuity, and then by waiting time, so I doubt you're queue is really LIFO unless you're using a custom entrance criteria.

If you want patients who've been to one of the two areas already to be prioritized above patients who haven't been to one yet (or vice-versa) you can change the entrance criteria of each object to use a custom configurable entrance criteria.

0 ·

Dash Ballarta commented · Oct 20 2016 at 1:54 PM

Hi Matt, you are correct in that the waiting areas are still evaluating via acuity and total wait time. However, I'm still getting some stragglers that somehow get missed from being evaluated.

mskloiterers.png

The throughput of patients is what i expect it to be for this model, but these folks never get seen - maybe due full beds at the time they get evaluated for rooms?

Dash

msk1.fsm

0 ·

mskloiterers.png (625.2 KiB)

msk1.fsm (6.3 MiB)

Matthew Gillespie ♦♦ Dash Ballarta commented · Oct 20 2016 at 4:48 PM

You just need to update your flowchart. There's no connection between the MSKExamTableArea and the WaitingAreaArea. You'll want to make a connection both ways between them.

0 ·

Dash Ballarta commented · Oct 20 2016 at 4:50 PM

doh! always the flowchart. Thanks matt!

0 ·

question