EDI Implementation Guide - Montana

1y ago
6 Views
2 Downloads
859.14 KB
31 Pages
Last View : 1m ago
Last Download : 3m ago
Upload by : Angela Sonnier
Transcription

STATE OF MONTANAEDI ImplementationGuideState of MontanaDepartment of Labor and IndustryEmployment Relations DivisionData Management Unit1805 Prospect Avenue, Helena MT 59601

Table of ContentsThe Worker’s Compensation DatabaseIntroduction to Electronic Data InterchangeGetting StartedImplementing EDIEDI Trading Partner AgreementEDI Third Party Administrator AttachmentDLI/ERD Trading Partner ProfileTrading Partner ProfileFirst Report of Injury (FROI) IAIABC Release #1 – Maintenance Code Table (MCO Table)Subsequent Report of Injury (SROI) IAIABC Release #1 - MCO TableDetailed Acknowledgement - IAIABC Release #1Header and Trailer - IAIABC Release #1Montana Report Submission TableMontana Subsequent Report CodesEDI Test Policy and ProcessSelecting a Transmission TypeEDI OverviewMontana Law 39-71-225, LinkMontana Administrative Rules, LinkGlossary***This guide contains Montana specific EDI information. It is a companion to theInternational Association of Industrial Accident Boards and Commissions (I.A.I.A.B.C),E.D.I. Implementation Guide, Release 1. You may download the I.A.I.A.B.C. E.D.I.Implementation Guide from their web site: www.iaiabc.org or you may contact them:I.A.I.A.B.C. 5610 Medical Circle, Suite 14 Madison, Wisconsin 53711,Telephone: 608-663-6355, FAX: 608-663-1546

The Workers Compensation DatabaseIn the late 1980s and early 1990s, Montana's workers' compensation system seemed tobe out of control. Premiums were rising at an alarming rate, medical costs weresoaring, and the courts appeared to be changing the rules on what benefits injuredworkers were entitled to receive. The unfunded liability at State Fund grew from tens ofmillions of dollars to hundreds of millions and private insurers were leaving the Montanamarketplace.Montana needed to gain better control of a program that paid out over 200 million inbenefits. In order to increase control, Montana needed improved managementinformation to focus and monitor reform efforts.During the 1993 legislative session, Representative Chase Hibbard introduced legislationthat created the workers' compensation database. The bill gave Montana its firstopportunity to collect and analyze data pertaining to many areas of workerscompensation.The law mandated data collection from insurers, employers, medical providers,claimants, adjusters, rehabilitation providers and the legal profession. The data providesmanagement information to the legislative and executive branches for the purpose ofmaking policy and management decisions, including: Performance information to identify quality and cost control issues and controlabuse; Trend information on medical, indemnity and rehabilitation costs and usage; Litigation and attorney involved data to identify trends, problems and costs of legalinvolvement.The database was designed with input and approval of a task force comprised ofadjusters, insurers, employers, legislators, State Fund, Montana Health Care Authority,the Legislative Auditor and rehabilitation providers. The task force adoptedInternational Association of Industrial Accident Boards and Commissions (IAIABC)standards. The team accepted forms-based reporting, guided rule development andapproved data elements to be collected and used in the development of both the FirstReport of Injury (FROI) and Subsequent Report of Injury (SROI) forms. These formsare currently used for reporting injury and benefit information to the Department ofLabor and Industry (DLI) Employment Relations Division (ERD).Initial development of the database was completed on April 17, 1995. The database nowprovides information from the FROI, SROI, independent contractors, UninsuredEmployer’s Fund, policy coverage, attorney fee agreements, and settlements.

