Eligibility Web Service Companion Guide 2010 Gateway EDI, LLC. Last Updated: 10/30-/2014 5:40:00 PM - 1 - Confi de nti al An d Propri e t ar y: This document, or any information contained herein, may not be duplicated, published, or disclosed by any means without prior permission of Gateway EDI, LLC.
Web Services Revision History Date Revision Author 1/1/2007 1.0 Initial Version 1/22/2010 1.1 Updated template Malvin Ly 2/25/2010 1.2 Updated payer specific fields Malvin Ly 4/19/2010 1.3 Updated date format, removed century. Malvin Ly 10/25/2010 1.4 Removed payer specific information. Malvin Ly 12/28/2010 1.5 Removed SSN requirement Malvin Ly 9/23/2011 1.6 Removed subscriber ID and provider ID requirements 12/12/2011 1.7 Added Provider Name as required field and removed Dependent Relationship Code from required fields 1/23/2012 1.8 Removed gender, date of birth and name from required fields, as applicable Malvin Ly Danielle Montgomery Danielle Montgomery 10/30/14 1.9 Added HCPCS Code Shikha Chauhan Confi de nti al An d Propri e t ar y: This document, or any information contained herein, may not be duplicated, published, or disclosed by any means without prior permission of Gateway EDI, Inc. 2
Table of Contents 1. INTRODUCTION...4 1.1. PURPOSE OF THIS GUIDE...4 1.2. DESCRIPTION...4 1.3. RESTRICTIONS...4 2. PARAMETERS...5 2.1. LIST OF REQUIRED ELIGIBILITY PARAMETERS...5 2.1.1. Information Source Details...5 2.1.2. Information Receiver Details...5 2.1.3. Subscriber Details...5 2.1.4. Dependent Details...6 3. ADDITIONAL INFORMATION...7 3.1. DOCUMENTATION...7 Confi de nti al An d Propri e t ar y: This document, or any information contained herein, may not be duplicated, published, or disclosed by any means without prior permission of Gateway EDI, Inc. 3
1. Introduction 1.1. Purpose of this guide The intent of this technical reference document is to provide a place to capture technical details about the Gateway EDI payer list web service. This manual provides an overview for different programming interfaces and classes that allow IT staff and programmers, who are developing external clients, to connect to Gateway EDI. 1.2. The Gateway EDI eligibility web service allows providers with registered with Gateway EDI to make realtime eligibility transactions from their practice management system, bypassing the need to log into the Gateway EDI website. 1.3. Restrictions For real-time transactions, it is required that the 270 transaction contain only one patient request. One patient is defined as either one subscriber loop if the member is the patient or one dependent loop if the dependent is the patient.
2.1. List of Required Eligibility Parameters This list of parameters are required fields for all eligibility transactions send to the Gateway EDI eligibility web service, except as otherwise noted. 2.1.1. Information Source Details: 1 GediPayerID The GEDI specific payer identifier 2.1.2. Information Receiver Details: 1 ProviderFirstName Provider First Name Required when individual provider name is sent in the inquiry 2 ProviderLastName Provider Last Name/Organization Name 3 NPI National Provider Identifier 2.1.3. Subscriber Details: 1 InsuredFirstName Subscriber First Name subscriber or if the Payer requires this information to identify the patient. 2 InsuredLastName Subscriber Last Name subscriber or if the Payer requires this information to identify the patient. 3 InsuranceNum Required when the payer needs this information to identify patient. 4 InsuredDob Subscriber Date of birth (YYYYMMDD) subscriber.
5 InsuredGender Subscriber Gender subscriber. 6 Insured HCPCS Codes Health Care Financing Administration Common Procedural Coding System Codes subscriber and provider believes payer supports this functionality and Service Type Codes is not passed in the request. 2.1.4. Dependent Details: 1 DependentFirstName Dependent First Name 2 DependentLastName Dependent Last Name 3 DependentDob Dependent Date of birth (YYYYMMDD) 4 DependentGender Dependent Gender 5 Dependent HCPCS Codes Health Care Financing Administration Common Procedural Coding System Codes dependent and provider believes payer supports this functionality and Service Type Codes is not passed in the request.
3.1. Documentation EligibilityWebServiceSample.zip Realtime Eligibility Webservice Vendor Toolkit.pdf Payer Specific Data Elements 2010.pdf