📅 Book a 30-min Demo📞 Call/text (571) 293-0242
Connector · Electronic health record (EHR)

Veradigm MCP Server & Agent Skill

Last updated

ibl.ai publishes a free Veradigm agent skill: a SKILL.md that teaches an AI agent to read Veradigm data and expose it as an MCP tool. Download it, connect your own Veradigm credentials, and run the agent on ibl.ai Agentic OS, where you own all the code and the data.

Veradigm EHR is an ambulatory electronic health record from Veradigm (formerly Allscripts). It holds patient demographics, problems, medications, allergies, results, encounters, procedures and clinical documents.

What is the Veradigm API, and what can an agent read from it?

The FHIR R4 API is read-only and follows USCDI, with provider and patient endpoints and Bulk FHIR $export on Group. The proprietary Unity API supports reads and writes for deeper Veradigm EHR integration.

  • API: Veradigm FHIR API (R4) and Unity API, through the Veradigm Connect developer program (Mixed)
  • Access: Partner or license program
  • Base URL: https://fhir.fhirpoint.open.allscripts.com/fhirroute/open/{organizationId} (patient endpoints in the Veradigm Endpoint Directory); capability statement at [FHIR path]/metadata
  • Authentication: SMART App Launch 2.0 (OAuth 2.0 authorization code); SMART Backend Services (JWT)

Open accounts at developer.veradigm.com are free and cover FHIR APIs and sandboxes. Unity API and EHR launch need a paid Integrator tier. Apps are approved for production, then each customer organization licenses them.

Standalone and EHR launch follow SMART App Launch 2.0.0 and OpenID Connect. System apps use client_credentials with a single-use JWT client assertion (2 to 20 minute expiry) and a JWKS endpoint the developer hosts.

What can an agent read from Veradigm?

  • Patients — Patient read and search on provider or patient FHIR endpoints.
  • Results and vitals — Observation and DiagnosticReport.
  • Problems and encounters — Condition, Encounter and Procedure.
  • Medications — Medication-related resources (MedicationRequest and related types).
  • Clinical documents — DocumentReference, with Provenance on request.
  • Population exports — Bulk FHIR: [FHIR path]/Group/[GROUP_ID]/$export for System apps; poll the Content-Location URL.

What can an agent write to Veradigm?

This skill only reads Veradigm data; it documents no write calls, so an agent built on it cannot change a Veradigm record.

Limits: Bulk $export is asynchronous: poll the Content-Location URL and respect retry-after; polling faster returns HTTP 429. Completed file packages expire after a period and can be downloaded more than once before then.

Records are HIPAA protected health information (PHI). Only System apps may run bulk exports, and each customer organization decides whether to license an app.

How do I connect Veradigm to an AI agent over MCP?

As of October 2026 we found no MCP server published by Veradigm itself.

The practical path is to host a small MCP server that wraps the Veradigm FHIR API (R4) and Unity API, through the Veradigm Connect developer program, or to give the agent the calls directly with the SKILL.md below.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

  1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
  2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
  3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

Veradigm supports per-user OAuth, so the server can use auth_type=oauth2 with auth_scope=user: each person connects their own Veradigm account in the chat the first time the agent needs it.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the Veradigm agent skill do?

The Veradigm skill is one SKILL.md file named iblai-connect-veradigm. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the Veradigm SKILL.md

Save it as .claude/skills/iblai-connect-veradigm/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

$ npx skills add iblai/vibe --all

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against Veradigm's documentation on October 20, 2026. Test it against your own Veradigm setup before you rely on it.

What can I ask a Veradigm agent to do?

  • “Pull the problem list and current medications for this patient from Veradigm EHR.”
  • “Start a bulk export for our attributed patient group and tell me when files are ready.”
  • “Show this patient's lab results from the last six months.”
  • “List the clinical documents filed for this patient this year.”

How do I run a Veradigm agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the Veradigm MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

Which ibl.ai agents work with Veradigm data?

Which ibl.ai platform skills does a Veradigm agent use?

What else should I know before connecting Veradigm to an AI agent?

Is there an official Veradigm MCP server?

Not that we found as of October 20, 2026: Veradigm documents the Veradigm FHIR API (R4) and Unity API, through the Veradigm Connect developer program, not an MCP server of its own.

The SKILL.md on this page gives an agent the integration directly, and any MCP server you host can be registered on ibl.ai.

Who can get Veradigm API credentials?

Open accounts at developer.veradigm.com are free and cover FHIR APIs and sandboxes. Unity API and EHR launch need a paid Integrator tier. Apps are approved for production, then each customer organization licenses them.

Does Veradigm data leave my infrastructure when an ibl.ai agent uses it?

On ibl.ai, you own all the code and the data. Self-hosted in your cloud or data center, the agent, its MCP connections and its conversation logs stay inside your perimeter.

Because the platform is model-agnostic, you can point the agent at a model you host, so Veradigm records need not reach a third-party model provider.

Is the Veradigm agent skill free to use?

Yes. The SKILL.md is a free download with no sign-up. It assumes you already have Veradigm credentials, and your agreement with Veradigm still governs how you use its API.

Which other data sources can an AI agent connect to alongside Veradigm?

Which other Healthcare systems have a connector?

Every connector, grouped by sector, is on the connectors hub.