Redix Developers Portal

🚀 Quick Start & Evaluation Workflow

1. Review API & SDK Documentation
   Browse the API reference, guides, and code samples. No registration needed.
2. Request Your Evaluation Kit
   Submit the Evaluation Request Form and sign our agreement. You will receive:
   • API source code (redix_api.py), Redix Engine, Python & JavaScript SDKs
   • Sample config files and full documentation (API Reference, User Guide, etc.)
3. Set Up Locally (Evaluation Package Users)
   • Copy redix_api.py and redix_cloud.conf from your kit
   • Install dependencies: pip install fastapi uvicorn pydantic typing-extensions aiosqlite prometheus-fastapi-instrumentator
   • Edit redix_cloud.conf (set engine location, base work dir, etc)
   • Set API Key (export REDIX_API_KEY=your_key or as env variable)
   • Start: uvicorn redix_api:app --host 0.0.0.0 --port 8000
   • Verify via API Reference (Swagger UI) and logs for "Redix engine ready"
4. Integrate in Your Stack
   Use our official SDKs for Python and JavaScript/Node.js for fast integration.

🎁 Request Your Evaluation Package

1. Fill out the evaluation request form or email support@redix.com.
2. Sign the Redix Evaluation Agreement.
3. Receive a secure download link for your full evaluation package (API, engine, SDKs, docs, config).
4. All setup and integration are performed on your own infrastructure.

📖 API Reference (Swagger UI)

• Open the Swagger UI to explore endpoints, parameters, and schemas. Read-only demo—do not upload or test with confidential data.
• All real API usage and file conversions must be performed in your own environment after requesting an evaluation kit.
• REST API Guide (PDF) — Complete REST API endpoints, deployment, error handling, and troubleshooting.
• Redix Client Python SDK Guide (PDF) — Full usage and integration details for the official Python SDK.
• Redix Client Node SDK Guide (PDF) — Full usage and integration details for the official Node.js SDK.
• Download Sample redix_cloud.conf — Example configuration for first-time setup.

Sample redix_cloud.conf configuration:

# redix_cloud.conf - Configuration file for Redix Healthcare Data Conversion API
# Copy this file to your deployment directory and customize the values below

[paths]
# Path to directory containing redix64.exe (Windows) or redix64 (Linux)
redix_libs_path = c:/program files/redix format converter engine
# Base working directory for API operations
base_work_dir = D:/ai/api

[server]
# Server binding configuration
host = 0.0.0.0
port = 8000
# API metadata
title = Redix Solutions: Healthcare EDI & Data Transformation
description = Convert healthcare data between different formats.
version = 2.0.0

[processing]
# Timeout for redix executable calls (seconds)
subprocess_timeout = 30
# Default file extensions
output_file_extension = .txt
error_file_extension = .txt

[security]
# CORS configuration - comma separated list of allowed origins
# Use * for all origins (development only)
# Production example: https://yourdomain.com,https://api.yourdomain.com
cors_origins = *
# Set to true to allow credentials in CORS requests
cors_allow_credentials = true

[logging]
# Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL
log_level = DEBUG
# Log file path (optional - leave empty to log to console only)
log_file = 

[directories]
# Subdirectory names under base_work_dir
input_dir = input
output_dir = output
error_dir = error
ack_dir = ack
staging_dir = staging
rules_dir = rules
archieve_dir = archive

[features]
# Enable/disable API documentation
enable_swagger_ui = true
# Swagger UI path
docs_url = /docs
# Enable file cleanup after processing
cleanup_temp_files = true

[staging_profiles]
# Specify the default profile to use if 'config_profile' is not provided in the API request.
# This must match a sub-section name defined below.
default_staging_profile = x12_837P_default_profile

# Define individual staging conversion profiles as sub-sections using the format:
# [staging_profiles.<profile_name>]
# All parameters within a profile should correspond to Redix executable arguments.
# Mandatory parameters: conversion_flag, ifd_file, ofd_file
# Optional parameters: warning_level, segment_terminator, element_separator,
#                       composite_separator, release_character (these will use
#                       the API's default if not specified in the profile)

[staging_profiles.x12_837P_default_profile]
conversion_flag = e
ifd_file = RMap_5_837P.ifd
ofd_file = RMap_5_837P_to_HIPAA_5010_A1.ofd
warning_level = 1
segment_terminator = new line
element_separator = *
composite_separator = :
release_character = ?
user_data = 0*\**:*\?
# user_data is typically per-transaction, so it's not ideal for a profile default.
# It can still be overridden in the API request if needed.

[staging_profiles.rmap_834_to_834]
conversion_flag = e
ifd_file = RMap_5_834.ifd
ofd_file = RMap_5_834_to_HIPAA_5010_A1.ofd
warning_level = 1
segment_terminator = new line
element_separator = *
composite_separator = :
release_character = \
user_data = 0*\**:*\?

[staging_profiles.837i_to_ub04_pdf]
conversion_flag = x
ifd_file = hipaa_5010_a2_837_inst_misa.ifd
ofd_file = PDF_CMS-UB04-VIEW-5010A2-PDFperClaim_red.ofd
warning_level = 1
segment_terminator = new line
element_separator = *
composite_separator = :
release_character = \
user_data = ub04.idx

# Add more profiles as needed following the [staging_profiles.<profile_name>] format
# Example:
; [staging_profiles.edi_inbound_997]
; conversion_flag = e
; ifd_file = inbound_edi_map.ifd
; ofd_file = 997_acknowledgment.ofd
; warning_level = 0
    

💻 Client SDKs & Integration Examples

from redix_client import RedixClient

client = RedixClient(base_url="https://your-api-domain.com", api_key="YOUR_API_KEY")

# Example 1: Direct file upload conversion
result = client.convert_file_upload(
    Input_File="./sample-data/837_claim.txt",
    IFD_File="./rules/hipaa_837.ifd",
    OFD_File="./rules/rmap_output.ofd",
    Conversion_Flag="x",  # X12 format
    WarningLevel=1,
    Segment_Terminator='~',
    Element_Separator='*',
    Composite_Separator=':',
    Release_Character='?',
    User_Data="client123"
)
print(result["output_file_view_url"])

# Example 2: Staging file conversion
staging_result = client.convert_staging_file(
    Staged_Filename="uploaded_claim.txt",
    Config_Profile="x12_837_default_profile",
    User_Data="override_data"
)
print(staging_result["conversion_result_summary"])

# Example 3: Initiate batch processing
batch_result = client.batch_convert_folder(
    Input_Subfolder="batch_claims",
    Config_Profile="x12_837_default_profile",
    Output_Subfolder="processed_claims"
)
job_id = batch_result["job_id"]
status = client.get_batch_status(job_id)
print(status["status"])
      

const { RedixClient } = require('@redixint/redix-client');
const client = new RedixClient({
    baseUrl: 'https://your-api-domain.com',
    apiKey: 'your-api-key'
});

// Example 1: Direct file upload conversion
const result = await client.convert_file_upload({
    Input_File: new File(['content'], '837_claim.txt'), // Or path
    IFD_File: new File(['content'], 'hipaa_837.ifd'),
    OFD_File: new File(['content'], 'rmap_output.ofd'),
    Conversion_Flag: 'x',
    WarningLevel: 1,
    Segment_Terminator: '~',
    Element_Separator: '*',
    Composite_Separator: ':',
    Release_Character: '?',
    User_Data: 'client123'
});
console.log(result.output_file_view_url);

// Example 2: Staging file conversion
const stagingResult = await client.convertStagingFile({
    Staged_Filename: 'uploaded_claim.txt',
    Config_Profile: 'x12_837_default_profile',
    User_Data: 'override_data'
});
console.log(stagingResult.conversion_result_summary);

// Example 3: Initiate batch processing
const batchResult = await client.batchConvertFolder({
    Input_Subfolder: 'batch_claims',
    Config_Profile: 'x12_837_default_profile',
    Output_Subfolder: 'processed_claims'
});
const jobId = batchResult.job_id;
const status = await client.getBatchStatus(jobId);
console.log(status.status);
      

📋 Supported Transaction Types & Formats

• CMS Mandate / PAS: X12 278 Request → FHIR R4 (with Provenance) NEW
• X12 (837, 835, 834, 270, 271, 277, 278, 999/TA1, etc.)
• UN/EDIFACT, HL7, NCPDP, NSF, UB92
• HL7 v2.x to FHIR R4 Transformation
  • 14 message types: ACK, ADT, BAR, DFT, MDM, ORM, ORU, OUL, QRY, RDE, REF, RSP, SIU, VXU
  • 85-90% field coverage with production-ready mappings
  • Web GUI, CLI, and REST API interfaces available
  • Sub-second processing (50-150ms average)
  • Learn more: Redix HL7-to-FHIR Package
• XML, CSV, PDF, Fixed/Variable flat files
• Redix PDF Module: EDI to PDF (CMS-1500, UB04, 835 Remittance, etc.)
• Database Module: ODBC integration (Oracle, SQL Server, MySQL, PostgreSQL)
• RMAP Module: Simplified CSV, grouped HIPAA mapping
• Custom formats and extensions via IFD/OFD rule sets

🏥 Healthcare Integration Use Cases

• Payer Compliance (CMS-0057-F): Implement the FHIR Prior Authorization API by wrapping your legacy X12 278 engine with Redix. View Architecture
• SaaS Platform Enhancement: Integrate HIPAA-compliant conversion into your app. Convert EDI to PDF, CSV, XML, etc.
• Enterprise Data Pipelines: Automate high-volume EDI, claims, and enrollment flows, with direct database integration.
• Healthcare Exchange Platforms: Enable payers/providers to exchange multi-format outputs, validate HIPAA files, and support batch workflows.

🔄 HL7-to-FHIR Transformation

Convert HL7 v2.x messages to FHIR R4 bundles with our production-ready transformation package:

• Quick Integration: Web GUI for testing, REST API for production automation
• 14 Message Types: ADT, ORU, DFT, ORM, SIU, and 9 more commonly used healthcare messages
• Fast Processing: 50-150ms per message on entry-level hardware
• Flexible Deployment: Linux, Windows, Docker, or Kubernetes
• Try It Now: Test at demo.redix.com (use sample data only)

Developer Resources:

• API endpoint: POST /api/convert with HL7 message payload
• Returns FHIR R4 bundle in JSON format
• Built-in validation with detailed error reporting
• Sample files and documentation included

View HL7-to-FHIR Package Details Try Live Demo

🔒 Privacy & Deployment Control

🤝 Support & Community

• Technical Help: support@redix.com
• Evaluation Onboarding: Reply to your onboarding message for personalized help
• Contribute: Submit pull requests to our GitHub repositories (evaluation users only):
  • Node.js SDK Repository: Contains the @redixint/redix-client package for Node.js integration with the Redix REST API.
  • Python SDK Repository: Hosts the redix-client package for Python developers to access Redix API functionalities.