Healthcare REST API & MCP Server for AI Agents.

12 MCP tools for Claude and Cursor. REST API with code examples in Python, C#, Java, Node.js, and curl. HIPAA X12, HL7, CDA to FHIR R4. Swagger sandbox included.

Getting Started

Three paths from evaluation to production

Try the Sandbox

Test the API Swagger or 12 conversion and compliance tools with sample data

Request Evaluation

Get the engine, API server, and SDKs for your infrastructure

Deploy Locally

On-premises, Docker, or private cloud. PHI stays in your environment.

Do not send PHI to the public sandbox. Evaluation and production deployments run on your infrastructure. API keys are created and rotated locally.

Online Sandbox

Self-service testing with sample data. Public key: demo-key-12345 (rate-limited).

AI Chat

Describe your integration challenge. AI Chat matches you to the right conversion tool and walks you through the workflow.

Launch AI Chat →

12 Conversion & Compliance Tools

Interactive tools for X12 → RMap, X12 → FHIR, Claims → PDF, HL7 → FHIR, CMS-0057-F ePA workflow, and more. Upload sample data and see results immediately.

Browse Tools →

API Access & SDKs

Programmatic access to the conversion engine

API Sandbox (Swagger)

Full REST API reference with try-it-out. Server: demo.redix.com. Header: X-API-Key: demo-key-12345.

Open Swagger UI

HIPAA-to-FHIR Sandbox

Upload X12 transactions (837, 835, 278, 270/271) and get FHIR R4 bundles back. Visual diff and validation included.

Open X12 to FHIR Tool

SDKs & Language Support

Official SDKs for Python and Node.js. The REST API is standard HTTP — any language with an HTTP client works.

Python SDK

pip install redix-client
PyPI Python 3.8+ SDK
View on PyPI

Node.js SDK

npm install redix-client
npm Node 18+ SDK
View on npm

C# / .NET

HttpClient + X-API-Key header
.NET 6+ VB.NET HTTP
See C# example below

Java

java.net.http.HttpClient
Java 11+ HTTP
See Java example below

curl / CLI

curl -H "X-API-Key: ..." -F file=@...
Bash PowerShell HTTP
See curl example below

Any HTTP Client

POST + X-API-Key + multipart/form-data
Go Ruby PHP Rust
View API spec

Quick Examples

Healthcare format conversion in a few lines

X12 837 to RMap curl
# Convert an X12 837 file to RMap
curl -X POST https://demo.redix.com/api/v2/convert/x12-to-rmap \
  -H "X-API-Key: demo-key-12345" \
  -F "file=@claim_837p.edi"

# Convert HL7 v2 message to FHIR R4
curl -X POST https://demo.redix.com/api/v2/convert/hl7-to-fhir \
  -H "X-API-Key: demo-key-12345" \
  -F "file=@patient_adt.hl7"
HL7 v2 to FHIR R4 Python
import os
from redix_client import RedixClient

api_key = os.getenv("REDIX_API_KEY", "demo-key-12345")
client = RedixClient(base_url="https://demo.redix.com", api_key=api_key)

# Convert HL7 v2 ADT message to FHIR R4 bundle
result = client.post('/api/v2/convert/hl7-to-fhir', json={"message": hl7_adt})
print(result["resourceType"])  # Bundle
X12 837 to FHIR R4 C#
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", apiKey);

using var form = new MultipartFormDataContent();
form.Add(new ByteArrayContent(File.ReadAllBytes("claim_837p.edi")),
         "file", "claim_837p.edi");

var response = await client.PostAsync(
    "https://demo.redix.com/api/v2/hipaa-to-fhir/837-professional", form);
var fhirBundle = await response.Content.ReadAsStringAsync();
HL7 to FHIR R4 Java
HttpClient client = HttpClient.newHttpClient();

HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://demo.redix.com/api/v2/convert/hl7-to-fhir"))
    .header("X-API-Key", apiKey)
    .header("Content-Type", "application/json")
    .POST(HttpRequest.BodyPublishers.ofString(
        "{\"message\": \"" + hl7Message + "\"}"))
    .build();

HttpResponse<String> response =
    client.send(request, HttpResponse.BodyHandlers.ofString());
String fhirBundle = response.body();

The REST API is standard HTTP. Use any language — no SDK required. See API Swagger for complete endpoint reference and request/response schemas.

Conversion Capabilities

Standards supported by the REST API

HIPAA X12 EDI

