Healthcare Data Conversion - On Your Servers

Convert and validate X12, HL7, and NCPDP transactions on your own servers. The same engine bridges existing pipelines to FHIR R4 and Da Vinci PAS.

Prior authorizationX12 278 → FHIR R4

A prior authorization request in X12 format, converted by the Redix engine into a FHIR Claim. The highlighted procedure code carries through from input to output.

X12 278 request 005010X217
ST*278*0002*005010X217
…
UM*HS*I*2
…
SV2**HC:33510
FHIR R4 Claim excerpt application/fhir+json
{
  "resourceType": "Claim", …
  "use": "preauthorization", …
  "item": [{ …
    "sequence": 1,
    "productOrService": { "coding": [{
      "system": "http://www.ama-assn.org/go/cpt",
      "code": "33510" }] }
  }], …
}
Actual Redix conversion · Synthetic data · Input and output excerptsTry X12 → FHIR
30+ yearsBuilding healthcare EDI software since 1994
Fortune 50 and 500In production environments supporting Fortune 50 payer and Fortune 500 healthcare organizations
Native C engineNo JVM; validation and conversion in one pass
Runs on your serversProduction PHI does not need to be sent to Redix

This production history belongs to the Redix engine and its EDI, PDF, and database modules. The FHIR and Da Vinci PAS modules are newer additions to the same engine.

Where Redix fits

Between the systems you run and the formats you need

Redix runs inside your environment. It reads data from your existing systems and partners, validates it, and converts it through maps you control.

Your systems

  • Claims and practice-management systems
  • Clearinghouses and trading partners (X12)
  • Clinical systems (HL7 v2, CDA)
  • Pharmacy systems (NCPDP)
  • Databases, XML, and flat files

Redix engine, on your servers

  • Validates against the implementation rules
  • Converts in one pass through the data
  • Driven by input and output maps you can review and change

What it produces

Established

  • Validated X12 with 999 and TA1 acknowledgmentsHIPAA Package
  • CMS-1500, UB-04, ADA J400, and 835 remittance PDFsPDF Module
  • Claims loaded into Oracle, SQL Server, or PostgreSQLDatabase Module
  • XML, NCPDP, and other formatsXML and NCPDP Modules

Newer

  • FHIR R4 from X12 837, 835, and 278HIPAA-to-FHIR Module
  • FHIR R4 from HL7 v2 and CDAHL7/CDA-to-FHIR Module
  • X12 278 to Da Vinci PAS for CMS-0057-FCMS PAS Compliance Suite

Available outputs depend on the licensed package or modules and the configured maps. Not every input converts to every output. We confirm coverage on your de-identified evaluation samples.

Deployment

Choose how it runs

You host Redix in your datacenter or cloud account and keep your data. Redix supplies the engine, maps, and updates, with support under a maintenance agreement.

On-premises engine

Command line, native DLL or shared library, or a folder watcher, on Windows or Linux.

Docker container

The engine behind a REST API, in a container you run on your own infrastructure.

REST API and SDKs

Python and Node.js SDKs, with an evaluation API for testing. See the Developer Portal.

Native C runtime

No JVM to install or tune. The same engine in every option.

Talk through your integration

Tell us the transactions and systems you run, and we will show you where Redix fits.