# 💊 DailyMed Drug Label Section Change Monitor (`snuggly_beanie_970/dailymed-label-section-change-monitor`) Actor

Detect exact version-to-version changes in DailyMed boxed warnings, indications, contraindications, dosage, interactions, warnings, adverse reactions and supply sections.

- **URL**: https://apify.com/snuggly\_beanie\_970/dailymed-label-section-change-monitor.md
- **Developed by:** [Ilia](https://apify.com/snuggly_beanie_970) (community)
- **Categories:** Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 drug label section results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## 💊 DailyMed Drug Label Section Change Monitor

Turn official DailyMed SPL version history into review-ready drug-label changes. Instead of returning a list of recently published labels, this Actor downloads the current and previous structured label, compares safety-critical sections, and shows exactly which text was added or removed.

### 📤 What you get

- version-to-version changes for boxed warnings, indications, dosage, contraindications, warnings, interactions, adverse reactions, and supply/storage;
- full current and previous section text plus sentence-level additions and removals;
- SHA-256 fingerprints for repeatable monitoring and audit trails;
- DailyMed Set ID, SPL versions, publication history, NDCs, and direct official label/XML/version-download links;
- search by generic or brand name, exact Set ID, publication date, or boxed-warning status.

### Example input

```json
{
  "drugNames": ["KEYTRUDA"],
  "publishedSince": "2026-01-01",
  "comparePreviousVersion": true,
  "emitUnchangedSections": false,
  "maxLabels": 10
}
```

Each dataset row is one meaningful section result, so a label that changed its boxed warning and adverse-reactions text produces two independently usable records. Run the same input on an Apify Schedule to watch a product, sponsor portfolio, or therapeutic area.

### 🗂️ Data source

The Actor uses the U.S. National Library of Medicine DailyMed REST API and official archived SPL ZIP files. Every result links back to the source label and retains both version numbers.

### 💰 Pricing

Pay only for section results written to the dataset. Empty searches and sections filtered as unchanged do not create result charges.

### 📥 Complete input reference

| Field | Type | Default | Purpose |
|---|---|---:|---|
| `drugNames` | array | `["KEYTRUDA"]` | Search one or more generic or brand names. |
| `setIds` | array | `[]` | Optionally monitor exact SPL Set IDs. |
| `publishedSince` | string | `"2026-01-01"` | Only labels published on or after this YYYY-MM-DD date. |
| `boxedWarningOnly` | boolean | `false` | Restrict name searches to labels containing an FDA boxed warning. |
| `comparePreviousVersion` | boolean | `true` | Download the prior archived SPL and calculate section-level changes. |
| `emitUnchangedSections` | boolean | `false` | Also store monitored sections whose normalized text is identical between versions. |
| `maxLabels` | integer | `10` | Maximum distinct DailyMed labels to inspect in one run. |

### 📤 Complete output reference

The default dataset is exportable as JSON, CSV, Excel, XML or RSS. Fields remain stable for scheduled runs and API integrations.

| Field | Type |
|---|---|
| `recordType` | string |
| `setId` | string |
| `drugTitle` | string |
| `publishedDate` | string |
| `currentVersion` | integer |
| `previousVersion` | integer / null |
| `sectionCode` | string |
| `sectionName` | string |
| `changeType` | string |
| `currentSectionText` | string |
| `previousSectionText` | string / null |
| `addedText` | array |
| `removedText` | array |
| `addedTextPreview` | string / null |
| `removedTextPreview` | string / null |
| `currentFingerprint` | string |
| `previousFingerprint` | string / null |
| `versionHistory` | array |
| `ndcs` | array |
| `officialLabelUrl` | string |
| `currentXmlUrl` | string |
| `previousZipUrl` | string / null |
| `scrapedAt` | string |

### 🔌 API & integrations

Run this Actor from the Apify Console, API, CLI, MCP, Make, Zapier or n8n. Replace the Actor identifier and token in this template:

```bash
curl -X POST "https://api.apify.com/v2/acts/dailymed-label-section-change-monitor/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

Results are stored in the run's default dataset and can be forwarded with Apify webhooks or scheduled Tasks.

### 🔎 Search keywords

DailyMed Drug Label Section Change Monitor, dailymed, drug, label, section, change, monitor, Apify Actor, scraper API, structured data, scheduled monitor, automation.

# Actor input Schema

## `drugNames` (type: `array`):

Search one or more generic or brand names.

## `setIds` (type: `array`):

Optionally monitor exact SPL Set IDs.

## `publishedSince` (type: `string`):

Only labels published on or after this YYYY-MM-DD date.

## `boxedWarningOnly` (type: `boolean`):

Restrict name searches to labels containing an FDA boxed warning.

## `comparePreviousVersion` (type: `boolean`):

Download the prior archived SPL and calculate section-level changes.

## `emitUnchangedSections` (type: `boolean`):

Also store monitored sections whose normalized text is identical between versions.

## `maxLabels` (type: `integer`):

Maximum distinct DailyMed labels to inspect in one run.

## Actor input object example

```json
{
  "drugNames": [
    "KEYTRUDA"
  ],
  "setIds": [],
  "publishedSince": "2026-01-01",
  "boxedWarningOnly": false,
  "comparePreviousVersion": true,
  "emitUnchangedSections": false,
  "maxLabels": 10
}
```

# 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("snuggly_beanie_970/dailymed-label-section-change-monitor").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("snuggly_beanie_970/dailymed-label-section-change-monitor").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 snuggly_beanie_970/dailymed-label-section-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snuggly_beanie_970/dailymed-label-section-change-monitor"
        }
    }
}
```

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/oeApqFESQLJySmWzI/builds/Hb3vJOnEhS8yDbFIt/openapi.json