Parse, validate, and convert all major HIPAA 5010 transaction sets. Bidirectional X12 ↔ RMap ↔ FHIR.

837P/I 835 834 270/271 276/277 278 820
View HIPAA Package

HL7 v2.x & CDA

Clinical messaging and document transformation to FHIR R4. 14 HL7 message types. CDA/C-CDA clinical documents.

ADT ORU ORM SIU MDM CDA
View HL7 Module

X12 → FHIR R4

Convert HIPAA X12 transactions to FHIR R4 bundles. Claims, eligibility, enrollment, and prior authorization.

FHIR R4 837 835 278 270/271
View X12 to FHIR

Platform Documentation

Guides for the engine, REST API, and SDKs

REST API Guide

Complete endpoint reference, authentication, request/response formats, and error handling. Updated January 2026.

Download PDF

AnyToAny Engine

Core runtime architecture, IFD/OFD mapping framework, module system, and deployment configuration.

View engine details

SDK Guides

Installation, authentication, and usage guides for Python and Node.js client libraries.

Python SDK Guide

CMS-0057-F PAS Documentation

Prior authorization API documentation for the CMS-0057-F January 2027 mandate

PAS API Reference

Endpoints, request/response formats, and code samples for Da Vinci PAS $submit and $inquire.

View reference

PAS Overview & Architecture

System architecture, data flows, deployment options, and integration patterns for CMS-0057-F compliance.

View overview

PAS Test Workflow

Step-by-step testing guide: CRD check, DTR Questionnaire, $submit/$inquire, and X12 278 conversion.

View workflow

Live ePA Workflow Demo

Interactive 3-step ePA demo: check coverage requirements, complete documentation, submit and track prior authorization.

Launch demo

MCP Server for AI Agents

12 healthcare conversion tools via the Model Context Protocol. Connect Claude, Cursor, or any MCP client.

What is MCP?

The Model Context Protocol is an open standard that lets AI agents call external tools. Instead of copy-pasting data, your AI assistant connects directly to the Redix conversion engine — validate, convert, and generate documents in a single conversation.

MCP Inspector

Test all 12 tools interactively in a browser. No installation required — the Inspector connects directly to the Redix MCP Server over SSE.

Launch Inspector

How it works: The MCP Server and REST API are fixed wrappers around the Redix AnyToAny Engine. Underneath, the engine uses IFD (Input Format Definition) flat files for validation and OFD (a proprietary language similar to Python/VB) for conversion — nothing is hardcoded. Pre-defined maps ship ~85% complete; consultation services finish the remaining payer-specific or workflow-specific requirements.

12 Available Tools

validate_x12 convert_x12_to_fhir convert_x12_to_rmap convert_rmap_to_x12 convert_x12_to_database generate_x12_from_database convert_hl7_to_fhir convert_cda_to_fhir convert_fhir_to_x12 convert_fhir_to_rmap generate_claim_pdf list_supported_formats

MCP Configuration

Add Redix to your AI client in seconds

Claude Desktop JSON
// ~/.config/claude/claude_desktop_config.json (Linux)
// ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
{
  "mcpServers": {
    "redix": {
      "command": "python3.11",
      "args": ["/path/to/redix-mcp-server/server.py"],
      "env": {
        "REDIX_API_URL": "https://demo.redix.com",
        "REDIX_API_KEY": "demo-key-12345"
      }
    }
  }
}
Claude Code / Cursor JSON
// .mcp.json (project root)
{
  "mcpServers": {
    "redix": {
      "command": "python3.11",
      "args": ["/path/to/redix-mcp-server/server.py"],
      "env": {
        "REDIX_API_URL": "https://demo.redix.com",
        "REDIX_API_KEY": "demo-key-12345"
      }
    }
  }
}
Remote SSE (any MCP client) URL
# SSE endpoint — no local installation required
https://demo.redix.com/sse

# MCP Inspector (browser-based testing)
https://demo.redix.com:6275

STDIO for local installations · SSE for remote/hosted access · MCP Server FAQ

Security & Deployment

Run on your infrastructure. No PHI leaves your environment.

On-Premises

Install in your data center

Docker

Container deployment

Kubernetes

Orchestrated at scale

Private Cloud

AWS, Azure, or GCP in your VPC

Support

Technical help and evaluation requests

Technical Support

Integration help, API questions, and deployment guidance for customers under active maintenance.

support@redix.com

Request a Demo

Evaluation packages, licensing, and technical consultation. Engine, API server, and SDKs for your infrastructure.

Request evaluation