MICHIGAN SECRETARY OF STATE ELECTRONIC INSURANCE VERIFICATION (EIV) TRANSMISSION OPTIONS AND FILE FORMAT GUIDELINES



Similar documents
TECHNICAL SPECIFICATIONS GUIDE CANADA SAVINGS BONDS. csb.gc.ca PAYROLL SAVINGS PROGRAM 20$ 40$ 80$ 50 $ 30$ TECHGUIDE-14

CONNECTICUT INSURANCE VERIFICATION SYSTEM (CTIVS)

Insurance Company Financial Responsibilty Electronic Reporting Users Guide

State of Idaho Transportations Department Online Insurance Verification System User Guide For Insurance Companies (Version 1.0)

FINAL RULE, AMENDMENTS TO REGULATION MOTORIST INSURANCE IDENTIFICATION DATABASE

Insurance Tracking And Compliance

Claims Electronic Data Interchange Implementation Guide

CONNECTICUT INSURANCE VERIFICATION SYSTEM (CTIVS)

Designated Agent means the party with which the division contracts under Section , C.R.S.

MONTANA INSURANCE VERIFICATION SYSTEM (MTIVS) Implementation Guide for Insurance Companies. Version 1.1 October 4, 2011

FINAL RULE, AMENDMENTS TO REGULATION MOTORIST INSURANCE IDENTIFICATION DATABASE

Nebraska Insurance Reporting Guide

FF/EDM Intro Industry Goals/ Purpose Related GISB Standards (Common Codes, IETF) Definitions d 4 d 13 Principles p 6 p 13 p 14 Standards s 16 s 25

RHODE ISLAND INSURANCE VERIFICATION SYSTEM (RIIVS)

Maryland MVA Batch Vehicle Access (BVA) User Guide

STATE OF NORTH CAROLINA DEPARTMENT OF TRANSPORTATION DIVISION OF MOTOR VEHICLES

Compromised Identity Exchange: How to Contribute Compromised Data

INSURANCE VERIFICATION NOTIFICATION NETWORK

Liability Insurance (Including Self-Insurance), No-Fault Insurance, and Workers Compensation USER GUIDE

Implementation Guide for. Direct Filing of. Telecommunications Returns

Market Maker Transaction Data Technical Specification

Business Online Transaction Import & Export (Download) File Formats REFERENCE DOCUMENT

Florida Blue Health Plan

State of New Jersey Uninsured Motorists Identification System. Insurance Company Participation Guide

Virginia Department of Taxation Specifications for Web Upload Server to Server Processing for Virginia Department of Taxation Forms

D a n s k e B a n k M e s s a g e I m p l e m e n t a t i o n G u i d e. M a s t e r C a r d C o r p o r a t e C a r d T r a n s a c t i o n s

Maine Revenue Services

Form ONRR-2014 Reporting Instructions ASCII Format

TITLE 18 INSURANCE DELAWARE ADMINISTRATIVE CODE

PROCEDURES MANUAL FOR IMPLEMENTATION OF THE FLORIDA MOTOR VEHICLE NO-FAULT LAW AND FINANCIAL RESPONSIBILITY LAW INITIAL/RELOAD REQUIREMENTS

PROCEDURES MANUAL FOR IMPLEMENTATION OF THE FLORIDA MOTOR VEHICLE NO-FAULT LAW AND FINANCIAL RESPONSIBILITY LAW DAILY REQUIREMENTS

Kansas Insurance Reporting Guide

Experian Secure Transport Service

Model User Guide for Implementing a Motor Vehicle Liability Insurance Reporting Program

Introduction. Companion Guide to X12 Transactions version 5010

SIX Trade Repository AG

Reporting Instruction Manual for Insurance Companies

Local Property Tax 3 rd Party Cash Payment Service Providers. Local Property Tax

Liability Insurance Validation Electronically (Nevada LIVE) Manual Specifications for the Rules of Practice

SBCH Medicaid Verification System File Exchange

Data Transmission Method Selection Monday, October 5, 2015

ALERT: October 2011 TIN Reference Response File and Address Validation Information for Group Health Plan (GHP) Responsible Reporting Entities (RREs)

New Employee Registry Program. Cover + 10 pages. DE 340 Rev. 4 (1-13) (INTERNET)

NEBRASKA ADMINISTRATIVE CODE

