ONC Health IT Dashboard and Open Data

The federal government's own measurement of American health IT, opened up as rows. The Office of the National Coordinator for Health IT - now operating under ASTP - publishes four searchable content types on its research portal: interactive Dashboards, Data Briefs built from national surveys, Quick Stats visualizations, and raw Datasets. Topic filters span Adoption, Interoperability, Information Blocking, Patient Access to Health Records, Public Health, Pharmacy and PDMP, TEFCA, and Historical Programs.

The named briefs read like a sixteen-year natural experiment: Non-Federal Acute Care Hospital Electronic Health Record Adoption, 2008-2024, Office-based Physician Electronic Health Record Adoption, 2008-2024, and Individuals' Access and Use of Patient Portals and Smartphone Health Apps, 2024. Behind the dashboards sit roughly twenty named tabular series - hospital adoption, physician adoption, EHR developer counts, Meaningful Use acceleration scorecards, Promoting Interoperability linkage files, e-prescribing geographies, REC KPI masterfiles, state privacy and consent policies, hospital TEFCA network participation.

It is one of six datasets Datadory catalogs in health care technology, and the only one measuring the incentive programs that digitized US medicine. Datadory packages those series as normalized rows - dictionary below, sample rows beneath - delivered daily, weekly, or hourly. [Get a sample of this dataset](#request) and judge the columns.

Two row shapes land in your warehouse. First, the state-year adoption row, exactly as documented for Maryland, 2015:

region                            : Maryland          region_code : MD
period                            : 2015
pct_hospitals_cehrt               : 1
pct_hospitals_basic_ehr_notes     : 0.95
pct_hospitals_send_clinical_info  : 0.93
pct_hospitals_receive_clinical_info : 0.67
pct_hospitals_find_clinical_info  : 0.86
pct_hospitals_patients_vdt        : 0.84

Second, the vendor row from the EHR developer-counts series:

developer                         : 3M Health Information Systems
provider_type                     : hospital          product_type : Commercial
program_year                      : 2011
tot_provs_report_developer        : 1

Read them as two halves of one story. The state row measures outcomes: every Maryland hospital on certified EHR technology by 2015, with view-download-transmit patient access already at 84 percent. The vendor row measures the market underneath - who sold the technology, to which provider segment, in which program year. The clinician file adds a third shape at provider level, keyed by NPI, CHPL ID and cleaned CEHRT ID so a clinician row joins to the exact certified product behind it.

Ten documented field groups anchor the dictionary below, verified against the portal's published series documentation during research. Survey series carry percentage measures; the developer-counts and clinician-linkage series carry entity rows with identifier keys. Series-specific measures outside these ten groups - TEFCA participation flags, state privacy-policy attributes, PDMP checking rates - ride on the same regional and period keys and ship on request rather than being promised in every row.

Geography - United States throughout. The acute care hospital adoption series covers all 50 states plus territories across more than fifteen annual periods, and several series add county detail below the state cut - the e-prescribing series is published at both county and state level. National totals sit alongside the regional cuts wherever the underlying survey supports them.

Temporal - the full incentive-program arc, 2008 through 2026 releases. Hospital and physician adoption briefs run 2008-2024; the patient portal and smartphone health app brief covers 2024; the Promoting Interoperability clinician file covers program years 2019-2024; the developer-counts series reaches back to 2011. Historical Program filters preserve the Meaningful Use era scorecards so pre-2015 baselines stay queryable.

Granularity - three tiers. Percentage measures per state or county per year on the survey series; developer-level rows in the vendor-counts series; provider-level rows in the clinician file. That split is why the same contract serves a policy analyst tracking a national curve and an analyst counting a specific vendor's installed base.

API, files, or your warehouse. Daily, weekly, or hourly.

Hourly suits event windows - an information-blocking compliance deadline or a TEFCA milestone week, when the narrative around these measures moves fastest. Daily suits policy tracking and competitive monitoring of the EHR vendor landscape, where developer counts shift quarter to quarter. Weekly suits benchmarking studies where the trend line matters more than any single release. Because every refresh reuses the same field dictionary, your join keys hold steady whichever cadence you choose: region and period for the survey series, developer and program year for the vendor series, NPI and CHPL ID for the clinician file.

• Health IT market sizing - the developer-counts series turns who sells certified EHRs into counted rows: developer names, provider segments, product types and providers-reporting counts by program year, the demand-side complement to vendor marketing claims; mapped to the market sizing use case.
• Policy and incentive-program evaluation - the 2008-2024 hospital and physician arcs measure whether the Meaningful Use and Promoting Interoperability programs moved adoption, with historical scorecards preserving each era's own metrics; see the citation-grade research use case.
• Interoperability benchmarking - send, receive, find and integrate composites by state quantify which regions actually exchange records rather than merely bought software; hospital TEFCA network participation adds the network-affiliation layer.
• Digital health equity studies - the 2024 patient portal and smartphone health app brief measures patient-side access, the consumer half of the adoption story most vendor datasets never touch.
• Provider-network mapping - NPI, CHPL ID and CEHRT ID keys let modelers join clinicians to certified products at scale, the linkage layer for network and affiliation graphs; paired with clinical corpora like MIMIC-IV.
• Regulatory-change monitoring - state privacy and consent law policy series track the patchwork governing record sharing jurisdiction by jurisdiction.

Journalists and academics get the citable federal baseline - sixteen years of adoption and interoperability measurement with named briefs behind every figure. Market researchers and consultants size the health IT vendor landscape from counted provider relationships instead of press releases. Investors and quants read developer-count shifts and adoption curves as demand signals for the public health IT vendors they cover. Data scientists and ML engineers get percentage panels with stable region-period keys ready for panel models, plus identifier-rich provider rows for linkage work. Developers building data products get a typed dictionary whose keys - NPI, CHPL ID, CEHRT ID - connect to the wider health data ecosystem. Policy analysts get the program-evidence trail without assembling it from PDFs.

Three things worth scoping upfront. First, temporal windows differ by series - adoption briefs end at 2024 while program-era files close on different years - so name the window you need when requesting a time series. Second, county-level detail exists on some series and stops at state level on others; confirm geography before building a sub-state design. Third, the source blends narrative briefs, dashboards and row-level series; what Datadory packages is the row-level data, with the briefs serving as interpretation rather than columns - if your project needs the narrative layer too, say so and it ships alongside the tables.