...
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 “Publishing” state.
Transitioning a set of cases to a “Published” state will result in the creation publishing publication record. The publication record will represent a set of a JSON file containing anonymized aggregated case data cases and hold metadata about when the publishing occurred.
The publication record will then be taken and all associated case will be aggregated, anonymized, serialized as JSON, and written to a temp file (see The File that is Downloaded for how data will be structured).
After being generated, the file is programmatically transferred to the location the HA will 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
...