MasterCard In tern et Gatew ay Service (MIGS)

Quick Reference Guide Version 1 January 19, 2012

EDI 101 Guide 1EDISOURCE BUYER S GUIDE

FLORIDA DIVISION OF WORKERS COMPENSATION. Submitter Instructions Creating a Florida WC SSL/FTP Account

Corporate Online. Import format for Payment Processing Service files

Motor Insurance Database Phase II 4 th EU Motor Insurance Directive

Communications and Connectivity

CMS Registration and Account Setup

Plastic Card Claims Automation Specifications Document

Manual of Instructions

NEWFOUNDLAND AND LABRADOR ELECTRONIC TAX SERVICE (NLETS)

Shipping Services Files (SSF) Secure File Transmission Account Setup

Electronic Invoicing Overview. April, 2010

Illinois Veteran Grant (IVG) Online Payment Manual Chapter 4

Electronic Data Reporting

Texas Private Passenger Auto Statistical Plan. General Reporting Instructions

Online Banking for Business Secure FTP with SSL (Secure Socket Layer) USER GUIDE

B. KTT Web-based File Transfer

STATE OF INDIANA INDIANA GOVERNMENT CENTER NORTH 100 NORTH SENATE AVENUE N1058 (B) INDIANAPOLIS, IN PHONE (317) FAX (317)

Electronic Income Withholding Orders Software Interface Specification for States and Employers

Commonwealth of Kentucky Transportation Cabinet. Kentucky Automobile Liability Insurance Reporting Guide

Commercial Automobile Insurance Manual

DEPARTMENT OF INSURANCE Statutory Authority: 18 Delaware Code, Sections 314 and 2741 (18 Del.C. 314 & 2741) 18 DE Admin. Code 606

Data Validation Center. (DVC) Processing User Guide.

The Automated Earnings Reporting System Submitting your payroll data online

AFN-StudentBillingEFTGuide

Copyright Telerad Tech RADSpa. HIPAA Compliance

Municipal Bond Payment Reporting Information Annual Information Reporting Requirement for Regulated Investment Companies

This chapter shall be known as the "Rhode Island Self-Service Storage Facility Act."

NC CD-ROM Media Specifications for 1099 Reporting

Georgia Electronic Conviction Processing System GECPS Implementation Process and User s Guide for Georgia Courts Version 2; Release 1

Department of Insurance

How To Amend A Law In Delaware

The bulk order types listed below will use the format detailed in the following sections:

ELECTRONIC RECORDS DISCLOSURE AND AGREEMENT READ AND SCROLL DOWN PLEASE READ THIS AGREEMENT CAREFULLY AND KEEP A COPY FOR YOUR RECORDS.

ICE Trade Vault. Public User & Technology Guide June 6, 2014

TELECOMMUNICATIONS REQUIREMENTS FOR TRANSMITTING ELECTRONIC DATA FILES ADMINISTRATIVE SERVICES OF KANSAS

State of Nevada Department of Health and Human Services (DHHS) Division of Health Care Financing and Policy (DHCFP)

Electronic Data Transmission Guide For International Mailers

The information in this document will be common for all X12N implementation guides.

Gentran User s Guide

AmeriHealth Administrators

Online Banking for Business Secure FTP with SSH (Secure Shell) USER GUIDE

DEBT COLLECTION SYSTEM ACCOUNT SUBMISSION FILE

File Transmission Methods Monday, July 14, 2014

Model User Guide for Implementing Online Insurance Verification

Florida Blue Health Plan

PROCEDURE FOR UPDATING LISTS THROUGH WEB INTERFACE

A. Purpose of the Guidelines

CashManager OnLine Positive Pay Set-Up Information

InstaMember USER S GUIDE

Enterprise Data Management Data Standard Person Core Matching Attributes Data Dictionary 10/13/2011

Digital Data & Image Format Guidelines For School Photography and Yearbook Publication Version

Combined Insurance Company of America

HIPAA X 12 Transaction Standards

Electronic Funds Transfer

Transcription:

MICHIGAN SECRETARY OF STATE ELECTRONIC INSURANCE VERIFICATION (EIV) TRANSMISSION OPTIONS AND FILE FORMAT GUIDELINES Rev. 12/22/2011

