Day 73 at VaccinateCA.com and I've got the update baton.
We tried guesstimating the number of shots in arms delivered as a result of folks getting vaccine information from our site, and came up with ~100,000 or so.
We tried guesstimating the number of shots in arms delivered as a result of folks getting vaccine information from our site, and came up with ~100,000 or so.
We continued doing the unglamorous but necessary data collection which powers most of our efforts: calling lots of pharmacies. Recent increases in call capacity have let us get to a bunch of lower priority locations and re-call ones which didn't know when they'd get first doses.
This brings us to about 3.5k locations in California with doses available. We're tightening the loop on catching increases in supply (and, relatedly, broadening in enforced eligibility criteria).
A pretty graph demonstrating last two tweets:
A pretty graph demonstrating last two tweets:
We are almost done with the rearchitecture of our backend, which will support markedly higher call and data volumes. It's moving onto Django/Postgres from being a Rube Goldberg collection of automation on top of Airtable. (I remain pleasantly amazed how far Airtable got us.)
We continue putting together a consortium of partners, on the data ingestion and data publication sides, to help reduce duplication of effort, use our calls to the best effect, and multiply our impact through platforms which have large reach on the Internet and/or communities.
At the moment, our #1 organizational priority is preparing for intensification of efforts over the coming month.
The default course of the vaccination campaign is not, unfortunately, up-and-to-the-right. We're trying to quickly reduce search costs as availability broadens.
The default course of the vaccination campaign is not, unfortunately, up-and-to-the-right. We're trying to quickly reduce search costs as availability broadens.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
