admin

Convert NCPDP Transactions to Comma Separated Value (CSV) files

This blog post describes the conversion of NCPDP D.0 transactions to CSV files and vice versa.

NCPDP Telecommunications Standard Version D.0 is an updated version of the HIPAA standard for pharmacy claims transactions. NCPDP D.0 includes the following transaction types:

  • B1 – Billing
  • B2 – Reversal
  • B3 – Re-bill
  • C1 – Controlled Substance Reporting
  • C2 – Controlled Substance Reporting Reversal
  • C3 – Controlled Substance Reporting Re-bill
  • D1 – Predetermination of Benefits
  • E1 – Eligibility Verification
  • N1 – Information Reporting
  • N2 – Information Reporting Reversal
  • N3 – Information Reporting Re-bill
  • P1 – Prior Authorization Request and Billing
  • P2 – Prior Authorization Reversal
  • P3 – Prior Authorization Inquiry
  • P4 – Prior Authorization Request Only
  • S1 – Service Billing
  • S2 – Service Reversal
  • S3 – Service Re-bill

Each transaction type contains request and response transactions, e.g., B1 request and B1 response. To help users integrate the NCPDP D.0 transactions into their existing applications, Redix International, Inc. has developed an NCPDP RMap (Redix Maps for NCPDP D.0) module. This module defines the NCPDP D.0 transactions in a CSV (comma separated value) format and yet carries 100% of the D.0 compliance. This format encapsulate NCPDP D.0 data into a more concise and readable format. It is easier to understand and to program because of the fewer number of records and fields. As a result, the Redix NCPDP RMap module is being used by many healthcare entities as their repository for storing their pharmacy claims data.

Redix NCPDP RMap Module

Click here to find more about the NCPDP RMaps specs. You can test the conversion by using this link.

Pre-Defined Maps

The Redix NCPDP RMap module contains pre-defined maps for all NCPDP D.0 transactions. These maps include the conversions from NCPDP D.0 to Redix CSV files and vice versa. Users can test the pre-defined maps by using this link.

Example

Below is an example of NCPDP B1 request transaction in D.0 format:

