These are actually all questions we didn’t want to provide hard answers to, with the idea that they’d be answered by whatever application is consuming the queue. The queue structure by itself is intended to cover both one queue per facility or one queue per service or even one queue per room, depending on how specific an implementation or application wants to be. That said, both service and location were intended to be optional rather than required fields.
That was the intention.
That wasn’t the intention with the design, i.e., the original intention was that patients only have an active queue entry when they are actually waiting, but I think queues have sort of morphed into what I originally intended the PatientVisitState to be.