Introduction to the Electronic Data InterchangeElectronic Data Interchange (EDI) is the computer-to-computer exchange of standardbusiness data using telecommunications. EDI allows insurers and the Department ofLabor and Industry a method of exchanging workers compensation informationelectronically. Many insurers nationwide use EDI routinely and ERD has worked hard tomake this service available for Montana's workers' compensation system.At this time, the Employment Relations Division (ERD) receives First Report of Injury(FROI) and Subsequent Report of Injury (SROI) information from insurers and sendselectronic acknowledgments each time data is received. ERD has also implementedpolicy reporting through EDI Proof of Coverage in conjunction with the National Councilon Compensation Insurance (NCCI).Montana Rules mandate insurers who send 50 or more FROIs in the preceding calendaryear to report electronically. Employment Relations Division also has voluntary tradingpartners. Regardless, insurers and third party administrators are required to sign atrading partner agreement with the Department of Labor and Industry. The agreementplaces them into test status. Upon successful completion of the testing requirements,the trading partner is approved to send production transactions. Trading Partners agreeto maintain their EDI reporting percentage at a 95% success rate.

Getting StartedThe following is a Claims Administrators Guide for how to start using EDI for reportingMontana’s Workers Compensation First Reports of Injury and Subsequent Reports ofInjury. The members of the IAIABC EDI Committee developed the guide for claimadministrators and the Montana Department of Labor and Industry (DLI) EmploymentRelations Division (ERD) has modified this guide for Montana’s Workers CompensationSystem and its needs.The benefits to reporting EDI are: Improved Data QualityReduction of paperworkAutomation - Eliminates data entryOn-line data storageFaster management reportingAutomated reconciliationReduced clerical workload and telephone calls/communicationHigh productivity without increasing staffMore timely communications Rapid exchange of business data Elimination of mail charges, courier services Improved production cycleUniform communications with all trading partners Following a national standard Allows for inter-state comparison of dataCost of using EDIYour costs may vary depending on software, telecommunications, and IAIABC fees.(IAIABC has a copyright on the flat file format for EDI. Their steering committeecomprised of Insurers and Jurisdictions voted to allow a yearly fee to those using thisformat to cover the cost of maintenance of this national standard).

Implementing EDIPreliminary QuestionsBe prepared to answer the following types of questions, which are often asked byDLI/ERD. Do you report to multiple states?Do you perform your own claims administration or do you use a third party?Who currently submits FROI and SROI reports to the jurisdictions?Do you support denials, corrections?Do you currently have access to a value added network or FTP transmission?Do you have an in-house computer system? If not, who provides your systemsupport?Are you willing to commit resources to the EDI project? If not now, when?Do you have the EDI facilities?Are you transmitting EDI for any workers compensation function?Do you support either ANSI X12n or Flat File format?What telephone communications are available?Preparation and Business Processes Examine and evaluate your business processes and how EDI will affect them. Conduct an in-depth review of all data elements using the DLI/ERD ElementTable.o Review the definition of each element.o Note the difference between these definitions and those of your firm.o Note those elements not statutorily valid on the Edit Matrix.o Note those elements not captured by your database that you wish to addas enhancements.o Determine if changes to hard copy forms are needed to be in alignmentwith the national standards. Identify reporting requirements for each data element. Conduct an in-depth review of the Maintenance Type codes (MTCs).o Apply the MTCs to reporting requirements.o Determine which MTCs are valid for DLI/ERD and which are not.o Once you have an understanding of the MTCs you can complete theClaim Event Table. Review test scenarios.o Determine those scenarios that are valid for DLI/ERD.

