General Companion Guide. Version Number: 1.4 September 16, 2003

Similar documents
EDI General Companion Guide. Version Number: 2.3

DentaQuest HIPAA Transaction Standard Companion Guide

ANSI ASC X12N 837 Healthcare Claim (Version X222A1-June 2010) Professional Companion Guide

Maryland Health Insurance Exchange (MHBE) Standard Companion Guide Transaction Information

USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270

Standard Companion Guide

West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270

Guide to the X214 Claim Acknowledgement Conduent EDI Solutions, Inc.

837 Health Care Claim Companion Guide. Professional and Institutional

Inland Empire Health Plan

HIPAA Transaction Standard Companion Guide. Refers to the Implementation Guides Based on ASC X12 version CORE v5010 Companion Guide

BLUE CROSS AND BLUE SHIELD OF LOUISIANA PROFESSIONAL CLAIMS COMPANION GUIDE

Blue Cross Blue Shield of Louisiana

Alameda Alliance for Health

Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837

Mississippi Medicaid Companion Guide to the X279A1 Benefit Inquiry and Response Conduent EDI Solutions, Inc. ANSI ASC X12N 270/271

HIPAA Transaction Health Care Claim Acknowledgement Standard Companion Guide (277CA, X214)

Medical Associates Health Plans and Health Choices

BLUE CROSS AND BLUE SHIELD OF LOUISIANA INSTITUTIONAL CLAIMS COMPANION GUIDE

BULLETIN BOARD SCREENS for HIPAA (BBS) UPDATED JULY 22, Once connected, the first screen displays the node number that you are connected to.

835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1

/277 Companion Guide. Refers to the Implementation Guides Based on X12 version Companion Guide Version Number: 1.1

Kentucky HIPAA HEALTH CARE PAYER UNSOLICITED CLAIM STATUS Companion Guide Unsolicited 277. Version 1.1

Louisiana Medicaid. HIPAA 5010A General Companion Guide Version Number 1.6 Created November 14, 2011

Administrative Services of Kansas (ASK)

Electronic Remittance Advice (835) (Refers to the Implementation Guides based on ASC X X221)

Refers to the Technical Reports Type 3 Based on ASC X12 version X223A2

276/ /277 Health Care Claim Status Request and Response Real-Time. Basic Instructions. Companion Document

If a claim was denied (or rejected on a TA1, 997, or 824), do not submit a reversal or replacement claim. Submit a new original claim.

Blue Shield of California

ASC X X220A1)

Standard Companion Guide. Refers to the Implementation Guide Based on X12 Version X212 Health Care Claim Status Request and Response (276/277)

General Companion Guide 837 Professional and Institutional Healthcare Claims Submission Version Version Date: June 2017

Anthem Blue Cross and Blue Shield. 834 Companion Guide

837 Health Care Claim Professional, Institutional & Dental Companion Guide

Eligibility Gateway Companion Guide

EMBLEMHEALTH HIPAA Transaction Standard Companion Guide

Electronic Transaction Manual for Arkansas Blue Cross and Blue Shield FEDERALEMPLOYEEPROGRAM (FEP) DentalClaims

Mississippi Medicaid Companion Guide to the X223A2 Institutional Conduent EDI Solutions, Inc. ANSI ASC X12N 837

SHARES 837P Companion Guide

837 Companion Guide. October PR.P.WM.1 3/17

HIPAA 276/277 Companion Guide Cardinal Innovations Prepared for Health Care Providers

ANSI ASC X12N 837 Healthcare Claim Companion Guide

Cabinet for Health and Family Services Department for Medicaid Services

Administrative Services of Kansas (ASK)

276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions

MOBIS Alabama, LLC IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS FUNCTIONAL ACKNOWLEDGEMENT TRANSACTON SET (997) VERSION/RELEASE

Standard Companion Guide

276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions

997 Functional Acknowledgment (Inbound)

Functional Acknowledgment

837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE

Mississippi Medicaid Companion Guide to the X224A2 Dental Conduent EDI Solutions, Inc. ANSI ASC X12N 837

270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response

Mississippi Medicaid Companion Guide to the ASC X12N 837 Professional Conduent EDI Solutions, Inc. ANSI ASC X12N 837

TRISPAN HEALTH SERVICES ANSI v4010a1

Blue Cross Blue Shield of Delaware

DSW Designer Shoe Warehouse

Integration Guide for Data Originators of Claim Status. Version 1.1

ANSI ASC X12N 835 Healthcare Claim Institutional, Professional and Dental Department of Labor-OWCP Companion Guide. May 31, 2017

ASC X12N INSURANCE SUBCOMMITTEE X061A1 820 GROUP PREMIUM PAYMENT FOR INSURANCE PRODUCTS

837 Professional Health Care Claim

Functional Acknowledgment - 997

Standard Companion Guide

EFS 997 Functional Acknowledgment X12/V4010/997: 997 Functional Acknowledgment Version: 1.3

Health Care Connectivity Guide

Functional Acknowledgment - 997

Electronic Data Interchange General Specifications

WEDI Acknowledgement Recommendations

< A symbol to indicate a value is less than another. For example, 2 < 3. This symbol is used in some BCBSNC proprietary error messages.

ACKNOWLEDGMENTS BEST PRACTICE

EDI Functional Acknowledgment

Refers to the Technical Reports Type 3 Based on ASC X12 version X /277 Health Care Claim Status Inquiry and Response

997 - Functional Acknowledgment Author: DOT FOODS, INC. Publication: March 3, 2005

824 Application Advice

Gold Coast Health Plan Healthcare Claim: 837 Companion Guide. Versions: X222A X223A2

997 Functional Acknowledgment

HIPAA X 12 Transaction Standards

WV MMIS EDI File Exchange User Guide Version 1.0 West Virginia Trading Partner Account Electronic Data Interchange (EDI) File Exchange User Guide

824 Application Advice X12/V4010/824: 824 Application Advice Version: 1.3

837 Professional Health Care Claim. Section 1 837P Professional Health Care Claim: Basic Instructions

Vendor Specifications 270/271 Eligibility Benefit Inquiry and Response ASC X12N Version for. State of Idaho MMIS

HIPAA X 12 Transaction Standards

EMBLEMHEALTH. HIPAA Transaction Standard Companion Guide

Partnership HealthPlan of California

A process in which a claim passes through a series of edits to determine proper payment liability. Transactions copied to Transaction Repository

834 Companion Document to the 5010 HIPAA Implementation Guide

Customer EDI Guidelines 997 Functional Acknowledgment

Assurant Health HIPAA Transaction Standard Companion Guide

6. CLAIMS EDI PROCESSING PROCEDURES A. General Information

Florida Blue Health Plan

837 Dental Health Care Claim

Document Version FUNCTIONAL ACKNOWLEDGEMENT (ANSI X12 VERSION 4040) 10/10/2008. X12V General Parts, Inc./CARQUEST

HIPAA--The Medicare Experience September, Kathy Simmons Technical Advisor OIS/Division of Data Interchange Standards

ANSI ASC X12N 837 Healthcare Claim (Version 4010A) Professional, Institutional, and Dental

To: Electronic Data Interchange (EDI) Partners:

