AnyToAny Format Converter Engine for production healthcare data
Validate, map, and convert X12, HL7, NCPDP, XML, database, and flat-file data in a single pass. Native C runtime, deployed on your servers or in Docker, with no SaaS dependency. AnyToAny powers Redix's core conversion and validation modules, including the HIPAA X12 Package, HIPAA to FHIR, HL7 v2 to FHIR, and CMS-0057-F prior authorization.
- Redix: 30+ years in healthcare EDI
- Native C, single pass
- On-premises or Docker
In production: a national US pharmacy organization used AnyToAny to migrate more than 100 healthcare conversion scripts onto one engine.
Validation, mapping, and output in one pass
Input Format Definition (IFD)
Describes the input structure, with syntax and semantic validation rules and per-element error handling. Plain, editable text files.
Output Format Definition (OFD)
Describes the output structure: field-to-field mapping rules, built-in transformation functions, and custom logic where you need it.
AnyToAny validates, maps, and writes the output in one pass through the data. The same engine serves real-time API calls and batch runs.
Modernize formats without destabilizing production
Keep existing workflows
X12 trading-partner connections and adjudication systems keep running while FHIR APIs are added alongside them.
Evaluate interoperability options
Add FHIR interfaces and prior-authorization workflows next to existing X12 processing. Conversion is one component of a compliance program, not the whole of it.
Native C runtime
No JVM dependency and no garbage-collection pauses. Performance depends on your workload and configuration.
Run in your datacenter or cloud
Deploy on-premises or in your own cloud account. Production PHI does not need to be sent to Redix.
Products and modules, with their current status
Core engine plus licensed modules. Each module adds pre-built definitions, validation rules, and mapping templates.
| Product or module | What it does | Status |
|---|---|---|
| HIPAA X12 Package | 5010 transaction sets: 837P/I/D, 835, 270/271, 276/277, 278, 834, 820 | In production use |
| HIPAA X12 Validator | Structural, inter-segment, and balancing checks with 999 and TA1 | In production use |
| RMap Module | Canonical tabular model between formats | In production use |
| Database Module | Load and extract via ODBC (Oracle, SQL Server, PostgreSQL) | In production use |
| PDF Module | CMS-1500, UB-04, ADA J400, and 835 remittance PDFs | In production use |
| NCPDP, HL7 v2, XML | Pharmacy, clinical messaging, and XML/XSD handling | In production use |
| HIPAA X12 to FHIR | 837, 835, and 278 to FHIR R4 | Demo available; production scope per project |
| HL7 v2 to FHIR | ADT and ORU to FHIR R4 (internal Tier-1 checks passed); ORM, MDM, SIU, VXU demo samples | Demo available; production scope per project |
| CMS-0057-F / Da Vinci PAS | X12 278 to FHIR PAS, plus CRD, DTR, and access-API demonstrations; FHIR to X12 278 in development | Sandbox available; production scope per project |
| X12 275 Attachments | Build and read 275 attachment payloads (CMS-0053-F) | Early access |
Every module runs on the same engine, so a team that already runs Redix for X12 adds FHIR without a second platform. Interfaces: command line, native library, and a REST API, plus an MCP interface for compatible AI clients.
CMS-0057-F integration approaches
X12-based
Keep 278 processing and convert X12 278 to FHIR PAS at the edge.
Hybrid
Run X12 and FHIR in parallel while partners move at different speeds.
FHIR-first
Use the RMap canonical model to produce FHIR PAS resources from your own data.
CMS-0057-F API requirements generally begin January 1, 2027; applicability and dates depend on payer type. Conversion is one component of that work. See the prior-authorization workflow in the CMS-0057-F Compliance Suite.
Written in C/C++, packaged for containers
Options below are subject to the supported operating system and build agreed for your project.
| Platform | Options |
|---|---|
| Container and cloud | Docker and Kubernetes; virtual machines or managed Kubernetes on AWS, Azure, or Google Cloud |
| Linux | RHEL, Rocky Linux, and AlmaLinux 8/9; Ubuntu 20.04/22.04 LTS |
| Windows Server | Windows Server 2016, 2019, 2022 with the 64-bit V9 engine. The V7 engine (32-bit and 64-bit builds) reaches end of life at the end of 2026 |
| UNIX | Solaris, HP-UX, and AIX builds on request |
Core engine plus the modules you need
Core engine
- Single-pass conversion runtime with built-in validation
- IFD/OFD mapping framework
- Delimited, fixed-length, JSON, and basic XML input and output
- Command line, native library, and REST API
Add-on modules
- HIPAA X12, RMap, Database, PDF
- HL7 v2, NCPDP
- XML Module: XSD and DTD validation, namespaces, XML mapping
- HIPAA to FHIR, HL7 to FHIR
- CMS-0057-F / Da Vinci PAS
Format and module coverage is confirmed in your evaluation and quote.
Ready to evaluate the engine?
Send a de-identified sample file and your target format. We recommend the modules you need and show you a working conversion path.