Systems and methods for determining facility exposure to a source condition
A method includes: obtaining, at a server, a diagnosis key published by a tracing service, the diagnosis key associated with a source device; identifying one or more detected proximity identifiers associated with the diagnosis key; identifying one or more affected network detection devices associated with the one or more detected proximity identifiers; retrieving, from a repository, device data for the one or more affected network devices, the device data identifying a facility of the one or more affected network devices; and generating facility exposure data for the facility, the facility exposure data defining exposure associated with the source device at the facility.
1. A method comprising:
obtaining, at a server, a diagnosis key published by a tracing service, the diagnosis key associated with a source device;
identifying one or more detected proximity identifiers associated with the diagnosis key;
identifying one or more affected network detection devices associated with the one or more detected proximity identifiers;
retrieving, from a repository, device data for the one or more affected network devices, the device data identifying a facility of the one or more affected network devices;
generating facility exposure data for the facility, the facility exposure data defining exposure associated with the source device at the facility.
2. The method of claim 1 , wherein generating facility exposure data comprises:
retrieving, from the repository, account data for at least one of the one or more affected network devices; and
identifying, based on the account data, an affected operator associated with the at least one affected network device.
3. The method of claim 2 , wherein generating facility exposure data further comprises:
retrieving, from the repository, network device proximity data for the at least one affected network device;
identifying, based on the network device proximity data, identifying subsequently affected network devices;
retrieving, from the repository, further account data for the subsequently affected network devices; and
identifying, based on the further account data, subsequently affected operators associated with the subsequently affected network devices.
4. The method of claim 2 , wherein generating facility exposure data further comprises identifying, based on the account data, subsequently affected network devices associated with the affected operator.
5. The method of claim 1 , wherein generating facility exposure data comprises:
retrieving, from the repository, proximity identifier data for the one or more detected proximity identifiers associated with the diagnosis key;
defining an exposure window at the facility according to the proximity identifier data.
6. The method of claim 1 , wherein generating facility exposure data comprises:
retrieving, from the repository, proximity identifier data for the one or more detected proximity identifiers associated with the diagnosis key;
mapping a path of the source device in the facility according to the proximity identifier data.
7. The method of claim 1 , wherein identifying one or more detected proximity identifiers associated with the diagnosis key comprises:
determining, from the diagnosis key, a set of source proximity identifiers issued by the source device over a predefined time period; and
comparing the set of source proximity identifiers to detected proximity identifiers stored at the repository, to identify the one or more detected proximity identifiers.
8. The method of claim 1 , further comprising providing a notification of the facility exposure data at the facility.
9. A server comprising:
a memory; and
a processor connected with the memory, the processor configured to:
obtain a diagnosis key published by a tracing service, the diagnosis key associated with a source device;
identify one or more detected proximity identifiers associated with the diagnosis key;
identify one or more affected network detection devices associated with the one or more detected proximity identifiers;
retrieve, from a repository connected to the server, device data for the one or more affected network devices, the device data identifying a facility of the one or more affected network devices;
generate facility exposure data for the facility, the facility exposure data defining exposure associated with the source device at the facility.
10. The server of claim 9 , wherein, to generate facility exposure data, the processor is configured to:
retrieve, from the repository, account data for at least one of the one or more affected network devices; and
identify, based on the account data, an affected operator associated with the at least one affected network device.
11. The server of claim 10 , wherein, to generate facility exposure data, the processor is further configured to:
retrieve, from the repository, network device proximity data for the at least one affected network device;
identify, based on the network device proximity data, identifying subsequently affected network devices;
retrieve, from the repository, further account data for the subsequently affected network devices; and
identify, based on the further account data, subsequently affected operators associated with the subsequently affected network devices.
12. The server of claim 10 , wherein, to generate facility exposure data, the processor is further configured to identify, based on the account data, subsequently affected network devices associated with the affected operator.
13. The server of claim 9 , wherein, to generate facility exposure data, the processor is configured to:
retrieve, from the repository, proximity identifier data for the one or more detected proximity identifiers associated with the diagnosis key;
define an exposure window at the facility according to the proximity identifier data.
14. The server of claim 9 , wherein, to generate facility exposure data, the processor is configured to:
retrieve, from the repository, proximity identifier data for the one or more detected proximity identifiers associated with the diagnosis key;
map a path of the source device in the facility according to the proximity identifier data.
15. The server of claim 9 , wherein, to identify the one or more detected proximity identifiers associated with the diagnosis key, the processor is configured to:
determining, from the diagnosis key, a set of source proximity identifiers issued by the source device over a predefined time period; and
comparing the set of source proximity identifiers to detected proximity identifiers stored at the repository, to identify the one or more detected proximity identifiers.
16. The server of claim 9 , wherein the processor is further configured to provide a notification of the facility exposure data at the facility.
17. A non-transitory computer-readable medium storing a plurality of computer-readable instructions executable by a processor, wherein execution of the instructions configures the processor to:
obtain a diagnosis key published by a tracing service, the diagnosis key associated with a source device;
identify one or more detected proximity identifiers associated with the diagnosis key;
identify one or more affected network detection devices associated with the one or more detected proximity identifiers;
retrieve, from a repository connected to the server, device data for the one or more affected network devices, the device data identifying a facility of the one or more affected network devices;
generate facility exposure data for the facility, the facility exposure data defining exposure associated with the source device at the facility.
18. The non-transitory computer-readable medium of claim 17 , wherein, to generate facility exposure data, execution of the instructions configures the processor to:
retrieve, from the repository, account data for at least one of the one or more affected network devices; and
identify, based on the account data, an affected operator associated with the at least one affected network device.
19. The non-transitory computer-readable medium of claim 18 , wherein, to generate facility exposure data, execution of the instructions further configures the processor to:
retrieve, from the repository, network device proximity data for the at least one affected network device;
identify, based on the network device proximity data, identifying subsequently affected network devices;
retrieve, from the repository, further account data for the subsequently affected network devices; and
identify, based on the further account data, subsequently affected operators associated with the subsequently affected network devices.
20. The non-transitory computer-readable medium of claim 17 , wherein, to generate facility exposure data, execution of the instructions configures the processor to:
retrieve, from the repository, proximity identifier data for the one or more detected proximity identifiers associated with the diagnosis key;
define an exposure window at the facility according to the proximity identifier data; and
map a path of the source device in the facility according to the proximity identifier data.