Message Implementation Guideline. MBUSI_003050_997_ServiceParts. based on. 997 Functional Acknowledgement X

Provider EDI Reference Guide for Blue Cross Blue Shield of Delaware

Prepared by the Minnesota Administrative Uniformity Committee (AUC)

997 Functional Acknowledgment

Transcription:

Louisiana Medicaid General Companion Guide Version Number: 1.4 September 16, 2003 2003 CAQH and WEDI "The Companion Guide is the copyrighted work of CAQH and WEDI. More information may be obtained by visiting the CAQH/WEDI website, http://www.wedi.org/snip/caqhimptools/, or by contacting WEDI and/or CAQH at these phone numbers: Workgroup for Electronic Data Interchange (WEDI), Jim A. Schuping, Executive Vice President, 703-391-2716 Council for Affordable Quality Healthcare (CAQH), Robin Thomashauer, Executive Director, 202-861-1493 1

Preface This Companion Guide to the ASC X12N Implementation Guides adopted under HIPAA clarifies and specifies the data content being requested when data is transmitted electronically to Louisiana Medicaid. Transmissions based on this companion document, used in tandem with the X12N Implementation Guides, are compliant with both X12N syntax and those guides. This Companion Guide is intended to convey information that is within the framework of the ASC X12N Implementation Guides adopted for use under HIPAA. The Companion Guide is not intended to convey information that in any way exceeds the requirements or usages of data expressed in the Implementation Guides. 2

Table of Contents 1 Introduction...4 1.1 Scope...5 1.2 Overview...5 1.3 References...5 1.4 Additional Information...6 2 Getting Started...6 2.1 Trading Partner Registration...6 2.2 HIPAA Testing and Approval Overview...7 3 Testing with the Payer...7 3.1 Software Vendor, Billing Agent, and Clearinghouse (VBC) List...7 3.2 HIPAA Desk Testing Service Enrollment...8 3.3 HIPAA Testing Service...9 3.4 MMIS Parallel Testing...9 4 Connectivity with the Payer / Communications...10 4.1 Supported Transactions...10 4.2 Submitter IDs & Passwords...11 4.2.1 New Submitter or Changing Submitter...11 4.2.2 HIPAA Testing Service...11 4.2.3 Test HIPAA Bulletin Board System (BBS) for Parallel Testing...11 4.2.4 Production HIPAA Bulletin Board System (BBS)...11 4.3 HIPAA Bulletin Board Dial-up Phone Numbers...11 4.3.1 Test...11 4.3.2 Production...12 4.4 Communication protocol specifications...12 4.4.1 Dial-Up Requirements...12 4.5 File Naming Conventions...12 4.5.1 Test File Names...12 4.5.2 Production File Names...12 4.6 File Transmission Procedures...13 4.6.1 BBS Error Codes...13 4.6.2 How To Connect and Login To The Louisiana EDI BBS...13 4.6.3 How To Submit A File To The Louisiana EDI BBS...13 4.6.4 Single File Submission...13 4.6.5 Multiple File Submission...14 4.6.6 How To Receive Responses and Download Files...14 4.6.7 HyperTerminal...14 4.7 Accepted Physical Media...15 4.7.1 Media Labeling...15 4.7.2 Tape Specifications...15 4.7.3 5.25 & 3.5 Diskette Specifications...15 4.7.4 Compact Disc...16 4.7.5 Requesting an 835...16 4.8 Accepted HIPAA Transactions...16 3

5 Contact information...16 5.1 EDI Customer Service and Technical Assistance...16 5.2 Provider Service Number...16 5.3 Applicable websites / e-mail...17 6 Control Segments / Envelopes...18 6.1 ISA-IEA...18 6.1.1 ISA - Interchange Control Header Segment...18 6.1.2 IEA - Interchange Control Trailer...19 6.2 GS-GE...19 6.2.1 GS Functional Group Header...19 6.2.2 GE Functional Group Trailer...20 6.3 ST-SE...20 7 Payer Specific Business Rules and Limitations...20 8 Acknowledgements and or Reports...20 8.1 997 Functional Acknowledgement...20 8.2 TA1 Interchange Acknowledgement...20 8.3 Valid EDI Delimiters for Louisiana Medicaid...20 9 Trading Partner Agreements...21 10 Appendix A - Acknowledgements...22 10.1 997 Functional Acknowledgement...22 10.2 TA1 Interchange Acknowledgement...27 11 Appendix B Windows HyperTerminal Instructions...28 12 Appendix C BBS Screen Shots...30 12.1 BBS Login Screen...30 12.2 BBS Main Menu...31 12.3 BBS File Upload...32 12.4 BBS File Upload Review Y/N...33 12.5 BBS File Uploaded Review Y...33 12.6 BBS File Download Selection Screen...34 12.7 BBS File Download List...35 12.8 BBS File Download Screen Step 1 of 2...36 12.9 BBS Receive File Step 2 of 2...37 13 Appendix D BBS Error Codes...38 14 Appendix E File Naming...39 14.1 Production File Names...39 14.2 Test File Names...39 1 Introduction The Health Insurance Portability and Accountability Act (HIPAA) of 1996 carries provisions for administrative simplification. This requires the Secretary of the Department of Health and Human Services (HHS) to adopt standards to support the electronic exchange of administrative and financial health care transactions primarily between health care providers and plans. HIPAA directs the 4

Secretary to adopt standards for translations to enable health information to be exchanged electronically and to adopt specifications for implementing each standard. HIPAA serves to: Create better access to health insurance Limit fraud and abuse Reduce administrative costs Protect Private Healthcare Information 1.1 Scope The HIPAA EDI Transaction Standard Companion Guide explains the procedures necessary for Trading Partners of Louisiana Medicaid to send/transmit Electronic Data Interchange (EDI) transactions. Supported transactions for Louisiana Medicaid Bulleting Board System (BBS) are listed below: Transaction Name Accepted by the LA Medicaid BBS Version Health Care Claim: Dental ASC X12N 837-004010X097A1 Health Care Claim: Professional ASC X12N 837-004010X098A1 Health Care Claim: Institutional ASC X12N 837-004010X096A1 Health Care Claim Payment/ Advice ASC X12N 835-004010X091A1 Health Care Services Request for Review and Response ASC X12N 278-004010X094A1 Functional Acknowledgement ASC X12N 997 Interchange Acknowledgement ASC X12N TA1 Batch Pharmacy NCPDP 1.1 This Companion Guide is not intended to replace the X12N Implementation Guides; rather it is intended to be used in conjunction with them. Additionally, the Companion Guide is intended to convey information that is within the framework and structure of the X12N Implementation Guides and not to contradict or exceed them. 1.2 Overview The appendices of this document contain large items like screen shots and reference lists. These items would spread text far apart in the main parts of the document and would have made it incoherent. Large items are referred to in context throughout this document. 1.3 References This section specifies additional documents useful to the reader. Washington Publishing Company (WPC) Website - www.wpc-edi.com All X12N Implementation Guides adopted for use under HIPAA and their corresponding Addenda are free when downloaded from this site. WEDI SNIP Website - www.wedi.org/snip/ - WEDI is an organization working to foster widespread support for the adoption of electronic commerce within healthcare and SNIP is a collaborative healthcare industry-wide process resulting in the implementation of standards and furthering the development and implementation of future standards. This website contains various resources on HIPAA administrative simplification. 5

