|
RMap is the short-hand term for
Redix Map (for HIPAA). RMaps are Redix defined CSV (Comma
Separated Value) healthcare formats that encapsulate
HIPAA data into a more concise, usable, and readable
format. The Purpose to RMaps is to aid our clients to
have a more effective and efficient system when
translating files.
The Advantages of RMAPs are:
 An
RMap file does not have all the qualifiers and constants
required by HIPAA. Thereby allowing:
-
smaller size files
-
pertinent data organized
-
quicker translation time
-
an easier way to query to and from databases
-
reduce need for tables within a mainframe DB
-
a provided crosswalk shows how each RMap element
maps to a HIPAA element
The
RMAP format could be used by customers as repository.
A
format to create HIPAA documents with less redundant
data needs. Particularly in the 837 formats, data is
construed in a per claim basis, allowing for conversion
to other claim based formats in a 1:1 claim ratio. This
also allows for filtering of claims to be done easily.
A
format that will continually be adapted by Redix to fit
the newest HIPAA formats, thus cutting down on client
maintenance issues when new HIPAA updates become
finalized.
RMAP Specifications and Maps
Each
RMAP has its own spreadsheet to describe its respective
file layout and structure. The following, for
example, is the structure of the RMAP for an 837
Professional file format.
Each RMAP
specification has its own corresponding HIPAA maps to help the Redix customers totally transparent to
the HIPAA business rules. For example,
RMAP_2_A1_837P_to_HIPAA_A1_837P is a map that will
convert the Redix RMAP_837 file to HIPAA 837 Professional
based on Addendum standard. The
HIPAA_A1_837P_to_RMAP_2_A1_837P is a separate map that
will convert the HIPAA 837 back to RMAP_837 file. All
of the related HIPAA business rules are built within the
maps.
In the below example, the map
RMap_2_A1_837P_to_HIPAA_A1_837_Prof is used. This
map will convert a RMAP_837 file to a HIPAA_837 based on
Addendum standard.
Inbound message definition (Message
from): RMap_2_A1_837P
The following is an example of the
input RMAP file.
Outbound message definition
(Message to): HIPAA_A1_837_Prof
The following is the output file.
|
