This is a how-to in order to help a UX and UI (because they aren’t the same damn thing!) volunteer get started on Safe Places and document things I found while getting up to speed so that you don’t have to waste your time.
Overview
Safe Places is a “business” tool to help health authorities (HA) and contact tracers conduct a contact trace with their patients more effectively, with location data, and publish exposure data to their subscribers (general public located in the HA zone) so subscribers can assess their risk and monitor symptoms if they are exposed to someone who has tested positive for an infectious diseases (e.g. COVID-19).
It consists of two core features
Contact Trace (also called the Redactor) tool to help volunteers and employees of a HA to conduct a contact trace in addition to the tools they are already using (which are already compliant with various health/privacy regulations)
Publish/Admin tool to help HA admins manage which data ultimately gets published to subscribers (using Safe Paths) and manage contact tracer users in their system
Safe Places Users
There are 3 distinct users of Safe Places
Contact tracer, our main user, is a person who contacts and works with a patient who tested positive for an infectious disease (e.g. COVID-19) - responsible for interviewing a patient, reviewing their location to assess who they’ve come into contact with, and, specifically with the Safe Places tool, remove sensitive location data before it can be published to the public by a HA admin
See this link for some more info on the contact tracer user https://www.today.com/health/what-coronavirus-contact-tracing-covid-19-contact-tracer-explains-job-t180125
Health Authority (HA) who owns their Safe Places tool, manages users (contact tracers), manages patient assignments, and can publish data to their subscribers on Safe Paths
Engineer (either on staff or recommended by Safe Paths team) that helps get the product setup for a HA - configuring the product, setting up a server, and connecting it to the Safe Places ecosystem
Demo Resources
Here is a demo link for Safe Places: https://covidsafepaths.org/safeplaces/
A video recording, presenting the Safe Places demo to a health authority: https://drive.google.com/file/d/19ZD_8LQ0NTkSQ5kVo9vAcvUDVfQz4vWZ/view
Documenting the demo workflow: https://drive.google.com/file/d/1oKTztTgcqXC_GPjAefu2hD-rGvFQGK80/view
Keep in mind that the demo does not necessarily function in the intended way a release would. For example, the demo show a patient saving data and emailing it to a contact tracer. Then, a contact tracer uploading a local file into Safe Places, etc. In other words, the demo shows users working with local data files, when in fact the release version will have a database to handle data saving, editing, and publishing.
UX Resources, Moving Forward
adam laskowitz has been working through the foundational UX based on what’s already been built and what is required to make the product more usable by HA and contact tracers. In conjunction with Steve Penrod providing invaluable information about the whole system and his experience interacting with our users on demo calls.
The start of this work can be found here:
High level user workflows: https://overflow.io/s/S3MFUA?node=697c4034
Wireflows
HA onboarding: https://overflow.io/s/S3MFUA?node=7fd2cbc2
HA Publisher tool: https://overflow.io/s/S3MFUA?node=586e2294
Contact Tracer Redaction (i.e. Contact Trace) tool: in notebook sketch form currently
Early high fidelity mock ups: https://www.figma.com/file/MlHKMJ02695qR2wsPByHCr/PLACES-April-2020?node-id=0%3A1
Again, keep in mind that these are heavily in progress work and shouldn’t be taken as final state in how the UX will work. Keep in touch with the Safe Places UX team to be up to date - via Yasaman Rajaee (Unlicensed).
What’s next?
This document will remain relatively up to date - at least that is the goal. If you’d like to help out with Safe Places you should either get in touch with Ali Raizin or adam laskowitz.
Specifically to come next:
Work through user flows for Contact Trace (redaction) tool
Rework user flows to reflect the “tool in addition to existing contact tracing tools” focus (originally reworking the UX focused on an all-encompassing tool, which is just false)
Wireframe the reworked user flows
Internal “test” with the product team
High fidelity mockups
Integrate processes with Front End dev team for implementation workflow
Add Comment