# CLIA Laboratory Openings & Status Change Leads (`scrapesignal_labs/clia-laboratory-change-leads`) Actor

Compare official quarterly CMS laboratory files to find new CLIA labs and changes in certificates, status, name, address, ownership profile, and test volume.

- **URL**: https://apify.com/scrapesignal\_labs/clia-laboratory-change-leads.md
- **Developed by:** [ScrapeSignal Labs](https://apify.com/scrapesignal_labs) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 laboratory 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## CLIA Laboratory Openings & Status Change Leads

Find laboratories entering or changing the regulated US clinical-testing market. This Actor automatically discovers the newest two quarterly CMS Provider of Services files for Clinical Laboratories, compares them by CLIA number, and surfaces new labs plus changes in certificate type, compliance or termination status, name, address, phone, facility profile, and reported test volume.

This is change intelligence rather than another static lab directory. Each result includes current and prior fields, an opportunity score, the two exact CMS source files, and a stable CLIA identifier for deduplication and CRM updates.

### Built for

- laboratory equipment, reagents, diagnostics, LIS, cybersecurity, and compliance sales
- staffing, courier, waste, calibration, maintenance, billing, insurance, and consulting providers
- healthcare market intelligence, territory design, diligence, and data enrichment
- scheduled new-lab alerts and AI or CRM workflows

### Signals

- new CLIA laboratory in the current quarterly file
- certificate-type change
- compliance or program-termination change
- address or state change
- facility-name change
- phone, facility type, control type, classification, or test-volume change
- optional removal from the current file

### Example input

```json
{
  "changeTypes": ["new-lab", "certificate-change", "address-change"],
  "states": ["CA", "AZ", "NV"],
  "maxItems": 1000
}
```

### Output highlights

CLIA number, current and prior facility names and addresses, phone/fax, current and prior certificate and status codes, certification dates, facility/control/classification codes, application dates, test volume, selected accreditation flags, change types, score, and links to both quarterly files.

### Source and caveats

The Actor uses the official CMS data catalog entry titled **Provider of Services File – Clinical Laboratories**, discovered through [data.cms.gov](https://data.cms.gov/data.json). CMS files use coded fields and are released periodically. A new row or changed value can represent a new operation, reactivation, ownership/reporting change, correction, recertification, or administrative update—not necessarily a newly constructed laboratory.

Verify important decisions with the laboratory, CMS/CLIA resources, state agencies, accrediting organizations, and appropriate compliance professionals. Do not interpret the lead score as a quality rating or clinical judgment.

# Actor input Schema

## `changeTypes` (type: `array`):

Select new-lab, certificate, status, location, name, profile, or removal signals.

## `states` (type: `array`):

Two-letter state codes. Empty means nationwide.

## `certificateTypes` (type: `array`):

Optional exact CMS codes.

## `facilityQuery` (type: `string`):

Case-insensitive search across facility name, city, and CLIA number.

## `maxItems` (type: `integer`):

Stop after saving this many highest-scoring laboratory changes.

## `currentCsvUrl` (type: `string`):

Advanced: official CMS CSV URL. Set both custom URLs together.

## `previousCsvUrl` (type: `string`):

Advanced: official CMS CSV URL. Set both custom URLs together.

## Actor input object example

```json
{
  "changeTypes": [
    "new-lab",
    "certificate-change",
    "status-change",
    "address-change",
    "name-change",
    "profile-change"
  ],
  "states": [],
  "certificateTypes": [],
  "facilityQuery": "",
  "maxItems": 500,
  "currentCsvUrl": "",
  "previousCsvUrl": ""
}
```

# Actor output Schema

## `dataset` (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("scrapesignal_labs/clia-laboratory-change-leads").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("scrapesignal_labs/clia-laboratory-change-leads").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 scrapesignal_labs/clia-laboratory-change-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesignal_labs/clia-laboratory-change-leads"
        }
    }
}

```

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/SB6fY9blYCj7qjmcb/builds/ex0hB5cWGuEW4d11B/openapi.json