Determine the Data Elements and MTCs that are required for eachscenario.o Draft hard copies of the scenarios using DLI/ERDs forms for testvalidation.Claim Administrator trading partner(s) should begin storing live claim data assoon as they are capable for later testing.Return to Element Requirement Table.Determine which data elements should be utilized as primary and secondarymatch data elements; match elements will generally be mandatory on theelement requirement table.Complete Match Data Table.Review each data element by MTC, decide which elements are Mandatory (M),Conditional (C), and which are Optional (O) for each MTC.Complete Element Requirement Table.There should be no indicators for those elements that are not valid for DLI/ERDbut they should remain on the table.Return to complete the Edit Matrix Table.Remove other indicators for those data elements that are not statutorily valid forDLI/ERD.Indicate those elements that are mandatory anywhere on the ElementRequirement Table.Review all data elements by Error Message. In other words, review all the dataelements for the, 001-mandatory field not present error message, and thencontinue through the next error messages.o It is imperative that the tables be reviewed and completed as soon as possible in theimplementation process, although time consuming.Review criteria for moving from test status to production status. Our test standardis 95% acceptance.Technology Solutions Examine and evaluate hardware and software requirements and options. Acquire Third Party Software to perform workers' compensation data extractionand transmission of reports over a network or Develop in-house written software to perform the above or Use third party services to convert your paper reports to electronically transmitthe information to DLI/ERD. IAIABC can provide a list of vendors certified by theIAIABC or you can search the Internet to find vendors. Remember, not allvendors are experienced in this technology. DLI/ERD or IAIABC takes noresponsibility for information found on the Internet. Choice of format: ANSI or Flat Format (Montana prefers using the Flat Fileformat) Choice or transmission options: VAN, FTP, or Third Party Administrator.

Completion of Trading Partner Agreement Obtain a copy of Montana DLI/ERD Trading Partner Agreement.Obtain authorization from legal bureau for use of Trading Partner Agreement.Master Trading Partner Profile.Complete Transmission Specifications.Review Montana Report Submission Table.Review element requirements.Review MCO Tables.Programming Develop an interface to load EDI information into your databaseDevelop edits on EDI information.Contact software vendors.Develop method of extracting the proper transactions to send per the rules andtriggers in the trading partner table.Implementation Scheduling Contact DLI/ERD and request EDI information such as triggers, rules, etc. Trading partnero Educationo Begin Trading Partner Agreement Test statusooooSend test FROIReview test dataProvide feedbackRepeat until 95% accurateooooSend test SROIReview test dataProvide feedbackRepeat until 95% accurate Production statuso Receive letter from DLI/ERD granting production status.o Discontinue sending hard copy FROIs and SROIs and begin electronictransmission on the date agreed upon for both FROIs and SROIs.

EDI Trading Partner AgreementMontana Department of".rf}.u: }!1 !R t } ! ;'RYWorkers’ Compensation Claims Assistance Bureau/Data Management UnitELECTRONIC DATA INTERCHANGE (EDI) TRADING PARTNER AGREEMENTObjective: To initiate, implement and maintain First Reports of Injury (FROI) andSubsequent Reports (SROI) through electronic filing.We, the undersigned, as representatives of our respective organizations, corporations orgovernmental entity, do hereby agree to the following:1. The Montana Department of Labor and Industry, Employment Relations Division("the Division") is the regulatory agency for workers' compensation and occupationaldisease laws in Montana. is an insurer providing workers'compensation insurance in Montana or the third party administrator for an insurer. TheDivision, the receiver, and , the sender, agree that the senderwill report workers’ compensation information to the receiver via the national standardsfor Electronic Data Interchange (EDI) developed by the International Association ofIndustrial Accident Boards and Commissions (IAIABC) EDI Project.2.You are a (circle one) mandatory/voluntary Trading Partner. This agreement willcommence upon the approval of the Division’s Claims Assistance Bureau, DataManagement Unit Supervisor, as demonstrated by his/her signature on thisdocument.3.The Trading Partners agree to use the IAIABC Claims Release 1 Flat File format.4.The Trading Partners will perform a test of the reporting system to determinewhether the transmission mechanism is acceptable. Trading Partners must meet alltechnical requirements as outlined in the State of Montana, EDI ImplementationGuide. The term of the test is sixty days from the commencement of this agreementunless the Division approves an extension.5.Once the testing requirements are met and production status granted the sender isno longer required to file paper forms.6.Once production status is granted, the sender is required to maintain a 95%acceptance rate.