Term Compression CRLF DEG DEG Mailbox Delimiter EIV EIV User Worksheet HTTPS MDCH SOS NAIC Code Zip compression format Carriage Return Line Feed DATA DICTIONARY Definition Data Exchange Gateway (State of Michigan, DTMB) Mailbox established by DEG to receive and distribute information Field separator. The delimiter used will be a pipe. Electronic Insurance Verification Document that insurance companies will fill out to request a user mailbox and provide SOS with contact information. Should be filled out by new and existing users. Hypertext Transfer Protocol Secure Michigan Department of Community Health Secretary of State National Association of Insurance Commissioners unique insurance company identifier Named Insured Public Act 91 requires insurance companies to transmit the name of each person named on the policy. This may not include everyone covered by the policy. Optional Field Any field that is not defined as required or statutory. Private A motor vehicle with at least four wheels, used in whole or in part for personal, Passenger Nonfleet Automobiles van, or station family, or household purposes. It may be a 2-door, 4-door, motor home, pickup, wagon. Public Acts 91 and 92 of 2011 Senate Bills 441 and 442 of 2011 were signed into law as Public Acts 91 and 92 and require insurance companies to provide certain automobile policy information to SOS. Required Field Any field that enables SOS to properly process incoming data. Public Act 91 allows SOS to establish the format and timeline necessary for transmitting policy information. Return Report SOS will return a VIN report listing the total number of VINs received and processed along with any invalid VINs contained in the file. MDCH will return a report that lists the total number of records received along with a count of errors for each required and statutory detail fields. Information specific to each error may not be available. SFTP Secure File Transfer Protocol SSL-FTP Secure Socket Layer-File Transfer Protocol Statutory Field Any field that contains the policy information required by Public Acts 91 and 92. Third Party Liability Vehicle Type Any individual, entity, or program that is, or may be, liable to pay for any medical assistance provided to a Medicaid beneficiary under the approved state Medicaid plan. The State Medicaid program pays only after the third party has met its legal obligation to pay. Vehicle Type specific to the file layout. S = vehicles that are statutorily reported and O = vehicles that are optionally reported, such as motorcycles & commercial vehicles. 2 of 7 Rev. 12/22/2011

In order to avoid issues concerning the receipt and processing of files, please read this document carefully and follow all requirements as they are outlined. EIV TRANSMISSION OPTIONS Information required to be reported by Public Acts 91 and 92 of 2011 can only be sent by an insurance company or its third-party reporting agency. Due to the type of information being reported, the data files must be sent encrypted using one of the following three protocols in order to comply with the State of Michigan s information security policy: 1) Access via the Internet using SSL-FTP. This method will require a connection (dial or leased line) to an Internet Service Provider. Data is encrypted using 128 bit SSL. 2) Access via the Internet using HTTPS. This method will require a connection (dial or leased line) to an Internet Service Provider. This requires a Web browser. Data is encrypted using 128 bit SSL. The Web browser accesses a State of Michigan Web server to transfer files. 3) Access via the Internet using SFTP. This method will require a connection (dial or leased line) to an Internet Service Provider. Data is encrypted using 128 bit SSL. The program the SOS uses to process the file you send does not edit the information in the files for accuracy. A report providing the number of records sent and any invalid VINs that were included in your file will be sent to the mailbox established for your company. (Please refer to the Technical Specifications for VIN reporting requirements and what is considered an invalid VIN.) MDCH will send separate notifications to insurance companies letting them know of any problems with information in the files other than the VINs. EIV FILE FORMAT REQUIREMENTS In order to avoid unnecessary return errors, please follow the File Format Requirements, including Global Requirements and Technical Specifications, exactly as they are described. GLOBAL REQUIREMENTS: File transmissions must be made on the first and 15 th of each month; Data files must be sent compressed using a zip compression format; Each file will contain one header record, one or more detail records, and one trailer record; If header or trailer records are not accurate, the file may not be processed resulting in noncompliance; All required and statutory fields must be populated correctly, or your file may not be processed resulting in noncompliance; All fields should be delimited using a pipe, and at the end of each record, a Carriage Return Line Feed (CRLF) (See Appendix A for a Sample of Delimiter); Blank fields shall remain empty, separated by a pipe ; Only policies meeting Michigan s no-fault requirements should be included in the file (for example, no storage insurance); The insurance company s complete list of policies (meeting Michigan s no-fault requirements) must be sent with each transmission (not just recent activity or changed policy information); Insurance companies must submit a legal address for organizations; and Insurance companies must submit a residential address for individuals. 3 of 7 Rev. 12/22/2011

