ASC X X220A1)

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

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

Alameda Alliance for Health

Standard Companion Guide

Inland Empire Health Plan

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

USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270

Medical Associates Health Plans and Health Choices

Administrative Services of Kansas (ASK)

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

Claim Status Inquiry and Response (276/277) (Refers to the Implementation Guides based on ASC X X212)

West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270

DentaQuest HIPAA Transaction Standard Companion Guide

Administrative Services of Kansas (ASK)

Florida Blue Health Plan

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

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

Florida Blue Health Plan

Blue Cross Blue Shield of Louisiana

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

Anthem Blue Cross and Blue Shield. 834 Companion Guide

Partnership HealthPlan of California

HIPAA Transaction 278 Request for Review and Response Standard Companion Guide

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

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

Blue Cross Blue Shield of Delaware

Assurant Health HIPAA Transaction Standard Companion Guide

Standard Companion Guide

It is recommended not to exceed 99 patient requests per Information Receiver Loop (2000B).

EMBLEMHEALTH. HIPAA Transaction Standard Companion Guide

EMBLEMHEALTH HIPAA Transaction Standard Companion Guide

837 Health Care Claim Companion Guide. Professional and Institutional

EDI Functional Acknowledgment

HIPAA Transaction Standard Companion Guide. ASC X12N Version X220A1 834 Benefit and Enrollment Maintenance

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

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

BlueCross BlueShield of VT. Vermont

Integration Guide for Data Originators of Claim Status. Version 1.1

BLUE CROSS AND BLUE SHIELD OF LOUISIANA PROFESSIONAL CLAIMS COMPANION GUIDE

Standard Companion Guide

Blue Shield of California

It is recommended that separate transaction sets be used for different patients.

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

BLUE CROSS AND BLUE SHIELD OF LOUISIANA INSTITUTIONAL CLAIMS COMPANION GUIDE

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

Blue Cross and Blue Shield of Kansas BCBSKS Proprietary 834 Acknowledgment HIPAA X220A1Health Care Benefits Enrollment and Maintenance

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

834 Companion Document to the 5010 HIPAA Implementation Guide

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

Cabinet for Health and Family Services Department for Medicaid Services

276 Health Care Claim Status Request Educational Guide

Standard Companion Guide

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

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

837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE

HIPAA X 12 Transaction Standards

997 Functional Acknowledgment

Eligibility Gateway Companion Guide

HIPAA X 12 Transaction Standards

HIPAA Transaction Standard Companion Guide ASC X X212A1 Health Care Claim Status Request and Response (276/277)

PEBTF 999 Functional Acknowledgement PEBTF. 999 Functional Acknowledgement. Page 1 Printed 2/9/ :51 AM

West Virginia HMO Rosters Companion Guide 834

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

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

834 Benefit Enrollment and Maintenance

270/271 Benefit Eligibility Inquiry/Response Transactions Companion Guide ANSI ASC X12N 270/271 (Version 4010A)

Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837

997 Functional Acknowledgment

X Envelops. University Hospitals Health Systems University Hospitals of Cleveland ASNI X12 Envelops Version Functional Group ID=

Functional Acknowledgment - 997

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

Companion Guide Benefit Enrollment and Maintenance 834

837 Health Care Claim Professional, Institutional & Dental Companion Guide

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

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

Medicare-Medicaid Encounter Data System

Functional Acknowledgment

Standard Companion Guide

DoD Transportation Electronic Business (DTEB) Convention

Appendix A Vendor Specifications for. State of Idaho MMIS

990 Response to a Load Tender

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

ANSI X12 version Receiving Advice/ Acceptance Certificate

SHARES 837P Companion Guide

837 Dental Health Care Claim

990 Response to a Load Tender

834 Benefit Enrollment and Maintenance

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

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

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

ACKNOWLEDGMENTS BEST PRACTICE

HIPAA X 12 Transaction Standards

DSW Designer Shoe Warehouse

Anthem Blue Cross and Blue Shield. 834 Enrollment Companion Guide. For. CERIDIAN / COBRA Enrollment

835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

4. ENCOUNTER DATA PROCESSING PROCEDURES A. General Information

