CMS: Provider API
summary
CMS builds a scheduling pipeline that turned community work into a working feed for vaccines.gov within weeks, using Bulk FHIR files that publish three core resources Location/Schedule/Slot. Implementation details: publishers push bulk CSV/NDJSON, aggregators must handle geocoding, rate limits, capacity semantics and two timestamps, and a centralized publishers registry on GitHub solves discovery. Key tradeoffs are slot granularity versus booking reliability and optional language tags; the prototype is live and used successfully for COVID vaccine scheduling.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:50Welcome
- 1:20Introductions
- 2:44Why are we here today
- 3:09Access
- 3:56Standards
- 5:03Accessibility
- 5:39Consumer Choice
- 6:17Federal Initiatives
- 7:22Users dont need API
- 7:34Patient Access API
- 8:01Scheduling API
- 8:30Community Effort
- 13:07Scheduling API User Needs
- 15:14Open Access
- 16:46Finding Data
- 22:43Data granularity
- 27:39Optional features
- 32:20Language support
- 34:43QA
related talks
26mUsing APIs to Transform the way CMS Shares Medicare Claims Data
13mLightning Talks - Leveraging APIs to Transform Healthcare
49mFHIR Bulk Data API and what's new in v2
22mAPI’s in public healthcare – case Health Village
42mBuilding on Cerner with SMART on FHIR
33mHealthcare Interoperability : From Buzzword to APIs
26mData with a mission: a COVID-19 API case study
42mAll of Us / Sync for Science