484848D0B156789012341014563663bbbbbbbb2007091598765bbbbb‑AM04C2987654321‑AM01C419620615C51CAJOSEPHCBSMITHCM123 MAIN STREETCNMY TOWNCOCOCP24567HNJSMITH@NCPDP.ORG‑AM07EM1D21234567E103D700006094268E730000D30D530D61D80DE20070915DF5DJ1EX4689EW1‑AM03EZ08DB00G2345DRJONES‑AM11D9557{DC50{DQ587{DU607{DN03

In the above, is a field separator, which is hex 1C.

 

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

Posted by admin

Convert HIPAA Transactions to Comma Separated Value (CSV) files

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.

Posted by admin in HIPAA

Redix HIPAA Compliance and Conversion Demo Services

Redix International, Inc. recently published a new website https://www.redixhipaa.com. This blog post describes the purpose and features of this new site.

Redix has been providing software to support HIPAA compliances and conversions for almost two decades. More than 200+ pre-defined HIPAA maps have been developed. These pre-defined maps allow users to easily integrate the HIPAA compliance and conversions into the users’ applications.

This new site provides a web-based interface to help users test the pre-defined maps. The interfaces are categorized into four sections:

  • HIPAA Compliance
    • HIPAA validation and compliance reporting for WEDI SNIP Types 1 through 5.
      • Type 1 EDI Standard Integrity Testing
      • Type 2 HIPAA Implementation Guide Requirement Testing
      • Type 3 HIPAA Balance Testing
      • Type 4 HIPAA Inter-Segment Situation Testing
      • Type 5 HIPAA External Code Set Testing
    • Supports compliance to 11 HIPAA transactions: 270, 271, 276, 277, 278 request, 278 response, 834, 835, 837 professional, 837 institutional, and 837 dental.
  • HIPAA Conversions
    • HIPAA conversions to PDF
      • 837 professional to CMS 1500
      • 837 institutional to CMS UB04
      • 837 dental to ADA J400
      • 835 to Medicare National Standard Intermediary Remittance Advice
    • HIPAA conversions to CSV
    • CSV conversions to HIPAA
    • HIPAA conversions to XML
      • Convert HIPAA transaction to XML
      • Supports 11 HIPAA transactions
    • XML conversions to HIPAA
      • Convert XML to HIPAA transaction
      • Supports 11 HIPAA transactions
    • NCPDP Conversions
      • NCPDP conversions to CSV
      • CSV conversions to HIPAA
      • HL7 Conversions
        • HL7 2.x conversions to FHIR
          • Convert HL7 2.x conversions to FHIR STU3
          • Following HL7 2.x messages are supported: ADT, ORU, MFN, PPP, SIU, and VXU.
        • C-CDA conversions to FHIR
          • Convert C-CDA to FHIR STU3

How to Test

The user can simply follow these steps:

  1. Go to the Redix HIPAA Compliance &Conversion Demo site: https://www.redixhipaa.com.
  2. Select a conversion type using the drop-down menus.
  3. Choose a file from your system. The file will be automatically uploaded, and then validated and converted. The outputs will be sent back to you.
  4. The output could be a single file or a zip file that contains multiple outputs.
  5. If the validation fails during the conversion process, an error message will be returned.

Since this is a demo site, you should follow these guidelines when submitting your file:

  • The file size must be less than 10 KB.
  • Do not use the real data.
  • The uploaded file will be automatically deleted 15 minutes after the file is submitted.

Redix HIPAA Products

Redix provides a suite of solutions to help enterprises exchange healthcare transactions electronically. These products include:

All of the pre-defined maps are built using the Redix AnyToAny Format Converter Engine and some of the modules.

Consultation Services

If our pre-defined maps do not meet your needs, you can contact us and we can help you to build customized maps.

Privacy Policy

Please refer to the Redix privacy policy before you use the site: https://www.redixhipaa.com/privacy

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.

Posted by admin in HIPAA

DISA Presentation on Healthcare Claims and Payments (835)

Back to the year 2001, I made the presentation at DISA (Data Interchange Standards Association) conference about the usage of HIPAA 835. The topic is “HealthCare eCommerce: Claims and Payments/ERA. Seventeen years later, I found out the content is still good. So, here is the presentation in PowerPoint.

Posted by admin in HIPAA

Test Results of CMS Blue Button 2.0 Sandbox

This blog post describes our initial test results of the CMS Blue Button 2.0 Sandbox 2.0 API. During this API’s test period, we built a web-based solution (https://www.redixbb.com) to allow Medicare beneficiaries to view their claim data. Press this link to view our prototype.

CMS published the Blue Button 2.0 Documentation for developers (https://bluebutton.cms.gov/developers/). The documentation is clear, and developers should be able to follow the documentation to implement a solution. While you are on the site, you should also check the support link to view the discussions and ideas on a certain topic.

This report can be used to help developers save development time. However, if Blue Button API specifications are changed in the future, this report will be revised accordingly.

  • In general, the Blue Button 2.0 API follows the FHIR STU 3 specifications (https://www.hl7.org/fhir/). However, not all of the FHIR specifications are supported. You can check the capability statement defined in the metadata for the Blue Button API (https://sandbox.bluebutton.cms.gov/v1/fhir/metadata). Currently, CMS Blue Button Sandbox supports three resources: Patient, Coverage, and EOB (ExplanationOfBenefit). Vital stats, such as Observation or AllergyIntotelenace are not supported.
  • The CMS authorization endpoint is:

           https://sandbox.bluebutton.cms.gov/v1/o/authorize/

           Note that “/” at the end is important. If you don’t include it, you will get a 404 error.

  • Blue Button Sandbox has 30,000 sample accounts from BBUser00000 to BBUser29999 with the password “PW00000!” to “PW29999!”. Note that the “!” is part of the password.
  • The maximum number of EOB records returned by the Blue Button Sandbox in one API call is 50. One can use “count=nn” to set the number of EOBs , where nn is a number between 1 and 50. Note that the FHIR standard uses “_count” (https://www.hl7.org/fhir/search.html) as a search parameter. In the Blue Button, however, “_count” will be ignored. One has to use “count” (no underscore) in order to set the number of EOBs to be returned.
  • The wildcard search is not supported. For example, the following statement will result in a 404 error.

https://sandbox.bluebutton.cms.gov/v1/fhir/ExplanationOfBenefit/carrier-209*

  • FHIR supports two search parameters, “_include” and “_revinclude”. Users can use these two keywords to query a resource and its referred resources. For example, users can use the _include parameter in patient resource queries to indicate that other resources that refer to the same subject (patient) be included in the results. Both “_include” and “_revinclude” are not supported in Blue Button API.
  • When registering your application on https://sandbox.bluebutton.cms.gov/v1/accounts/mfa/login, you need to define a field “Redirect Uris”. The redirect field must start with “http://”, regardless of the environment. If you only enter “localhost:my_port/my_application_entry_point” for your development environment, it will not work and a “Enter a valid URL” error will be returned. Also, the “Redirect Uris” must be a valid path in your application. If not correctly set, an error “invalid_request: mismatching redirect URI” will be returned.
  • Once an access token is obtained from the Blue Button, the token will be good for the next 36,000 seconds, i.e., 10 hours.
  • Duplicates of ExplanationOfBenefit.id in the sandbox were reported. We are assuming this will not be a problem in production.
  • The math in an EOB does not add up correctly in the sandbox. We are also assuming that this will not be an issue in the production environment.
Posted by admin in Blue Button, FHIR

Convert HIPAA 837 Dental to ADA J400 Form

This blog post describes the mapping specifications and the conversion between HIPAA 837 dental and ADA (America Dental Association) J400 in PDF format.

This was one of the 300+ pre-defined HIPAA maps that Redix International, Inc. has developed in the past 20 years. The user can integrate this map into their system with no further work.

You can test the map by going to Redix HIPAA Compliance and Conversion Demo.

A blank ADA J400 form looks like the following.

Mapping Specification

 

The ADA J400 form is using the box id to identify the meaning of each field. For example, a patient name is in box 12 and the patient date of birth is in box 13. The patient name in a HIPAA 837 dental is defined in 2010BA. Below is a table to describe the box id in the ADA J400 form and its corresponding element in HIPAA 837 dental.

Form Box IDMapping
1Checkbox Xwalked from 2300 CLM12, 19
22300 REF02 (REF01="G1" | "G3")
32010BB NM101, N3xx, N4xx
4Checkbox Xwalked by existence of 2320 loop
52330A NM103-05, 07
6Not Mapped
7DNE in HIPAA 837
82330A NM109
92320 SBR03
10Checkbox Xwalked from 2320 SBR02
112330B NM103, N3xx, N4xx
122010BA NM103-05,07, N3xx, N4xx
132010BA DMG02, converted
14Checkbox Xwalked From 2010BA DMG01
152010BA NM109
162000B SBR03
172000B SBR04
18Checkbox Xwalked From 2000B SBR02, overwritten by 2000C PAT01
19DNE in HIPAA 837
20Same as box 12 Unless Entire Set overwritten by 2010CA Equivalent
21Same as box 13 Unless overwritten by 2000CA, converted
22Checkbox Xwalked Same as box 14 unless overwritten by 2000CA
232300 CLM01
24(1-10)2300 DTP03 (DTP01="472"), overwritten by 2400 DTP03 (DTP01="472"), converted
25(1-10)2400 SV304:01
26(1-10)2400 TOO01 (first one only)
27(1-10)2400 TOO02, concatenated
28(1-10)2400 TOO03:01-05, concatenated
29(1-10)2400 SV301:02
30(1-10)2400 SV301:07
31(1-10)2400 SV307
32DNE in HIPAA 837
332300 CLM02
34Multiple mappings. "X" Xwalked from 2300 DN201
352300 NTE02, concatentated
36Xwalked from 2300 CLM09
37Xwalked from 2300 CLM08
38DNE in HIPAA 837
39Not Mapped
40Checkbox Xwalked from 2300 DN101
412300 DTP03 (DTP01="452")
422300 DN102
43Checkbox Xwalked from 2400 SV305
442400 DTP03 (DTP01="441"), converted
45Xwalked from 2300 CLM11:01-02
462300 DTP03 (DTP01="439")
472300 CLM11:04
482010AA NM103-05,07, N3xx, N4xx
492010AA NM109 (NM108="XX")
502300 REF02 (REF01="0B")
512300 REF02 (REF01="EI" | "SY")
521000A PER03 | 05 | 07 (qual="TE")
52A2300 REF02 (last one, not "0B", "EI", "SY")
53Xwalked from 2300 CLM06
54Same as box 49, unless overwritten by 2310B equivalent
55Same as box 50, unless overwritten by 2310B equivalent
562010AA N3xx, N4xx
56a2010AA PRV03, overwritten by 2310B PRV03
57Same as box 52
58Not Mapped

Some of the notes about this conversion:

  • Validates the input file. Only the file 837 is validated, the file will be converted.
  • Generates PDF file for each claim.

Example

Below is an 837 dental example:

 

ISA*00*          *00*          *ZZ*123456789012345*ZZ*123456789012345*030101*1253*^*00501*987654321*1*T*:
GS*HC*123456789012345*123456789012345*19991231*0802*123456789*X*005010X224A2
ST*837*0322*005010X224A2
BHT*0019*00*0123*20061123*1023*CH
NM1*41*1*41-LAST*41-FIRST*41-MIDDLE***46*41-46-PRIMARY
PER*IC*41-CONTACT*TE*41-TE*FX*41-FX*EM*41-EM
PER*IC*41-CONTACT*TE*41-TE*FX*41-FX*EM*41-EM
NM1*40*2*40-NAME*****46*40-46-PRIMARY
HL*1**20*1
PRV*BI*PXC*2000A-TAXONOMY
CUR*85*CAD
NM1*85*1*85-LAST*85-FIRST*85-MIDDLE***XX*1234567893
N3*85-ADDRESSLINE1*85-ADDRESSLINE2
N4*85-CITY*FL*33411
REF*EI*123456789
REF*1G*85-1G-SECONDARY
REF*0B*85-0B-SECONDARY
PER*IC*85-CONTACT*TE*85-TE*FX*85-FX*EM*85-EM
PER*IC*85-CONTACT*TE*85-TE*FX*85-FX*EM*85-EM
NM1*87*1
N3*87-ADDRESSLINE1*87-ADDRESSLINE2
N4*87-CITY*FL*33411
NM1*PE*2*PE-NAME*****PI*PE-PI-PRIMARY
N3*PE-ADDRESSLINE1*PE-ADDRESSLINE2
N4*PE-CITY*FL*33411
REF*2U*PE-2U-SECONDARY
REF*EI*123456789
HL*2*1*22*1
SBR*S********CI
NM1*IL*1*ENERST*WILLIAM***SUF*MI*IL-MI-PRIMARY
DMG*D8*19751221*M
NM1*PR*2*PLAN ABC*****PI*PR-PI-PRIMARY
N3*PR-ADDRESSLINE1*PR-ADDRESSLINE2
N4*PR-CITY*MO*64015
HL*3*2*23*0
PAT*19
NM1*QC*1*GAGA*SINGER***SUF
N3*123 APPLEWOOD LN
N4*GARDEN CITY*MO*64015
DMG*D8*19751221*M
REF*Y4*QC-Y4-SECONDARY
CLM*SMITH788*4000***11:B:1*Y*C*Y*I
DTP*439*D8*20060108
DTP*452*D8*20060108
DTP*472*D8*20060108
DTP*050*D8*20051030
DN1*36*27
DN2*8*E****JP
PWK*OZ*BM***AC*DMN0012
CN1*02*550
AMT*F5*152.45
REF*G3*13579
REF*4N*1
REF*F8*R555588
REF*9F*12345
REF*G1*13579
REF*9A*RJ55555
REF*9C*RP44444444
REF*D9*TJ98UU321
K3*STATE DATA REQUIREMENT
NTE*ADD*PATIENT IS EXTREMELY SENSITIVE TO PAIN AND REQUIRES ADDITIONAL SEDATION
HI*BK:52403*BF:52404
HCP*03*100*10*RPO12345
NM1*DN*1*SMITH*JO0HN***SUF*XX*1234567893
PRV*RF*PXC*DN-TAXONOMY
REF*0B*DN-0B-SECONDARY
REF*1G*DN-1G-SECONDARY
REF*G2*DN-G2-SECONDARY
SBR*P*01*GR00786******13
CAS*OA*93*15.06
AMT*D*411
AMT*EAF*75
AMT*A8*273
OI***Y***I
MOA***A4
NM1*IL*1*JORDAN*DALE*E**SUF*MI*IL-MI-PRIMARY
N3*IL-ADDRESSLINE1*IL-ADDRESSLINE2
N4*IL-CITY*MO*64015
NM1*PR*2*HEALTH PLAN A*****PI*PR-PI-PRIMARY
DTP*573*D8*20040203
LX*1
SV3*AD:D8080*4000****1
TOO*JP*12*L:O
DTP*472*D8*20060108
DTP*441*D8*19980401
DTP*452*D8*20040927
DTP*446*D8*20041027
DTP*196*D8*20041015
DTP*198*D8*20041029
CN1*02*550
REF*6R*54321
REF*9A*RJ55555
REF*9C*RP44444444
AMT*T*45
HCP*03*100*10*RPO12345
SE*94*0322
GE*1*123456789
IEA*1*987654321

The generated PDF file is as follows.

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.

Posted by admin in HIPAA

Convert HL V2.x MFN, PPP, REF, SIU, and VXU message to FHIR

In our previous posts, we described the conversions between HL7 2.x ADT and ORU messages and FHIR STU3. This blog post explains how we convert other HL7 2.x messages to FHIR STU3 (3.0.1).  These “other” messages include the following:

  • MFN: master file – staff practitioner
  • PPP: patient pathway
  • REF: patient reference
  • SIU: scheduling information unsolicited
  • VXU: unsolicited vaccination record update

Below is a table that shows the mappings between the above HL7 2.x messages and all possible FHIR resources. Note that the section number can be changed in a different release.

HL7 2.x Message Type FHIR Resource URL Section
MFN Practitioner http://hl7.org/fhir/stu3/practitioner-mappings.html 8.4.9.2
PPP Patient http://hl7.org/fhir/stu3/patient-mappings.html 8.1.14.4
Condition http://hl7.org/fhir/stu3/condition-mappings.html 9.2.7.4
REF Patient http://hl7.org/fhir/stu3/patient-mappings.html 8.1.14.4
SIU Appointment http://hl7.org/fhir/stu3/appointment-mappings.html 12.10.9.2
Patient http://hl7.org/fhir/stu3/patient-mappings.html 8.1.14.4
VXU Patient http://hl7.org/fhir/stu3/patient-mappings.html 8.1.14.4
Immunization http://hl7.org/fhir/stu3/immunization-mappings.html 11.6.7.3
ImmunizationRecommendation http://hl7.org/fhir/stu3/immunizationrecommendation-mappings.html 11.7.7.2
MedicationAdministration http://hl7.org/fhir/stu3/medicationadministration-mappings.html 11.2.8.2

 

Some of the notes about this conversion:

  • Validates the input file. Only the file is validated, the file will be converted.
  • Generates FHIR in json format
  • Uses “bundle” as an FHIR resourceType
  • Uses “transaction” as type
  • Uses uuid for the “id” in each resource
  • Uses “urn:redix-fhir” for the identifier.system
  • Uses “PUT” method in the “request” collection. To make sure that the patient data is unique in the FHIR data server, “ifNoneExist” method is used.

You can test the conversion by going to Redix HIPAA Compliance and Conversions, and then select a file of the supported message type from your system by pressing the “Select File” button. After a file is selected, your file will be automatically converted to an FHIR message, providing the file is a valid HL7 2.x file. You will see the message type and the version number of your HL7 file. In the following example, it is SIU and V2.4, respectively.

After the conversion, you might want to upload the FHIR JSON message to your FHIR data server. The default FHIR data server is HAPI, http://fhirtest.uhn.ca/. You can press the button “Upload to FHIR Data Server” to upload your FHIR resources to the FHIR data server.

You can, of course, use your own FHIR data server. To do so, you will need to first signup and then define your data server as a default FHIR data server.

Example

Use the following SIU file as an example:

MSH|^~\&|app|sender|HL7API|PKB|201303080949||SIU^S12|ABC0000000001|P|2.4
SCH|ID123||||||^checkup^||||^^^201411201231^201411201232|||||||||||||||
NTE|||My comment|
PID|||5555555555^^^NHS^NH||Smith^John^Joe^^Mr||19700101|M|||My flat name^1, The Road^London^London^SW1A 1AA^GBR||john.smith@hotmail.com^NET~01234567890^PRN~07123456789^PRS|john.smith@company.com^NET~01234098765^WPN||||||||||||||||N|
PV1|||^^^^^^^^health centre

The above ADT message is converted to the following FHIR message in JSON, which includes three resources: Patient and Appointment.

{
  "resourceType": "Bundle",
  "type": "transaction",
  "entry": [
    {
      "resource": {
        "resourceType": "Appointment",
        "id": "3AE29201-9255-442C-986D-104E2D261444",
        "identifier": [
          {
            "system": "urn:redix-fhir",
            "value": "ID123.2014-11-20T12:31:00.2014-11-20T12:32:00"
          },
          {
            "system": "urn:originator",
            "value": "ID123"
          }
        ],
        "appointmentType": {
          "coding": [
            {
              "system": "http://example.org/appointment-type",
              "code": "checkup"
            }
          ]
        },
        "description": "My comment",
        "participant": [
          {
            "actor": {
              "reference": "Patient/3AE29223-9255-442C-986D-115E2D260101"
            }
          }
        ]
      },
      "request": {
        "method": "POST",
        "url": "appointment?identifier=redix-fhir|ID123.2014-11-20T12:31:00.2014-11-20T12:32:00"
      }
    },
    {
      "resource": {
        "resourceType": "Patient",
        "id": "67713845-5E10-4E45-9FF4-1409BEB75540",
        "identifier": [
          {
            "system": "urn:redix-fhir",
            "value": "Smith.John.male"
          },
          {
            "system": "submit_mrn",
            "value": "5555555555"
          }
        ],
        "name": [
          {
            "use": "official",
            "family": "Smith",
            "given": [
              "John"
            ],
            "suffix": "Mr"
          }
        ],
        "telecom": [
          {
            "system": "phone",
            "value": "john.smith@hotmail.com",
            "use": "home"
          },
          {
            "system": "phone",
            "value": "john.smith@company.com",
            "use": "work"
          }
        ],
        "gender": "male",
        "birthDate": "1970-01-01",
        "deceasedBoolean": "false",
        "address": [
          {
            "use": "home",
            "line": "My flat name 1, The Road",
            "city": "London",
            "state": "London",
            "postalCode": "SW1A 1AA"
          }
        ],
        "link": [
          {
            "other": "5555555555"
          }
        ]
      },
      "request": {
        "method": "PUT",
        "url": "Patient?family=Smith&given=John&gender=male",
        "ifNoneExist": "identifier=redix-fhir|Smith.John.male"
      }
    }
  ]
}

Contact Us

We can help you to develop conversions for messages besides ADT, ORU, MFN, PPP, SIU, REF, and VXU. Feel free to reach out or connect with me at @redixfhir. We are sure that we help you to develop a conversion tool that will satisfy your requirements.

 

Posted by admin in FHIR

Convert HIPAA 835 Electronic Remittance Advice to PDF

This blog post describes the mapping specifications and the conversion between a HIPAA 835 electronic remittance advice and a report form in PDF format.

This conversion is different from HIPAA 837 conversions because there is no corresponding standard form, such as CMS 1500 or UB04 that can be used in the mapping process. Instead, we followed the instructions from Medicare National Standard Intermediary Remittance Advice and developed a generic report form for remittance advice in PDF format, as shown below. This mapping is not meant to be final since users may want to customize the layout of the form. Regardless, this mapping specification can be served as a template for future customization. You can test the map by going to Redix HIPAA Compliance and Conversion Demo.

 

Mapping Specification

Below is a table to describe the mapping between HIPAA 835 and the above report file.

HIPAA 835 Electronic Remittance AdviceCMS Report
FPE2000 TS303, converted
PAIDBPR16, converted
CLM#calc: physical count of claims per ST (not reset outside of ST)
TOB2100 CLP08 + 09
Patient2100 NM103-05 (NM101="QC")
HIC2100 NM109
PAT STAT"01"
CLAIM STAT"1"
SVC FROM2100 DTP03 (DTP01="232"), converted
SVC THRU2100 DTP03 (DTP01="233"), converted
PCN2100 CLP01
MRNNot Mapped
ICN2100 CLP07
CHARGESNot Mapped
REPORTED2100 CLP03
NCVD/DENIED"0.00"
CLAIM ADS"0.00"
COVERED2100 AMT02 (AMT01="AU")
DAYS/VISITSNot Mapped
COST REPT"0"
COVD/UTIL"0"
NON-COVERED"0"
COVD VISITS"0"
NCOVVISITS"0"
PAYMENT DATANot Mapped
DRG AMOUNT"0.00"
DRG/OPER/CAP"0.00"
LINE ADJ AMT"0.00"
OUTLIER"0.00"
CAP OUTLIER"0.00"
CASH DEDUCTCAS03 (CAS01="PR", CAS02="1")
BLOOD DEDUCTCAS03 (CAS01="PR", CAS02="66")
COINSURANCECAS03 (CAS01="PR", CAS02="2")
PAT REFUND"0.00"
MSP LIAB MET"0.00"
REIM RATE2100 MOA01
MSP PRIM PAYER"0.00"
PROF COMPONENT"0.00"
ESRD AMOUNTCAS03 (CAS01="CO", CAS02="118")
PROC CD AMOUNT2100 MOA02
ALLOWED/REIM2100 CLP04
G/R AMOUNTCAS03 (CAS01="CO", CAS02="43")
INTERST2100 AMT02 (AMT01="I")
CONTRACTCAS03 (CAS01="CO", CAS02="A2")
PER DIM AMT2100 MOA01
NET REIM AMT2100 CLP04
REV2110 SVC04
DATE
HCPCS2110 SVC01:02
APC/HIPPS
MODS2110 SVC01:03
QTY2110 SVC05
CHARGES2110 SVC02
ALLOW/REIM2110 SVC03
GC2110 CAS01
RSN2110 CAS02
AMOUNT2110 CAS03
REMARK CODES2110 LQ02 (LQ01="HE"), Last occurrence
NOTES"REMARK CODES" code value is obtained from database "835Data"
REASON CODES2110 CAS01 (unique only)
DESCRIPTION"REMARK CODES" code value is obtained from the database "835Data"

Some of the notes about this conversion:

  • Only if the input file 835 is validated successfully, the file will be converted.
  • Each remittance advice will be generated in a separate PDF file.

Example

Below is an 835 example:

ISA*00*          *00*          *ZZ*123456789012345*ZZ*123456789012345*030101*1253*^*00501*987654321*1*T*:
GS*HP*123456789012345*123456789012345*19991231*0802*123456789*X*005010X221A1
ST*835*1234
BPR*C*150000*C*ACH*CTX*01*999999992*DA*123456*1512345678*123121234*01*999988880*DA*98765*20020913
TRN*1*12345*1512345678
DTM*405*20020916
N1*PR*INSURANCE COMPANY OF TIMBUCKTU
N3*1 MAIN STREET
N4*TIMBUCKTU*AK*89111
REF*2U*999
PER*BL*JOHN WAYNE*TE*8005551212*EX*123
N1*PE*REGIONAL HOPE HOSPITAL*XX*6543210903
N4*SEGMENT MISSING FROM IG*AK*89111
LX*110212
TS3*6543210903*11*20021231*1*211366.97********138018.4**73348.57
TS2*2178.45*1919.71**56.82*197.69*4.23
CLP*666123*1*211366.97*138018.4**MA*1999999444444*11*1
CAS*CO*45*73348.57
NM1*QC*1*JONES*SAM*O***HN*666666666A
MIA*0***138018.4
DTM*232*20020816
DTM*233*20020824
QTY*CA*8
LX*130212
TS3*6543210909*13*19961231*1*15000********11980.33**3019.67
CLP*777777*1*15000*11980.33**MB*1999999444445*13*1
CAS*CO*45*3019.67
NM1*QC*1*BORDER*LIZ*E***HN*996669999B
MOA***MA02
DTM*232*20020512
PLB*6543210903*20021231*CV:CP*-1.27
SE*30*1234
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.


Posted by admin in HIPAA

Convert HIPAA 837 Professional to CMS 1500 Form

This blog post describes the mapping specifications and the conversion between HIPAA 837 professional and CMS 1500 in PDF format.

This was another one of the 300+ pre-defined HIPAA maps that we have developed in the past. The user can integrate this map into their system with no further work. You can test the map by going to Redix HIPAA Compliance and Conversion Demo.

A blank CMS 1500 form looks like the following. 

Mapping Specification

The CMS 1500 form is using the box id to identify the meaning of each field. For example, a patient name is in box 2 and the patient address is in 5. The patient name in a HIPAA 837 professional is defined in 2010BA. Below is a table to describe the box id in the CMS 1500 form and its corresponding element in HIPAA 837 professional.

CMS 1500 Form Box IDHIPAA 837 Professional Corresponding Field(s)
1Checkbox Xwalked from 2000B SBR09
1a2010BA NM109
22010BA NM103-05 overwritten by 2010CA NM103-5 if exists
32010BA DMG02, 03 overwritten by 2010CA DMG02, 03 if exists
42010BA NM103-05
52010BA N3xx, N4xx overwritten by 2010CA N3xx, N4xx if exists
6Checkbox Xwalked from 2000B SBR02 | 2000C PAT01
72010BA N3xx, N4xx
8(Internally Used)
923230A NM103-05
9a2320 SBR03
9b(Internally Used)
9c(Internally Used)
9d2320 SBR04
10aCheckbox Xwalked from 2300 CLM11:01 | :02 | :03="EM"
10bCheckbox Xwalked from 2300 CLM11:01 | :02 | :03="AA"
10cCheckbox Xwalked from 2300 CLM11:01 | :02 | :03="OA"
10 (state)if 2300 CLM11:01 | :02 | :03="AA" then CLM11:04
112000B SBR03
11a2010BA DMG02, 03
11b2000x REF02 (REF01="Y4")
11c2000B SBR04
11dCheckbox Xwalked from 2310 Existence
12Signature Field (Not Mapped)
13Signature Field (Not Mapped)
142300 DTP01, 03 (DTP01="431" | "438")
152300 DTP01, 03 (DTP01="454" |"304" | "453" | "439" | "455" | "471" | "090" | "091" | "444")
162300 DTP03 (DTP01="360" & "361") concatenated
172310A, D NM101, 03-05
17a2310A REF01-02
17b2310A, D NM109
182300 DTP03 (DTP01="435" & "096") concatenated
19(reserved for proprietary usage)
202300 AMT02 (AMT01="NE"), Checkbox Xwalked from existence of 2310C
21"9" if HI01:01("BK") exists, else "0"
21A2300 HI01:02 (HI01:01="BK" | = "ABK")
21B2300 HI02:02 (HI01:02="BK" | = "ABK")
21C2300 HI03:02 (HI01:03="BK" | = "ABK")
21D2300 HI04:02 (HI01:04="BK" | = "ABK")
21E2300 HI05:02 (HI01:05="BK" | = "ABK")
21F2300 HI06:02 (HI01:06="BK" | = "ABK")
21G2300 HI07:02 (HI01:07="BK" | = "ABK")
21H2300 HI08:02 (HI01:08="BK" | = "ABK")
21I2300 HI09:02 (HI01:09="BK" | = "ABK")
21K2300 HI10:02 (HI01:10="BK" | = "ABK")
21L2300 HI11:02 (HI01:11="BK" | = "ABK")
222300 CLM05:03 when is "7" | "8", REF02 (REF01="F8")
232300 REF02 (REF01="G1")
24A2400 DTP03 (DTP01="472")
24B2400 SV105 | 2300 CLM05:01
24C2300 CLM05:03
24D2400 SV101:02-:06 concatenated
24E2400 SV107:01-:04 concatenated
24F2400 SV102
24G2400 SV104
24H"Y" if 2400 SV111 | SV112 are present
24I(Not mapped, currently assuming NPI is used in 'J')
24JNM109 (NM108="XX") (2010A is used, overwritten by 2310B if present, ultimately overwritten by 2420A if exists)
252010AA REF02 (REF01="EI" | "24") | NM109 (NM108<>"XX") | 2010AB NM109 (NM108<>"XX")
262300 CLM01
27Checkbox Xwalked from CLM07
282300 CLM02
29DNE
30(Internally Used)
31Signature Field (Not Mapped)
322310C NM103, N3xx, N4xx (If 2310 DNE then same contents from Box 33 are used)
32a2310C NM109 (If 2310 DNE then same contents from Box 33a are used)
32b(Not mapped, currently assuming NPI is used in 'A')
332010AA NM103, N3xx, N4xx, PER04,06,08 (qual = "TE")
33a2010AA NM109 (NM108="XX")
32b(Not mapped, currently assuming NPI is used in 'A')

Some of the notes about this conversion:

  • Validates the input file. Only the file 837 is validated, the file will be converted.
  • Generates PDF file for each claim.

Example

Below is an 837 professional example:

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

The generated PDF file is as follows.

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.

Posted by admin in HIPAA

Convert HIPAA 837 Institutional to CMS 1450/UB04 Form

This blog post describes the mapping specifications and the conversion between HIPAA 837 institutional and CMS 1450 (also known as UB04) in PDF format.

We have been in the HIPAA compliance and conversion business for the past 18 years. Through the years, we have developed more than 300 pre-defined HIPAA maps that allow users to plug and play the maps into the users’ system with no further work. One of the pre-defined maps that we have done a while ago is the HIPAA 837 Institutional (5010_A2) to CMS 1450 form in PDF format.

You can test the map by going to Redix HIPAA Compliance and Conversion Demo.

A blank CMS 1450 or UB04 form looks like the following. 

Mapping Specification

The CMS 1450 form is using the box id to identify the meaning of each field. For example, a patient name is in box 8a and the patient address is in 9a. The patient name in a HIPAA 837 institutional is defined in 2010BA. Below is a table to describe the box id in the CMS 1450 form and its corresponding element in HIPAA 837 Institutional.

CMS 1450 Form Box IDHIPAA 837 Institutional Corresponding Field(s)
12010AA NM103, N3xx, N4xx, PER04,06,08 (when qualifier is "TE")
2NM103, N3xx, N4xx, NM108, NM109 from 2010AA. Overwritten by 2010AB when exists.
3a2300 CLM01 (not always PCN)
3b2300 REF02 (REF01="EA")
42300 CLM05:01 + :03
52010AA NM109 (NM108="24") | REF01 (REF02="EI")
62300 DTP03 (DTP01="434"), converted
7(Internally Used)
8a2010BA | overwritten by 2010CA NM109 | REF01-02
8b2010BA | overwritten by 2010CA NM103-05
9a2010BA | overwritten by 2010CA N3xx
9b2010BA | overwritten by 2010CA N401
9c2010BA | overwritten by 2010CA N402
9d2010BA | overwritten by 2010CA N403
9e2010BA | overwritten by 2010CA N404
102010BA | overwritten by 2010CA DMG02, converted
112010BA | overwritten by 2010CA DMG03
122300 DTP03 (DTP01="435"), split, converted
132300 DTP03 (DTP01="435"), split, converted
142300 CL101
152300 CL102
162300 DTP03 (DTP01="096"), converted
172300 CL103
182300 HI01:02 (HI01:01="BG")
192300 HI02:02 (HI01:01="BG")
202300 HI03:02 (HI01:01="BG")
212300 HI04:02 (HI01:01="BG")
222300 HI05:02 (HI01:01="BG")
232300 HI06:02 (HI01:01="BG")
242300 HI07:02 (HI01:01="BG")
252300 HI08:02 (HI01:01="BG")
262300 HI09:02 (HI01:01="BG")
272300 HI10:02 (HI01:01="BG")
282300 HI11:02 (HI01:01="BG")
292300 CLM11:04
30(Internally Used)
312300 HI01:02, :04, converted (HI01:01="BH")
322300 HI02:02, :04, converted (HI01:01="BH")
332300 HI03:02, :04, converted (HI01:01="BH")
342300 HI04:02, :04, converted (HI01:01="BH")
352300 HI02:02, :04, converted (HI01:01="BI")
362300 HI02:02, :04, converted (HI01:01="BI")
37(Internally Used)
382010BA NM103, NM104, N3xx, N4xx
39a2300 HI01:02, :05 (HI01:01="BE")
39b2300 HI04:02, :05 (HI01:01="BE")
39c2300 HI07:02, :05 (HI01:01="BE")
39d2300 HI10:02, :05 (HI01:01="BE")
40a2300 HI02:02, :05 (HI01:01="BE")
40b2300 HI05:02, :05 (HI01:01="BE")
40c2300 HI08:02, :05 (HI01:01="BE")
40d2300 HI11:02, :05 (HI01:01="BE")
41a2300 HI03:02, :05 (HI01:01="BE")
41b2300 HI06:02, :05 (HI01:01="BE")
41c2300 HI09:02, :05 (HI01:01="BE")
41d2300 HI12:02, :05 (HI01:01="BE")
42 (1-22)2400 SV201
43 (1-22)2400 SV202:02, xwalked from codef database
44 (1-22)2400 SV202:02,:03,:04,:05,:06 all concatenated
45 (1-22)2400 DTP03, converted (DTP01="R72")
46 (1-22)2400 SV205
47 (1-22)2400 SV203
48 (1-22)2400 SV207
49 (1-22)(internally used)
50aAll boxes 50-65 placed using qualifier SBR01
2010BB | 2330B NM103 (Payor roll is primary)
50b2010BB | 2330B NM103 (Payor roll is secondary)
50c2010BB | 2330B NM103 (Payor roll is tertiary)
51a2010BB | 2330B NM109 (Payor roll is primary)
51b2010BB | 2330B NM109 (Payor roll is secondary)
51c2010BB | 2330B NM109 (Payor roll is tertiary)
52a2300 CLM09 | 2330 OI06 (Payor roll is primary)
52b2300 CLM09 | 2330 OI06 (Payor roll is secondary)
52c2300 CLM09 | 2330 OI06 (Payor roll is tertiary)
53a2300 CLM08 | 2330 OI03 (Payor roll is primary)
53b2300 CLM08 | 2330 OI03 (Payor roll is secondary)
53c2300 CLM08 | 2330 OI03 (Payor roll is tertiary)
54a2300 AMT02 (AMT01="F5") | 2330 AMT02 (AMT01="D") (Payor roll is primary)
54b2300 AMT02 (AMT01="F5") | 2330 AMT02 (AMT01="D") (Payor roll is secondary)
54c2300 AMT02 (AMT01="F5") | 2330 AMT02 (AMT01="D") (Payor roll is tertiary)
55aDNE
55bDNE
55cDNE
562010BA | 2330A NM109 (NM109="XX")
57a2010BA | 2330A REF02 contatenating all (Payor roll is primary)
57b2010BA | 2330A REF02 contatenating all (Payor roll is secondary)
57b2010BA | 2330A REF02 contatenating all (Payor roll is tertiary)
58a2010BA | 2330A NM103-05 (Payor roll is primary)
58b2010BA | 2330A NM103-05 (Payor roll is secondary)
58c2010BA | 2330A NM103-05 (Payor roll is tertiary)
59a2000B | 2320 SBR02 (crosswalked) (Payor roll is primary)
59b2000B | 2320 SBR02 (crosswalked) (Payor roll is secondary)
59c2000B | 2320 SBR02 (crosswalked) (Payor roll is tertiary)
60a2010BA | 2330A NM109 (Payor roll is primary)
60b2010BA | 2330A NM109 (Payor roll is secondary)
60c2010BA | 2330A NM109 (Payor roll is teritary)
61a2000B | 2320 SBR04 (Payor roll is primary)
61b2000B | 2320 SBR04 (Payor roll is secondary)
61c2000B | 2320 SBR04 (Payor roll is tertiary)
62a2000B | 2320 SBR03 (Payor roll is primary)
62b2000B | 2320 SBR03 (Payor roll is secondary)
62c2000B | 2320 SBR03 (Payor roll is tertiary)
63a2300 | 2330B REF02 (REF01="G1") (Payor roll is primary)
63b2300 | 2330B REF02 (REF01="G1") (Payor roll is secondary)
63c2300 | 2330B REF02 (REF01="G1") (Payor roll is tertiary)
64a2300 | 2330B REF02 (REF01="F8") (Payor roll is primary)
64b2300 | 2330B REF02 (REF01="F8") (Payor roll is secondary)
64c2300 | 2330B REF02 (REF01="F8") (Payor roll is tertiary)
65aEmployer DNE in 837
65bEmployer DNE in 837
65cEmployer DNE in 837
66"9" or "0" based on ICD qualifier
672300 HI01:02 (HI01:01="BK" | "ABK")
67a2300 HI01:02 (HI01:01="BF" | "ABF")
67b2300 HI02:02 (HI02:01="BF" | "ABF")
67c2300 HI03:02 (HI03:01="BF" | "ABF")
67d2300 HI04:02 (HI04:01="BF" | "ABF")
67e2300 HI05:02 (HI05:01="BF" | "ABF")
67f2300 HI06:02 (HI06:01="BF" | "ABF")
67g2300 HI07:02 (HI07:01="BF" | "ABF")
67h2300 HI08:02 (HI08:01="BF" | "ABF")
67i2300 HI09:02 (HI09:01="BF" | "ABF")
67j2300 HI10:02 (HI10:01="BF" | "ABF")
67k2300 HI11:02 (HI11:01="BF" | "ABF")
67l2300 HI12:02 (HI12:01="BF" | "ABF")
67m2300 HI01:02 (second HI) (HI01:01="BF" | "ABF")
67n2300 HI02:02 (second HI) (HI02:01="BF" | "ABF")
67o2300 HI03:02 (second HI) (HI03:01="BF" | "ABF")
67p2300 HI04:02 (second HI) (HI04:01="BF" | "ABF")
67q2300 HI05:02 (second HI) (HI05:01="BF" | "ABF")
68(internally used)
692300 HI02:02 (HI02:01="BJ" | "ABJ")
70a2300 HI01:01 (HI01:01="PR" | "APR")
70b2300 HI02:01 (HI02:01="PR" | "APR")
70c2300 HI03:01 (HI03:01="PR" | "APR")
71DNE
72a2300 HI01:02 (HI01:01="BK" | "ABK")
73(internally used)
742300 HI01:02,:04, converted (HI01:01="BP"| "BR"| "ABR")
74a2300 HI01:02,:04, converted (HI qual="BO" | "BQ" | "BBQ")
74b2300 HI02:02,:04, converted (HI qual="BO" | "BQ" | "BBQ")
74c2300 HI03:02,:04, converted (HI qual="BO" | "BQ" | "BBQ")
74d2300 HI04:02,:04, converted (HI qual="BO" | "BQ" | "BBQ")
74e2300 HI05:02,:04, converted (HI qual="BO" | "BQ" | "BBQ")
75(internally used)
762310A NM109,08,03,04
772310B NM109,08,03,04
782310C NM109,08,03,04
79DNE
802300 NTE02
81(reserved for proprietary usage)
Other Locations on Form
Creation DateSystem Date
PageTotal Service Lines / 22, rounded up
Of (page)Current LX count mod 22 calculation
Total Covered ChargesSUM 2400 SV203
Total Non-Covered ChargesSUM 2400 SV207
Other Notes
"Payor Roll"A notion (via variable in the OFD) that defined if entity is in reference to Primary, Secondary or Tertiary payment roll. Used to determine if block of data is in reference to "submitting" insurance, or "other insurance".
End of Crosswalk

Notes

We have developed a conversion tool that will take an 837 institutional file and convert it to the UB04 form in PDF format. Some of the notes about this conversion:

  • The input file will be validated first. Only the file 837 is validated successfully; the 837 file will be converted.
  • Each claim will result in a separate CMS 1450 PDF file.

Example

Below is an 837 Institutional example:

ISA*00*          *01*SECRET    *ZZ*SUBMITTERS ID  *ZZ*RECEIVERS ID   *030101*1253*^*00501*000000905*1*T*:
GS*HC*SENDER CODE*RECEIVER CODE*19991231*0802*1*X*005010X223A2
ST*837*1024*005010X223A2
BHT*0019*00*1024*20050711*1335*CH
NM1*41*2*REGIONAL PPO NETWORK*****46*123456789
PER*IC*SUBMITTER CONTACT INFO*TE*8001231234
NM1*40*2*CONSERVATIVE INSURANCE*****46*000110002
HL*1**20*1
NM1*85*2*LOCAL HOSPITAL*****XX*1122334455
N3*3423 SMALL STREET
N4*COLUMBUS*OH*432150000
REF*EI*111002222
HL*2*1*22*0
SBR*P*18*34561W******CI
NM1*IL*1*SMITH*JAMES*A***MI*34902390F
N3*934 NORTH STREET
N4*COLUMBUS*OH*432150000
DMG*D8*19621015*M
NM1*PR*2*CONSERVATIVE INSURANCE*****PI*00123
CLM*W392-49141*14.84***13:A:1**A*Y*Y
DTP*434*RD8*20050617-20050617
DTP*435*DT*200506170800
CL1*1*1*01
AMT*F3*14.84
REF*9A*459804390823
REF*D9*32423466233
HI*BK:53081 
HCP*00*0**333001234*********T1
NM1*71*1*RIVERS*DAWN****XX*1234567893
REF*1G*A12345
LX*1
SV2*0301*HC:A9999*14.84*UN*1
DTP*472*D8*20050617
SE*32*1024
GE*1*1
IEA*1*000000905

The generated PDF file is as follows.

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.

Posted by admin in HIPAA