question

When I first opened the model the System Console was reporting a couple syntax errors in the Next Activity for activity 200 in the WalkIn and Ambulance tracks, so I fixed those. You were using getlabelnum instead of gettablenum.

Then when I ran the model I didn't see exactly what you saw, but I did see several patients getting stuck in the model. When I quickly looked over your Predecessors and Next Activities of the activities in your track, they didn't seem logical to me. I don't have a lot of time tonight, so I'll look again in the morning, but you should go back and review the activity ID's specified in your Predecessors and Next Activity fields, because I don't think they are what you want. The one predecessor I really question is the long one defined for activity 200. I don't think you need a long one for it. The way you have defined your activities as a long list of yes/no decision points in a chain, I would think you only need to say 190 once you get everything else correct.

I personally like to click the Table icon on the Track Activity window to view the track in table form when reviewing my predecessors. Unfortunately your Next Activity's are all displayed as simply "Based on Percentages" so the table view doesn't work well for them. I do have a suggestion for you though. Most of your Next Activities are based on just two choices, so if you don't use a pick list option, and instead write something like bernoulli(gettablenum(ProcedurePercentages, PP_R_ADMITS, getlabel(patient,"ESI")), 220, 230) then you will be able to see the expression in the activity table view. The table view will show one-liner expressions you type in yourself!

I'll help you out more tomorrow if you don't fix the problem first yourself!