When a user has indicated a health condition on a self-report, use Emergency Exposure Management to identify other users who might have come in contact with the affected user. You can analyze multiple data sources, such as location, meetings, workspace reservations, badge scans, and Wi-Fi access data of the affected user to identify potentially exposed users.

1. Navigate to Emergency Exposure Management > Create New.
   The Report generation status field is set to Not Initiated and the Active check box is selected.
2. From the Affected user field, select the user's name.
3. Click the lock icon () in the Tracing system field and select one or more tracing system options to query corresponding data sources.
   You can select multiple sources together for better identification of potentially impacted users.

   Table 1.

   Tracing system (Required application/plugin)	Query
   Location	Users co-located with the affected user, for example, on the same floor or building.
   Outlook meetings (Microsoft Office 365)	Users who accepted the same meetings as the affected user during the specified time period.
   Workplace reservations (Workplace Safety Management)	Users who had reservations for the same shifts as the affected user during the specified time period.
   Badge reader (Contact Tracing)	Users who swiped their badge on the same badge reader devices as the affected user, during the specified time period.
   Employee daily log (Contact Tracing)	The list of users with whom the affected users interacted during the specified time period.
   Visitor log (Contact Tracing and Employee Health Screening)	The list of visitors who interacted with the affected user during the specified time period. Visitors who are invited by the affected user and have been screened through and let in are queried.
   Wi-Fi access log (Contact Tracing)	Users who used the same Wi-Fi access points as the affected user during the specified dates. Wi-Fi access log data used to identify potentially impacted users depends on the Wi-Fi location preferences and the available integrations. For more information, see Retrieving Wi-Fi access log data. Note: Data received via a real-time API will be for a period based on the data retention policy of your Wi-Fi service provider.
   Handheld/Wearables (Contact Tracing)	Users using handheld or wearable devices in the close proximity with the affected user for more than the permissible time during the specified time period.
   Field service (Field Service Management)	Customers attended by an affected field agent during the specified time period. Also queries other field agents who interacted with the affected agent or visited the same customer as the affected agent during the specified time period.

4. When required for a selected tracing system, provide the start and end dates.
   1. In the Start date field, provide the estimated date of infection.

      Because the infection window that you're concerned about may vary, pick a start date such as 14 days prior to the date of reported symptoms.

   2. In the End date field, provide the date of reported symptoms, at least one day prior to today.
5. Click Save.
   Related lists appear that are filled in after you run a diagnostics report.
6. Click Run Diagnostics.
   A scheduled job fetches potentially impacted user data from the selected sources and loads the data in corresponding related lists. Refresh a list to see the potentially impacted users immediately.

   If you selected the Handheld/Wearables option, a diagnostic request task is created. Follow the instructions in the task to fetch the potentially exposed users.

   If you selected the Wi-Fi access log option, the Wi-Fi data queried is based on the location preference set for the affected user's location. The available options are:

   • Mist Systems integration: The Wi-Fi data is fetched from Mist Systems when you run the diagnostic request.

     If the site network is Bluetooth LE-enabled and the organization has provided users with a BLE device, the Wi-Fi access using the BLE devices is used to identify potentially exposed users.

   • Cisco DNA Spaces integration: The Wi-Fi data is available based on the Cisco tier value set in the sn_imt_tracing.wifi_log_cisco_tier property:
     • If the wifi_log_report value is set, the data is imported from the Wi-Fi access data files for the specified days from the SFTP server and queried by the location path to identify potentially exposed users.
     • If the proximity_report value is set, a diagnostic request task is created to fetch the potentially exposed users. Follow the instructions in the task to fetch data on potentially impacted users from the selected data source. For more information, see Fetch potentially exposed user data from a data source.
   • Manual import: The Wi-Fi data is imported from a Microsoft Excel spreadsheet into the Wi-Fi Access Register table.
7. (Optional) Add manually the potentially affected users, for example, users who visited a location with an affected user.
   1. In the Impacted users added manually list, click New.
   2. Select the potentially affected user.
   3. (Optional) Add comments about why you added the user.
      Entering comments helps identify other users who might be potentially impacted by this user if this user starts to show symptoms.
   4. Click Submit.
   The user appears in the Impacted users added manually related list.