Florida Division of Workers’ Compensation Claims EDI Release 3

Florida Division of Workers’ Compensation Claims EDI Release 3
Training (Continued)

FL Trading Partner Tables (requirements documents)

FL EDI Reporting requirements are defined in the Trading Partner Tables:
Required Report(s) Data needed on the Report(s) Applied Editing

The FL EDI Trading Partner Tables are used to convey FL’s EDI reporting requirements. Although they may appear “technical” and are used by IT staff and EDI Vendors to determine FL’s requirements, they were written by and for “business” staff.

These very important requirements documents can be found on the Claims EDI webpage, and are your resource for determining when a transaction should be filed and why it may have errored.

These are the Requirement Tables

FL Supplement Overview:
Tracks all monthly additions or corrections to the requirement tables. Check periodically for updates to this Supplement and all Tables.

What is an Event?

An Event is a business circumstance that occurs in the life of a WC Claim which requires the reporting of EDI information to DWC. These circumstances reflect FL’s requirements, including: First Report of Injury events Subsequent Report events Periodic events

Claim Business Events Claim Event Flow in FL 1. Establish Claim with
2. Initial Payment or Equivalent 9. Lump Sum Payment(s) 7. Suspend 10. Periodic Reports 3. Changes to Benefits/Amnts 5. Reinstate 11. Changes (Non-Indemnity) Benefits 6. Change 4. Suspension of all Benefits 12. Cancel 8. Claim Closure

This training has been redesigned to follow this claim event flow, regardless of whether an MTC is in the Primary or Secondary Implementation.

FL identifies all of the transactions (MTC’s) that are required for reporting specific business events on its Event Table.

Due to the national standard format and sequencing requirements, FL requires the reporting of more business events (MTC’s) than were required via paper forms.

Interpreting the FL Event Table
Example: Florida requires the submission of a FROI MTC 00 for First Reports of Injury or Illness based on the insurer’s mandate date …

… when disability is immediate & continuous & lost time is greater than seven (7) days.

The filing must receive a TA within 21 calendar days after the claim administrator’s knowledge of the injury.

A DWC-1 or IA-1 (ACORD 4) form must also be sent to the employee & employer

Periodic (Claim Cost) Reports
In addition to reporting “typical” business claim Events, FL requires the claim administrator to report the “cost status” of the claim via Periodic (Claim Cost) Reports

POP QUIZ

What is the Paper Equivalent of a
Periodic Report for FL?

Answer: DWC-13 Claim Cost Report

POP QUIZ

What are the Periodic MTC’s accepted by FL?

Answer: MTC SA & FN

Event Table FL Periodic Reports
SA Sub-Annual – Submitted every 6 months after the DOI, as defined on FL’s Event Table. FN Final – Submitted when Claim Administrator determines no further benefits will be paid.

We will now look at the online copy of FL’s Event Table….

Event Table In addition to the Event Table, FL describes its business events in the ‘MTC Filing Instructions’. This document (created by Karen Kubie ) is a quick reference tool displaying what MTC’s to use in reporting required business events to FL. MTC Filing Instructions

Helpful Resources

FL MTC Filing Instructions

FL Trading Partner Tables
Data needed on the Report(s)

Element Requirements The FL Element Requirement Table describes the data elements required for each electronic event (MTC) documented on the Event Table.

Element Requirements Data Element requirements are defined for each transaction (FROI or SROI) at the Maintenance Type Code (MTC) level.

Element Requirements Requirement Codes express FL’s requirement severity by data element and report type (FROI or SROI). The following slides define FL’s requirement codes.

Element Requirements The Element Requirement Table contains 6 worksheets: FROI Element Requirements FROI Conditions (for MC’s) SROI Element Requirements SROI Conditions (for MC’s) Benefit Segment Requirements Benefit Conditions (for MC’s)

Element Requirements F =
Fatal. The data element is essential to process the transmission/transaction.

Edits will NOT be applied, nor will the data be loaded for FL.
Element Requirements X = Exclude. The data element is not applicable to the standard requirements for the MTC and may or may not be sent. Edits will NOT be applied, nor will the data be loaded for FL.

Element Requirements M =
Mandatory. The data element must be present and must pass all edits (documented in the Edit Matrix) or the transaction will be rejected.

Element Requirements MC =
Mandatory/Conditional. The data element becomes mandatory under conditions documented on the applicable “Conditional Requirements” worksheets. If the defined condition exists, the data element becomes mandatory and mandatory rules apply.

