Search saves lives: solving healthcare problems with search
summary
NHS testing moves from straight‑line distance to travel‑time matching using a driving model + graph traversal that returns driving times for up to 100,000 locations per request, serves peaks of 100,000 concurrent users, and delivers results under 50 milliseconds by switching JSON to protobuf, running in‑memory on dedicated redundant servers (six instances) with no PII written to disk. It operates globally (92 countries), ingests GTFS from ~15,000 agencies (3.5M stops, 200k routes), and powers 111/999, job and workforce matching; it works in production.
AI-written summary · about
chapters (28)
- 0:00Introduction and speaker background
- 1:25Agenda and talk overview
- 2:08COVID-19 testing challenges in 2020
- 3:57Problems with straight-line distance search
- 6:27Limitations of bounding boxes and polygons
- 8:38Searching using transport networks
- 12:32Requirements for healthcare search solution
- 16:28Building the driving time model
- 17:55Handling large location datasets
- 18:58Achieving sub-50ms response times
- 19:39Scaling for high concurrent demand
- 21:01Ensuring user data privacy
- 21:42Customizing the solution for healthcare
- 22:44Live implementation and results
- 23:48Expanding beyond COVID-19 testing
- 25:53Searching by time vs distance for transport
- 27:20Challenges of public transport data
- 28:23Global public transport coverage
- 29:25Additional transport modes: cycling
- 30:09Multimodal transport search capabilities
- 30:31Workforce planning use cases
- 31:13Emergency response and mobile doctors
- 31:55Healthcare planning at scale
- 32:41Why search relevancy matters in healthcare
- 33:01Future of time-based healthcare search
- 33:43Q&A: Offline pre-calculations
- 34:04Q&A: User feedback and model improvements
- 34:48Q&A: Handling road closures and events
