Picked a pin at random to check for some formatting issues. I'm just struck by how we got this info just by asking nicely.
(I'm obscuring identifying information because this information will age rapidly; vaccinateCA.com will update but a Twitter screengrab will not.)
This is *not* the sort of petabyte scale computation that the tech industry often thinks of when we think data problem. It's a very, very human scale dataset.
But as we get good at ingesting updates rapidly, we can ask it useful questions, like "Where's nearest short waitlist?"
"But how will you go from unstructured text notes to something a computer can operate on? Spin up an ML team to do natural language parsing and then..."
No it probably sounds closer to "Read from computer, type into a computer, ideally very quickly."
On the scale of difficult logistical problems "Call every pharmacy in California in a day" sounds intuitively "Hmm, pretty hard" but then you actually put numbers on it you realize a motivated high school class could do it successfully if they didn't have anything else to do.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Up bright and early (joking, I live in Tokyo) to hit a Bay Area morning radio show and then work on day 6 of VaccinateCA.com
What we hope to do today:
* Call ~500 vaccine sites looking for up-to-the-minute availability. In particular, we want to probe who is not able to administer at present due to the batch which went bad, while finding who took or will take delivery today.
* Greatly improve the search experience, hopefully landing a prototype today and then rolling out today or tomorrow. You should be able to give us a few trivial facts about the vaccine seeker and get a prioritized list of recommendations.
You know the sales team tradition of banging a gong when you get a commit?
We've got a gong bot that flags every time we find accessible vaccine.
I like this gong so much. (That it is not audible is a plus.)
Also like the emergent culture of people reacting to it with the :vaccine: emoji.
It's fundamentally the same purpose as the sales gong, right?
You're going to get told No, a lot. That's a useful result! Pick up the phone immediately and try to get some more Noes. Occasionally you get a Yes in there. *gong*
Happy MLK Day. Here's what vaccinateCA.com hopes to accomplish today:
* Call ~500 pharmacies in California to learn their current status of vaccine availability.
* Improve website UX on mobile devices after relaunch on new tech stack at ~midnight.
* Continue learning nuances about pharmacy IVR systems to improve call efficiency, both for us and the responding pharmacist.
* Start scoping out multiple ways to expose our data, via e.g. a text-based interface, chatbot, etc, and APIs / ways to package for gov't frontline.
So an interesting observation from vaccinateCA.com: we're effectively discovering availability bottom's up, starting from where the patient would perceive supply, rather than top down, starting from where a hypothetical national logistics coordinator would see supply.
That hypothetical coordinator might scratch their head at some of the results: "That's funny, I dispatched to X, Y, and Z on the same date. Why does X have it but Y and Z do not?"