Maximum Occupancy > 1 Error

Question

question

Cinar Tuncel asked Sep 30, '16 Matthew Gillespie answered Oct 3, '16

Maximum Occupancy > 1 Error

@Logan Gold

I'm getting an error message in the HEALTHCARE model when patients try to move from Waiting Room to Patient Bed.

Beds are part of Pre Procedure Area of a surgery platform and the model flow goes like this;

1- Patient Arrives to Check-in (waits in the waiting room, if needed)

2- Patient goes to Pre Procedure

3- Patient gets Transferred to Operating Room (This step has, Reserve Current location box checked, so that patients can return back to the same Pre Procedure Bed after the surgery is done)

But that step 3 always generates the same "You cannot reserve a room for more than one patient at a time!" error. Although both the Pre Procedure Beds, and Operating Rooms have Maximum Capacity = 1

Software Version:

FlexSim HC 5.0.12

healthcare max occupancy

· 4

Lou Keller commented · Sep 30, 2016 at 08:53 PM

I'll need your model to take a closer look at what's happening and what you've built. In the meanwhile, I've attached a current PreOp-OR-PostOp model that you might want to examine for technique purposes. Notice that the model handles InPatients, OutPatients and Emergency Patients in the same simulation. Anyway, send me your model, and I'll take look! Lou preop-or-pacu-model-2016.fs

0 ·

preop-or-pacu-model-2016.fsm (1007.7 KiB)

Cinar Tuncel commented · Sep 30, 2016 at 09:23 PM

I've looked at the model you sent and couldn't see any box checked to reserve location to get the patients back to the same place. But attached is the model I used . thanks for the help.model1a-v3-dedicated-pr-assignment.fsm

0 ·

model1a-v3-dedicated-pr-assignment.fsm (12.8 MiB)

Adrian Haws commented · Oct 01, 2016 at 07:30 PM

@CINAR TUNCEL

It doesn't make sense to me why you would be getting that error. However, it's hard to know if that issue might be influenced by the other errors you have in your model currently. It's always a good idea to take care of an issue when you see it, because it could have consequences on other parts of your model.

I'm not sure if you have any previous experience with using the "Reserve Current Location" option, but I've attached a small model showing its implementation. If you're not as familiar with it, be aware of a couple small details. One, make sure to reserve the location the patient is currently in, not the location the patient is traveling to. Two, make sure that there is a connection in the flowchart back to the location you had reserved.

If you're still having this issue, try creating a smaller model demonstrating the problem for us to look at.

I hope this helps.

0 ·

reserve-location.fsm (110.2 KiB)

Cinar Tuncel Adrian Haws commented · Oct 03, 2016 at 01:54 PM

I initially had a different version without reserved location, and it worked well. That's why I couldn't figure out why only the Reserve Current Location started causing this error.

Also a smaller model I just created works fine, with reserved locations.

0 ·

Answer 1 · 2016-10-03T16:48:16Z

Matthew Gillespie answered Oct 3, '16

You're reserving beds and then only some of the patients ever go back to their reserved beds. This is causing issues when the patient leaves the model and the bed now has a pointer to something random in your model that it says reserved it. This model is a simplified version of your model that usually shows the error, try running it a few times if you don't see it immediately.

I would recommend only reserving the location if you know for sure that the patient will be returning to that location. The other option would be to use the Unreserve a Location pickoption in an Activity Start Trigger whenever a patient with a reserved location leaves a model to "unreserve" their bed.

reservedlocation.fsm (66.0 KiB)

question