Screening Surveillance Reporting

screening surveillance cwg daily-ops control-room cluster outbreak public-health series

How to read and interpret public-health screening results in the Daily Ops view and Event Control Room for series event outbreak surveillance.

Screening Surveillance Reporting

Screening results from series events flow into two reporting surfaces in real time - the Daily Ops view for day-level trend surveillance, and the Event Control Room for event-level operational oversight.

Overview

When public-health screening is active, every patient contact at a series event generates a screening record across three symptom categories: Respiratory, GI (gastrointestinal), and Mental Health. Those records roll up into two reporting surfaces designed for different levels of oversight:

  • Daily Ops (/web/) - the big picture for a selected date: how many patients were screened across all venues, how many had positive results in each category, and whether any venue/day combination has crossed the series' outbreak detection threshold.
  • Event Control Room (/web/event/{id}/control-room) - a live, event-specific view: total positives, jobs still awaiting screening, and a per-category breakdown with proportion bars and per-symptom detail.

Together, these two surfaces give the CMO and surveillance team the data they need for day-to-day outbreak monitoring during a series.

Before You Start

  • You need to be signed in to a team account with access to the relevant event(s).
  • Screening data only appears for events linked to a series where screening is enabled. See Setting Up CWG Screening for how this is configured.
  • Both views are available to all team members - no additional admin permissions are required.

Daily Ops: Series Screening Rollup

The Ops Dashboard at /web/ includes a Screening section when series events are active on the selected date. This section summarises screening results across all venues for the day.

Reading the Rollup

The rollup shows one row for each of the three screening categories - Respiratory, GI, and Mental Health. Each row shows:

  • The number of positive screens for that category - that is, patients where at least one symptom other than None was recorded.
  • The total patients screened for that category.
  • A per-symptom breakdown - for example, "Cough 8 · Fever 4 · Cold 2" - so you can see which specific symptoms are contributing to the positive count.

At the bottom of the rollup you'll also see:

  • Total positives across all three categories.
  • Total screened - the number of patients with at least one screening panel answered.
  • Awaiting screening - jobs that have a patient record but where at least one panel is still unanswered. This count tells you how much data may still be coming in.

Screenshot: The Daily Ops screening rollup section showing three category rows - Respiratory, GI, and Mental Health - each with a positive count, total screened, and per-symptom breakdown, displayed in amber state

Colour Coding: Amber and Red

Amber rows are the normal operating state. They mean positives have been recorded but no outbreak threshold has been crossed.

Red rows mean the positive count for that category has crossed the series' cluster threshold at a single venue on the current day. A red row is your signal to investigate - it means the rate of positive results at one location is at or above the level the series defines as a potential cluster.

Screenshot: The Daily Ops screening rollup with one category row shown in red, indicating the cluster threshold has been breached at a venue for that symptom category, and the other two rows remaining in amber

The threshold is applied per venue per day, not to the aggregate total. A large event with many positives spread across multiple venues won't trigger a red row unless a single venue sees a concentration of positives on a single day.

Navigating Between Dates

Use the date navigation on the Ops Dashboard to step through previous days. The rollup updates to reflect the selected date. This lets you track symptom trends day by day across the full series period.


Event Control Room: Screening Island and KPI Strip

The Event Control Room (/web/event/{id}/control-room) provides a real-time view of a single event. Screening data appears in two places.

The KPI Strip

At the top of the Control Room, a strip of headline figures includes a Screening +ve tile showing the total positive screens recorded for this event. This number updates live as clinicians complete screening panels and their devices sync.

If any jobs are still awaiting screening - patient present but panels not yet answered - a secondary note shows "+ N awaiting" in muted text alongside the positive count, where N is the number of incomplete jobs.

Screenshot: The Event Control Room KPI strip showing the "Screening +ve" tile with a positive count in amber and a muted "+ 3 awaiting" note beside it

When the positive count crosses the cluster threshold, the KPI tile colour changes from amber to red as a visual alert.

The Screening Island

Below the KPI strip, the Screening island shows a more detailed breakdown of results for the event. It can be expanded and collapsed using the button in the island header.

Each row in the island represents one screening category and shows:

  • A large positive count on the left - your at-a-glance figure for that category.
  • The category name and total screened count on the right.
  • A proportion bar showing what fraction of screened patients were positive. The bar is amber under the threshold and turns red once the threshold is crossed.
  • A per-symptom breakdown beneath the bar - for example, "Fever 4 · Cough 3" - showing which symptoms are appearing most frequently in that category.

Screenshot: The Event Control Room screening island expanded, showing all three category rows with large positive counts on the left, proportion bars in amber, and per-symptom breakdowns beneath each row

If no screening data has been recorded for the event yet, the island displays: "No screening recorded yet for this event. Completed patient screens will appear here as they sync."


Understanding Cluster Detection

The cluster threshold is a series-level setting that defines when positive screening results at a single location become a potential outbreak signal. It represents the number of positive screens in a single symptom category at a single venue on a single day that warrants investigation.

For example, if the threshold is set to 5 and on Tuesday the Main Arena sees five or more Respiratory positives, the Respiratory row turns red in both the Daily Ops rollup and the Event Control Room.

A red indicator means: investigate this combination of venue, date, and symptom category. It's a prompt for CMO review and follow-up - not an automatic confirmation that an outbreak has occurred.

The aggregate positive count for the whole series can be high without triggering a red signal, provided no single venue/day combination crosses the threshold.


Tips & Best Practices

  • Check the Daily Ops rollup at the end of each competition day. The awaiting screening count tells you how many jobs still have incomplete panels. A persistently high awaiting count may point to a training or connectivity issue with the clinical team.
  • Use the Event Control Room for live oversight during an event. The KPI strip gives you at-a-glance surveillance numbers without leaving the operational view. Open the Screening island when you need the per-symptom detail.
  • Red means investigate, not panic. A cluster signal is a surveillance prompt. Cross-reference the venue, date, and symptom category with event scheduling and presenting times before deciding whether to escalate.
  • Allow for sync lag. Clinicians working offline have their screening data upload when connectivity is restored. The awaiting count may temporarily overstate the backlog if crews are operating in low-connectivity areas.
  • Step through previous dates in Daily Ops. Tracking the per-category positive counts day by day is the easiest way to spot rising trends early in the series.

Troubleshooting

The Screening section isn't showing on the Daily Ops page.

Screening data only appears when there are series events with screening enabled active on the selected date. If the date you're looking at has no series events, the Screening section won't be displayed. Try selecting a date when a series event was running.

The Screening island in the Control Room is showing an error.

The island displays "Couldn't load screening - Retry" if there's a temporary data loading issue. Tap Retry to reload. If the error persists, check your network connection and refresh the page.

The awaiting screening count isn't going down.

Remaining incomplete jobs are likely from crews who are still offline, or who haven't yet completed their panels. Screening data syncs as soon as a device reconnects. If counts don't drop after crews have finished their shifts, follow up with those crews to check connectivity and confirm the panels were completed on their devices.

The positive count seems lower than expected.

Positive counts only include jobs where at least one screening panel has been answered. Jobs still awaiting screening are not counted in the positive total - they're tracked separately in the awaiting figure. If the positive count looks low, check whether the awaiting count is high, which may mean data is still syncing from offline devices.


Related Features