Centers for Medicare and Medicaid Services (CMS) Websitewww.cms.hhs.gov/hipaa/hipaa2/ The website provides answers to Frequently Asked Questions, links to other HIPAA sites, and information on the law, regulations, and enforcement are located here. 1.4 Additional Information Specific Companion guides for the 837-I, 837-P, 837-D, 835, & 278 transactions are available for download from within our testing service. These companion guides outline specific payer requirements for LA Medicaid. Please enroll to gain access for testing and companion guide downloads. Refer to Testing Enrollment 2 Getting Started 2.1 Trading Partner Registration This section describes how to register as an EDI trading partner with Louisiana Medicaid Current Electronic Claim Submitters: Louisiana Medicaid trading partners who submit electronic claims currently in the old proprietary formats do not need to do any other registration with Louisiana Medicaid for HIPAA. Submitter numbers will remain the same. However, if a new submitter ID is required or you are changing submitters (i.e. using a Clearinghouse) and need to have your provider number linked to a different submitter ID, contact Unisys Provider Relations at (225) 924-5040 or 800-473.2783 NEW Electronic Claim Submitters: Providers that do not currently submit their claims electronically but want to, should contact the Provider Relations at (225) 924-5040 or 800-473.2783 and request a submitter ID to become an electronic submitter for LA Medicaid. Or, a provider can name an existing submitter who will send their claims on their behalf. This assignment to an existing submitter must also go through Provider Relations at (225) 924-5040 or 800-473.2783. To follow up on the status of a requested Submitter ID, please call Provider Enrollment at (225) 237-3370 6

2.2 HIPAA Testing and Approval Overview This section provides a general overview of the HIPAA testing and approval process. Subscribe to the Software Vendor, Billing Agent and Clearinghouse (VBC) List. o VBCs identified in the list are those that have enrolled with the LA Medicaid HIPAA Desk testing service and are pursuing HIPAA readiness. Testing Enrollment o A provider s Software Vendor, Billing Agent or Clearinghouse must complete and return an enrollment form to get enrolled in the LA Medicaid HIPAA Testing Service. HIPAA Testing Service o Submitters will test transactions with a secure, web based testing program for each LA Medicaid claim type they identified on their enrollment form for validation. MMIS Parallel Testing o Parallel HIPAA transactions along with their corresponding proprietary electronic claims are compared for appropriate adjudication results. o Based on a successful parallel test(s), production approval for HIPAA transactions is granted. 3 Testing with the Payer This section contains a detailed description of the testing phase. The following information will help you enable your software vendor, billing agent or clearinghouse to become HIPAA approved. Instructions are also provided for those who do not have a software vendor, billing agent or clearinghouse. Note: If you currently submit claims electronically to LA Medicaid, your current method WILL NOT be HIPAA compliant without modifications by your Software Vendor, Billing Agent or Clearinghouse. The only exception to this statement is for electronic billing of Non-Ambulance Transportation claims which are exempt from HIPAA, and POS Pharmacy who will be approved through their switch vendors. All other claims are affected. From this point on a "Software Vendor, "Billing Agent", or "Clearinghouse" will be referred to collectively as a VBC. 3.1 Software Vendor, Billing Agent, and Clearinghouse (VBC) List If you are a LA Medicaid provider AND a. You do not have a Software Vendor, Billing Agent or Clearinghouse (VBC) OR b. Your VBC does not plan on becoming HIPAA ready 7

You should: Subscribe to the weekly VBC list and HIPAA updates by emailing the HIPAA EDI group at (the * asterisk is part of the email address). Put "subscribe to VBC list" in the subject line. VBCs identified in the list are those that have enrolled with the LA Medicaid HIPAA testing service and are pursuing HIPAA readiness. The list will include contact information, the types of X12N HIPAA transactions they support, and a status of "Enrolled", "Testing", Parallel, or "Approved." The final "Approved" status means a provider can submit HIPAA EDI claims THROUGH the approved VBC to LA Medicaid. The list will be updated and emailed weekly to subscribers as VBCs enroll and progress through the testing process. LA Medicaid encourages all providers to be good consumers and use the VBC list to shop for a VBC that best suits their needs and their budget as the features, functions, and costs vary significantly between VBCs. Find the one that is right for you. Providers can also monitor the list to see how their VBC are progressing toward production approval. The weekly VBC list will be emailed to those providers who have sent a subscription request to (the * asterisk is part of the email address), and will also be available on the web at www.lamedicaid.com/hipaa 3.2 HIPAA Desk Testing Service Enrollment The first step toward your HIPAA readiness is to have your VBC contact LA Medicaid and enroll in our testing service. As a provider who bills electronically, your VBC will be tasked with making your claims HIPAA ready. Therefore, the VBC must contact the LA Medicaid HIPAA EDI Group to enroll. (*Some providers develop their own electronic means of submitting claims to LA Medicaid. In this case the provider would be considered the VBC) The testing enrollment form is available on the web at www.lamedicaid.com/hipaa VBCs can also get an enrollment form by contacting the HIPAA EDI group by emailing a request for enrollment form to (the * asterisk is part of the email address) or by calling (225) 237.3318 The Software Vendor, Billing Agent, or Clearinghouse must complete the form and return it by email to LA Medicaid A HIPAA EDI representative will issue the VBC login information for our testing service. Companion guides for the 837-I, 837-P, 837-D, & 278 transactions are available for download from within the HIPAA Desk testing service. Our testing service is now available 24-hours-a-day, 7-days-a-week. 8

Once your VBC has contacted LA Medicaid for enrollment in the LA Medicaid HIPAA testing service, advancement toward HIPAA readiness can begin. Please have your VBC enroll early, even if they are not ready to send a test file. It is important that LA Medicaid understands that they intend on becoming HIPAA compliant. In addition, LA Medicaid will communicate with all the VBCs primarily through the HIPAA Desk testing service so being enrolled early ensures they are getting all the information they need. 3.3 HIPAA Testing Service Once your VBC has contacted LA Medicaid and the enrollment form is processed, login information will be issued to the named testers on the enrollment form. The testing service is a secure web based application that requires an Internet connection and a web browser. The testing service will have everything a VBC needs to test for HIPAA readiness with LA Medicaid. Companion Guides for the 837I, 837P, 837D, & 278 transactions and other necessary and useful documentation will be available for download from within the HIPAA Desk testing service. There are several testing programs in the HIPAA Desk testing service that correspond with LA Medicaid claim types. VBCs will be enrolled into the testing programs according to the claim types indicated on their enrollment form. Each testing program includes several tasks that must all be perfumed successfully to complete HIPPA Desk testing. Upon completing of HIPAA Desk testing the VBC will begin MMIS Parallel Testing. The testing service is comprehensive and evaluates SNIP 1-7 types of testing. 3.4 MMIS Parallel Testing Please refer to the section on Connectivity with the Payer / Communications to for instructions on how to gain access to our test HIPAA Bulletin Board System (BBS). Parallel testing will compare a current proprietary electronic claim file with a parallel HIPAA EDI file, both utilizing the same source data. Generally, the current proprietary and HIPAA EDI file should adjudicate the same. NOTE: For those submitters who have not previously sent proprietary electronic Medicaid claims, such a TAD billers, your parallel testing process will be slightly different. TAD billers will consult their most recent remittance advice and construct a parallel HIPAA EDI file using the same claim data from the paper claims, which were reported on their most recent remittance advice. The HIPAA EDI file must be constructed and transmitted to the test HIPAA BBS within 7 days of receiving the remittance advice. These claims will be compared to the HIPAA file sent to the test BBS, which was generated from the same data. Any discrepancies will need to be resolved by your assigned HIPAA EDI QA parallel testing support person. If a tester does not have an assigned support person, please contact the HIPAA EDI QA group, please email (the * asterisk is part of the email address) or call 225.237.3318 Listed below are the Parallel testing requirements: 9