7. The format of data elements and definitions will conform to the IAIABC datadictionary, including future amendments, unless otherwise agreed between theTrading Partners. The Division will provide the sender with a minimum of thirtydays notice prior to implementing amendments.8.Technical requirements, data elements, and codes specific to Montana are found inthe State of Montana EDI Implementation Guide.9. Any error in transmission will be timely identified by the Division, and sent to thesender via the acknowledgment record. The sender will correct the identified errorsand resubmit the record within 14 days of receiving the acknowledgment record.10.The sender will pay any and all EDI transmission costs.11.This agreement may not be modified or terminated except by the written agreementof the Trading Partners, with either party giving at least thirty days written notice tothe other party.

IN WITNESS WHEREOF, the parties hereto have executed this Agreement asdated below:Trading PartnerDoug Roope, Unit Manager, Data ManagementName and TitleMontana Department of Labor and IndustryAddressCity, State Zip CodePhoneEmployment Relations Division1805 ProspectHelena, MT 59601Ph: (406) 444-1600FaxFax:(406) 444-4140e-mailEmail: doug.roope@mt.govSignatureSignatureDateDate

ELECTRONIC DATA INTERCHANGE (EDI) TRADING PARTNER AGREEMENTThird Party Administrator AttachmentThird party administrators often send reports to DLI/ERD for several insurers. Please completethe following for each insurer Federal Employer Identification Number (FEIN).Insurance company name:FEIN:Insurance company name:FEIN:Insurance company name:FEIN:Insurance company name:FEIN:Insurance company name:FEIN:

DLI/ERD Trading Partner ProfileTrading Partner Type:Master Trading Partner Name:Master FEIN:JurisdictionState of Montana, Employment Relations Division81-0302402Physical Address:City:State:Postal Code:1805 ProspectHelenaMontana (MT)59601Mailing Address:City:State:Postal Code:P.O. Box 8011HelenaMontana59604-8011Contact Information:EDI Business Contact:Doug Roope(406) 444-1600(406) 444-4140Doug.Roope@mt.govPhone:FAX:E-mail:EDI Contact:Mike Bartow(406) 444-3089(406) 444-4140MBartow@mt.govTransmission Profile –DLI/ERD Receiver SpecificationsReceiver Name:Master FEIN:State of Montana, Employment Relations Division81-0302402Postal Code: 59604-8011Transaction Information: Transactions 148, A49, and AK1 – Flat File ReleaseFlat File Record Delimiter: Carriage return line feed.Acknowledgement Information: Response period 24 Hours, Monday through FridayTransmission Frequencies: May transmit Monday through Friday.Electronic Mailbox(s) for this Profile:TypeAccount IDAerie EDI GroupEBIX (formerly Claims Harbor/Claimport)IVANS/AdvantisMitchell Regulatory Reporting SolutionsHealth TechISO wcPrism SolutionsDirect Reporting sFTPAs assignedUNICOMMTUNICOMMTWCSTAs assignedAs assignedAs assignedAs assignedUser IDAs assignedN/AWCST014As assignedAs assignedAs assignedAs assigned

Trading Partner ProfileTrading Partner Type:D Carrier D Third Party AdministratorSender Name:Sender’s FEIN:D Employer D Service BureauSender’s Postal Code:(Must have 9 digits)Physical Address:City:StatePostal Code:Mailing Address:City:State:Postal Code:Contact Information:Name:Title:Phone:Fax:E-mail:Receiver Name:Master FEIN:Business Contact:Technical Contact:Transmission Profile – Sender’s ResponseState of Montana, Employment Relations Division81-0302402Postal Code:59604-8011Transaction Information: Transactions 148, A49, AK1 – Flat File Release (IAIABC Claims Release 1)Transmission Frequencies: May transmit Sunday - Saturday. Acknowledgments processed Monday - Friday.Select one :Electronic Mailbox(s) for this itchell Regulatory Reporting SolutionsHealth TechDirect Reporting sFTPISO wcPrism Solutions

