RMap Module
RMap is Redix's tabular canonical format for HIPAA transactions: related data grouped in plain comma-separated records instead of X12 segments and loops. Convert X12 to and from RMap, load it into databases, or build Da Vinci PAS request bundles from it.
- CSV-based
- X12 ↔ RMap
- RMap → Da Vinci PAS
- HIPAA 5010
HIPAA data without segment-level syntax
Readable records
One record per billing provider, one per subscriber, and so on, with no HL hierarchy. Business users can review the files; developers can parse them in any language.
A round trip to X12
RMap is designed to carry the data needed to produce X12 output again, through the RMap-to-HIPAA maps. Redix maintains the maps as the HIPAA standards change.
| Aspect | RMap | HIPAA X12 |
|---|---|---|
| Structure (837 example) | Related data grouped in one record; no HL segments | Data split across segments in an HL hierarchy |
| Qualifiers | Minimal | Extensive qualifier requirements |
| Separators | Comma only | Segment, element, and component separators |
| X12 output | Produced through an RMap-to-HIPAA map | Native format |
RMap to Da Vinci PAS
Organizations without X12 278 infrastructure can build Da Vinci PAS request bundles directly from RMap 278 data, and still generate an X12 278 from the same data when a trading partner requires it.
Generated FHIR output is checked against the agreed PAS version, terminology, and the receiving payer's requirements as part of each project. CMS-0057-F API requirements generally begin January 1, 2027; applicability and dates depend on payer type. A FHIR bundle is one component of a prior-authorization program. See the CMS-0057-F Compliance Suite for the full workflow.
HIPAA 5010 maps in both directions
| Transaction | X12 to RMap | RMap to X12 |
|---|---|---|
| 270 / 271 Eligibility | Yes | Yes |
| 276 / 277 Claim status | Yes | Yes |
| 278 Services review (request and response) | Yes | Yes |
| 820 Premium payment | Yes | Yes |
| 834 Enrollment | Yes | Yes |
| 835 Claim remittance | Yes | Yes |
| 837P / 837I / 837D Claims | Yes | Yes |
Plus RMap 278 request to Da Vinci PAS FHIR. Inbound maps check the X12 against the HIPAA definitions as they convert.
Outbound: generate a HIPAA file
- Write the data in RMap format
- Run the RMap-to-HIPAA map
- Get an X12 837, 834, 270, or other transaction
Inbound: validate and import
- Feed the incoming X12 file to its map
- The engine checks it against the HIPAA definitions
- Review the conversion result and reported issues, then use the RMap output
With the Database Module, load RMap directly into SQL Server, Oracle, PostgreSQL, or MySQL, or generate RMap from database queries for outbound files.
Try RMap on synthetic data
Use the hosted synthetic samples, with no local installation; demo access and registration rules apply. Request an evaluation key to test your own files. Do not upload PHI.
How the module is licensed
AnyToAny Engine
Required. The core engine: single-pass processing, IFD/OFD definitions, and the runtime.
RMap Module
This module. HIPAA 5010 to and from RMap maps, format documentation, and sample files. Does not require the HIPAA Package. PAS mapping availability and API access are confirmed for your deployment.
Database Module
Optional. Write RMap to a database or generate it from queries, via ODBC.
The AnyToAny Engine is required for every conversion; each module is licensed separately.
See your data as RMap
Convert a synthetic sample in the demo, then send a de-identified file and we show the round trip on your data.