# EMR / EHR Tech-Stack Detector (`signalserver/emr-ehr-detector`) Actor

Detects the EMR/EHR or RIS a medical practice runs by scanning its own website: patient-portal links, login pages, booking flows. Feed it practice URLs, get back the incumbent system, confidence and evidence per practice. Covers 30+ ambulatory EMR and radiology RIS vendors.

- **URL**: https://apify.com/signalserver/emr-ehr-detector.md
- **Developed by:** [Joep van Acht](https://apify.com/signalserver) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $500.00 / 1,000 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

## EMR / EHR Tech-Stack Detector

Detects which **EMR/EHR or RIS/PACS** a medical practice runs by crawling the
practice's own website — patient-portal links, login pages, booking flows —
and matching vendor-hosted domains and HTML fingerprints.

Covers the major ambulatory EMRs (athenahealth, Epic/MyChart, eClinicalWorks,
NextGen, ModMed, Greenway, Veradigm/Allscripts, Practice Fusion, AdvancedMD,
Kareo/Tebra, DrChrono, Elation, CareCloud, Cerner, MEDITECH...) plus
radiology RIS/PACS vendors (eRAD, RamSoft, MedInformatix, Intelerad, AbbaDox,
Fujifilm Synapse, Novarad, Exa and more).

### Input

- **websites** — list of practice domains/URLs, or
- **items** — list of `{company, website}` objects (company name carried to output)
- **maxSubpages** — portal-likely subpages crawled per site (default 5)
- **concurrency** — parallel sites (default 10)
- **proxyConfiguration** — optional Apify Proxy

### Output (dataset, one row per site)

`company · website · final_url · top_emr · version · portal_host ·
all_detections · confidence (high/medium) · evidence · categories ·
account_type · pages_crawled · status`

`high` = vendor-hosted portal domain found (structural detection).
`medium` = vendor references in on-site text.

### Detection approach

Structural-first: the patient-portal link **domain** is the strongest tell,
so every anchor/script/iframe/form host is resolved and matched against the
fingerprint set — body-text mentions only ever reach `medium` confidence.
One bad site never kills the run; every row gets a status.

# Actor input Schema

## `startUrls` (type: `array`):

The websites of the medical practices / companies to scan. Paste URLs or domains, use Bulk edit to paste a whole list, upload a file, or link a Google Sheet.

## `proxyConfiguration` (type: `object`):

Optionally route requests through Apify Proxy (helps with IP-blocked hosts; uses proxy traffic).

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://premier-podiatry.com"
    },
    {
      "url": "https://kraffeye.com"
    },
    {
      "url": "https://cocortho.com"
    },
    {
      "url": "https://waynepodiatry.com"
    },
    {
      "url": "https://precisionimagingcenters.com"
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `detections` (type: `string`):

One row per scanned practice: detected EMR/RIS, confidence, evidence, portal host and crawl status.

# 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 = {
    "startUrls": [
        {
            "url": "https://premier-podiatry.com"
        },
        {
            "url": "https://kraffeye.com"
        },
        {
            "url": "https://cocortho.com"
        },
        {
            "url": "https://waynepodiatry.com"
        },
        {
            "url": "https://precisionimagingcenters.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("signalserver/emr-ehr-detector").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 = { "startUrls": [
        { "url": "https://premier-podiatry.com" },
        { "url": "https://kraffeye.com" },
        { "url": "https://cocortho.com" },
        { "url": "https://waynepodiatry.com" },
        { "url": "https://precisionimagingcenters.com" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("signalserver/emr-ehr-detector").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 '{
  "startUrls": [
    {
      "url": "https://premier-podiatry.com"
    },
    {
      "url": "https://kraffeye.com"
    },
    {
      "url": "https://cocortho.com"
    },
    {
      "url": "https://waynepodiatry.com"
    },
    {
      "url": "https://precisionimagingcenters.com"
    }
  ]
}' |
apify call signalserver/emr-ehr-detector --silent --output-dataset

```

## MCP server setup

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

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/ZupH8MfmXsTNbAiYC/builds/Lm4XZMAJuKED3d9sZ/openapi.json