1. Submitter must have an active submitter ID with Louisiana Medicaid. 2. Upload a copy of a production Electronic Medicaid Claim (EMC) file. The EMC copy must be uploaded within 7 days from the original submission to production. Files that are not uploaded within the time requirement will void the parallel test results. Positive results are required for promotion to production. 3. Upload a parallel HIPAA file that was constructed using the same production data in the copy of the original production EMC file. The HIPAA file cannot be more than 7 days older than the original production EMC file. Note: Both files may be uploaded in a compressed file using Winzip or Pkzip. NOTE: For those submitters who have not previously sent proprietary electronic Medicaid claims, such a TAD billers, your parallel testing process will be slightly different. TAD billers will consult their most recent remittance advice and construct a parallel HIPAA EDI file using the same claim data from the paper claims, which were reported on their most recent remittance advice. The HIPAA EDI file must be constructed and transmitted to the test HIPAA BBS within 7 days of receiving the remittance advice. These claims will be compared to the HIPAA file sent to the test BBS, which was generated from the same data. Any discrepancies will need to be resolved by your assigned HIPAA EDI QA parallel testing support person. If a tester does not have an assigned support person, please contact the HIPAA EDI QA group, please email (the * asterisk is part of the email address) or call 225.237.3318 4. For each file that is uploaded, 2 reports will be posted to the BBS for download. One report will contain any errors/denials and the other will contain the detail payment information with a summary. (Error/denial code descriptions are available for download from within HIPAA Desk). The goal for the HIPAA file and the EMC to process the same. Any discrepancies will need to be resolved by your assigned HIPAA EDI QA parallel testing support person. If a tester does not have an assigned support person, please contact the HIPAA EDI QA group, please email (the * asterisk is part of the email address) or call 225.237.3318 5. A member of the parallel test team on the HIPAA EDI QA team gives production approval. Approval is based on the success of a parallel test. Once approved, the submitter will be given access to the production HIPAA BBS, and receive a status of Approved on the VBC list. 4 Connectivity with the Payer / Communications 4.1 Supported Transactions The HIPAA EDI BBS supports the following transactions: Transaction Name Version Health Care Claim: Dental ASC X12N 837-004010X097A1 Health Care Claim: Professional ASC X12N 837-004010X098A1 Health Care Claim: Institutional ASC X12N 837-004010X096A1 Health Care Claim Payment/ Advice ASC X12N 835-004010X091A1 Health Care Services Request for Review and Response ASC X12N 278-004010X094A1 Functional Acknowledgement ASC X12N 997 Interchange Acknowledgement ASC X12N TA1 Batch Pharmacy NCPDP 1.1 10