TECHNICAL SPECIFICATIONS: Header Record (Record size 30) FIELD NAME START LENGTH TYPE REQUIRED/ OPTIONAL/ DESCRIPTION CONDITIONAL Header identifier 1 5 AN REQUIRED 5-character field consisting of a space, followed by the word HDR, followed by a space File date 6 8 N REQUIRED File date formatted YYYYMMDD PIN 14 6 N REQUIRED 6-digit number assigned to each user ID by SOS Mailbox ID 20 8 AN REQUIRED 8-character alpha-numeric field assigned by SOS Batch number 28 2 N REQUIRED 2-digit batch number. The first batch sent on a particular date will have a batch assignment of 01. Each subsequent batch for that date must have the batch number increase by one (02, 03, 04, etc) File type 30 1 AN REQUIRED 1-character alpha field to identify the file type. Allowed values are: T = Test or P = Production 4 of 7 Rev. 12/22/2011

Detail Record All fields should be delimited using a pipe, and at the end of each record a Carriage Return Line Feed (CRLF). Blank fields shall remain empty, separated by a pipe. (See Appendix A for a Sample of Delimiter) FIELD NAME MAXIMUM LENGTH TYPE STATUTORY/ REQUIRED/ OPTIONAL/ CONDITIONAL DESCRIPTION VIN 17 AN STATUTORY Up to 17 character alpha-numeric VIN of the vehicle. All alpha characters in the VIN must be CAPITALIZED. Only alpha-numeric characters are allowed no special characters of any type. Vehicle Type 1 AN REQUIRED Vehicle Type specific to the file layout. S = vehicles that are statutorily reported and O = vehicles that are optionally reported, such as motorcycles. Insurance Company 50 AN STATUTORY Name NAIC Code 5 AN REQUIRED Policy Number 30 AN STATUTORY Total Number of Named Insured(s) 2 N REQUIRED Count of all named insured(s) being reported in the record Address 1 of residence 50 AN STATUTORY Organization Legal address Individual Residential address 50 AN OPTIONAL Address 2 of residence Named Insured s City 35 AN STATUTORY of residence Named Insured s State 2 A STATUTORY 2 character alpha state abbreviation of residence Named Insured s Zip of 5 N STATUTORY 5 digit numeric zip code residence Last Name (or Organization Name) 40 AN STATUTORY If policy type is private passenger non-fleet, this must be the insured s last name. If the policy type is commercial, this should be the organization s Middle Name First Name 20 AN OPTIONAL name. 40 AN CONDITIONAL CONDITIONAL based on policy type: STATUTORY for private passenger, nonfleet OPTIONAL for commercial Suffix Additional Named Insureds 3 AN OPTIONAL Abbreviated Name Suffix (JR, SR, etc) Maximum length 103 char. AN STATUTORY Include, if applicable, any Additional Named Insureds, in full name blocks including (in order) last name, middle name, first name, and suffix. (i.e. Last Name Middle Name First Name Suffix ) 5 of 7 Rev. 12/22/2011

Trailer Record (Record size 30) FIELD NAME START LENGTH TYPE Trailer identifier REQUIRED/ OPTIONAL/ CONDITIONAL DESCRIPTION 1 5 AN REQUIRED 5-character field of a space, followed by the word TLR, followed by a space. File date 6 8 N REQUIRED File date (same date as in header) formatted YYYYMMDD Record count 14 8 N REQUIRED 8-digit numeric field of the total number of detail records in the file (not counting the header and trailer records). The field should be RIGHT JUSTIFIED and ZERO FILLED. Filler 22 6 AN REQUIRED 6 space characters Batch number 28 2 N REQUIRED 2-digit batch number. The batch number should be the same as in the header (see header description) File type 30 1 A REQUIRED 1-character alpha field to identify the file type. The file type should be the same as in the header (see header description for allowed values) 6 of 7 Rev. 12/22/2011

APPENDIX A SAMPLE OF DELIMITER All fields should be delimited using a pipe, and at the end of each record a Carriage Return Line Feed (CRLF). Blank fields shall remain empty, separated by a pipe.