Data.gov Federal Dataset Catalog — Pharmacy Query
Datadory delivers data gov federal dataset catalog pharmacy query data covering America's federated discovery layer: 552,271 indexed federal, state, county and city collections, with a pharmacy slice that surfaces CMS formulary and dispensing releases, VA pharmacy operations, DC and Connecticut pharmacy licensing, and CDC pharmacy vaccination counts — resolved into typed tables and delivered daily, weekly, or hourly.
What is the Data.gov Federal Dataset Catalog — Pharmacy Query?
The Data.gov Federal Dataset Catalog — Pharmacy Query is the Diversified Support Services shelf's widest net: one search across the U.S. government's federated catalog of 552,271 datasets — federal agencies plus state, county and city contributors — run against the word pharmacy and resolved into a working shortlist. The catalog itself is assembled by GSA's Technology Transformation Services; what Datadory adds is the part researchers actually want: the relevance-ranked pharmacy slice pulled out of unrelated matches, its records typed into a stable schema, publishers named, and the whole thing delivered as tables you can join.
The leading hits read like a cross-section of American pharmacy regulation and operations: OneVA Pharmacy from the Department of Veterans Affairs, CMS's Division of Pharmacy Releases Index, DC pharmacy locations from the Health Regulation and Licensing Administration, Connecticut's annual in-state pharmacy license counts, and the CDC's weekly estimate of influenza vaccinations administered in pharmacies. Of the first hundred results, 39 come from CMS alone, with state portals and the VA filling most of the rest.
What do sample rows look like?
One query, five very different publishers — exactly why the slice needs typing before it joins anything:
title: OneVA Pharmacy
publisher: Department of Veterans Affairs
observed_format: API
title: Division of Pharmacy Releases Index dataset
publisher: Centers for Medicare & Medicaid Services
title: Pharmacy Locations
publisher: Health Regulation and Licensing Administration (DC)
title: In-State Pharmacy Licenses Issued By Year
publisher: State of Connecticut data portal
title: Weekly Cumulative Estimated Number of Influenza Vaccinations Administered
in Pharmacies and Physician Medical Offices, Adults 18 years and older,
United States (ARCHIVED)
publisher: Centers for Disease Control and PreventionA federal health system, a federal payer, a District regulator, a state licensing register and a national disease-surveillance count. One row shape covering all five is the difference between a bookmark list and a dataset.
What fields does each catalog record carry?
Ten verified fields carry every record in the slice — enough to identify the collection, date it, attribute it and know what shape its distributions take:
Where does coverage run, and at what grain?
- Geography: United States throughout — federal publishers (CMS, the VA, the CDC) alongside state portals such as Connecticut's and Washington's, city contributors like Baton Rouge and Austin, and District-level regulators.
- Temporal: a live catalog snapshot, reviewed August 2026. Member collections range from one-off historical files to continuously updated feeds, and at least one leading result — the CDC pharmacy-vaccination series — is explicitly archived, which is why every record ships with its issued and modified dates intact.
- Granularity: dataset-level metadata records, not row-level data. One row per cataloged collection; the rows inside each collection arrive as a separate, scoped pull.
Set against the Datadory catalog average quality score of 7.81, this record scores 6/10 — the ceiling of a discovery index rather than a defect. The slice tells you precisely what exists and who owns it; the strongest finds graduate into dedicated catalog records of their own.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Name the cut when you request the sample: CMS pharmacy releases only, state licensing registers only, or the full relevance-ranked result set. The sample ships first either way; the ongoing feed lands on whatever cadence your models need.
Every delivery travels with the field dictionary above, decoded publisher labels and coverage notes mapped to the agencies you named.
Who uses this data, and for what?
A discovery index earns its keep at the front of a project:
- Competitive landscape mapping — drug-retail strategists establish which agencies publish pharmacy licensing, dispensing and formulary material before commissioning deeper pulls; knowing that CMS contributes 39 of the first hundred results tells you where the volume lives. The pattern is written up on our competitive intel product teams use cases page.
- Regulatory footprint tracking — compliance teams watch state registers (DC pharmacy locations, Connecticut license counts) and pharmacy-benefit-manager oversight filings as new entrants and rule changes land.
- Demand signals for retail clinics — the CDC's weekly estimate of influenza vaccinations administered in pharmacies is a seasonality input for staffing and inventory models.
- Research scoping — market analysts settle scope, geography and years available in one pass; see diversified support services data for market researchers.
- Source triage for data teams — the typed slice works as a seed list for wider collection programs, replacing hand-searching the catalog end to end; see diversified support services data for data scientists.
Market Researchers & Consultants get the landscape mapped before they commit; Competitive Intelligence & Product Teams get the publisher mix behind the market; Data Scientists & Analysts get a typed seed list; and Journalists, Academics & Students get the fastest route from a pharmacy question to the agency that owns it.
Notes and related datasets
Provenance note — the catalog is the U.S. government's federated index, assembled from agency harvests. Datadory's contribution is curation: separating genuine pharmacy-regulation material from local-government billing extracts that merely match the keyword, a distinction the raw result set does not make for you.
Methodology note — ranking follows the catalog's own relevance order at review time, and an archive flag travels with any record that carries one, so an ended series never masquerades as a live feed.
Completeness note — the field dictionary above maps fully to the published record layout, and the 6/10 score is stated plainly because breadth here is the point: no single-agency feed covers fifty states' worth of pharmacy regulators in one schema.
Where to go next — when a find deserves depth, reach for the dedicated records: CMS Medicare Part D Prescribers by Provider and Drug, CMS National Average Drug Acquisition Cost (NADAC), DailyMed Structured Product Labeling Repository, CVS.com — Pharmacy & Health Catalog, and OSHA Enforcement & Injury Data for the workforce-safety side of the same shelf. The full shelf sits on the diversified support services data hub, the ranked view at best diversified support services datasets, and the publisher profile at Data.gov source profile.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
title | string | DCAT dataset title as supplied by the publishing agency. | Monthly Prescription Drug Plan Formulary and Pharmacy Network Information |
description | text | Agency-provided abstract of the dataset contents. | |
publisher.name | string | Publishing organisation, from federal agencies to state and city portals. | Centers for Medicare & Medicaid Services |
issued | date | Date the dataset was first released. | |
modified | datetime | Last update timestamp reported by the agency. | |
keyword | text | Subject keywords used for search matching, e.g. 'pharmacy'. | pharmacy |
distribution[].format | string | File or service format of each distribution: CSV, JSON, XML, ZIP, KML, GeoJSON, ArcGIS GeoServices REST, OGC WMS, Web Page. | text/csv |
distribution[].accessURL / downloadURL | string | Locator recorded on each distribution; resolved by Datadory during acquisition and never surfaced raw. | |
license | string | Rights designation the publishing agency attaches to each catalog record. | |
accessLevel | enum | Visibility classification the assigning agency declares, such as public. | public |
Questions buyers ask
What is the Data.gov Federal Dataset Catalog — Pharmacy Query?
A curated slice of the U.S. government's federated catalog — 552,271 indexed datasets from federal, state, county and city publishers — filtered to pharmacy. It returns typed catalog records naming each collection, its publisher, its dates and its distribution formats, so a researcher sees the whole regulatory landscape in one result set instead of one agency at a time.
How much pharmacy material does the catalog actually hold?
Roughly a hundred-plus pharmacy-related records surface in the relevance-ranked query, with deep pagination beyond. Concentration is lopsided: 39 of the first hundred results come from CMS alone — prescription drug plan formularies, pharmacy network files and the Division of Pharmacy Releases Index — with the VA, the CDC and state portals supplying most of the remainder.
Is this the underlying pharmacy data or a map to it?
A map, deliberately. Each record is a dataset-level metadata document: what the collection contains, who publishes it, when it was issued and modified, and what file shapes it takes. Row-level content arrives as separate scoped pulls once you have chosen which collections matter — which is exactly the decision this slice exists to inform.
Which agencies dominate the pharmacy results?
CMS leads with 39 of the first hundred results, followed by the Department of Veterans Affairs with OneVA Pharmacy, the CDC's pharmacy-vaccination surveillance, and a long tail of state and local publishers — Connecticut's license counts, DC's pharmacy locations, Austin's pharmacy billing extracts. Knowing the mix up front prevents a search that quietly samples only one regulator.
What formats sit underneath the catalog records?
Member collections publish as CSV, JSON, XML and ZIP most often, with KML and GeoJSON for mapped material such as DC pharmacy locations, plus ArcGIS and OGC web services for geographic layers. Distribution formats travel on each record, so a format-constrained pipeline can be planned before any data moves.
Why does this record score 6 out of 10?
Because a discovery index is graded differently from a panel. Its value is breadth — 552,271 collections searchable through one schema — while depth belongs to the individual collections it points to, and result quality varies with how loosely a publisher uses the word pharmacy. Curation closes most of that gap; the score reflects what remains.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.