Attachment-F FSCJ Current System Technical Specifications

Texas Medicaid. HIPAA Transaction Standard Companion Guide

997 Functional Acknowledgment (Inbound)

Transcription:

HIPAA Transaction Standard EDI Companion Guide Benefit Enrollment and Maintenance (834) (Refers to the Implementation Guides based on ASC X12 005010X220A1)

2 Disclosure Statement: This Companion Guide has been prepared for Fidelis Care Trading partners who are willing to enroll for Benefit Enrollment and Maintenance (834) files. It is in conjunction with the ASC X12 5010 version of HIPAA Technical Report Type 3. This document is considered a living document and may be subject to change when required. It is NOT intended to provide information that exceeds or contradicts the requirements of the ASC X12 Electronic Data Interchange Transaction set defined by HIPAA. If there are any changes to this document, it will be incorporated and published as a newer version at fideliscare.org. The complete EDI guideline for each transaction is available at http://wpc-edi.com Preface: Fidelis Care can offer EDI 834 data for its trading partners who would like to receive and process electronically. This Companion Guide to the v5010 ASC X12N Implementation Guides, along with associated information adopted under HIPAA, clarifies and specifies the data content when exchanging electronically with Fidelis Care. Transmissions based on this Companion Guide, used in tandem with the v5010 ASC X12N Implementation Guides, are compliant with both ASC X12 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.

3 Table of Contents 1. Introduction... 5 Scope... 5 Overview... 5 References... 5 2. Getting Started... 6 Working with Fidelis Care... 6 Trading Partner Registration... 6 3. Testing with Fidelis Care... 6 4. Connectivity/Communications with Fidelis Care... 6 Process Flows... 6 Transmission Administrative Procedures... 7 Retransmission Procedure... 7 Communication Protocol Specifications... 7 System Maintenance... 7 5. Contact Information... 8 6. Control Segments/Envelopes... 8 ISA-IEA... 9 GS-GE... 9 ST-SE... 10 Delimiters... 10 7. Fidelis Care Specific Business Rules and Limitations... 10 8. Acknowledgments and Reports... 10 9. Trading Partner Agreements... 11 10. Transaction Specific Information... 11 APPENDICES... 12 1. Transmission Examples... 12

4 2. Frequently Asked Questions... 12 3. Change Summary... 12

5 1. Introduction Scope This Companion Guide has been prepared for Fidelis Care Trading partners who are interested in receiving Benefit Enrollment and Maintenance files (834) electronically. It provides necessary information about the transaction, connectivity details, contact information etc. that are useful. Overview The Health Insurance Portability and Accountability Act of 1996 (HIPAA) requires that all health insurance payers in United States comply with the EDI standards as established by the Secretary of Health and Human Services (HHS). This Companion Guide covers the following topics and more: Establish connection to send 834 files Data requirements Testing with Fidelis Care Control segment information Sample EDI 834 file References The complete 834 guide for ASC X12 005010X220A1 and other guides are available at http://www.wpc-edi.com For more information, please visit fideliscare.org or call the Provider Call Center at 1-888-FIDELIS (1-888-343-3547) 24 hours a day, 7 days a week.

6 2. Getting Started Working with Fidelis Care If you would like to work with Fidelis Care to receive Benefit Enrollment and Maintenance (834) file, please contact your Fidelis Care Representative or call 1.888.FIDELIS. Trading Partner Registration Trading partner setup is a must before exchanging any files. Fidelis Care will collect required information from trading partner upon contract and complete trading partner setup. Trading partners will be notified after successful registration to proceed with next steps. 3. Testing with Fidelis Care After the account has been setup, Fidelis Care will work on gathering data requirements and other details to begin testing. Remember, we need to have SFTP connection established to exchange files. Please refer next section for the details. Test file will be created, validated and shared with trading partners via SFTP. Trading partners are expected to validate the feed and acknowledge. This will ensure the files will be exchanged in production without any problems. If you find any issues during testing, Fidelis Care should be notified so file can be fixed and resent. If you have specific scenarios for their testing, we should be informed to prepare test files. 4. Connectivity/Communications with Fidelis Care Process Flows 834 files can be generated either daily or weekly. The frequency and time will be decided after working with trading partners and the feed will be scheduled as either Full file or incremental files. Here is the process flow:- Fidelis Care extracts the member and plan information based on criteria required for each trading partner The extract file goes through EDI mapping that creates X12 The X12 file will be validated and sent to trading partners via SFTP connection Trading partners get email notification stating the file is available If there are any issues with the file, Fidelis Care should be contacted with issues.

