...
| Gliffy | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
CT’s are expected to redact / remove sensitive location history (such as personal residence) from the patients SPL file and gain consent prior to storing the location history in a database where the data can be aggregated and published as “points of concern” for the community to receive exposure notifications based on.
Deployment of Safe Places at an HA
Overview
Safe Places is an open source white-label web application. The business logic and UI/UX of the web app is functional to spec, but a production deployment of the web application on the infrastructure of the HA requires development work to actualize.
There are 3 primary reasons for why the application doesn’t work at an HA after simply downloading it from our open source repo’s:
The Safe Places web application requires a database backend to function correctly. There is a wide variety of database technologies in use across the landscape of HA’s. We’ve not assumed or optimized for any specific database technology. We’ve left that open to be “finished” by a development team looking to install Safe Places
An identity management platform is also required to ensure that only authenticated personnel have access to the Safe Places web application. There are a variety of ways an HA may be implementing identity management. We assume it exists, but leave the actual implement to be “finished” by a development team looking to install Safe Places.
We publish a file of public concern points (GPS lat,long,time of infected carriers) to be publicly accessible for all mobile app clients. How that file is published or moved from the server it was published from to an endpoint which is publicly accessible may vary from HA to HA. We’ve also left this open to be finished.
It’s very unlikely that a non-development team will be able to download our source code and make it production functional unless they implement our example backend exactly as it’s written.
Server Requirements
There are no specific requirements for the server the code is installed on. There are a variety of ways to make a deployment successful. The two largest workload stress points are as follows:
The server which is hosting the file to be downloaded by mobile apps will experience load in proportion to the active case load and the number of active mobile app users in the jurisdiction of the HA.
The server which is hosting the ingest endpoint will experience load in proportion to the number of active cases.
The server which hosts the Safe Places software will experience load in proportion to the number of active cases and the number of contact tracers working those cases in parallel.