You have Javascript and/or stylesheets
disabled. Turning off Javascript or stylesheets disables the interactive functions
of this page and prevents the definitions of the various terms underlined below
from appearing when you place your mouse cursor over them.
Important update (5/4/2012)
The v4010 cut-off date has been extended to June 30. On July 1, all 837 transactions must be submitted in the v5010 format. All v4010 transactions submitted after June 30 will be rejected. If your practice management software is not v5010 ready or your clearinghouse does not have up-convert capabilities, please contact UHIN for information regarding their up-convert options.
In addition, on July 1, we will discontinue sending 864 Unformatted Error Reports for v4010 837 transactions. The 277CA Health Care Claim Status Acknowledgement includes the same information and is being used for v5010 837s instead of the 864.
Important dates (4/6/2012)
April 30 is the last day Regence will accept 837 Health Care Claims transactions in v4010 format. On May 1, all 837 transactions must be submitted in v5010 format and v4010 transactions will be rejected.
In addition, on May 1, we will discontinue sending 864 Unformatted Error Reports. The 277CA Health Care Claim Status Acknowledgement includes the same information and will be used instead of the 864.
Note: If your practice management software is not v5010 ready or your clearinghouse does not have up-convert capabilities, please contact UHIN for information regarding their up-convert options.
Now accepting v5010 claims and 999 and 277CA acknowledgement transactions are available 03/23/2012)
We are now accepting v5010 claims and 999 and 277CA acknowledgement transactions are available. We are upholding the March 31 date and will be fully complaint in v5010 format on April 1.
Effective April 1, Regence will no longer support the following v4010 transactions:
Use accurate ZIP code information to avoid rejection of your HIPAA v5010 claims (03/09/2012)
The full nine digit zip code must be included on all claim address information (e.g., Billing, Pay to, Mailing, Service location, etc). Pease do not use a default to “zip+0000”, you must use complete and accurate ZIP code information.
We strongly urge you to take action now and convert to v5010 before the March 31 enforcement date. Please review the important upcoming dates below:
March 12 - Regence will begin accepting v5010 claims. For a two week period, only a 999 acknowledgement response will be returned. Anyone who requires a 277CA response should not submit during this time.
March 23 - The 999 and 277CA acknowledgement transactions will be available.
March 31 - All submitters must be able to send v5010 claims to Regence by the CMS “Delayed Enforcement” period end date.
Important update and reminders (2/7/2012)
837 Health Care Claims transition to v5010
- Regence is on track to transition all submitters to v5010 837 P, I and D claims in early March.
- All UHIN submitters that are not yet ready to transition should continue working to complete their UHIN certification and SNIP Level 4 certification with us and all necessary v5010 testing as soon as possible.
- You may continue to send v4010 transactions in alignment with the CMS “Delayed Enforcement” period until March 31, 2012. After March 31, UHIN submitters must have all certification and testing completed and may only send v5010 claims to Regence.
Note: There will be no extensions past the CMS “Delayed Enforcement” period. We will enable all transactions to be conducted in v5010 on March 31, if not sooner. If you are not able to meet this deadline, please contact your clearinghouse, EDI Support or UHIN to discuss options.
835 Remittance Advice set up information
There are no certification or testing requirements for v5010 835. We strongly urge you to begin receiving v5010 835s as soon as possible. Request to be set up for V5010 835s by sending an email with the following information:
Subject: v5010 835 set up
Trading partner ID used to receive 835 remits: HT__________________
First and last name of contact:
Email of contact:
Phone number of contact:
We will notify you when your set up has been completed and the date that you will begin receiving v5010 835’s.
Important claims submission information (1/20/2012)
Until further notice, please continue to send v4010 claims to Regence BlueCross BlueShield of Utah. We are continuing to test with selected trading partners and expects to be ready to accept v5010 in early March. The UHIN payer list will then be updated with a description next to TPID HT00000-100 which will read “Regence 5010 Active”. Please also note that you cannot submit v5010 claims to Regence until you have first completed your UHIN certification and self testing to ensure that you meet Regence SNIP level 4 certification requirements. Claims that do not meet SNIP level 4 requirements will not be accepted.
If you are unable to send v4010 claims to Regence, you can access UHINt to key your claims. If you are not able to use this option, please contact our EDI support team at 1 (800) 713-1693 or via email to discuss other claims submission options.
All other transactions (e.g., 270 Eligibility Request and Response, 835 Remittance Advice) can be conducted with Regence in v5010.
HIPAA 5010 transaction compliance enforcement delay
Have you heard or read the Centers for Medicaid & Medicare Services (CMS) news release regarding a 90-Day Period of Enforcement Discretion for Compliance with New HIPAA Transaction Standards? Below is a clarification of what this means to you.
The deadline for v5010 compliance has not changed. The date was January 1, 2012, however if you have not yet completed UHIN certification, reached SNIP Level 4 certification or completed all of your necessary v5010 testing, you may continue to send Regence v4010 transactions in alignment with the recently announced CMS “Delayed Enforcement” period until March 31, 2012. It is important to understand that after March 31, 2012, you will need to have all certification and testing completed and may only send v5010 claims at that time.
Regence Payer Identification number is changing
In conjunction with the transition to HIPAA v5010 transactions, Regence has a new Payer Identification number.
The new TPID, HT000001-100, must be used for all v5010 transactions. The new single number will replace all six of the previous Regence Payer Identification numbers.
Please continue to use one of the following Payer Identification numbers when sending Regence v4010 transactions:
- HT000001-001 Institutional 837 transactions
- HT000001-002 Professional 837 transactions
- HT000001-005 Dental 837 transactions
- HT000001-011 FEP Institutional transactions
- HT000001-012 FEP Professional transactions
- HT000001-015 FEP Dental transactions
835 Remittance Advice set up information
Providers who would like to be set up to receive v5010 835 remit transactions prior to the March 31 CMS deadline, may submit a request by sending an email with the following information:
Subject: v5010 835 set up
Trading partner ID used to receive 835 remits: HT__________________
First/last name of contact:
Email of contact:
Phone number of contact:
You will be notified when your 835 set up has been completed and the date when you will begin receiving v5010 835’s.
Taxonomy code requirement effective January 1
Effective January 1, 2012, taxonomy codes are required for v5010 837 P, I and D claims.
The Health Care Provider Taxonomy Code Set is 10-digits and alpha numeric (e.g., 208D00000X). It is designed to classify health care providers by type and specialty.
- Providers may have more than one taxonomy code. (A complete list of taxonomy codes can be obtained from the Washington Publishing Company website.)
- The taxonomy code is intended to allow a health plan to be able to identify a provider's specialty and is used to correctly identify a provider and/or price a claim appropriately.
- During the National Provider Identifier (NPI) enrollment process, providers must select a primary and, if applicable, a secondary taxonomy code associated with their provider type. Providers are supplied a list of taxonomy codes to choose from that correspond to the type of services the provider renders.
Helpful taxonomy code submission information:
- Report taxonomy code in the PRV segment.
- If a taxonomy code is present, it must be valid.
- If you send a rendering provider loop, include the PRV at the 2310B level. If no rendering provider loop, include the PRV at the 2000A level.
- Note: You cannot send a taxonomy code in both the billing and rendering level on the claim.
A taxonomy code will also be required when submitting paper claims beginning January 1. If no taxonomy code is present, it could delay the processing of your claim or result in an incorrect payment.
Regence NPI rule change
To better support v5010 we have changed our NPI rules. Please submit your NPI only on your claims. We will no longer accept legacy provider numbers on the following electronic claim transactions:
837 - Health Care Claims:
D - Dental
I - Institutional
P - Professional
This rule applies to all claim transactions. You can make these changes in advance of v5010 implementation while sending v4010A1. Note: Your Tax Identification Number (TIN) must be reported in loop segment 2010BB. Please do not report your legacy provider number in this loop.
Claims processing and payment may be delayed if your NPI is not included on your claim. If you do not have an NPI please enumerate as soon as possible to ensure timely and accurate processing of your claims.
HIPAA 5010 address requirements
The following information regarding v5010 changes to address requirements may be helpful.
The v5010 format has three different address fields that providers need to complete:
- Billing address (the location where the service was rendered)
- Mailing address
- Pay-to address
Billing Provider Address
The billing provider address is the street address where the services were provided, which may or may not be the mailing address. The purpose of this information is to ensure that providers receive remittance advices at the correct payment location.
The Billing Provider Address is reported in the 2010 AA, N3 of the 837 claim transaction and must contain only a street address, also known as a physical address.
If your office is in a rural location, you can no longer report a P.O. Box in the Billing Provider loop. You must report your street address. If you do not know the street address, contact your local Post Office to obtain the address or the best description of your physical location.
Note: P.O. Box and lock box addresses cannot be reported in the N3 Billing Provider Address segment. If you use a P.O. Box address in this segment, your 837 will be considered out of compliance and your claim will not be accepted.
Payment delivery location
If you use a P.O. Box or lock box address as the delivery location for payments, continue to report the P.O. Box address in the Pay-to Address segment as previously.
2010-AA Billing Address and 2010 AB Pay-to-Address
Use only 2010 AB Pay-to-Address if you receive payment at a P.O. Box. Note: If you do not include any information in the Pay-to-Address segment, this indicates to Regence that you would like your remittance sent to the billing provider/physical location street address.
If you did not use your street address when you enrolled with Regence, it might cause a problem. We use the address that you provided at initial enrollment. You do not need to submit any changes if you want to receive payment exactly as you do today and you will be using the following 5010 provider loops correctly:
- 2010 AA Billing Address - can only contain street addresses
- 2010 AB Pay-to Address - use only if you receive payment at a P.O. Box. If you change your billing address to a street address from a P.O. Box and do not include the Pay-to Address information, we may not be able to identify you, causing claims to be pended or rejected. Note: If you do not include any information in the Pay-to-Address segment, this indicates to Regence that you would like your remittance sent to the billing provider/physical location street address.
Please monitor your 277CA and 999 reports and fix any errors that are listed.
HIPAA 5010 background information
On January 16, 2009, the U.S Secretary of Health and Human Services issued Final Rules for updated versions to the electronic transactions originally outlined under the Administrative Simplification Subtitle of the Health Insurance Portability and Accountability Act (HIPAA) of 1996. HIPAA 5010 is comprised of these rules.
The legislation mandates industry-wide migration from HIPAA 4010A1 to HIPAA 5010 for electronic health information transactions effective January 1, 2012.
HIPAA X12 version 5010 and National Council for Prescription Drug Programs (NCPDP) version D.0 are the new sets of standards that regulate the electronic transmission of specific health care transactions, including:
- Claims
- Eligibility
- Referrals
- Remittances
- Claim status
The following covered entities are required to conform to HIPAA 5010 standards:
- Hospitals
- Pharmacies
- Health plans
- Health care clearinghouses
- Dentists and other dental professionals
- Physicians and other health care professionals
The current transaction standard is X12 version 4010A1 for eligibility, claims status, referrals, claims, and remittances; and NCPDP version 5.1 for pharmacy claims.
Important dates
2009
2011
- January
- 4010A1 continues in dual-use
- Begin testing with your clearinghouse partner
2012
- January 1
- March 31
- CMS “Delayed Enforcement” period ends