7 The following diagram explains this process. Transmission Administrative Procedures Fidelis Care transmits 834 files over SFTP connection. We generally push the files to trading partner s FTP site but can host the site as well. If Fidelis Care hosts, connections are available 24 hours a day, seven days a week except during the planned maintenance window. Please refer System Maintenance section for the details. If there are any unplanned maintenance, an email notification will be sent. Retransmission Procedure Retransmissions can be made on the following occasions: Connectivity failure If a trading partner requires the file to be resent If there are any issues in the file that needs to be corrected and resent Communication Protocol Specifications Fidelis Care uses SFTP to upload files. We will be contacting trading partners to obtain host name, user name and password to connect to their site and upload files. If folders are being used by trading partners, Fidelis Care would like to know the information for accurate uploading of files. System Maintenance Below is the Fidelis Care Maintenance Window schedule, which begins on Saturdays at 6 PM and ends on Sundays by 6 PM. All systems will be unavailable periodically over these scheduled weekends. If there are any changes, it will be communicated before the start of any scheduled maintenance window.

8 2018 Fidelis Care Maintenance Window Schedule: Month Planned Maintenance January 2018 Jan. 20 and 21 February 2018 Feb. 17 and 18 March 2018 March 17 and 18 April 2018 April 14 and 15 May 2018 May 19 and 20 June 2018 June 23 and 24 July 2018 July 14 and 15 August 2018 Aug. 18 and 19 September 2018 Sept. 15 and 16 October 2018 Oct. 13 and 14 November 2018 Nov. 17 and 18 December 2018 Dec. 15 and 16 5. Contact Information Phone Fidelis Care Provider Call Center, 1-888-FIDELIS (1-888-343-3547) 24 hours a day, 7 days a week. Trading partners can also contact their Fidelis Care Representative for any information. 6. Control Segments/Envelopes This topic gives information about the control segments and the values to use for each element. Interchange control number gets increment by one for each file. Transaction specific segments can be found in the 834 guidelines document and should be used with all mandatory/required values.

9 ISA-IEA Please refer to the below table to get the values for ISA-IEA segments. ISA01 00 or 03 Authorization Information Qualifier ISA02 SPACES Authorization Information. It can be blank ISA03 00 Security Information Qualifier ISA04 SPACES Security Information. It can be either zeroes or left blank ISA05 ZZ Interchange ID Qualifier ISA06 Fidelis Care ID Interchange Sender ID. Fidelis Care ID will be provided. ISA07 ZZ Interchange ID Qualifier ISA08 Partner ID Interchange Receiver ID. Collected from trading partners. ISA09 DATE Interchange Data. YYMMDD format ISA10 TIME Interchange Time. HHMM format ISA11 ^ Repetition Separator ISA12 00501 Interchange control version number ISA13 Control Number Interchange control number. It gets incremented for each file ISA14 0/1 Acknowledgement requested. 0 or 1 ISA15 T/P Usage Indicator. Test or Production ISA16 > Component Element Separator IEA01 1 Number of included Functional Groups IEA02 Control number Interchange control number that was sent in ISA segment GS-GE Below table refers for GE-GE segments. One ISA may contain more than one GS/GE loops. GS01 BE Functional Identifier Code GS02 Fidelis Care ID Application sender's ID GS03 Partner ID Application Receiver's ID GS04 Date DATE expressed in CCYYMMDD GS05 Time TIME expressed in HHMM or HHMMSS GS06 Control number Group control number GS07 Always 'X'. Responsible Agency code. Accredited Standards Committee. GS08 005010X220A1 Version Identifier code GE01 1 No of Transaction sets included GE02 Group control number Group control number

