Provider Change Events

Description

One row per healthcare-provider change event, unified across 7 federal archive-and-diff sources into a single append-only table with an event_type discriminator. Where the other Healthparse products describe who a provider is, this one tells you what just changed — a new physician enumerated in your territory, a provider newly billing Medicare, an address change, a deactivation, a hospital ownership change, a new lab certificate, a mammography-facility certification change, or a hospital equipment-purchase jump. Every event is observational — a dated record that a specific fact changed between two published federal file versions — never an inference about why.

Events are derived by diffing successive releases of each source file (every release is retained, so diffs are exact and repeatable), and each event carries its source file family, the source_vintage (which file release produced it), and a dedupe_key that is stable across re-ingests.

• Source: CMS (data.cms.gov, download.cms.gov, downloads.cms.gov) and FDA (fda.gov) — 7 file families, per-type table below.
• Refresh cadence: by source — twice-weekly (Tue/Fri), weekly (Wed), and quarterly ingest groups.
• Row count: 297,204 (2026-08-29 export). Weekly volume since launch has run between 35,000 and 85,000 events in normal weeks, depending on which source files were released; the per-type table below is from the same 2026-08-29 export.
• Vintage: 2026-08-28 (most recent ingest in the 2026-08-29 export).
• Event-date range: 2005-06-13 → 2026-08-27, plus one ownership-change row dated 2026-10-31: the CMS CHOW file publishes effective dates, and a change can be filed ahead of its effective date. Registry events carry the enumeration and deactivation dates NPPES itself records (back to 2005); ownership changes run back to 2016; the diff-derived types begin at the 2026-07 baseline.

The 11 event types

All eleven types are emitting. The five NPPES/CHOW/HCRIS-derived types carry dates the source itself publishes (enumeration and deactivation dates back to 2005, ownership effective dates back to 2016, fiscal years back to 2019); the other six began at the July 2026 baseline, when their first two file versions were compared, and build forward from there.

Table: provider_change_events

Snowflake: HEALTHPARSE_DATA.PROVIDER_CHANGE_EVENTS.PROVIDER_CHANGE_EVENTS

details payload by event type (populated types)

// new_enumeration
{ "entity_type": "individual", "taxonomy_code": "390200000X", "parent_org_name": null }
// address_change (old + new full address pair)
{ "old": { "address": "2323 N CENTRAL EXPY # 1000", "city": "RICHARDSON", "state": "TX", "zip": "75080" },
  "new": { "address": "210 S PRESTON RD STE 30", "city": "PROSPER", "state": "TX", "zip": "75078" } }
// deactivation
{ "deactivation_date": "2026-07-07" }
// ownership_change (CHOW)
{ "chow_type": "ACQUISITION/MERGER", "chow_type_code": "AM", "provider_kind": "hospital",
  "buyer":  { "ccn": "150056", "npi": "1144266024", "org": "INDIANA UNIVERSITY HEALTH INC" },
  "seller": { "ccn": "150161", "npi": "1568492916", "org": "INDIANA UNIVERSITY HEALTH NORTH HOSPITAL INC" } }
// capex_jump (dollars by asset class + trigger thresholds)
{ "fy_end_year": 2025, "movable_equipment_purchases": 4286370,
  "prior_year_movable_equipment_purchases": -10000, "total_purchases": 5638633,
  "fixed_equipment_purchases": 383411, "building_purchases": 968852,
  "hit_asset_purchases": null, "threshold_dollars": 1000000, "threshold_multiple": 2 }

The remaining types carry: newly_billing — capabilities/capabilities_added (partb, dme, hha, pmd, hospice); enrollment_pending — provider_kind, nppes_matched; new_lab_certificate / lab_cert_upgrade — old/new certificate type and code; new_mammo_facility — phone, recertified.

Example queries (Snowflake)

-- 1. "New physician in territory": new enumerations + address changes
--    into Texas in the last 30 days.
SELECT "event_date", "event_type", "npi", "entity_name", "city", "state"
FROM HEALTHPARSE_DATA.PROVIDER_CHANGE_EVENTS.PROVIDER_CHANGE_EVENTS
WHERE "state" = 'TX'
  AND "event_type" IN ('new_enumeration', 'address_change')
  AND "event_date" >= dateadd(day, -30, current_date)
ORDER BY "event_date" DESC;

-- 2. Compliance: deactivated NPIs, most recent first (feed this into a
--    credentialing re-check).
SELECT "event_date", "npi", "entity_name",
       PARSE_JSON("details"):"deactivation_date"::date AS deactivated_on
FROM HEALTHPARSE_DATA.PROVIDER_CHANGE_EVENTS.PROVIDER_CHANGE_EVENTS
WHERE "event_type" = 'deactivation'
ORDER BY "event_date" DESC
LIMIT 100;

-- 3. Roll-up velocity: hospital & SNF acquisitions by buyer org, 2024+.
SELECT PARSE_JSON("details"):"buyer":"org"::string AS buyer_org,
       count(*) AS facilities_acquired
FROM HEALTHPARSE_DATA.PROVIDER_CHANGE_EVENTS.PROVIDER_CHANGE_EVENTS
WHERE "event_type" = 'ownership_change'
  AND "event_date" >= '2024-01-01'
GROUP BY 1
ORDER BY facilities_acquired DESC
LIMIT 25;