Frequently Asked Questions
- What are NJCRIB's definitions for the Valid Values for DN0074 Claim Type Code?
- Should Trading Partners file new claims if the injury or death of the employee is covered by Federal Employer's Liability Act, the Longshore and Harbor Workers' Compensation Act or the Jones Act?
- Is the NJCRIB Jurisdiction Claim Number (Agency Claim Number – Release 1.0) required on all transactions following the Original First Report of Injury report?
- What Employer FEIN should be used for employers with multiple corporate relationships?
- What should be transmitted to NJCRIB if a key match field (SSN, Last Name and DOI) is changed?
- Is there a difference between an EDI MTC CO Correction and a MTC 02 Change?
- What Impairment Body Part Codes will be used by NJCRIB?
- What edits will NJCRIB apply?
- If, after reaching production status, a problem develops with the system I am using to generate or transmit EDI reports to NJCRIB, what should I do to make sure NJCRIB is informed and that New Jersey receives all my claims in a timely fashion?
- What exceptions are available to a claim administrator regarding the NJCRIB EDI Reporting Requirements?
- How can the trading partner or a claim administrator monitor the data quality of their EDI transmissions once in production?
- How long after I send a transmission to NJCRIB should I expect to receive an electronic acknowledgement?
- Where is the Test/Production Indicator found?
- Once a trading partner has moved into production, where should their questions be directed?
- When will I be placed in production status by NJCRIB?
- While testing, can a trading partner test the FROI and the SROI together?
- What are "test" transmissions?
- What steps must be taken to become a third-party EDI Service Vendor for New Jersey EDI trading partners?
- What steps must be taken to become a trading partner with NJCRIB?
- Where are NJCRIB's EDI Requirements found?
- How do I contact NJCRIB with questions on EDI Reporting?
No, these are federal programs. There are no requirements to file as these injuries are outside of NJCRIB's jurisdiction.
Refer to NJCRIB's Edit Matrix – Match Data Table & Element Requirement Table located under the NJCRIB R3 EDI Imp Guide (njcribedi.info). Jurisdiction Claim Number (Agency Claim Number – Release 1.0) is a key match item for all reports following the First Report of Injury.
Use the FEIN of the corporate entity that has the legal responsibility for handling a given workers' compensation claim.
Send a MTC 02 Change transaction (First Report of Injury) to change any key match field(s). Please Note: Only one (1) key match field can be changed with a FROI MTC 02. Refer to NJCRIB's Edit Matrix – Match Data Table located under the NJCRIB R3 EDI Imp Guide (njcribedi.info).
Yes, there is a very important distinction between Corrections and Changes. Use the MTC 02 Change when data previously sent to NJCRIB on either a First or Subsequent Report is identified by the Claim Administrator to be different than previously reported. The MTC CO Correction is used in response to a report previously sent to NJCRIB that NJCRIB acknowledged via the acknowledgment with a "TE" (accepted with errors). The CO must match a previously sent transaction and contain the data element(s) or conditions identified on the acknowledgment as being in error. Refer to IAIABC Claims Release 3 Implementation Guide for additional information (www.iaiabc.org).
Please refer to NJCRIB's Edit Matrix – Valid Value Table located under the NJCRIB R3 EDI Imp Guide (njcribedi.info).
NJCRIB's edits and complete requirements (NJCRIB Trading Partner Tables) are located under the NJCRIB R3 EDI Imp Guide (njcribedi.info).
Immediately after a trading partner becomes aware that data/claims are not being sent or received by NJCRIB, you must begin using alternative or backup measures to send paper submissions immediately. Contact the NJCRIB EDI Coordinator (njcribedi@verisk.com) right away to develop a temporary reporting plan. Otherwise, your organization may be subject to penalties for failure or late reporting as provided by New Jersey law.
No exceptions will be made. However, hardship situations brought to the attention of the ITS Director by an Officer of the organization will be addressed by NJCRIB on a case-by-case basis.
NJCRIB recommends that the Claim Administrator develop tools to use the acknowledgment details to track overall performance.
The cut-off for receipt of data from NJCRIB Trading Partners will be 2:59 AM, Monday through Friday. Processing of NJCRIB Trading Partner Data will start at 3:00 AM. On Saturday and Sunday, Trading Partners can connect and upload FROI/SROI files which will be processed Monday at 3:00 AM. New Jersey Trading Partners will receive acknowledgment files no later than 5:00 AM (pending any unforeseen processing issues). If you have not received an acknowledgement within that time frame and have not received an advisory, please contact the NJCRIB EDI Support Mailbox at njcribedi@verisk.com.
The Test/Production Indicator is DN0104, located on the Header Record. Refer to the IAIABC EDI Release 3 Implementation Guide (www.iaiabc.org) for more information regarding data definitions and the specific construction of the Header Record.
All questions should be directed to the NJCRIB EDI Support Mailbox at njcribedi@verisk.com.
It is NJCRIB's goal to begin testing and moving our trading partners into production as quickly as possible after the testing process has been completed, which is described in the "NJCRIB – Release 3.0 Implementation Test Plan" under NJCRIB EDI Resources (njcribedi.info).
NJCRIB recommends that trading partners successfully test and implement their FROI transmissions before beginning their testing of SROI transmissions. This is because NJCRIB expects to use the data from the FROI production documents in the SROI test. However, exceptions may be considered if recommended by the NJCRIB EDI Coordinator. For additional information, see the "NJCRIB – Release 3.0 Implementation Test Plan" under NJCRIB EDI Resources (njcribedi.info).
Testing is a process used to determine whether you and NJCRIB can send and receive EDI reports. Testing with NJCRIB requires adherence to the NJCRIB Test Schedule and the submission of required test transactions. Testing serves two purposes: 1) it ensures that all technical details regarding the transmission process are correct for all three systems --reporters, the VAN, and NJCRIB; and 2) it requires that the data details within the specific transaction types meet NJCRIB requirements. The sender will be responsible for evaluating the acknowledgement transactions NJCRIB returns in response to the test. For additional information, see the "NJCRIB – Release 3.0 Implementation Test Plan" under NJCRIB EDI Resources (njcribedi.info).
Please refer to the "Registration Instructions" link under the Trading Partner Profile section (njcribedi.info). All certified vendors should send an email to njcribedi@verisk.com requesting to become a vendor. Upon NJCRIB's receipt of this request, an internal approval process will be conducted. All certified vendors who become approved reporters or senders of information to NJCRIB must also complete and pass the necessary testing procedures.
Please refer to the "Registration Instructions" link under the Trading Partner Profile section (njcribedi.info).
Please refer to the "NJCRIB R3 EDI Imp Guide" link under the NJCRIB EDI Resources section (njcribedi.info).
Send an email to the NJCRIB EDI Support Mailbox at njcribedi@verisk.com.