First Report of Injury - Release 1 - MCO TableDATA 00370038003900400041ELEMENTSTransaction Set IDMaintenance Type CodeMaintenance Type Code DateJurisdictionAgency Claim NumberInsurer FEINInsurer NameThird Party Administrator FEIN 1Third Party Administrator NameClaim Administrator Address LINE 1Claim Administrator Address LINE 2Claim Administrator CityClaim Administrator StateClaim Administrator Postal CodeClaim Administrator Claim NumberEmployer FEINInsured NameEmployer NameEmployer Address LINE 1Employer Address LINE 2Employer CityEmployer StateEmployer Postal CodeSelf Insured IndicatorIndustry Code 2Insured Report NumberInsured Location NumberPolicy NumberPolicy EffectivePolicy ExpirationDate of InjuryTime of InjuryPostal Code of Injury SiteEmployers Premises IndicatorNature of Injury CodePart of Body Injured CodeCause of Injury CodeAccident Description/Cause 1Initial TreatmentDate Reported to EmployerDate Reported to Claim MMMOOOO

00670068Social Security NumberEmployee Last NameEmployee First NameEmployee Middle InitialEmployee Address Line 1Employee Address Line 2Employee CityEmployee StateEmployee Postal CodeEmployee PhoneEmployee Date of Birth 1Gender Code 1Marital Status CodeNumber of DependentsDate Disability BeganDate of DeathEmployment Status CodeClass CodeOccupation DescriptionDate of HireWageWage PeriodNumber of Days WorkedDate Last Day WorkedFull Wages Paid for Date of Injury IndicatorSalary Continued IndicatorDate of Return to WorkAlthough Third Party Administrator FEIN, Employee Date of Birth, Gender Code andAccident Description/Case are listed as Optional fields, we respectfully request thesefields to be sent with valid values. The fields aid us in workers’ compensation studiesand data quality endeavors.1If you send Industry Code, please only send NAICS. If you do not know the NAICScode, please leave it blank. (Effective 4-1-09).2MMMOOOMMMOOOOOOOOMOOOOOOOOO

Subsequent Report of Injury - Release 1- MandatoryConditional Optional (MCO) TableDATA 00860087ELEMENTSREQTransaction Set IDMaintenance Type CodeMaintenance Type Code DateJurisdictionAgency Claim NumberInsurer FEINThird Party Administrator FEINClaim Administrator Postal CodeClaim Administrator’s Claim NumberInsured Report NumberDate of InjurySocial Security NumberNumber of DependentsConditional with 57, 82, 97Date Disability BeganEmployee Date of DeathConditional with 55, 82, 97WageWage PeriodNumber of Days WorkedSalary Continued IndicatorPre-existing DisabilityDate of Maximum Medical ImprovementReturn to Work QualifierConditional with 72Date of Return/Release to WorkConditional with 71Claim StatusClaim TypeAgreement to Compensate CodeDate of RepresentationLate Reason CodeNumber of Permanent ImpairmentsNumber of Payment/Adjustments Conditional with 85 if 0Number of Benefit ReductionsConditional with 92 if 0Number of Paid to Date/Reduced Conditional with 95 if 0Number of Death Dependent/Payee RelationshipsConditional with 55,57, 97Permanent Impairment Body Part Code Conditional with 84Permanent Impairment PercentConditional with 83Payment/Adjustment CodeSee belowPayment/Adjustment Paid to DateSee belowPayment/Adjustment Weekly AmountSee belowCCCCCCC

