Radiology

On a multi-test order, the Kanban board places the whole order card into a single column based on one test's status, even when the order's other test is in a completely different, still-active state. A sibling test's own status badge stays correct on the card, but the order itself is no longer visible under its own proper column, so staff scanning that column for work can miss it.
Impact
High. The worst case seen: an order with one Cancelled test and one Awaiting report test (scan done, report pending review) is bucketed entirely under "Cancelled." Anyone scanning the Awaiting report column for reports to review would never see it, since the order looks fully closed out. A milder version of the same issue was already flagged in the Reschedule bug report, where a sibling Waiting test got hidden the same way when its order moved into Exceptions.
Environment
Clinq HMS, NSS Hospital demo, Radiology Orders (Kanban view), logged in as admin@clinq.local. Seen on RAD-ORD-1-6 (Abirami Balasubramaniam) and RAD-ORD-1-15 (Anu).
Steps to Reproduce

1. Open RAD-ORD-1-6 (Abirami Balasubramaniam) on the Radiology Orders Kanban board, filtered to the last 7 days.
2. This order has two tests: CT Brain Plain and Contrast (Cancelled) and Barium Swallow Study (Awaiting report).
3. Look at which Kanban column the order card sits in: it's under "Cancelled," not "Awaiting report."
4. Open the card: the Barium Swallow Study test correctly still shows its own "Awaiting report" badge — its status wasn't changed, it's just not visible under the Awaiting report column.
5. Same pattern on RAD-ORD-1-15 (Anu): one test Rescheduling, one test still Waiting — the whole order sits under "Exceptions," and the Waiting test isn't visible under the Waiting column either.
   Expected vs Actual
   Expected: each test's status should drive its own visibility, or the Kanban column choice for a multi-test order should reflect whichever test still needs action, not just one that happens to be Cancelled or in Exception.
   Actual: the order card is placed in a single column (Cancelled, Exceptions, etc.) based on one test, which can bury a sibling test that is still awaiting action (report review, scheduling) and make it invisible under its own correct column.
   Notes
   Related to, but distinct from, the already-reported Reschedule flow bug (stale status until refresh, empty Resource/Technician dropdown). This report is specifically about the Kanban board's column placement logic for multi-test orders, independent of the refresh/dropdown issues.