Element Requirements Data Elements defined as M or MC (and the condition applies) are required fields. If they are not present on the transaction, the transaction will receive a Mandatory Field Not Present error (Error # 001).

Element Requirements IA =
If Applicable/Available. Data should be sent if available or applicable to the claim. If present, data will be edited for valid value and/or format. If the data passes the edits, the data will be loaded. If the data does not pass the edit, the data will not be loaded, and no error will be returned by FL.

Element Requirements NA =
Not Applicable. The data element is not applicable to FL’s requirements for the MTC, and may or may not be sent. FL will not be editing or loading these data elements for this MTC.

Element Requirements For DN’s that are on both the FROI and SROI, FL has identified which transaction (FROI Or SROI, or Both) from which it will edit/load data, and from which the data will be ignored (N/A).

Element Requirements Interpreting Requirement Tables FL’s Claim Number is not required on a FROI 00, 04, AQ or AU, but is Mandatory on a FROI 01 or 02.

Conditional Requirement Code Data Element Number and Name
Element Requirements FL Conditional Requirements Table Conditional Requirement Code Data Element Number and Name Business Conditions

Element Requirements Additional requirement codes were developed for the MTC 02 (Change) transaction. These will be discussed later in the training.

Element Requirements A Benefits segment is expected when indemnity benefits have been paid on the claim, for each applicable Benefit Type Code value indicated in the Edit Matrix. Only one Benefits segment can be sent for each Benefit Type Code.

Element Requirements “Event” Benefits Requirements are described on the Event Benefits Segment Requirement Table.

Element Requirements R =
Restricted. The data element value will not be accepted by FL. For example, FL does not accept Benefit Type Code 090 (PI) (Permanent Partial Disfigurement) for DOI’s < 08/01/79 or > 12/31/93

Element Requirements Restricted Benefit Types for FL

Element Requirements DN’s in the Benefits segment are required based on the MTC as well as the Benefit Type Code being paid. Net Weekly Amount

Element Requirements Data defined as N/A on the Element Requirement Table, or was not required by the “Condition” will not be edited, processed or loaded to DWC’s system if sent for that MTC. This is commonly misunderstood.

Element Requirements Example: Gross/Net Amounts are not required for MTC SA or FN. If these data elements are sent incorrectly, they will not be errored. However, if Gross/Net Amounts are sent wrong on the next Event where they ARE required (CA, CB, etc.) they WILL be errored.

Element Requirements Although the same data element may be on both the FROI and SROI, the Element Requirement Table will depict on which transaction the data is required. The other transaction will list the requirement as N/A, which means it will not be edited, processed or loaded to DWC’s system if sent for that MTC.

Element Requirements Example: Claim Type is not looked at on the FROI 00, but is required on the corresponding SROI IP. If it is only sent on the FROI and not the SROI, they will both reject.

Element Requirements We will now look at the online copy of FL’s Element Requirement Table….

Questions?

FL Trading Partner Tables
Applied Editing

The Edit Matrix details the edits applied by FL.

Pop Quiz: If a Transaction successfully passes all edits, what Application Acknowledgement Code is sent?

“TA” Transaction Accepted
Answer: “TA” Transaction Accepted

Pop Quiz: If a Transaction fails an edit, what Application Acknowledgement Code is sent?

“TR” Transaction Rejected
Answer: “TR” Transaction Rejected

Edit Matrix The FL Edit Matrix consists of 8 worksheets:
1. DN-Error Message Table 2. Value Table 3. Match Data Table 4. Sequencing Table 5. Duplicate Processing (Proprietary)

6. Population Restrictions
Edit Matrix Three proprietary worksheets (5., 7., and 8.) were added by FL to express additional editing. 6. Population Restrictions 7. FL Min_Max Table (Proprietary) 8. FL Calculation Table (Proprietary)

FL DN-Error Message Table (“L” Table)
The 1st Tab FL DN-Error Message Table (“L” Table)

Edit Matrix FL DN-Error Message Table
Contains “standard” logical edits developed for Release 3. Assists the claim administrator in determining what caused a specific error. (FL refers to this as the “L” Table.)

Release 3 Data Element Numbers and Names are listed down the left columns.

Error Message Numbers and associated descriptions are listed across the top of the table.

Edit Matrix FL DN-Error Message Table DN Numbers and Error Message Numbers are returned on the Acknowledgement to communicate errors.

The spreadsheet is populated with edit defaults by IAIABC. F = Fatal Technical data elements are essential for a transaction to be processed.

L = Edit applies to the data elements based on the requirements indicated on the Element Requirement Table. FL added some “L’s” to table (where allowed).

FL has added two proprietary codes: FL = Edit results in a nonfatal error which will be documented on the FL Claims EDI Data Warehouse. IA = Edit will be run. If edit fails, no error will be returned and data will not be loaded.

Edit Matrix FL DN-Error Message Table

FL has remapped some current R1 Error Codes to new or different Release 3 Error Codes.

FL Value Table

Edit Matrix FL Value Table
Conveys the code values that are expected to be reported to FL and code values that may be suppressed.

Edit Matrix FL Value Table The FL “Quick” Code Reference Guide assists in interpreting FL’s Value Table in the Edit Matrix. FL Quick Code Reference ( FL DWC Website)

Edit Matrix FL Value Table
The Value Table is separated into two sections: Section 1: If a Data Element is collected by FL but a certain code value is grayed out (i.e., Not Statutorily Valid in FL), the filing will be rejected if that value is sent.

Edit Matrix FL Value Table – Section 1
Reflects the FROI and SROI Maintenance Type Codes (MTC’s) FL will accept.

FL does not accept FROI MTC CO or UI, or SROI MTC CO or RE.

Edit Matrix FL Value Table Section 1 (cont’d):
If a Data Element is not collected by FL (reflected as “N” in “Capture?” column) and code values are grayed out, a filing will not be rejected if sent with those values.

Ex: FL does not require or process Initial Treatment Codes.

Edit Matrix FL Value Table Section 2:
If a Data Element is statutorily valid in FL (e.g., physician payments), but not required to be reported, the corresponding code value(s) is grayed out on the table, and the filing will not be rejected if sent with that value.

Section 2: FL will NOT process the grayed out values; however, they ARE statutorily valid (e.g. atty fees).

Ex: 330 (Total Employer’s Legal Expenses) Ex: 340 (Total Claimant’s Legal Expenses) Clm Admins may suppress these values.

Questions?

FL Match Data Table

Edit Matrix FL Match Data Table
Describes the data elements that will be used by FL to determine if the transaction will create a new claim, or be associated with an existing claim in DWC’s database.

If you receive Error # 117, “Match Data Value Not Consistent With Value Previously Reported,” check this table to see which data elements are being used as match data.

Match criteria will be also applied between FROI and SROI combo filings. If any of the match data is different between the FROI and SROI, they will not be paired together for processing.

DWC has added a column to the Match Data table to identify how we are matching to combine FROI with corresponding SROI’s.

Match Data Rules Standard Match Data Rules are described in Section 4 of the IAIABC R3 Implementation Guide.

FL Sequencing Table

Edit Matrix FL Sequencing Table The FL Sequencing Table elaborates on standard error messages related to transaction “sequencing” (error # ).

Transaction Sequencing
Standard minimum Transaction Sequencing limitations are described in Section 4 of the IAIABC R3 Implementation Guide.

Understanding Transaction Sequencing in Section 4 of the IAIABC R3 Imp. Guide is necessary for understanding the FL Sequencing Table.

Edit Matrix FL Sequencing Table
The FL Sequencing Table illustrates the sequence in which business events (MTC) typically occur during the life of a claim and what MTC must have preceded the subsequent MTC.

Claim Event Flow in FL 1. Establish Claim with 2. Initial Payment or Equivalent 9. Lump Sum Payment(s) 7. Suspend 10. Periodic Reports 3. Changes to Benefits/Amnts 5. Reinstate 11. Changes (Non-Indemnity) Benefits 6. Change 4. Suspension of all Benefits 12. Cancel 8. Claim Closure

Now lets try to interpret the Edit Matrix “Minimum” Sequencing edits.

FL accepts FROI 00 (with SROI) or FROI 04 to establish a claim. No FROI sequencing edits are applied

Shows the minimum sequencing edits that will be applied for an IP or initial payment equivalent MTC.

Element Error Text (DN0291) is the FL error message text sent on the AKC which clarifies the Error Message Code “Invalid Event Sequence”.

If you do not understand what is meant by the 50 byte error text, you should look it up for more explanation.

FL Duplicate Processing

Edit Matrix FL Duplicate Processing

Edit Matrix FL Duplicate Processing
In addition to duplicate errors (#057), there are sequencing (#063) and matching errors (#117) in this table.

Edit Matrix FL Duplicate Processing Although we do not accept a 00/IP after a previous 00/IP, we WILL accept a 00/IP after a paper DWC-1; however, we will process this as an “00/IP SROI ONLY” and not as a First Report on your Report Card/Statistics.

FL Population Restrictions

All FL data element edits are documented in this worksheet.
Edit Matrix FL Population Restrictions All FL data element edits are documented in this worksheet.

Edit Matrix Population Restrictions
Each Population Restriction contains: The DN # and Name;

The Error # and Error IAIABC Message description;

The specific text describing the edit; and If you do not understand the 50 byte error message you received, this is the column that explains how the edit was applied.

The FL-specific text clarifying the IAIABC Error Message Text.

FL Min_Max Table (Proprietary)

FL Min_Max Table (Proprietary)
Edit Matrix FL Min_Max Table (Proprietary)

FL Calculation Table (Proprietary)

Edit Matrix FL Calculation Table (Proprietary)

Edit Matrix FL Calculation Table (Proprietary) This table will be used to validate the “Gross Weekly Amount” (based on the Wage sent) and the “Benefit Type Amount Paid” expected from the Claim Administrator (based on the weeks/days sent.)

Edit Matrix FL Calculation Table (Proprietary) DWC bases all financial calculations on the Average Wage that is sent. This includes calculations of Calculated Weekly Comp Amount, Gross Weekly Amount, Net Weekly Amount and Benefit Type Amount Paid.

Edit Matrix FL Calculation Table (Proprietary) For Example: If the Comp Rate sent is correct for the claim, but the Average Wage is incorrect for the claim, the transaction will reject (TR), due to the fact that the Comp Rate will not equal 66 2/3% of the Average Wage sent.

How do you know which Table/Tab to look at to research an error?...
Error 001 – Element Requirement Table (including Conditions Tab) Error 057 – Edit Matrix: Pop Rest and Duplicate Tab Error 063 – Edit Matrix: Pop Rest, Sequencing and Duplicate Tab Error Edit Matrix: Pop Rest and Match Data Tab All Other Error #’s: Pop Restrictions Tab

We will now look at the online copy of FL’s Edit Matrix….

Questions?

How Will EDI Errors Be Communicated to Claim Administrators?

The Division will acknowledge every EDI R3 transaction received with the standard EDI Acknowledgement format: ‘AKC’. AKC Report

The ‘AKC’ acknowledgement will identify how many transactions passed edits (TA -Transaction Accepted); how many failed edits (TR -Transaction Rejected); and the specific error(s) that caused the transaction to reject.

FL does not use the TE – “Transaction Accepted with Errors” Acknowledgement Code; however, certain errors will display in the warehouse as “TA-FL” and must be addressed by the claim administrator.

Acknowledgement results from the previous day’s transmission(s) will be posted by 9:00 a.m. the following morning in the EDI Data Warehouse (will be discussed more during the training.)

Transmissions received on or before 9:00 p. m. , E. S. T
Transmissions received on or before 9:00 p.m., E.S.T., will be processed by DWC the same day the transmission was sent. Transmissions will be acknowledged the next calendar day (usually by 9:00 a.m. E.S.T.)

Transmissions received after 9:00 p. m
Transmissions received after 9:00 p.m. EST will be processed by DWC the following calendar day, and will be acknowledged the day after the transmission is processed.

If you need to confirm if or when a particular filing or group of filings were received by the Division, you can “Search for Batches” in the Data Warehouse to determine when the FROI and/or SROI batch was received (Click on the “Batch ID” for batch details.

FL processes transmissions 7 days a week, including holidays.

If a transaction is improperly rejected by the Division, the entire batch will be re-processed and re-acknowledged using the ‘ARC’ Acknowledgement format (see the technical training PowerPoint for more details on the Acknowledgement Process)

If a transaction is improperly rejected by FL, the Claim Administrator will receive credit for the date the transaction was originally received by the Division.

FL provides EDI Claim Administrators the capability of viewing all FROI’s & SROI’s received, via the on-line Claims EDI Data Warehouse.

The on-line Claims EDI Data Warehouse will assist claim administrators in resolving EDI errors faster, and may also assist in resolving issues with the Centralized Performance System (CPS). Claims EDI Warehouse

More detailed information regarding the on-line Claims EDI Data Warehouse is provided later in the EDI training class. Claims EDI Warehouse

What is a JCN List and why do I need one?

JCN stands for “Jurisdiction Claim Number” and is assigned by DWC to a specific accident for a specific claim administrator.

JCN’s must be sent on all Subsequent reports, even on legacy cases that started prior to EDI So where do you get these numbers?

Claim Administrators are able to obtain a listing of JCN’s for all their Open claims, or those closed on or after , via the warehouse.

An updated listing is created weekly.
The JCN List contains the Date Prepared for the last DWC 1, 4, 12 and/or 13 on file with DWC. An updated listing is created weekly. Only the last 3 lists generated are kept on the EDI Warehouse. Note: The list can be downloaded to a text delimited file and modified as needed.

Jurisdiction Claim Number (JCN) Lists
are discussed in more detail later in the training.

FL BUSINESS SCENARIOS

FL SCENARIO ASSUMPTIONS

General scenario assumptions are included in the scenarios to assist in understanding the sample data that is presented.

The FL Scenarios were enhanced from the IAIABC scenarios in the R3 Implementation Guide. All the 2001 dates were moved forward to 2007 (the next year where all dates fell on the same day of the week).

Calculated Weekly Compensation Amount is the Comp. Rate, and is 66 2/3% of the Average Wage. The statutory comp rate max is not accurate per FL law.

Scenarios are presented in uppercase text. However, data may be sent to FL in mixed case format (except between FROI/SROI combos for match data.) Payment of indemnity benefits is based upon a 5 day work week The Industry Code must be a 2002 or 2007 NAICS code.

FL Scenarios contain required sample data elements pertinent to the scenario. These data are identified as “M” (Mandatory) or “MC” (Mandatory/Conditional) on the FL Element Requirement Table.

Additional data elements may be present in the scenario if they are identified as “IA” (If Applicable/Available) on the Element Requirement Table (e.g., Middle Initial and Suffix).

Although Claim Administrators may send additional data elements marked “NA” (Not Applicable), such data will not be edited or loaded by FL, and therefore not presented in the scenarios.

Note: Do not use the FL Business Scenarios to determine if a data element is required for a particular MTC. The Element Requirement Table is the official source of FL’s data element requirements per MTC and the conditions under which the data must be present.

FL SCENARIO PROFILES

FL Scenario Profiles Unless otherwise noted in the scenario narrative, the basic scenario profile information for all scenarios will be as follows….

FL Scenario Profiles Description Data Name: John James Smith, Jr.
Injured Employee Description Data Name: John James Smith, Jr. SSN: DOI: June 15, 2007 DOB: May 1, 1953 Empmnt Status: Full Time

FL Scenario Profiles Description Data Class Code: 2802 (Carpenter)
Injured Employee Description Data Class Code: (Carpenter) Days Worked/Week: 5 Wage: $15.00 Wage Period: Hourly (FROI)

FL Scenario Profiles Employer/Insured Description Data
Employer: Acme Construction Inc. FEIN: Physical Location: 32 Meadowbrook Lane Anytown, FL 32399 Industry (NAICS):

Insurer/Claim Administrator
FL Scenario Profiles Insurer/Claim Administrator Description Data Insurer: Old Reliable Ins. Co. FEIN: Average Wage: $600.00 Wage Period: Weekly (SROI)

FL SCENARIOS A FROI must be paired with the applicable SROI that is reporting the initial payment or equivalent, unless the FROI is reporting a Full Denial (MTC 04), Cancel (MTC 01), Change (MTC 02) or Acquired Claim (MTC AQ).

Complete Scenario for FROI/SROI Combo MTC “00” with “IP”
Disability Immediate & Continuous Rule 69L (1)(a)1., F.A.C.

Indemnity Benefits other than TP or IB or settlement will be paid, an
NEW CLAIM: Lost Time Case Where Disability is Immediate and Continuous If the Initial Payment of Indemnity Benefits will be made by the Claim Administrator, and Indemnity Benefits other than TP or IB or settlement will be paid, an Electronic First Report of Injury or Illness is due.

Due: 21 Days after Claim Administrator’s Knowledge of the Injury
NEW CLAIM: Lost Time Case Where Disability is Immediate and Continuous Send: FROI 00 with SROI IP Due: 21 Days after Claim Administrator’s Knowledge of the Injury Note: Also provide FORM DWC-1 or IA-1 to the employee & employer.

To avoid late filing penalties for an Electronic First Report of Injury or Illness, the EDI DWC-1 should be triggered immediately upon the CA’s disposition of the claim (payment or denial), to allow time for correction of potential errors and resubmission and subsequent receipt/acceptance by the Division within the filing due dates specified in Rule 69L-56, F.A.C.

FROI “00” Scenario Narrative
Employee fell from ladder at employer’s warehouse on 6/15/07. Employee broke his leg. Foreman witnessed the accident. Employee treated and released from the Emergency Room.

FROI “00” Scenario Narrative
Employee earned $15.00 an hour working 40 hours a week. Employer reported injury to insurer on 6/17/07.

FROI MTC “00” SCENARIO Claim Administrator reported the loss to DWC on 6/29/07.

FROI MTC “00” SCENARIO Insurer is identified.
Claim Administrator details are provided (remainder are on R21).

FROI MTC “00” SCENARIO Employer/Insured information is reported.
The Employer’s name is on the R21 The rest of the Employer’s address is on the R21 NAICS Code

FROI MTC “00” SCENARIO If applicable, Policy Number should be reported, but Effective Date & Expiration Date are not required.

FROI MTC “00” SCENARIO Details of the accident are included.
Employee broke leg falling from a ladder.

FROI MTC “00” SCENARIO Employer reported injury to claim administrator on 6/17/07.

FROI MTC “00” SCENARIO Details about injured employee are sent.
The rest of the Employee’s name and address is on the R21

FROI MTC “00” SCENARIO Date the initial disability began & other FROI fields must be reported on the SROI. Manual “Risk” Class Code is only on the FROI.

FROI MTC “00” SCENARIO Employee earned $15.00 an hour and worked 5 days a week. Employee has not returned to work.

FROI MTC “00” SCENARIO FROI Companion Record - R21

FROI MTC “00” SCENARIO Claim Administrator Claim Number is repeated in the R21. It links the R21 companion to the related 148.

FROI MTC “00” SCENARIO Claim Administrator FEIN is sent.
Claim Administrator Name is sent, and rest of the Claim Admin Address. 456 Main St

FROI MTC “00” SCENARIO ID qualifier = S.
Positions 232 to 246 contain a Social Security Number.

FROI MTC “00” SCENARIO Remainder of Employee name, address fields and phone are here in the R21 record.

FROI MTC “00” SCENARIO Type of Loss Code is reported on the SROI.
Employee has not returned to work.

FROI MTC “00” SCENARIO Insured FEIN and Insured Name are reported.

FROI MTC “00” SCENARIO Insurer Name and Insurer Type Code are reported.

FROI MTC “00” SCENARIO Details of accident site:

FROI MTC “00” SCENARIO Employer Name, Physical address and contact information.

FROI MTC “00” SCENARIO Employer Mailing Address information is not required.

FROI MTC “00” SCENARIO Claim Type Code and EP Salary Indicator are to be reported on the SROI.

FROI MTC “00” SCENARIO Variable Segment Counters include:
Two Accident/Injury Narratives, and One Witness segment.

FROI MTC “00” SCENARIO Accident description exceeds 50 characters; two segments are needed to send entire narrative description.

Variable Segment Population Rules for FROI
ACCIDENT/INJURY DESCRIPTION NARRATIVES SEGMENT: No more than 10 (50 byte narrative text) segments per claim, and the number of segments sent must equal the “Number” of Accident/Injury Description Narratives segment counter.

POP QUIZ If the Accident Description Narrative segments are 50 characters each, and this Accident Description is 161 characters…

…how many segments must be sent to report the entire Accident Description Narrative?

ANSWER = d (4 segments) * DN Data Element Name Data Beg End 0038
Accident/Injury Description Narrative AS HELEN WAS LEAVING HER WORK SITE (BLDG 500) SHE 1601 1650 WAS WAITING FOR HER HUSBAND TO PICK HER UP ON THE 1651 1700 STEPS OF THE BLDG. AS SHE LEANED AGAINST THE RAIL 1701 1750 ING & FELL. 1751 1800 * *If the last segment is less than 50 characters, it should be padded with spaces to complete the 50 character segment.

FROI MTC “00” SCENARIO Foreman Jones was the only witness.

Variable Segment Population Rules for FROI
WITNESSES SEGMENT: No more than 5 witnesses per claim, and the number of segments sent must equal the “Number” of Witnesses segment counter.

Questions on the FROI?

Florida Division of Workers’ Compensation Claims EDI Release 3

Similar presentations

Presentation on theme: "Florida Division of Workers’ Compensation Claims EDI Release 3"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Florida Division of Workers’ Compensation Claims EDI Release 3

Similar presentations

Presentation on theme: "Florida Division of Workers’ Compensation Claims EDI Release 3"— Presentation transcript:

Similar presentations

About project

Feedback