---
title: "How many orders each lab queue holds (ITE-638)."
method: GET
path: "/Labs/queue-counts"
tags: ["Labs"]
---

# How many orders each lab queue holds (ITE-638).

`GET /Labs/queue-counts`

The badges are on screen constantly, and they are what kept the unbounded fetch alive —
counting in the browser meant loading every lab order to do it. This is four numbers and
no rows.

## Query parameters

- `orderedById` string

## Response `200`

OK

- LabQueueCountsDto — How many orders each queue holds. One round trip, no rows.
  - `review` union
    - integer
    - string, int32
  - `flagged` union
    - integer
    - string, int32
  - `flaggedCritical` union — How many of int LabQueueCountsDto.Flagged are Critical. The flagged badge turns red on this — asking the flagged <i>page</i> "is anything critical" misses a critical older than a page of newer abnormals, and a badge that stays amber over a live critical is the queue hiding the one thing it exists to surface.
    - integer
    - string, int32
  - `awaitingResults` union
    - integer
    - string, int32
  - `reviewed` union
    - integer
    - string, int32

## Changes

- **2026-09-02** `061f8d95e1d1` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/clinicos/apis/pawthosx-business-api-v1/changes/Labs/queue-counts/get.md)

---

[API](https://skmtc.dev/clinicos/apis/pawthosx-business-api-v1.md) · [All operations](https://skmtc.dev/clinicos/apis/pawthosx-business-api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/clinicos/pawthosx-business-api-v1/revisions/061f8d95e1d1/schema)