Setting Up CWG Screening

Public-health screening for series events is enabled via a toggle in Information Governance, with the screening panel content provisioned once by your IndieBase administrator before go-live.

Overview

Series events - such as major multi-sport games - may require every patient contact to be screened for symptoms across three categories: Respiratory, GI (gastrointestinal), and Mental Health. When screening is active, clinicians must answer all three panels before a job can be closed.

Setting up screening involves two steps that need to happen in order:

1. Panel provisioning - your IndieBase administrator seeds the canonical symptom lists for your team using a one-time server command.
2. Enabling the toggle - you, as team owner or administrator, switch screening on in Information Governance in Team Settings.

Once both steps are done, screening panels automatically appear on all jobs linked to your series events. Non-series events are unaffected.

Before You Start

• You must be the team owner or a designated team administrator to access Information Governance.
• Screening panel content must have been provisioned by your IndieBase administrator before you enable the toggle. Speak to your account manager or support contact if you're unsure whether this step has been completed.

Step 1: Panel Provisioning (Administrator Task)

Before the Enable screening toggle has any effect, the three screening panels must be set up for your team by an IndieBase administrator. This is a one-time step done ahead of the series.

The administrator runs the following command to seed the panels and activate screening in one step:

php artisan cwg:seed-screening-configs {team} --enable

This command creates the three canonical panel configurations (Respiratory, GI, Mental Health) with the correct symptom lists, and sets the team's screening flag to enabled at the same time. You may find screening is already active after provisioning - check the toggle described in Step 2 below.

Once your team has reviewed the symptom lists and is satisfied they're correct, the administrator runs a second command to lock the wording for go-live:

php artisan cwg:seed-screening-configs {team} --lock

Locking prevents the panel wording from being changed during live operations, ensuring the data collected across the series remains consistent. You don't need to run either command yourself - this is a task for your IndieBase administrator.

Step 2: Enable the Screening Toggle

1. Open Team Settings from the left-hand navigation.
2. Scroll down to the Information Governance section.
3. Find the Screening card.
4. Switch the Enable screening toggle on.

The toggle saves immediately - there's no separate save button. From this point, screening panels appear on all jobs under your series events, and the Job Done action is blocked until all three panels are answered on each job.

If the Screening card isn't visible in Information Governance, panel provisioning may not have been completed for your team yet. Contact your IndieBase administrator or account manager.

How Screening Scope Works

Screening only applies to jobs that meet both of these conditions:

• The job belongs to an event linked to a series.
• Your team has Enable screening switched on.

Regular events, standalone jobs, and events not linked to a series are completely unaffected. Clinicians working non-series events won't see any screening panels.

Cluster Threshold

Each series includes a cluster threshold - a number of positive screens in a single symptom category at a single venue on a single day that the series considers a potential outbreak signal. When positive counts for a category at one venue on one day reach or exceed this threshold, the relevant indicators turn red in the Daily Ops view and Event Control Room.

The threshold is set at the series level by your IndieBase administrator. If you need to review or change it, contact your account manager.

Tips & Best Practices

• Enable screening before the series opens. Jobs created before screening was enabled won't have retrospective screening panels added to them.
• Brief your clinical team ahead of go-live. Clinicians at series events will see new panels appear in the job sidebar as soon as screening is enabled. A brief heads-up prevents confusion on the first day.
• Avoid disabling screening mid-series unless absolutely necessary. Jobs created while screening was active will still require all three panels to be answered before they can be closed.

Troubleshooting

The Screening card isn't visible in Information Governance.

You must be the team owner or an administrator to see the Information Governance section. If you can see Information Governance but not the Screening card, the panel provisioning step may not have been completed for your team. Contact your IndieBase administrator.

The toggle is on but clinicians can't see screening panels.

Check that the relevant event is correctly linked to a series. Events that aren't part of a series won't show screening panels even when the toggle is on. If the event is linked to a series and panels still don't appear, contact IndieBase support.

I need to change the symptom options on a panel.

The symptom lists are locked at go-live to ensure consistent surveillance data across the series. If a change is genuinely required before locking, contact your IndieBase administrator. After the lock step has been run, the wording cannot be changed without a formal process.

The toggle was already on when I checked - do I need to do anything?

If the --enable flag was used during provisioning, the toggle will be switched on automatically. Check that you're happy with the setting and leave it on if the series is ready to go live. No further action is needed.

Related Features

• Information Governance - the full Information Governance section, including PID storage, 2FA enforcement, and data access settings
• Completing Screening Panels - the clinician guide for answering the three symptom panels on a patient record
• Screening Surveillance Reporting - how to read screening results in Daily Ops and the Event Control Room