0088008900900091009200930094009500960097M - MandatoryPayment/Adjustment Start DateSee belowPayment/Adjustment End DateSee belowPayment/Adjustment Weeks PaidSee belowPayment/Adjustment Days PaidSee belowBenefit Adjustment CodeSee belowBenefit Adjustment Weekly Amount Conditional with 92,94Benefit Adjustment Start DateConditional with 92,93Paid to Date/Reduced Earnings/Recoveries Code See belowPaid to Date/Reduced Earnings/Recoveries Amount See BelowDependent/Payee RelationshipConditional with 55 & 57CCCCCCCCCCLij Nov 09C - ConditionalO - OptionalExplanation of Conditionals:If Employee Date of Death DN57 has data, then DN55, DN82, and DN97 must have data and viceversa.If Return to Work Qualifier DN71 has data, then DN72 must have data and vice versa.If Permanent Impairment Body Part Code DN83 has data, then DN84 must have data and viceversa.For Payment Adjustment Codes 010 (Fatality):If a fatality has occurred due to injury/OD, report the occurrence in DN85 as code 010 or 510.If Payment/Adjustment Code DN85 has data, then DN57 must have data.For Payment Adjustment Codes 070 (TPD)If Payment/Adjustment Code DN85 is 070, the following Payment/Adjustment fields must be sentwith valid data: Paid to Date DN86, Start Date DN88, End Date DN89, Weeks Paid DN90 and DaysPaid DN91. Weeks Paid DN90 is a 4N and Days Paid is a 1N field – 4 and 1 character (spaces),respectively in Number format. Number Format: Unsigned, right justified, zero fill.For Payment Adjustment Codes 010, 020, 030 (pre 7-1-87 Date of Injury), 040, 050, 090, 240,and 410:If Number of Payment/Adjustments DN79 (the counter) is greater than 0, then DN85 through DN89must have valid data. Weeks Paid DN90 is a 4N and Days Paid is a 1N field – 4 and 1 character(spaces), respectively in Number format. Number Format: Unsigned, right justified, zero fill.If Payment/Adjustment Code DN85 has data, then DN79 (the counter) must be greater than 0.If any data element 0085 through 0089 has data, then all data elements 0085 through 0091 musthave data.For Payment Adjustment Codes 500 through 570 (Lump Sums):If Number of Payment/Adjustments DN79 (the counter) is greater than 0, thenPayment/Adjustment Code DN85, the amount paid to date DN86, end date DN89, and days paidDN91 must have data.Enter 1 for one lump sum, a 2 for two lump sums etc. inPayment/Adjustment Days Paid DN91.If DN85 has data, then DN79 (the counter) must be greater than 0.If any data element 0085 through 0091 has data, then data elements 0085, 0086, 0089, and 0091must have data.If Number of Benefit Adjustments DN80 (the counter) is greater than 0, then DN92 throughDN94 must have data. Payment/ Adjustment Code DN85 must have data.

If Benefit Adjustment Code DN92 has data, then DN80 (the counter) must be greater than 0.If any data element 0092 through 0094 has data, then 0092 through 0094 and DN85 must havedata.If Number of Paid to Date/Reduced Earnings/ Recoveries DN81 (the counter) is greater than0, then the code DN95 and the amount DN96 must have data.If Paid to Date/Reduced Earnings/ Recoveries Code DN95 has data, then DN81 (the counter) mustbe greater than 0.If the code DN95 has data, then the amount DN96 must have data and vice versa.Explanations of Mandatory Field Maintenance Type Code DN0002:If Maintenance Type Code DN02 is SA, then DN73 must be either O (open), R (reopen). X(reopen/closed), or C (closed) depending on the status of the claim.If Maintenance Type Code DN02 is FN, then 0073 must be X (reopen/closed) or C (closed).Lij/ Nov 2009Detail Acknowledgement – Release 1DATA ction Set IDRecord Sequence NumberDate ProcessedTime ProcessedInsurer FEINClaim Administrator Postal CodeThird Party Administrator FEINAcknowledgement Transaction Set IDApplication Acknowledgement CodeInsured Report NumberClaim Administrator Claim NumberAgency Claim NumberMaintenance Type Code (from original transaction)Maintenance Type Date (from original transaction)Request Code (purpose)Free form textNumber of ErrorsElement NumberElement Error NumberVariable Segment NumberREQMMMMCCCMMCCOCCOOMMMM

