RMap Module FAQ.
Common questions about the Redix RMAP module — HIPAA-compliant CSV format, bidirectional X12 conversion, supported transactions, and database integration.
What is the Redix RMAP module?
RMAP (Redix Map for HIPAA) is a collection of HIPAA maps that convert between HIPAA healthcare standards and Redix's internal CSV (Comma Separated Value) formats. The CSV formats encapsulate HIPAA data into a more concise, usable, and readable format, simplifying healthcare EDI mapping.
What is the purpose of Redix developing the RMAP module?
Many healthcare companies previously used UB92 or NSF standards, which do not contain all the data that HIPAA requires. Others use proprietary file formats with claim data stored in databases.
RMAP was developed to streamline the process while remaining completely HIPAA compliant. It provides a much simpler data format that preserves all HIPAA-mandated data, fostering healthcare EDI automation.
What are the advantages of using the RMAP module?
- Smaller file sizes — fewer records and fields, making it easier to develop and manage healthcare data
- Easier to understand from a business perspective
- Quicker translation time, enhancing EDI integration
- Easier way to query to and from databases
- A provided crosswalk shows how each RMAP element maps to a HIPAA element, ensuring compliance
Many clients have adopted the Redix RMAP formats as their own internal database format for storing healthcare data.
Can the Redix RMAP module be licensed alone?
No. The RMAP module is an add-on module for the Redix AnyToAny Format Converter Engine. Users must also license the engine.
What does the RMAP module include?
Maps for each HIPAA transaction in two categories:
HIPAA to RMAP (for receiving HIPAA files) — 12 maps:
- 270 Eligibility Request, 271 Eligibility Response
- 276 Claim Status Request, 277 Claim Status Response
- 278 Services Review Request, 278 Services Review Response
- 820 Group Payment Remittance
- 834 Eligibility Audit Report
- 835 Claim Remittance Advice
- 837 Institutional, 837 Dental, 837 Professional
RMAP to HIPAA (for submitting HIPAA files) — the same 12 transaction types in reverse.
All maps use HIPAA 5010A1 NPI editions and RMAP Version 5.
Can RMAP be used with the Database module?
Yes. When both RMAP and Database modules are licensed, predefined maps are available for:
- SQL Server — RMAP to SQL Server (12 types) and SQL Server to RMAP (12 types)
- Oracle — RMAP to Oracle (12 types) and Oracle to RMAP (12 types)
This provides a total of 48 predefined database maps covering all HIPAA transaction types for both database platforms.
What is the RMAP Version 5 format?
RMAP Version 5 is the current CSV-based format used by all RMAP maps. It uses HIPAA 5010A1 NPI editions.
Important: The component separator must be set to # (not :) when working with RMAP files, because RMAP data values may contain colons.
Still have questions? Contact us or try our AI Chat for instant answers.