4.2 Submitter IDs & Passwords 4.2.1 New Submitter or Changing Submitter Requests for a new submitter ID, or request to change submitter IDs must both be directed to Provider Relations at (225) 924-5040 or 800-473.2783. Make these requests early so the submitter ID will be ready for parallel testing and production approval. Note: A Submitter ID is required before a password can be issued for parallel testing. Refer to the section on Trading Partner Registration for obtaining a Submitter ID. The HIPAA Desk testing service can be used without a LA Medicaid submitter ID, but requires a user ID and password. Parallel testing REQUIRES a LA Medicaid submitter ID and a password. 4.2.2 HIPAA Testing Service The User ID and Password for the Louisiana Medicaid HIPAA Desk Testing service is provided by the HIPAA EDI QA group after a testing service enrollment form has been completed and returned. Please refer to the section on HIPAA Testing Service Enrollment. 4.2.3 Test HIPAA Bulletin Board System (BBS) for Parallel Testing All providers and submitters who currently send electronic claims to LA Medicaid can use their existing Submitter IDs. They are still valid for HIPAA. However you must be assigned a password to access the Test HIPAA BBS for parallel testing. Passwords will be available for download from within the HIPAA Desk testing service. In addition, you can ask any HIPAA EDI group representative that you have been in contact with for support. Or you can contact the HIPAA EDI Group at (225) 237.3318. 4.2.4 Production HIPAA Bulletin Board System (BBS) Submitter ID and Password for accessing the Production HIPAA bulletin board is the same as for the Test HIPAA bulletin board. The Production bulletin board will be updated with the information after approval is given. 4.3 HIPAA Bulletin Board Dial-up Phone Numbers 4.3.1 Test *Note: As an emergency alternative if the lines below are not working, this number may be used 225.927.8028 This number does not roll to an open line when busy, so when the difficulty is cleared with the lines below, return to using the primary lines below. Dial 225.927.4123 to Upload the following types of files to Test. 837 Institutional 837 Dental 837 Professional Proprietary claims files for parallel testing Dial 225.237.3296 to Upload & Download the following type of file: 278 Prior Authorization (Health Care Services Request for Review and Response Dial 225.237.3214 to Download the following types of files TA1 Interchange Acknowledgement 997 Functional Acknowledgement 11

835 Payment Advice MMIS Reports for parallel testing 4.3.2 Production *Note: As an emergency alternative if the lines below are not working, the following numbers may be used: 225.927.4337, 225.927.6098, 225.927.6547 These numbers do not roll to an open line when busy, so when the difficulty is cleared with the lines below, return to using the primary lines below. Dial 225.927.4326 to Upload the following types of files to Production. 837 Institutional 837 Dental 837 Professional Dial 225.927.6536 to Upload & Download the following type of file 278 Prior Authorization (Health Care Services Request for Review and Response Dial 225.927.4621 to Download the following type of files TA1 Interchange Acknowledgement 997 Functional Acknowledgement 835 Payment Advice 4.4 Communication protocol specifications 4.4.1 Dial-Up Requirements Windows o Dial-up Software that uses an asynchronous modem supporting Z-Modem protocol and a minimum baud rate of 9600 kbps Unix o Unisys will accept the BLAST protocol for asynchronous transmission at 14.4, 9.6, 4.8, 2.4 and 1.2 kbps. 4.5 File Naming Conventions This section describes how files should be named for files uploaded to the BBS and those mailed on tape, disk, or Compact Disc (CD). 4.5.1 Test File Names In order to complete parallel testing, two files must be uploaded to the Test HIPAA BBS. One will be a copy of a production Electronic Medicaid Claim (EMC) file named the same. Those names are listed in the table in Appendix E File Naming Conventions > Test File Names. The other file will be a HIPAA parallel file using the same data as the production EMC file and the same name as for production. Please refer to Appendix E File Naming > Test File Names 4.5.2 Production File Names Please refer to Appendix E File Naming > Production File Names 12

4.6 File Transmission Procedures 4.6.1 BBS Error Codes Please refer to Appendix D BBS Error Codes for descriptions of any error codes returned by the BBS. 4.6.2 How To Connect and Login To The Louisiana EDI BBS To login to the Louisiana EDI BBS, submitters must first have a valid Submitter ID and Password, see Trading Partner Registration Configure the dialup software to dial the Louisiana EDI BBS using the appropriate phone numbers from the Bulletin Board Dial-Up Phone Numbers section. Once connected to the BBS, submitters should see the BBS Login Screen. Once connected to the BBS Login Screen, submitters must enter a valid Submitter ID and Password. Enter a Submitter ID and press the [Enter] Key. Then type the corresponding password and press the [Enter] key. At this point, press the [Y] key to complete the authentication process or press the [N] key to exit. The BBS Main Menu should appear. 4.6.3 How To Submit A File To The Louisiana EDI BBS Login to the Louisiana EDI BBS using your Submitter ID and Password. At the BBS Main Menu press the [A] key to select the Send File(s) option of the Main Menu. The BBS File Upload screen will display An open dialog screen should appear. If it does not, then manually start the upload process. Consult your dial-up software documentation for details. Usually, there will be an option to upload/download through your software. After the file is uploaded to the BBS, the BBS File Upload Review Y/N will display. If you want to review the files and their edits, press the [Y] key and the BBS File Uploaded Review Y screen will display a list of uploaded files. To bypass the file review screen press the [N] key, you will be redirected back to the BBS Main Menu. 4.6.4 Single File Submission A Single File Submission is an ASCII text file containing an X12N Transaction, *Proprietary EMC file, or NCPDP file. The following rules apply to the file. The file must have a valid file extension. For more information see Appendix E File Naming The file must be an ASCII Text File. 13

The file must be a valid X12N 837, 278, NCPDP, or *Proprietary electronic claim. *For parallel testing purposes, Louisiana proprietary file formats can be sent to the Test Louisiana HIPAA BBS. Note: Proprietary files are never to be sent to the Production HIPAA BBS. 4.6.5 Multiple File Submission Multiple files can be uploaded to the Louisiana HIPAA BBS by sending a compressed file. The compressed file can contain any number of files. PKZip or WinZip can be used to create the compressed files: The compressed files must comply with the following rules: The compressed file cannot be encrypted. The compressed file cannot be password protected. Each file contained in the compressed file must conform to the Single File Submission requirements. 4.6.6 How To Receive Responses and Download Files Login to the BBS. From the BBS Main Menu, press the [B] key to retrieve files. The BBS File Download Selection Screen will display. Select a file type to download from the BBS File Download Selection Screen. The BBS File Download List will display a list of files available for download. Select the file to download. The BBS File Download Screen Step 1 of 2 screen will display giving a choice to compress the files before download. Choose [Y] to compress the file or [N] to download the file uncompressed. The BBS Receive File Step 2 of 2 screen will be displayed. A Browse for Folder dialog should be display on entry into the screen. Select a target location to download your file. If the dialog box is not displayed, manually start the download process. Consult you Dial-up Software documentation for details. After the selected file or files are downloaded, the screen will navigate back to the BBS File Download Selection Screen. 4.6.7 HyperTerminal HyperTerminal comes with all Microsoft Windows operating systems. Step by step instructions for using HyperTerminal are provided in Appendix B Windows HyperTerminal Instructions. 14

4.7 Accepted Physical Media 4.7.1 Media Labeling The following label information is required on all Tapes, Diskettes, and CDs. LMMIS Tape, Disk, or CD Label 1. Creation Date 2. Submitter ID 450 3. Reel Number 5. Records 6. Amount $ 4. Provider or Company Name 7. Computer Used 8. Claim Type 9. OP System 10. File Name 1. The billing date of the submission as it appears on the encoded claims and as it appears on the Submission Certification. 2. The submitter's ID number. 3. An external identifying number that makes the magnetic diskette unique - any six characters or digits the submitter wishes. This number must be unique to the submitter's tape/diskette/cd library and must be listed in Section I of the "Submission Certification." 4. The name of the provider, billing agent, or clearinghouse submitting the tape/diskette/cd. 5. The count of Medicaid claims contained on all the batches of the tape/diskette/cd. 6. The total dollar amount billed on the tape/diskette/cd for all the claims. 7. Type of machine used to create diskette/tape. Be specific, e.g., IBM 34, Series I, TRS 80, Kaypro, IBM PC. 8. The type(s) of claims encoded on the tape/diskette/cd, e.g., Pharmacy, Hospital Inpatient, Hospital Outpatient, and Physician/Professional. 9. Operating system used e.g. CPM, CPM-86, PC-DOS, NECDOS, Turbodos, etc. 10. File Name - Directory name of internal file (left justify). 4.7.2 Tape Specifications The following specifications must be adhered to when submitting tape input media. Tape - 9 track, 7" to 10 1/2" reels with silver mylar reflector (standard reels). Recording Density - 1,600 bytes per inch required. Recording Code - Extended Binary Coded Decimal Interchange Code (EBCDIC). File Labels - None. The tape may have a leading tape mark and must have an end of file mark. Unfilled Final Block - Fill with spaces or use a short block. Do not fill the last block with 9s, high, or low values. Tapes must be an uncompressed format. 4.7.3 5.25 & 3.5 Diskette Specifications IBM & IBM PC compatibles 5.25 Diskette o 96TPI o ASCII 15

o MS-DOS, PC DOS 3.5 Diskette o 270 TPI 1.44 Megs o Double-sided high density o ASCII o MS-DOS, PC-DOS 4.7.4 Compact Disc CD-R and CD-RW discs are acceptable. 4.7.5 Requesting an 835 Submitters who currently receive electronic remittance advice (ERA) from LA Medicaid should contact the HIPAA EDI QA group at 225.237.3318 to request an 835. A test 835 will be created for the submitter to evaluate. Alert: The change from ERA to 835 is mutually exclusive. The 835 will replace the current ERA. Both cannot be generated in production. Once the switch is made to the 835 in production you cannot be switched back to the proprietary ERA. In addition, the switch is performed at the submitter level. Therefore, all the providers who are linked to the submitter get their payment advice on an 835. So, the submitter requesting the 835 in production must be certain that their providers are prepared to handle the 835, or are not concerned with receiving it. 4.8 Accepted HIPAA Transactions The HIPAA EDI Bulletin Board accepts the following transactions: Transaction Version Name 837D 004010X097A1 Dental 837P 004010X098A1 Professional 837I 004010X096A1 Institutional 278 004010X094A1 Prior Authorization NCPDP 1.1 Batch 1.1 Pharmacy 5 Contact information 5.1 EDI Customer Service and Technical Assistance If you have questions in regards to this document please contact the EDI HIPAA QA group at (the * asterisk is part of the email address) or (225) 237.3318. 5.2 Provider Service Number For detailed information concerning the payment of claims, please contact Providers Relations @ 800-473-2783 16

For enrollment as a new electronic submitter for Louisiana Medicaid, or to change submitter numbers, contact Provider Relations at (225) 924-5040 or 800-473.2783 @ (225) 237-3370 5.3 Applicable websites / e-mail Email (the * asterisk is part of the email address) for all HIPAA EDI testing and support questions. Louisiana Medicaid s website for HIPAA information: www.lamedicaid.com/hipaa 17

6 Control Segments / Envelopes 6.1 ISA-IEA This section describes Louisiana Medicaid s use of the interchange control segments. It includes a description of expected sender and receiver codes, authorization information, and delimiters. ISA User Option (Usage): Required Element Summary: 6.1.1 ISA - Interchange Control Header Segment Interchange Control Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 16 Ref Id Element Name Req Type Min/Max ISA01 I01 Authorization Information Qualifier M ID 2/2 LA Medicaid: Use 00 for this element ISA02 I02 Authorization Information M AN 10/10 LA Medicaid: Must be spaces ISA03 I03 Security Information Qualifier M ID 2/2 LA Medicaid: Use 00 for this element ISA04 I04 Security Information M AN 10/10 LA Medicaid: Must be spaces ISA05 I05 Interchange ID Qualifier M ID 2/2 LA Medicaid: Use ZZ for this element ISA06 I06 Interchange Sender ID M AN 15/15 LA Medicaid: Use the 7 digit Unisys assigned submitter ID (i.e. 450XXXX) followed by spaces ISA07 I05 Interchange ID Qualifier M ID 2/2 LA Medicaid: Use ZZ for this element ISA08 I07 Interchange Receiver ID M AN 15/15 LA Medicaid: Use LA-DHH-MEDICAID for this element ISA09 I08 Interchange Date M DT 6/6 LA Medicaid: The date format is YYMMDD ISA10 I09 Interchange Time M TM 4/4 LA Medicaid: The date format is HHMM ISA11 I10 Interchange Control Standards Identifier M ID 1/1 LA Medicaid: Use U for this element ISA12 I11 Interchange Control Version Number M ID 5/5 LA Medicaid: Use 00401 for this element ISA13 I12 Interchange Control Number M N0 9/9 LA Medicaid: Must be identical to the interchange trailer IEA02. Must be unique for every transmission submitted. ISA14 I13 Acknowledgment Requested M ID 1/1 LA Medicaid: Use 1 for this element ISA15 I14 Usage Indicator M ID 1/1 LA Medicaid: T = Test Data P = Production Data ISA16 I15 Component Element Separator M 1/1 LA Medicaid: Must be a colon : - ASCII x3a 18

IEA 6.1.2 IEA - Interchange Control Trailer Interchange Control Trailer Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Required Element Summary: Ref Id Element Name Req Type Min/Max IEA01 I16 Number of Included Functional Groups M N0 1/5 LA Medicaid: Number of included functional groups IEA02 I12 Interchange Control Number LA Medicaid: Must be identical to the value in ISA13 M N0 9/9 6.2 GS-GE This section describes Louisiana Medicaid s use of the functional group control segments. It includes a description of expected application sender and receiver codes. Also included in this section is a description concerning how Louisiana Medicaid expects functional groups to be sent and how Louisiana Medicaid will send functional groups. These discussions will describe how similar transaction sets will be packaged and Louisiana Medicaid s use of functional group control numbers. GS 6.2.1 GS Functional Group Header Functional Group Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 8 User Option (Usage): Required Element Summary: Ref Id Element Name Req Type Min/Max GS01 479 Functional Identifier Code M ID 2/2 LA Medicaid: Use the value HC for this element GS02 142 Application Sender's Code M AN 2/15 LA Medicaid: Must be identical to the value in ISA06 GS03 124 Application Receiver's Code M AN 2/15 LA Medicaid: Use LA-DHH-MEDICAID for this element GS04 373 Date M DT 8/8 LA Medicaid: The date format is CCYYMMDD GS05 337 Time M TM 4/8 LA Medicaid: The time format is HHMM GS06 28 Group Control Number M N0 1/9 LA Medicaid: Assigned and maintained by the sender GS07 455 Responsible Agency Code M ID 1/2 LA Medicaid: Use the value X for this element GS08 480 Version / Release / Industry Identifier Code LA Medicaid: Use the transaction version value for this element: For example 004010X096A1 M AN 1/12 19

GE 6.2.2 GE Functional Group Trailer Functional Group Trailer Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Required Element Summary: Ref Id Element Name Req Type Min/Max GE01 97 Number of Transaction Sets Included M N0 1/6 LA Medicaid: Number of transactions sets included GE02 28 Group Control Number LA Medicaid: Must be identical to the value in GS06 M N0 1/9 6.3 ST-SE This section describes Louisiana Medicaid s use of transaction set control numbers. Only one ST-SE transaction loop is permitted per file. 7 Payer Specific Business Rules and Limitations This information is available in the specific companion guides for the 837 P, 837 I, 873 D, & 278 transactions. The companion guides are available for download from within the HIPAA Desk Testing Service. Refer to the section on HIPAA Desk Testing Service Enrollment. 8 Acknowledgements and or Reports Please see appendix A for detail on the 997 and TA1 Acknowledgements This section contains information and examples on any applicable payer acknowledgements 8.1 997 Functional Acknowledgement Please refer to Appendix A Acknowledgments > 997 Functional Acknowledgement 8.2 TA1 Interchange Acknowledgement Please refer to Appendix A Acknowledgments > TA1 Interchange Acknowledgement 8.3 Valid EDI Delimiters for Louisiana Medicaid Definition ASCII Decimal Hexadecimal Segment Separator ~ 126 7E Element Separator * 42 2A Compound Element Separator : 58 3A 20

9 Trading Partner Agreements If you currently send electronic claims to Louisiana Medicaid, no additional agreements are required for HIPAA. However, if you are a new provider or a submitter that would like to submit electronically, please contact Provider Relations at (225) 924-5040 or 800-473.2783 @ (225) 237-3370 21

10 Appendix A - Acknowledgements 10.1 997 Functional Acknowledgement Interchange Control Header Pos: Max: 1 ISA Not Defined - Mandatory Loop: N/A Elements: 16 User Option (Usage): Required Example: ISA*00* *00* *ZZ*LA-DHH-MEDICAID*ZZ*4599999 *030423*0944*U*00401*000000001*1*T*:~ Element Summary: ISA/GS-These segments are the same as the inbound 837 with the exception of the Sender/Receiver Codes are reversed, as Louisiana has now become the Sender. Also, the GS01 is now FA -Functional Acknowledgment, rather than HC -Health Care Claim. Ref Id Element Name Req Type Min/Max ISA01 I01 Authorization Information Qualifier M ID 2/2 LA Medicaid: 00 will be used for this element ISA02 I02 Authorization Information M AN 10/10 LA Medicaid: Spaces will be used ISA03 I03 Security Information Qualifier M ID 2/2 LA Medicaid: 00 will be used for this element ISA04 I04 Security Information M AN 10/10 LA Medicaid: Spaces will be used ISA05 I05 Interchange ID Qualifier M ID 2/2 LA Medicaid: ZZ will be used for this element ISA06 I06 Interchange Sender ID M AN 15/15 LA Medicaid: LA-DHH-MEDICAID will be used for this element ISA07 I05 Interchange ID Qualifier M ID 2/2 LA Medicaid: ZZ will be used for this element ISA08 I07 Interchange Receiver ID M AN 15/15 LA Medicaid: Will be the 7 digit Unisys assigned submitter ID (i.e. 450XXXX) followed by spaces ISA09 I08 Interchange Date M DT 6/6 LA Medicaid: The date format is YYMMDD ISA10 I09 Interchange Time M TM 4/4 LA Medicaid: The time format is HHMM ISA11 I10 Interchange Control Standards Identifier M ID 1/1 LA Medicaid: Will be U for this element ISA12 I11 Interchange Control Version Number M ID 5/5 LA Medicaid: Will be 00401 for this element ISA13 I12 Interchange Control Number M N0 9/9 LA Medicaid: Will be identical to the interchange trailer IEA02. Will be unique for every transmission submitted. ISA14 I13 Acknowledgment Requested M ID 1/1 LA Medicaid: Will be 1 for this element ISA15 I14 Usage Indicator M ID 1/1 LA Medicaid: T = Test Data P = Production Data ISA16 I15 Component Element Separator M 1/1 LA Medicaid: Will be a colon : - ASCII x3a 22

Functional Group Header Pos: Max: 1 GS Not Defined - Mandatory Loop: N/A Elements: 8 User Option (Usage): Required Example: GS*FA*LA-DHH-MEDICAID*4599999*20030423*0944*1*X*004010X098A1~ Element Summary: Ref Id Element Name Req Type Min/Max GS01 479 Functional Identifier Code M ID 2/2 LA Medicaid: Will be the value FA for this element GS02 142 Application Sender's Code M AN 2/15 LA Medicaid: Will be LA-DHH-MEDICAID for this element GS03 124 Application Receiver's Code M AN 2/15 LA Medicaid: Will be identical to t he value in ISA06 GS04 373 Date M DT 8/8 LA Medicaid: The date format is CCYYMMDD GS05 337 Time M TM 4/8 LA Medicaid: The time format is HHMM GS06 28 Group Control Number M N0 1/9 LA Medicaid: Assigned and maintained by the sender GS07 455 Responsible Agency Code M ID 1/2 LA Medicaid: Will be the value X for this element GS08 480 Version / Release / Industry Identifier Code LA Medicaid: Will be the value of the transaction version being validated by the 997. For Example, 004010X096A1, 004010X097A1, or 004010X098A1 for this element M AN 1/12 TRANSACTION SET HEADER Pos: 010 Max: 1 ST Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Required Example: ST*997*0001~ Element Summary: ST-This segment identifies the start of the Transaction. The only difference between this ST and the 837 ST is the ST01 identifies the transaction as 997. Ref Id Element Name Req Type Min/Max 143 Transaction Set Identifier Code M ID 3/3 LA Medicaid: 997 will be used in the element FUNCTIONAL GROUP RESPONSE HEADER Pos: 020 Max: 1 AK1 Heading - Optional Loop: N/A Elements: 2 User Option (Usage): Required Example: AK1*HC*1~ Element Summary: AK1-This segment starts the acknowledgment group. Ref Id Element Name Req Type Min/Max AK01 479 Functional Identifier Code M ID 2/2 LA Medicaid: HC is the only valid value 23

TRANSACTION SET RESPONSE HEADER Pos: 030 Max: 1 AK2 Heading - Optional Loop: AK2 Elements: 2 User Option (Usage): Required Example: AK2*837*000001~ Element Summary: AK2-The AK202 will display the same Transaction Set Control Number as the ST that is being acknowledged. Ref Id Element Name Req Type Min/Max AK201 143 Transaction Set Identifier Code M ID 3/3 LA Medicaid: 837-Health Care Claim Data Segment Note Pos: 040 Max: 1 AK3 Heading - Optional User Option (Usage): Situational Example: AK3*SV1*23**8~ Element Summary: AK3-This segment identifies which 837-segment contain an error. Loop: AK2/AK3 Elements: 4 Ref Id Element Name Req Type Min/Max AK301 721 Segment ID Code M ID 2/3 LA Medicaid: This is the two or three characters which occur at the beginning of a segment. This segment identifies which 837-segment contain an error. AK304 720 Segment Syntax Error Code LA Medicaid: This code is required if an error exists. See Implementation Guide for Valid Values O ID 1/3 Data Segment Note Pos: 050 Max: 99 AK4 Heading - Optional User Option (Usage): Situational Example: AK4*8**2~ Element Summary: Loop: AK2/AK3 Elements: 4 Ref Id Element Name Req Type Min/Max AK403 723 Segment Syntax Error Code LA Medicaid: This code is required if an error exists. See Implementation Guide for Valid Values M ID 1/3 24

TRANSACTION SET RESPONSE TRAILER Pos: 060 Max: 1 AK5 Heading- Mandatory Loop: N/A Elements: 6 User Option (Usage): Required Example: AK5*R*5~ Element Summary: Ref Id Element Name Req Type Min/Max AK501 717 M ID 1/1 Transaction Set Acknowledgment Code AK502 718 LA Medicaid: This element will indicate Acceptance or Rejection based on syntax edits. See Implementation Guide for Valid Values Transaction Set Syntax Error Code LA Medicaid: This code is required if an error exists. See Implementation Guide for Valid Values O ID 1/3 FUNCTIONAL GROUP RESPONSE TRAILER Pos: 070 Max: 1 AK9 Heading- Mandatory User Option (Usage): Required Example: AK9*R*1*1*0~ Element Summary: Loop: AK2/AK3 Elements: 9 Ref Id Element Name Req Type Min/Max AK901 715 M ID 1/1 Functional Group Acknowledgment Code AK905 718 LA Medicaid: This element will indicate Acceptance or Rejection based on syntax edits. See Implementation Guide for Valid Values Functional Group Error Code LA Medicaid: This code is required if an error exists. See Implementation Guide for Valid Values O ID 1/3 Transaction Set Trailer Pos: 080 Max: 1 SE Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Required Example: SE*422*0001~ Element Summary: Ref Id Element Name Req Type Min/Max 721 Segment ID Code M ID 2/3 LA Medicaid: This is the two or three characters which occur at the beginning of a segment. This segment identifies which 837-segment contain an error. 720 Segment Syntax Error Code LA Medicaid: This code is required if an error exists. See Implementation Guide for Valid Values O ID 1/3 25

Functional Group Trailer Pos: Max: 1 GE Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Required Example: GE*1*1~ Element Summary: Ref Id Element Name Req Type Min/Max GE01 97 Number of Transaction Sets Included M N0 1/6 LA Medicaid: Number of transactions sets included GE02 28 Group Control Number LA Medicaid: Will be identical to the value in GS06 M N0 1/9 Interchange Control Trailer Pos: Max: 1 IEA Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Required Example: IEA*1*000000001~ Element Summary: Ref Id Element Name Req Type Min/Max IEA01 I16 Number of Included Functional Groups M N0 1/5 LA Medicaid: Number of included functional groups IEA02 I12 Interchange Control Number LA Medicaid: Will be identical to the value in ISA13 M N0 9/9 26

10.2 TA1 Interchange Acknowledgement The TA1 will be available on the BBS immediately after submission of an 837. Please note the LA Medicaid sends the TA1 report separate from the 997-Functional Acknowledgement. This segment acknowledges the reception of an X12 interchange header and trailer from a previous interchange. If the header/trailer pair was received correctly, the TA1 reflects a valid interchange, regardless of the validity of the contents of the data included inside the header/trailer envelope. The validity of the data contained within the actual transaction will be acknowledged in the 997. Interchange Acknowledgement Pos: Max: 1 TA1 Not Defined - Mandatory Loop: N/A Elements: 5 User Option (Usage): Required Example: TA1*000568426*030615*0200*A*000~ Element Summary: Ref Id Element Name Req Type Min/Max TA101 I12 Interchange Control Number M N0 9/9 LA Medicaid: Will be the Interchange Control Number of the original Transaction being acknowledged. TA102 I08 Interchange Date M DT 6/6 LA Medicaid: Will be the date of the original Transaction being acknowledged. YYMMDD TA103 I09 Interchange Date LA Medicaid: Will be the time of the original Transaction being acknowledged. HHMM M TM 4/4 TA104 I17 Interchange Acknowledgement Code LA Medicaid: This will indicate if the envelopes are Accepted with no errors, Accepted with errors, or Rejected due to errors. See Implementation Guide for valid values. TA105 I18 Interchange Note Code LA Medicaid: This will display the error code indicating the error with the Interchange Control Structure. See Implementation Guide for valid values. M ID 1/1 M ID 3/3 27

11 Appendix B Windows HyperTerminal Instructions This section provides Louisiana Medicaid s specific transmission administrative procedures. Note: Perform the following steps to electronically submit your transactions using Windows 95/98, NT & XP HyperTerminal program. From your Windows desktop, click Start on the task bar and point to Programs. From the Programs menu, point to Accessories and click HyperTerminal. Note: You may need to point to Communications before HyperTerminal, depending on your version of Windows. Double-click the HypterTrm icon in the newly displayed window. If you have not previously assigned a modem in Windows 95/98, you will be prompted to do so now. At the Connection Description screen, enter a name for this connection, select an icon and click OK. (This connection can be saved after the session has ended for future use, so use a name that you will remember). At the Phone Number screen, enter the area code and phone number that the modem will dial and click OK. (If you need to dial a 9 to access an outside line, enter a 9 before the phone number. [Example: 9,12259274123 ]). At the Connect screen, ensure the phone number that is displayed is correct. (Make any changes by selecting Modify). Click Dial and wait for the modem to dial and connect to the Louisiana Medicaid BBS. After the connection is made, the Host computer will prompt you for your Trading Partner ID. Enter your 7 digit Submitter ID and press Enter. See Figure 1 When the Host computer prompts you for your Password, enter your password and press Enter. (The Password that you type will not be displayed on the screen). See Figure 1 Next, the Host computer will display a short menu and ask you to make a selection. Select the appropriate letter for the operation you wish to perform and press Enter. See Figure 2 Click Transfer on the HyperTerminal menu and select Send File When the Send File applet is open, click the Browse On the Select File to Send applet, click the arrow pointing downward at the end of the Look in field and select the location of your 837 data file. 28

When the Open button is clicked, the Send File applet will appear with the pathname. Click on the Send button to begin transmission. File will be sent to the Louisiana Medicaid system. Please review the BBS User Manual for information on downloading files and details about claims submission. Figure 1 Figure 2 29

12 Appendix C BBS Screen Shots 12.1 BBS Login Screen Screen Description: This screen allows a Submitter to login to the Louisiana EDI BBS. Once you have logged in to the BBS the following message will be displayed. Press [Y] to continue or [N] to logoff. Once authentication is complete, the BBS will navigate to the BBS Main Menu. 30

12.2 BBS Main Menu Screen Description: The Louisiana EDI BBS Main Menu is the main entry point of the BBS. Screen Options Option Name Description A Send File(s) This option navigates to the File Upload Dialog. B Receive File(s) This option navigates to the Transmission Retrieval screen, where Submitters can download response files from the Louisiana EDI BBS Q Logoff This option allows a Submitter to logoff from the Louisiana EDI BBS. Note: In the upper left hand corner of the screen, the version number and region appears. Before attempting to upload claims, verify that you are in the correct region. 31

12.3 BBS File Upload Screen Description: The Transmission Submission File Upload Dialog allows users to upload a file to the Louisiana EDI BBS. Once a Submitter navigates to the screen, an Open File dialog screen should be displayed allowing a file to be uploaded. If the Open File dialog screen does not display, then the upload process must be started manually. Consult the dialup software for details. 32

12.4 BBS File Upload Review Y/N Screen Description: The File Upload Review dialog screen allows Submitters to choose whether or not to review the files they have submitted and any edits that the file received. Screen Options Option Name Description Y Yes This option navigates to the Louisiana BBS File Upload Review. N No This option navigates to the Louisiana EDI BBS Main Menu. 12.5 BBS File Uploaded Review Y Screen Description: This screen displays the files that were uploaded to the Louisiana EDI BBS. Once this screen is displayed press the [ENTER] key to navigate to the Louisiana EDI BBS Main Menu. 33

12.6 BBS File Download Selection Screen Screen Description: This screen allows Submitters to navigate to the File Download areas where the Responses can be downloaded. Note: This screen differs depending on the Region. An image for each region is displayed below. Screen Sample - Production Screen Sample Test Screen Options Option Name 1 997 Functional Acknowledgements 2 835 Remittance Advice Description This option navigates to the File download screen where Submitters can download 997 response files from the Louisiana EDI BBS. This option navigates to the File Download screen where Submitters can download 835 response files from the Louisiana 34

EDI BBS. 3 278 Prior Auth Responses This option navigates to the File Download where submitters can download 278 response files from the Louisiana EDI BBS. 4 TA1 Responses This option navigates to the File Download screen where Submitters can download TA1 response files from the Louisiana EDI BBS. 5 Testing Reports (Test Only) This option navigates to the File Download screen where Submitters can download Test Reports from the Louisiana EDI BBS. Q Quit This option navigates to the Louisiana EDI BBS Main Menu. 12.7 BBS File Download List Screen Description: This screen allows users to view and download of Response Files that reside on the Louisiana EDI BBS. Since there can be multiple files stored for a Submitter on the BBS, the files can be listed on several pages. The screen allows Submitters to scroll up or down pages of file listings. Screen Options Option Name Description P Previous (Page) This option scrolls to the previous page of files. N Next (Page) This option scrolls to the next page of files. 1 thru 10 Download (file) [1 10] This option allows Submitters to download a single file. After a user selects this option a Compress Dialog screen will be displayed allowing a user to compress the file before downloading. A Download All This option allows a user to download all of the files from the particular download area. The files will be compressed and stored in a compressed file archive. Q Quit Navigates to the BBS File Download Selection Screen. 35

12.8 BBS File Download Screen Step 1 of 2 Screen Description: This screen allows users to choose if the file to be downloaded is to be compressed. Once the selection is made, the Louisiana EDI BBS Receive File Step 2 of 2 screen will start the download process. Screen Options Option Name Description Y Yes Compress the selected file or files before downloading. N No Do not compress the selected file or files before downloading. 36