Connector Β· Electronic health record (EHR)

MEDITECH Expanse MCP Server & Agent Skill

Last updated

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

MEDITECH Expanse is an electronic health record used by hospitals and health systems. It holds patient demographics, encounters, problems, allergies, medications, results, immunizations, care plans and clinical documents.

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

View-only US Core FHIR R4 APIs for USCDI data and patient-access FHIR APIs (DSTU2 and R4). Greenfield Workspace offers a sandbox against a real MEDITECH EHR with interactive docs; FHIR scheduling APIs are listed for Expanse customers.

  • API: MEDITECH Interoperability Services: US Core FHIR R4 (tested in Greenfield Workspace) (FHIR R4)
  • Access: Issued by your administrator
  • Base URL: https://{organization-host}/v1/uscore/R4 (per organization; listed in MEDITECH's brands bundle at https://fhir-apis.meditech.com/v1/brands)
  • Authentication: SMART on FHIR (OAuth 2.0 authorization code); OAuth 2.0 client credentials

Developers, vendors and MEDITECH customers can register for Greenfield Workspace to test. It is not connected to customer environments, so production access is arranged with each MEDITECH customer organization.

Data exchange is protected by SMART on FHIR and OAuth 2.0. A live customer server lists authorization_code, client_credentials and refresh_token grants at {host}/oauth/token, with client secret or private_key_jwt client auth.

What can an agent read from MEDITECH Expanse?

  • Patients β€” Patient read and search (US Core R4).
  • Results and vitals β€” Observation and DiagnosticReport read and search.
  • Problems and allergies β€” Condition and AllergyIntolerance read and search.
  • Medications and immunizations β€” MedicationRequest and Immunization read and search.
  • Clinical documents β€” DocumentReference read and search.
  • Encounters and procedures β€” Encounter and Procedure read and search.

What can an agent write to MEDITECH Expanse?

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

Records are HIPAA protected health information (PHI). The US Core API is view-only; apps reach a hospital's data only through that MEDITECH customer's endpoint and approval.

How do I connect MEDITECH Expanse to an AI agent over MCP?

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

The practical path is to host a small MCP server that wraps the MEDITECH Interoperability Services: US Core FHIR R4 (tested in Greenfield Workspace), 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.

MEDITECH Expanse supports per-user OAuth, so the server can use auth_type=oauth2 with auth_scope=user: each person connects their own MEDITECH Expanse 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 MEDITECH Expanse agent skill do?

The MEDITECH Expanse skill is one SKILL.md file named iblai-connect-meditech. 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 MEDITECH Expanse SKILL.md

Save it as .claude/skills/iblai-connect-meditech/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 MEDITECH's documentation on October 20, 2026. Test it against your own MEDITECH Expanse setup before you rely on it.

What can I ask a MEDITECH Expanse agent to do?

  • β€œPull the active medication list for this patient from MEDITECH.”
  • β€œShow this patient's immunization history.”
  • β€œList lab results from the last 30 days and highlight abnormal values.”
  • β€œSummarize the problems and allergies on file before tomorrow's visit.”

How do I run a MEDITECH Expanse agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the MEDITECH Expanse 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 MEDITECH Expanse data?

Which ibl.ai platform skills does a MEDITECH Expanse agent use?

  • /iblai-api-agent-mcp β€” MCP connectors for ibl.ai agents, end to end
  • /iblai-vibe-agent-mcp β€” Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,…
  • /iblai-api-agent-tool β€” Enable or disable an ibl.ai agent's tools via the platform API

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

Is there an official MEDITECH Expanse MCP server?

Not that we found as of October 20, 2026: MEDITECH documents the MEDITECH Interoperability Services: US Core FHIR R4 (tested in Greenfield Workspace), 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 MEDITECH Expanse API credentials?

Developers, vendors and MEDITECH customers can register for Greenfield Workspace to test. It is not connected to customer environments, so production access is arranged with each MEDITECH customer organization.

Does MEDITECH Expanse 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 MEDITECH Expanse records need not reach a third-party model provider.

Is the MEDITECH Expanse agent skill free to use?

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

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

Which other Healthcare systems have a connector?

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