...
Contact Tracer (CT) begins CT interview over phone
CT prompts interviewee to upload data from SafePaths app to SafePlaces
CT works with interviewee to redact, update, and add points of concern
CT concludes interview and transitions case data from “In Progress” state to “Staged for Publishing”
Admin user of SafePlaces/HA selects cases that are in a state of “Staged for Publishing”
Admin user performs further redaction on aggregated case data
After further redaction, the admin user transitions the cases from “Staged for Publishing” to a “Released for Publishing” “Publishing” state
The admin user will then make trigger the creation of the JSON file by submitting one final API request from the SafePlaces UI resulting in the SafePlaces application creating a JSON file of the anonymized aggregate Transitioning cases to a “Published” state will result in the creation of a JSON file containing anonymized aggregated case data (see The File that is Downloaded). The
After being generated, the file is then programmatically uploaded transferred to the location the HA plans to host published data fromwill host the JSON file from (specified in the organization’s settings). The HA is responsible for implementing this functionality within their own API or by extending the existing example application. How an HA serves up the file could be differ from one HA to the next (could be AWS s3, gcloud, standard file server, etc.).SafePaths mobile application hits the endpoint the HA has configured to host published data from and performs intersection logic
...