10 ST-SE Please refer to the below table to get the values for ST-SE segments. One ISA may contain more than one ST/SE loop. ST01 834 Transaction Set Identifier Code ST02 1 Transaction Set control number. Increased by 1 for each set ST03 005010X220A1 Implementation Convention Reference SE01 NNNNN Number of Included segments SE02 1 Transaction Set Control Number The 834 files are expected to follow the above standard and values for the ISA-IEA, GS-GE, and ST-SE control segment values. All the other standard EDI segments that are specific to the transaction should be used as per X12 ASC 5010 guide. Delimiters The following delimiters will be used in the 834 file. If trading partners have any other preference, we will consider them. Element Delimiter - * Composite Delimiter - > Terminator Delimiter - ~ 7. Fidelis Care Specific Business Rules and Limitations Fidelis Care will gather data requirements from trading partner to create EDI X12 file. This X12 file will contain all the required information. If there are any limitations, trading partners will be notified. Production files can be sent as either Full files or incremental files and it can be either daily or weekly. Test files will have T in ISA15 indicator whereas production files will have P. Fidelis Care has its own file naming convention that can be used for the 834 files. However, we can also follow trading partner s standard if there are any. This will be discussed during kick off and finalized. 8. Acknowledgments and Reports Fidelis Care does not require acknowledgment for the 834 files. However, if there are any issues, we expect trading partners to notify Fidelis Care.

9. Trading Partner Agreements 11 If a trading partner agreement is required, Fidelis Care will work with them and collect necessary documents during trading partner registration phase. 10. Transaction Specific Information The EDI 834 transaction is called as Benefit and Enrollment Maintenance transaction set. It is a standard format for exchanging healthcare member plan data between employers and healthcare insurance sponsors electronically. It is commonly used for new enrollments, changes to existing enrollments or termination of a plan. It contains, subscriber details, plan information, eligibility start/end date, etc. Member level details will be present in INS segment. INS*Y*18*024**A***FT~ INS03 codes specifies the type of action: 001 for change, 021 for addition, 024 for termination, 025 for Reinstatement and 030 for Audit or compare REF segments are used to provider Subscriber number, policy number, client number etc. NM1*IL segment will contain Subscriber information along with ID. NM1*IL*1*JONES*JOE*M***34*011444000~ Health coverage dates, i.e. Benefit begin and end dates are available in DTP segment. DTP*348*D8*20170601~ [348 Begin Date] DTP*349*D8*20170731~ [349 End Date] Fidelis Care elects to send all members with a subscriber Indicator = Y. i.e. INS01 = Y. INS*Y*18*024**A***FT~ For more details about each segment, please refer to TR3 guide at http://www.wpc-edi.com/.

12 APPENDICES 1. Transmission Examples Sample Data for 834 ISA*00* *00* *ZZ*FIDELIS *ZZ*RECEIVER *170524*0520*^*00501*111223344*1*T*>~ GS*BE*FIDELIS*RECEIVER*20170524*052035*1234*X*005010X220A1~ ST*834*0001*005010X220A1~ BGN*00*UP-00001*20170524*0520*ES***2~ N1*P5*FIDELIS CARE NEW YORK*FI*111222333~ N1*IN*TEST*FI*987654321~ INS*Y*18*024**A***FT~ REF*0F*333449876~ REF*1L*654987123~ REF*23*v12345F~ REF*17*N~ REF*ZZ*PLAN0000~ DTP*356*D8*20170601~ NM1*IL*1*LAST*FIRST****34*000111111~ PER*IP**TE*7165550100~ N3*MY STREET~ N4*BUFFALO*NY*00123~ DMG*D8*18110101*M~ HD*024**VIS**IND~ DTP*348*D8*20170601~ DTP*349*D8*20170601~ SE*20*0001~ GE*1*1234~ IEA*1*111223344~ 2. Frequently Asked Questions To be updated 3. Change Summary The below table refers to the version and changes made to this document. Date Version Description Author 05/30/2017 1.0 Initial version HIPAA EDI Team 12/29/2017 1.1 2018 Maintenance window updates HIPAA EDI Team