# Redox MCP for AI Agents AI Agent Connect

> Redox MCP lets you search patient records, pull clinical conditions, and write back vitals or observations directly to an EHR via the Redox healthcare API. It bridges the gap between your AI agent and clinical data using FHIR standards and Redox Data Models.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_vkjMJUhpElzGUBW33LqwwW8NlPpFijvpbWdCCZWf/ai-agent-connect
- **Tags:** fhir, health-interoperability, patient-data, clinical-records, ehr-integration

## Description

You're tired of jumping between different EHR portals and manually hunting for a patient's current vitals or problem lists. This Connector lets your AI agent do that heavy lifting for you. It connects your agent to the Redox healthcare ecosystem, meaning you can ask for a patient's active diagnoses or push new clinical observations in plain English. Whether you're pulling FHIR records or sending asynchronous updates through Redox Data Models, it handles the mapping and the handshake for you. It's a major time-saver for anyone building health tech because you can verify mappings and test production flows without leaving your workspace. You can find this among the 4,000+ tools in the Vinkius catalog to get your healthcare project moving faster.

## Tools

### search_condition
Retrieve diagnoses or problem list items for a patient. Use this to get a quick summary of a patient's medical history.

### search_patient
Search for a patient using the Redox FHIR API. It helps you find the right record using specific identifiers.

### create_observation
Save vitals or observations back to the EHR. Use this to update patient records with new clinical data.

### post_data_model
Send a Redox Data Model API event. This is useful for triggering notifications or syncing data across systems.

## Prompt Examples

**Prompt:** 
```
Search for patient identifier 'urn:redox:source:MR|12345' in the production environment for destination 'clinical-hub'.
```

**Response:** 
```
I've initiated the search in the clinical-hub destination. I found a patient record matching that identifier. Would you like to see the full FHIR resource details?
```

**Prompt:** 
```
Retrieve all active conditions for patient ID 'P123' in the development environment.
```

**Response:** 
```
I've fetched the conditions for patient P123. The list includes:

* **Essential hypertension**
* **Type 2 diabetes mellitus**

Do you need the specific codes or onset dates for these?
```

**Prompt:** 
```
Post a Redox Data Model event for a new appointment notification using this JSON payload.
```

**Response:** 
```
I've sent the Data Model payload to the Redox API. The event has been successfully queued for processing. Here is the response metadata:

| Status | Event ID | Timestamp |
| :--- | :--- | :--- |
| Success | RX-99281 | 2026-07-10T15:06:04Z |
```

## Capabilities

### Find patient records
Search for patient data using specific identifiers and destination slugs.

### Pull clinical conditions
Retrieve active diagnoses and problem lists for specific patients.

### Write back clinical data
Save vitals and observations back to the EHR using FHIR bundles.

### Send data model events
Push asynchronous notifications or synchronous queries using Redox JSON Data Models.

### Manage environments
Switch between development and production environments for safe testing.

## Use Cases

### Verifying FHIR resource mappings
A developer needs to ensure their app correctly maps a vitals bundle. They ask their agent to use create_observation to push a test record and verify it shows up in the EHR.

### Quickly checking a patient's problem list
A clinical ops lead needs to know a patient's active conditions. They ask their agent to run search_condition for a specific ID to get a summary in seconds.

### Syncing appointment notifications
A startup wants to notify a clinic about a new booking. They have their agent use post_data_model to send a standardized JSON event to the Redox API.

### Logging wearable data to an EHR
A health app collects blood pressure from a watch. It uses create_observation to send that data directly into the patient's clinical record.

## Benefits

- Faster patient lookups using search_patient to find records by destination slugs instantly.
- Real-time clinical context with search_condition to see active diagnoses without opening a new tab.
- Automated writebacks using create_observation to update vitals without manual data entry.
- Flexible data flow with post_data_model for asynchronous notifications across healthcare systems.
- Safer development by switching between dev and production environments for testing and deployment.

## How It Works

The bottom line is you get direct, natural language access to clinical data without the usual EHR friction.

1. Subscribe to the Connector and grab your Redox API Key.
2. Connect your preferred AI client to the Connector.
3. Start asking for patient data or posting clinical updates in natural language.

## Frequently Asked Questions

**Can the Redox MCP help me manage FHIR records?**
Yes. It allows your AI agent to search for patients and retrieve clinical conditions using FHIR standards, making it much easier to handle healthcare data.

**Can I use this Connector to write data back to an EHR?**
Yes, you can. It includes the ability to save vitals and other clinical observations directly back to the EHR using structured bundles.

**Is the Redox MCP safe for testing new integrations?**
Yes. It includes environment management so you can switch between development and production environments to test your workflows safely.

**Does the Redox MCP support asynchronous notifications?**
It does. You can use it to send Redox Data Model events, which is great for triggering notifications or syncing data across different systems.

**Who is the best audience for the Redox MCP?**
It's ideal for health tech developers building medical tools, clinical ops teams needing faster data access, and startups looking for robust healthcare interoperability.

**Can I search for patients across different healthcare systems?**
Yes, by using the `search_patient` tool with the specific `destination_slug` and `identifier`, you can query any connected system in your Redox network.

**Does this support writing clinical data back to an EHR?**
Yes. The `create_observation` tool allows you to perform writeback operations by sending FHIR bundles containing vitals or other clinical observations.

**What is the difference between FHIR tools and the Data Model tool?**
The `search_patient` and `search_condition` tools use the FHIR API for standardized resource access, while `post_data_model` uses Redox's proprietary JSON Data Models for broader interoperability events.