# Medicare Account Change Feed (`dyalaalsharif/my-actor`) Actor

Detect verified CMS Medicare enrollment and revalidation changes between monthly public datasets. Get organization-level changes with NPI, specialty, due dates, and provider-reassignment context in a ready-to-use dataset. Independent product; not affiliated with CMS or HHS.

- **URL**: https://apify.com/dyalaalsharif/my-actor.md
- **Developed by:** [Dyala Alsharif](https://apify.com/dyalaalsharif) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 medicare account changes

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

**Medicare Account Change Feed** tracks verified **CMS Medicare enrollment and revalidation changes** between monthly public datasets.

Instead of manually comparing millions of Medicare enrollment records, credentialing, provider-network, revenue-cycle, and healthcare data teams can retrieve organization-level changes enriched with **NPI, Medicare Enrollment ID, specialty, due-date, and provider-reassignment context** in a ready-to-use dataset.

**Current edition:** September 2026 sample\
**Available records:** 20 verified account changes\
**Detected event:** `NEW_UPCOMING_DATE_SURFACED`\
**Price:** $0.10 per returned account change

### Quick start

Choose the starting record and number of results in **Input**, then run the Actor. Results are returned as a structured dataset ready for review, export, or API use.

### What does this Actor detect?

The current edition focuses on a specific verified event:

**NEW\_UPCOMING\_DATE\_SURFACED**

This means an enrollment had no populated revalidation due date in the August 2026 CMS snapshot and shows an upcoming due date of **February 28, 2027** in the September 2026 snapshot.

The Actor does not claim that an organization needs a vendor, is actively shopping for credentialing services, or intends to purchase anything.

It reports a documented change in public Medicare enrollment data.

### What information is included?

Each returned account change contains structured fields such as:

- Organization name
- State
- Medicare Enrollment ID
- Detected event
- Previous due-date status
- Current due date
- Provider type
- Number of NPIs associated with the due enrollment
- Enrollment specialties
- Reassignment relationship count
- Unique reassignment NPIs
- Unique reassignment enrollments
- Reassignment specialty count
- Multi-employer relationship count
- Maximum employer associations
- CMS group reassignment count
- Evidence describing the compared CMS snapshots

### Input

#### Start from account number

Choose which record number to start from.

Current range:

**1 to 20**

Example:

```json
{
  "startFrom": 6,
  "maxResults": 5
}
```

This returns records **6 through 10**, subject to the available inventory and maximum charge limit.

#### Number of account changes

Choose how many account changes you want returned.

Current range:

**1 to 20**

Examples:

- `startFrom: 1`, `maxResults: 5` → records 1–5
- `startFrom: 6`, `maxResults: 5` → records 6–10
- `startFrom: 11`, `maxResults: 5` → records 11–15
- `startFrom: 16`, `maxResults: 5` → records 16–20

### Example output

```json
{
  "success": true,
  "product": "Medicare Account Change Feed",
  "edition": "September 2026 sample",
  "target_event": "Blank -> 2027-02-28",
  "account_change_number": 6,
  "account_change": {
    "account": "Eyecare Associates, Inc.",
    "state": "AL",
    "medicare_enrollment_id": "O20040823000825",
    "event": "NEW_UPCOMING_DATE_SURFACED",
    "detected_in": "September 2026",
    "previous_due_date": "BLANK / NONE",
    "current_due_date": "2027-02-28",
    "provider_type": "Non-DME Part B",
    "due_enrollment_npis": 34,
    "reassignment_relationships": 89,
    "reassignment_unique_npis": 89,
    "reassignment_specialty_count": 1
  },
  "source": "Derived from publicly available CMS data."
}
```

### Pricing

This Actor uses **Pay Per Event** pricing.

Each returned **Medicare Account Change** costs:

**$0.10 per account change**

Examples:

- 1 result = $0.10
- 5 results = $0.50
- 10 results = $1.00
- 20 results = $2.00

Platform usage is currently included in the Actor pricing.

### Data sources and methodology

The current edition is derived from publicly available Medicare enrollment data published by the U.S. Centers for Medicare & Medicaid Services (CMS).

The underlying process compares monthly CMS snapshots, verifies changes at the Medicare Enrollment ID level, groups account-level information, and enriches selected records with public Medicare reassignment data where applicable.

The current September 2026 sample was created from August 2026 and September 2026 CMS snapshots.

The current 20-record inventory was selected by verified due-enrollment NPI footprint.

This is **not** a sales score, purchase-intent score, or prediction of commercial opportunity.

### Important interpretation notes

`due_enrollment_npis` and `reassignment_unique_npis` measure different scopes and should not be treated as interchangeable.

Some provider types may legitimately have zero reassignment relationships.

A surfaced Medicare revalidation date does not establish that an organization needs outside assistance or intends to hire a credentialing, enrollment, consulting, or revenue-cycle vendor.

Users should independently evaluate how the information applies to their own workflow.

### Potential use cases

The feed can support workflows such as:

- Medicare enrollment monitoring
- Credentialing and revalidation research
- Provider-network research
- Revenue-cycle market intelligence
- Organization-level Medicare account monitoring
- Internal business-development research
- Public healthcare-data analysis

### Current edition limitations

This is currently a **20-account September 2026 sample edition** designed to validate the account-change delivery model.

It is not currently a live national Medicare monitoring service, and running the Actor does not trigger a fresh CMS-wide comparison.

Future editions may expand the available inventory, event types, filters, and monthly coverage.

### Independence and disclaimer

This is an independent data product.

It is **not affiliated with, endorsed by, sponsored by, certified by, or operated by CMS or the U.S. Department of Health and Human Services (HHS).**

Results are derived from publicly available CMS data and may reflect limitations, corrections, delays, or changes present in the source datasets.

Users are responsible for independently verifying information before making operational, commercial, compliance, or business decisions.

# Actor input Schema

## `startFrom` (type: `integer`):

Enter a record number from 1 to 20. Use 1 to start from the beginning. Example: entering 6 starts with account change #6.

## `maxResults` (type: `integer`):

Choose how many verified account changes to return (1 to 20). Each returned result costs $0.10. Example: start at 6 and request 5 results to receive records 6 through 10.

## Actor input object example

```json
{
  "startFrom": 1,
  "maxResults": 5
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dyalaalsharif/my-actor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("dyalaalsharif/my-actor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call dyalaalsharif/my-actor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dyalaalsharif/my-actor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/sbVjP2aqL4qKGyvj7/builds/21Whs7L1wLoAkq7UX/openapi.json