Fix specialty Call next vs WAITING KPI mismatch.

Admins without a desk now scan all specialty service points, KPIs use the same branch as queue ops, and empty Call next flashes explain tickets vs other branches. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-18 11:41:45 +00:00
parent 4c4dfc7dbf
commit bd8218fb45
5 changed files with 235 additions and 21 deletions
@@ -11,6 +11,8 @@
      <p class="text-sm text-slate-600">
        @if (($qi['routing_mode'] ?? null) === 'shared_pool')
          Call next takes the next waiting patient in line for this queue (shared pool).
+        @elseif (! empty($queueCallNextScansAllPoints))
+          Call next picks the next waiting patient across service desks for this specialty at this branch.
        @else
          Call next operates on your assigned service point only — tickets routed to other rooms or desks stay there.
        @endif
@@ -72,6 +72,7 @@
                        'queueCallNextRoute' => 'care.specialty.call-next',
                        'queueCallNextParams' => ['module' => $moduleKey],
                        'branchId' => $branchId ?? null,
+                        'queueCallNextScansAllPoints' => ($practitionerScope ?? null) === null,
                    ])

                    @if ($workspaceVisit)