Header and Trailer – Release 1ELEMENTSDATA 05Transaction Set IDSender IDReceiver IDDate Transmission SentTime Transmission SentOriginal Transmission DateOriginal Transmission TimeTest/Production IndicatorInterchange Version IDMMMMMOCOCMM00010106Transaction Set IDDetail Record CountMMTrailer:OC denotes that the field is optional. If you enter a date and/or time in the respectivefield, then the field becomes conditional. It must be a valid date and time.Montana Report Submission TableReportMTCDescriptionReport Submission CriteriaWhen Due148/FROI00 Original FROIAll First Reports of Injury30 days from date thecarrier is notified ofaccident or occupationaldisease (OD)SA Semi-AnnualSix month anniversaryof date of injury or OD,while the claim is openClosure of claimWithin 14 calendar days ofeach six month anniversaryfrom date of injury or ODWithin 14 calendar days ofsix month anniversary ofdate of injury or OD afterclaim is closed or at time ofclaim closure14 calendar days fromrequest of Department orExecutive BranchA49/SROI(Claim Status ‘O’ or‘R’)SA Semi-Annual or FNFinal(Claim Status ‘C’ or‘X’)UR Upon RequestWhen Department needs up-to-datecost of claim data

Montana Subsequent Report CodesMaintenance Type Codes (DN2)SA – Semi Annual (Claim Status Open, Reopen/Closed, or Closed)FN – Final (Claim Status Reopen/ Closed or Closed)UR – Upon RequestIP – Initial PaymentWage Period (DN63)1 WeeklyRTW Qualifier (DN71)1 – RTW Without Restrictions2 – RTW With Restrictions5 – Released RTW Without Restrictions6 – Released RTW With RestrictionsClaim Status (DN73)O – OpenC – ClosedR – ReopenX – Reopen/CloseClaim Type (DN74)I – IndemnityZ – Occupational DiseaseAgreement to Compensate (DN75)W – Without LiabilityL – With LiabilityLate (payment to claimant) Reason Codes (DN77)C1 - Lack of coverage informationE4D1 - Dispute concerning coverageE5D2 - Dispute concerning compensability in wholeE6D3 - Dispute concerning compensability in partL1D4 - Dispute concerning disability in wholeL2D5 - Dispute concerning disability in partL3D6 - Dispute concerning impairmentL4E1 - Wrongful determination of no coverageL5E2 - Errors from employerL8E3 - Errors from employeeL9- Errors from state- Errors from health care provider- Errors from other claim administrator/TPA- No excuses- Late notification, employer- Late notification, employee- Late notification, state- Late notification, health care provider- Tech processing delay/computer failure- Manual processing delayPermanent Impairment Body Part Code (DN83): 99Compensation Payment Codes (DN85)010- Fatality020- PTD021- PTD, Supplemental030- PPD, Scheduled040- PPD, Unscheduled050- TTD070- TPD090- PPD, Disfigurement240- Employer Paid410- Vocational RehabilitationMaintenance500- Lump Sum Other501- Medical Lump Sum510- Lump Sum Fatality520- Lump Sum PTD524- Lump Sum Employer PaidBenefits Paid To FamiliesPermanent TotalCost of Living AdjustmentsPermanent Partial Benefits (Pre 7-1-87 Date of Injury)Permanent Partial BenefitsTemporary Total BenefitsTemporary Partial BenefitsPermanent Partial Benefits paid for disfigurementSalary Paid By The Employer In Lieu Of CompensationRetraining, Total & Partial Rehab Benefits, AuxiliaryBenefitsNot Otherwise Classified or Combination of Benefits.Paid To Claimant As A Settlement Of Medical Liability

