Campus update regarding EDI release

Work Comp Campus main

Jan. 11, 2021

Work Comp Campus update regarding EDI release

The Workers' Compensation Modernization Program (WCMP) is planning an electronic data interchange (EDI) feature release Jan. 28. This release addresses priority feedback from stakeholders to deliver new functionality and will include the following.

  • Update FEIN validation rules:  FEIN edits will be updated to allow more flexibility in situations such as sole-proprietors.
  • 5XX benefit handling:  Maintenance Type Codes (MTCs) will no longer be required in the benefit segment when 5XX benefit types are reported.
  • Add SU to valid sequencing for EDI transactions:  Sequencing requirements will be updated to allow submission of the following MTCs after an SU:  04, AB, CA, CB, CD, EP, FN, IP, NT, PD, PX, SA, SX.
  • Duplicate EDI transactions within the same batch:  When duplicate transactions (same MTC and Claim Admin Claim Number) are present in a single batch, the first instance will be accepted (assuming all validation rules are passed) and the second instance will reject with a duplicate transaction error message instead of the entire batch failing.
  • Date of birth rejection when null in Campus:  When an Employee Security ID/WID (DN0206) and SSN/PIN (DN0042/DN0154) match on an employee with a null date of birth in Campus the submission will no longer reject. Instead the submitted date of birth will be used to update the employee record in Campus.
  • Edit date of birth on all employee details pages:  Department of Labor and Industry staff members will be able to update dates of birth on all employee records to allow for successful submission of MTCs that reject due to a date of birth mismatch.
  • Additional EDI sequencing updates for UI and PY:  Sequencing requirements will be updated to allow submission of the following MTCs after a UI:  FROI 02, 04, CD, EP, IP, FN, NT, PD, SU; and to allow submission of the following MTCs after a PY:  AB, CA, CB, SX.
  • Granting claim access to the adjuster by matching on claim adjuster email address:  Claim adjuster indicated on MTC submission will be added to claim if the following conditions are met:
    • adjuster is a member of the insurer or claim administrator group listed on the file; and
    • adjuster email address submitted in Claim Administrator Claim Representative E-Mail Address (DN0138) is an exact match to their Campus login email address.
  • Adding and/or switching the linked claim party administrator:  Claim Administrator will be updated or added on legacy files if different than existing file.
  • PX/SA sequencing updates:  The list of acceptable MTCs that can precede a PX will be expanded to:  IP, AP, EP, PY or SROI UR; and the list of acceptable MTCs that can precede an SA will be expanded to:  00, AU, AQ, UI or FROI UR.
  • SROI UR sequencing updates:  SROI URs will not be accepted on files with accepted FROI URs, regardless of a presence of a FROI 02 or NT.
  • NT/SROI 02 benefit sequencing:  Presence of benefits will now be irrelevant on SROI 02 and SROI NT transactions. (Exception:  SROI 02s referencing benefit changes will require benefit segments.)
  • DN0297 DN0003 comparison edit:  The First Day of Disability After the Waiting Period (DN0297) will now be able to be greater than the Maintenance Type Code Date (DN0003). In other words, DN0297 will be able to be a future date.
  • Error message updates:  Some error messages that were prioritized as confusing by stakeholders are being updated to be more specific. Data element names, instead of just numbers, are used when space allows.

Current error message

Updated error message

Row count mismatch during TransactionParty load. Expected:  6 Actual:  5

Duplicate Entity for DN0006/DN0098 relationship OR Duplicate Entity for DN0187/DN0098

Cannot insert the value NULL into column 'LocationID', table 'WCMP.dbo.TransactionParty
Location'; column does not allow nulls. UPDATE fails.

Employer Mailing address attributes are not valid

The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens
when a target row matches more than one source row. A MERGE statement cannot
UPDATE/DELETE the same row of the target table multiple times. Refine the
ON clause to ensure a target row matches at most one source row, or use the
GROUP BY clause to group
the source rows.

Duplicate DN0036, DN042, DN0422 invalid scenario OR Invalid scenario, please contact help desk

Cannot insert the value NULL
into column 'BenefitTypeID', table 'WCMP.dbo.Claim
Benefit'; column does not allow nulls. UPDATE fails.

Benefit Type Code is not valid

Row count mismatch during TransactionParty load. Expected: 6 Actual: 7

Duplicate Entity for DN0006/DN0098 relationship OR Duplicate Entity for DN0187/DN0098 relationship

Cannot insert the value NULL
into column 'ClaimPermanent ImpairmentBodyPartID', table 'WCMP.dbo.ClaimPermanent
Impairment'; column does not allow nulls. UPDATE fails.

Permanent Impairment Body Part Code is not valid

Cannot insert the value NULL into column 'ClaimDenial
ReasonID', table 'WCMP.dbo.ClaimDenial'; column does not allow nulls. UPDATE fails.

Full/Partial Denial Code is not valid

 


Sequencing

If you receive a sequencing error that points to a match data mismatch, email the EDI team at dli.edi@state.mn.us for the correct data. Use "Invalid match data error" in the subject line and in the body of the email message; also include the jurisdiction claim number (JCN) and/or your claim admin claim number.


How to reach us

Visit the DLI website for updates about Campus and training resources. EDI-specific questions can be email to the EDI team at dli.edi@state.mn.us. All other Campus-related questions can be emailed to the Workers' Compensation Division Help Desk at helpdesk.dli@state.mn.us.


Contact us