This blog post describes the conversion of HIPAA transactions to CSV files and vice versa.
HIPAA has defined 12 transactions, ranging from healthcare claim, payment and remittance advice, healthcare enrollment, and eligibility, etc. Because of the complexity of the HIPAA transactions in both syntax and semantics, healthcare professionals found it is difficult to integrate the HIPAA transactions to their existing applications. Some of the difficulties are:
- Healthcare claim (837) is using the HL (hierarchical level) segment to represent different loop level of the claim data.
- Some of the related claim data are split into multiple segments, e.g., single billing provider is split into seven segments.
- Use the code qualifier extensively.
- Use four different separators to formulate the data.
Because of the above, users came to us and asked if it was possible to have a simple format that can represent HIPAA data. We have then since created an RMap (Redix Maps for HIPAA) module. This module defines the HIPAA transaction in a CSV (comma separated value) format and yet carries 100% of the HIPAA compliance. This format encapsulate HIPAA data into a more concise and readable format. It is easier to understand and program because of the fewer number of records and fields. As a result, the RMap module is being used by many healthcare entities as their repository for storing their healthcare data.
Redix RMap Module
The following table compares the Redix RMap format with the HIPAA format.
|
Redix RMap Format |
HIPAA Format |
Complexity |
- Related data are grouped together in a single record, e.g.
- One record for a single Billing Provider
- One record for a single Subscriber
- Does not use complicated Hierarchical Level (HL) segments
- Minimum use of code qualifiers
- Does not require any component element separators
|
- Related data are split into multiple segments, e.g.
- Seven segments for a single Billing Provider
- Nine segments for a single Subscriber
- Uses complicated Hierarchical Level (HL) segments
- Extensive use of code qualifiers
- Requires component element separators
|
Total Number of Segments or Records |
Has fewer records, e.g. an RMAP 837 Professional file has 35 records. |
Has more segments, e.g. a single HIPAA 837 Professional file has a total of 226 segments. |
File Size |
Smaller file sizes, e.g. a typical RMAP 834 file is 76KB in size, smaller than the equivalent HIPAA 834 file, which is 94 KB. Both files contain the same information. |
Larger file sizes, e.g. if a HIPAA 834 file is 94KB in size, then the equivalent Redix RMAP file is around 76 KB. Both files contain the same information. |
HIPAA Compliance |
Yes. Redix ensures that all generated files are 100% HIPAA-compliant. |
Yes |
Backward Compatibility – Will new versions of the format support older versions? |
100% |
No, based on past history. |
Click here to find out more about the RMaps. You can use this link to review the RMap definitions.
Pre-Defined Maps
The Redix RMap module contains pre-defined maps for all of 12 HIPAA transactions.
The maps are divided into two categories: HIPAA to RMAP for users that receive HIPAA files, and RMAP to HIPAA for users that submit HIPAA files.
HIPAA to RMAP (Inbound Process):
Map Name |
Source Message Type |
Target Message Type |
HIPAA_A1_NPI_270_to_RMAP_5 |
HIPAA 5010A1 (NPI) 270 Eligibility Request |
Redix RMAP Version 5 270 |
HIPAA_A1_NPI_271_to_RMAP_5 |
HIPAA 5010A1 (NPI) 271 Eligibility Response |
Redix RMAP Version 5 271 |
HIPAA_A1_NPI_276_to_RMAP_5 |
HIPAA 5010A1 (NPI) 276 Claim Status Request |
Redix RMAP Version 5 276 |
HIPAA_A1_NPI_277_to_RMAP_5 |
HIPAA 5010A1 (NPI) 277 Claim Status Response |
Redix RMAP Version 5 277 |
HIPAA_A1_NPI_278_REQ_to_RMAP_5 |
HIPAA 5010A1 (NPI) 278 Services Review Request |
Redix RMAP Version 5 278REQ |
HIPAA_A1_NPI_278_RES_to_RMAP_5 |
HIPAA 5010A1 (NPI) 278 Services Review Response |
Redix RMAP Version 5 278RES |
HIPAA_A1_NPI_820_to_RMAP_5 |
HIPAA 5010A1 (NPI) 820 Group Payment Remittance |
Redix RMAP Version 5 820 |
HIPAA_A1_NPI_834_to_RMAP_5 |
HIPAA 5010A1 (NPI) 834 Eligibility Audit Report |
Redix RMAP Version 5 834 |
HIPAA_A1_NPI_835_to_RMAP_5 |
HIPAA 5010A1 (NPI) 835 Claim Remittance Advice |
Redix RMAP Version 5 835 |
HIPAA_A2_NPI_837_Inst_to_RMAP_5 |
HIPAA 5010A2 (NPI) 837 Institutional Claim Payment Request |
Redix RMAP Version 5 837I |
HIPAA_A2_NPI_837_Dent_to_RMAP_5 |
HIPAA 5010A2 (NPI) 837 Dental Claim Payment Request |
Redix RMAP Version 5 837D |
HIPAA_A1_NPI_837_Prof_to_RMAP_5 |
HIPAA 5010A1 (NPI) 837 Professional Claim Payment Request |
Redix RMAP Version 5 837P |
RMAP to HIPAA (Outbound Process):
Map Name |
Source Message Type |
Target Message Type |
RMAP_5_270_to_HIPAA_A1_NPI |
Redix RMAP Version 5 270 |
HIPAA 5010A1 (NPI) 270 Eligibility Request |
RMAP_5_271_to_HIPAA_A1_NPI |
Redix RMAP Version 5 271 |
HIPAA 5010A1 (NPI) 271 Eligibility Response |
RMAP_5_276_to_HIPAA_A1_NPI |
Redix RMAP Version 5 276 |
HIPAA 5010A1 (NPI) 276 Claim Status Request |
RMAP_5_277_to_HIPAA_A1_NPI |
Redix RMAP Version 5 277 |
HIPAA 5010A1 (NPI) 277 Claim Status Response |
RMAP_5_278REQ_to_HIPAA_A1_NPI |
Redix RMAP Version 5 278REQ |
HIPAA 5010A1 (NPI) 278 Services Review Request |
RMAP_5_278RES_to_HIPAA_A1_NPI |
Redix RMAP Version 5 278RES |
HIPAA 5010A1 (NPI) 278 Services Review Response |
RMAP_5_820_to_HIPAA_A1_NPI |
Redix RMAP Version 5 820 |
HIPAA 5010A1 (NPI) 820 Group Payment Remittance |
RMAP_5_834_to_HIPAA_A1_NPI |
Redix RMAP Version 5 834 |
HIPAA 5010A1 (NPI) 834 Eligibility Audit Report |
RMAP_5_835_to_HIPAA_A1_NPI |
Redix RMAP Version 5 835 |
HIPAA 5010A1 (NPI) 835 Claim Remittance Advice |
RMAP_5_837D_to_HIPAA_A2_NPI |
Redix RMAP Version 5 837D |
HIPAA 5010A1 (NPI) 837 Dental Claim Payment Request |
RMAP_5_837P_to_HIPAA_A2_NPI |
Redix RMAP Version 5 837P |
HIPAA 5010A1 (NPI) 837 Professional Claim Payment Request |
RMAP_5_837I_to_HIPAA_A2_NPI |
Redix RMAP Version 5 837I |
HIPAA 5010A1 (NPI) 837 Institutional Claim Payment Request |
Example
You can test the conversion using this link. Below is an example of the RMap 837 Professional and its corresponding 837 file.
RMap 837 Professional (use “*” as a separator):
RMP*RMap_5_837P*20120925*0629*HIPAA_5010_837_Prof_to_RMap_5.map
IGM*00**00**ZZ*123456789012345*ZZ*123456789012345*030101*1253**00501*987654321*1*T*:*HC*123456789012345*123456789012345*19991231*0802*123456789*837*2021*1*987654321*1*123456789*52*2021**^*005010X222A1*005010X222A1
TR1*PREMIER BILLING SERVICE**************TGJ23*XYZ REPRICER*66783JJT*00*0123*20051015*1023*CH*JERRY*TE*3055552222*************2
PR0****KILDARE*BEN****1234567893*1234 SEAWAY ST**MIAMI*FL*33111***EI*123456789*****************************************2345 OCEAN BLVD**MIAMI*FL*33111************CONNIE*TE*3055551234*************2**************1
SB0*P******CI*19430501****SMITH*JANE***MI*111223333*******F**********KEY INSURANCE COMPANY*PI*999996666*3333OCEAN ST**SOUTH MIAMI*FL*33000***************PBS3334**1
PT0*19****SMITH*TED***236 N MAIN ST**MIAMI*FL*33413**19730501*M
CL0*26407789*79.04*11*1*Y*A*Y*I*P*********4779*2724*2780*53081****************************************************BK*BF*BF*BF
PR3*******************KILDARE*BEN****1234567893*204C00000X*G2*KA6663**************************************1
PR4**KILDARE ASSOCIATES***1234567893*2345 OCEAN BLVD**MIAMI*FL*33111
OS0*S*01****CI**Y*P*Y*SMITH*JACK***MI*T55TY666*236 N MAIN ST**MIAMI*FL*33111*********KEY INSURANCE COMPANY*PI*999996666*************************************1
LX0*HC*99213*****43*UN*1**1*2*3*4*************************20051003
LX1****************************************
LX0*HC*90782*****15*UN*1**1*2***************************20051003
LX1****************************************
LX0*HC*J3301*****21.04*UN*1**1*2***************************20051003
LX1****************************************
EOF
HIPAA 837 Professional:
ISA*00* *00* *ZZ*123456789012345*ZZ*123456789012345*030101*1253*?*00501*987654321*1*T*
GS*HC*123456789012345*123456789012345*19991231*0802*123456789*X*005010X222A1
ST*837*2021*005010X222A1
BHT*0019*00*0123*20051015*1023*CH
NM1*41*2*PREMIER BILLING SERVICE*****46*TGJ23
PER*IC*JERRY*TE*3055552222
NM1*40*2*XYZ REPRICER*****46*66783JJT
HL*1**20*1
NM1*85*1*KILDARE*BEN****XX*1234567893
N3*1234 SEAWAY ST
N4*MIAMI*FL*33111
REF*EI*123456789
PER*IC*CONNIE*TE*3055551234
NM1*87*2
N3*2345 OCEAN BLVD
N4*MIAMI*FL*33111
HL*2*1*22*1
SBR*P********CI
NM1*IL*1*SMITH*JANE****MI*111223333
DMG*D8*19430501*F
NM1*PR*2*KEY INSURANCE COMPANY*****PI*999996666
N3*3333OCEAN ST
N4*SOUTH MIAMI*FL*33000
REF*G2*PBS3334
HL*3*2*23*0
PAT*19
NM1*QC*1*SMITH*TED
N3*236 N MAIN ST
N4*MIAMI*FL*33413
DMG*D8*19730501*M
CLM*26407789*79.04***11:B:1*Y*A*Y*I*P
HI*BK:4779*BF:2724*BF:2780*BF:53081
NM1*82*1*KILDARE*BEN****XX*1234567893
PRV*PE*PXC*204C00000X
REF*G2*KA6663
NM1*77*2*KILDARE ASSOCIATES*****XX*1234567893
N3*2345 OCEAN BLVD
N4*MIAMI*FL*33111
SBR*S*01*******CI
OI***Y*P**Y
NM1*IL*1*SMITH*JACK****MI*T55TY666
N3*236 N MAIN ST
N4*MIAMI*FL*33111
NM1*PR*2*KEY INSURANCE COMPANY*****PI*999996666
LX*1
SV1*HC:99213*43*UN*1***1:2:3:4
DTP*472*D8*20051003
LX*2
SV1*HC:90782*15*UN*1***1:2
DTP*472*D8*20051003
LX*3
SV1*HC:J3301*21.04*UN*1***1:2
DTP*472*D8*20051003
SE*52*2021
GE*1*123456789
IEA*1*987654321
About Us
Redix International, Inc. is an enterprise software company. Redix develops software and provides services to help organizations convert their proprietary or organization-specific data to standardized data. Among the standardized formats supported are X12, EDIFACT, XML, NSF, UB92, HIPAA, HL7, CDA, Blue-Ribbon, FHIR, NCPDP, and PDF.