Health · head-to-head

CMS.gov vs Coronavirus in the UK

CMS.gov

CMS Provider Data Catalog exposes hundreds of Medicare quality, cost, and comparison datasets (hospitals, nursing homes, dialysis facilities, and more) through a DKAN-based metastore and datastore API that returns JSON by default and CSV on request, with no signup required. A live GET against the dataset-listing and datastore query endpoints succeeds with no credentials. A live Origin-header probe against the datastore query endpoint returns no Access-Control-Allow-Origin header on either a GET or an OPTIONS preflight, and since access needed no key at all, the stored 'API Key' auth was corrected to 'None'.

Coronavirus in the UK

The UK Health Security Agency's public data API — successor to the original coronavirus.data.gov.uk service, which now 301-redirects to ukhsa-dashboard.data.gov.uk — serving case, death, hospitalisation, and vaccination figures for COVID-19 alongside other respiratory illnesses like flu and RSV, broken down by UK nation, region, and local authority. No API key is required; the dataset is organised into browsable themes, sub-themes, and topics from the root JSON endpoint, with COVID-19 confirmed live under infectious_disease/respiratory. The stored url is corrected to the current docs entry point since the old one now redirects here. A live GET against api.ukhsa-dashboard.data.gov.uk returns Access-Control-Allow-Origin: *, resolving the stored 'unknown' cors to 'yes'.

CMS.govCoronavirus in the UK
AuthenticationNoneNone
Pricingfreefree
FormatsJSON, CSVJSON
CORSnoyes
HTTPSYesYes

Coronavirus in the UK supports CORS, while CMS.gov doesn't — pick Coronavirus in the UK for direct browser calls.

More comparisons