| CPC G06V 40/166 (2022.01) [G06F 21/32 (2013.01); G06V 40/1365 (2022.01); G06V 40/172 (2022.01); G16H 10/60 (2018.01); G16H 20/00 (2018.01); G16H 40/40 (2018.01); G16H 40/63 (2018.01); G16H 40/67 (2018.01); G16H 50/30 (2018.01); G16H 50/70 (2018.01); G16H 50/80 (2018.01); G16H 80/00 (2018.01); G16H 40/20 (2018.01)] | 21 Claims |

|
1. A system comprising:
a database system implemented using a server computing system comprising a plurality of batch servers configurable to implement batch job processing comprising:
configuring, by the server computing system, a variable batch size according to a detected one of a range of reopening phases associated with a shared health event to process batches of patient records stored in a database associated with the database system, each reopening phase having a respective one of a range of restrictions on patient location;
for each batch of the patient records:
performing load balancing for the plurality of batch servers to process the batch of patient records using an interface system implementing the load balancing, the interface system being communicably coupled with the plurality of batch servers, the load balancing including analyzing and forwarding traffic to distribute workload among the plurality of batch servers;
obtaining, from a database, by the server computing system, data identifying a plurality of cancelled health-related appointments for the batch of patient records, the cancelled health-related appointments associated with the shared health event;
associating, by the server computing system, each of the patient records of the batch with a risk category from a plurality of risk categories ranging from a lowest risk to a highest risk, wherein a risk category is determined based at least on a treatment associated with a cancelled health-related appointment;
communicating, by the server computing system, with a client computing device associated with a patient having a cancelled health-related appointment to schedule a return appointment based at least on the detected reopening phase and on a risk category associated with a patient record of the patient, the communicating including receiving, by the server computing system, current health condition information of the patient;
based at least on the current health condition information of the patient showing symptoms consistent with symptoms associated with the shared health event, identifying, by the server computing system, the patient as a potential infected patient; and
performing, by the server computing system, contact tracing based at least on people that the patient has been in contact with while experiencing the symptoms.
|