umSumSumSumPPD, Scheduled (Pre 7-1-87 Date Of Injury)PPD, UnscheduledVocational Rehabilitation MaintenanceTTDTPDPPD, DisfigurementBenefit Adjustment Codes (DN92)A – Apportionment/ContributionH – Court Ordered Lien Against Workers’ Compensation BenefitsB – SubrogationP – Prepaid Benefit/AdvancesC – Overpayment CreditS – Social Security DisabilityPaid to Date/Reduced Earnings/Recoveries Codes (DN95)300 - Funeral Expenses Paid To Date400 - Other vocational rehabilitation paid to date330 - Employer’s Legal Expenses Paid To Date420 - Consultant/expert witness fees paid to date byinsurer350 - Total Payments To Physicians Paid To Date430 – Unallocated Prior Indemnity BenefitsPaid to Date(Including Reimbursement To Claimant)440 – Unallocated Prior Medical Paid to Date360 - Hospital Costs Paid To Date450 – Pharmaceutical Paid to Date(Including Reimbursement To Claimant)800 – Special Fund Recovery370 - Other Medical to Medical Provider Paid to810 – Employer’s Deductibles Recovery(Includes Reimbursement to Claimant)820 – Subrogation Recovery380 - Vocational Rehabilitation evaluation paid to date830 – Overpayment Recovery390 - Vocational Rehabilitation education paid to date840 – Unspecified RecoveryDependent Payee Relationship (DN97)2 – Widow3 – Widower4 – Son or Daughter5 – Brother or Sister6 – Mother or Father7 – Disabled Child Over 1

EDI Test Policy and Process Selecting a Transmission Type EDI Overview Montana Law 39-71-225, Link Montana Administrative Rules, Link Glossary ***This guide contains Montana specific EDI information. It is a companion to the International Association of Industrial Accident Boards and Commissions (I.A.I.A.B.C), E.D.I. Implementation Guide .

Related Documents:

4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 –Advance Ship Notice EDI 810 - Invoice EDI 860 –PO Change Request EDI 846 - Inventory Advice/Update EDI 865 –PO Change Seller

collection of EDI data is received in a batch. The batch of EDI data includes a plurality of EDI documents and each of the plurality of EDI documents has at least one EDI transaction corresponding to a transaction type. The EDI transactions included in the EDI documents are identified by decoding the received EDI data according to EDI standards.

4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 – Advance Ship Notice EDI 810 - Invoice EDI 860 – PO Change Request

1. What is EDI? 2. What is the 'Omni-hannel' 3. Omni-Channel EDI solutions 4. Where does EDI fit into the marketplace? 5. Third Party Logistics (3PL) EDI 6. Online Retailers and CommerceHub EDI 7. eCommerce Platform EDI 8. B2BGateway EDI and QuickBooks Online 9. Pricing 10. Customer Service 11. B2BGateway Fact Sheet & Trading Partners 12 .

TrueCommerce EDI Buyer's Guide As supply chains become more complex, EDI offers the technology . and provides all the components required for EDI, such as mapping, translation, and connectivity to trading partners. . h EDI 940 - Warehouse Shipping Order h EDI 945 - Warehouse Shipping Advice h EDI 997 - Functional Acknowledgement

MAPPING Involves transforming an EDI document into another format (such as XML, a flat file, a delimited file, etc.) TRANSLATION The process of accepting in bound EDI data, or preparing an outbound file for transmission COMMUNICATIONS Refers to the transmission of the EDI transaction Accepted. The EDI message conforms to all agreed upon EDI .

EDI Notepad EDI Notepad is the ultimate EDI editor, providing all those clever features you've always wanted when working with EDI transactions. These features include several viewing modes, syntax validation for all EDI standards and versions, edit tools to edit or build EDI documents,

Certification Standard Animal Nutrition – V5 for January 2020 P a g e 7 81 Daily ration: Average total quantity of feedingstuffs, calculated on a moisture content of 12 %, required daily by an animal of a given species, age category and yield, to satisfy all its needs (Regulation 1831/2003).