RMAP is the shorthand term for “Redix Map for HIPAA”. The RMAP module consists of a collection of HIPAA maps. These maps convert to and from the HIPAA healthcare standards and Redix internal formats. The Redix internal formats are CSV (Comma Separated Value) formats that encapsulate HIPAA data into a more concise, usable, and readable format.

Many healthcare companies have been using the UB92 or NSF standards in the past for healthcare claims. Unfortunately, both the UB92 and NSF standards do not have all of the data that HIPAA requires. Therefore, when converting a HIPAA message into a UB92 message, some HIPAA data will not be passed. On the other hand, some healthcare users do not support the X12 or HIPAA standards, and neither do they support the NSF or UB92 standards. Instead, they use some proprietary file format for healthcare claims or eligibility checking. Their claim data are stored in databases, and they need to generate HIPAA messages out of their databases.

RMAP was developed to streamline the process and remain completely HIPAA compliant. RMAP is a much simpler data format that preserves all of the HIPAA-mandated data.

Advantages of using the RMAP module are:

• smaller size files; fewer records and fields and much easier to develop
• easier to understand from a business perspective
• quicker translation time
• an easier way to query to and from databases
• a provided crosswalk shows how each RMAP element maps to a HIPAA element

As a result, many clients have adopted the Redix RMAP formats as their own internal database format for storing healthcare data.

No, the RMAP module is an add-on module on the Redix AnyToAny Format Converter Engine. The user will need to license the Redix AnyToAny Format Converter Engine as well.

The RMAP module consists of the maps of each HIPAA transaction. Also, the maps are divided into two categories: HIPAA to RMAP and RMAP to HIPAA.

HIPAA to RMAP:

RMAP to HIPAA: