NPPES Healthcare Organization Change Monitor

Monitor organization lifecycle changes from the newest official CMS NPPES Weekly Version 2 release. The Actor supports a filtered weekly feed and an exact-NPI watchlist while excluding NPI-1 individuals and unnecessary personal fields.

What it delivers

• organization_npi_enumerated — a new organization NPI whose enumeration date falls inside the official weekly period.
• organization_npi_reactivated — an organization NPI whose reactivation date falls inside the official weekly period.
• organization_npi_deactivated — watchlist mode only, and only when the Actor previously confirmed that NPI as an active NPI-2 organization through an exact official NPPES API lookup.

This Actor does not classify weekly-feed deactivations because CMS commonly strips deactivated weekly rows down to NPI and date, leaving no organization/individual discriminator.

Modes

Weekly feed

Use mode: "weeklyFeed" to receive nationwide events or filter by exact two-letter state codes and/or exact NUCC taxonomy codes. Paid runs require a stable monitorId; use the same ID for scheduled weekly runs so replay protection remains continuous.

Watchlist

Use mode: "watchlist" with 1–100 NPIs. New entries are normalized, deduplicated, and checked sequentially against the official NPPES Read API. NPI-1 records, inactive/zero-result lookups, mismatches, throttled responses, and malformed responses fail closed before event delivery.

Free preview

The default input returns exactly 10 deterministic nationwide enumeration/reactivation records from the current official release. It does not accept filters or watchlists, does not write replay state, and is non-billable. Rerunning the same release returns the same 10 event identities.

Recurring use

The Actor discovers the newest official CMS archive on every run. Schedule paid monitors weekly for continuity. A new official release produces new deterministic event IDs and new qualifying paid results. Rerunning the same release with the same monitorId suppresses already delivered events and duplicate charges.

The Actor intentionally processes only the newest release. It does not guess future filenames or backfill missed archives.

Output and privacy

Visible output is restricted to event identity, event type/date, NPI, organization name, one taxonomy code, city/state/ZIP5, official source period/provenance, and observation time. Qualified deactivation output is narrower and omits organization details.

The Actor does not publish NPI-1 individuals, phone numbers, authorized officials, other-name arrays, full street addresses, licenses, endpoints, or raw source rows. Taxonomy descriptions are omitted because the approved weekly source provides taxonomy codes but not descriptions.

NPI lifecycle data does not prove licensure, credentialing, payer enrollment, operation, legitimacy, or buying intent. Do not use the output as the sole basis for consequential healthcare, employment, credit, insurance, or eligibility decisions.

Billing behavior

The production pricing event is qualifying-organization-change. The planned launch price is $0.01 per unique validated event, with Apify platform usage included. Empty, failed, stale, malformed, duplicate, replayed, and excluded results are non-billable.

Billing integrity order:

1. Persist the visible validated event.
2. Persist durable per-monitor delivery and global billing ledger claims.
3. Charge only after both writes succeed.
4. Never retry a charge whose durable global claim already exists.

Automatic apify-default-dataset-item pricing must remain disabled. The Actor fails closed in paid modes until the custom pay-per-event configuration exists.

Official sources

• CMS NPI Files index: https://download.cms.gov/nppes/NPI_Files.html
• CMS NPPES Weekly Version 2 archive discovered from that index
• NPPES Read API v2.1: https://npiregistry.cms.hhs.gov/api/

No authentication, proxy, browser automation, CAPTCHA handling, or access-control workaround is used.

Local development

npm install
npm run build
npm test
apify actor:run

Default runtime memory is 512 MB. The default preview is designed to complete within Apify's five-minute Store QA limit.