Geisinger Health Plan



Similar documents
Geisinger Health Plan

Geisinger Health Plan

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

820 Payroll Deducted and Other Group Premium Payment for Insurance Products

HIPAA EDI Companion Guide For 270/271 Eligibility Inquiry & Response Companion Guide Version: 3.0

Claim Status Request and Response Transaction Companion Guide

835 Health Care Payment/ Remittance Advice Companion Guide

Health Care Claim: Dental (837)

835 Claim Payment/Advice

Electronic Transaction Manual for Arkansas Blue Cross and Blue Shield FEDERAL EMPLOYEE PROGRAM (FEP) Dental Claims

Combined Insurance Company of America

HIPAA Compliance Tools: ANSI ASC X12N HIPAA Implementation Guides

XEROX EDI GATEWAY, INC.

ANSI X12 version Remittance Advice

Health Plan of San Joaquin

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

How To Use An Electronic Data Exchange (Edi)

National Electronic Data Interchange Transaction Set Companion Guide Health Care Claims Institutional & Professional 837 ASC X12N 837 (004010X096)

835 Dental Health Care Claim Payment / Advice. Section 1 835D DentalHealth Care Claim Payment / Advice: Basic Instructions

Blue Cross and Blue Shield of Texas (BCBSTX)

DEPARTMENT OF HEALTH & MENTAL HYGIENE MEDICAL CARE PROGRAM

835 Health Care Claim Payment / Advice

835 Transaction Companion Guide Healthcare Claim Payment/Advice. Version X91A1 (Addendum)

HIPAA X 12 Transaction Standards

HIPAA TRANSACTION 837 INSTITUTIONAL STANDARD COMPANION GUIDE

How To Write A Health Care Exchange Transaction

UPMC HEALTH PLAN. HIPAA EDI Companion Guide

Sanford Health Plan. Electronic Remittance Advice 835 Transaction Companion Guide Trading Partner Information

810 Invoice ANSI ASC X12 Version 4010

278 HEALTH CARE SERVICES REVIEW REQUEST AND RESPONSE COMPANION GUIDE

Alameda Alliance for Health

835 Health Care Claim Payment / Advice

Arkansas Blue Cross Blue Shield EDI Report User Guide. May 15, 2013

Florida Blue Health Plan

997 Functional Acknowledgment

276/277 HIPAA Transaction Companion Guide HIPAA/V005010X212 VERSION: 1.0 DATE: 02/05/2014

EDI Acknowledgement Transactions 1.1 Strategy for Oregon Trading Partners

HIPAA Glossary of Terms

Purpose of the 270/271 Health Care Eligibility Benefit Inquiry and Response

ANSI X12 version Text Message

Indiana Health Coverage Programs

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

837 Health Care Claim: Institutional Companion Guide. HIPAA version 5010

HIPAA 835 Companion Document

Florida Blue Health Plan

837 Health Care Claim Companion Guide Professional and Institutional. Version 1.14 November 24, 2010

BLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE

Centers for Medicare & Medicaid Services (CMS)

CoreSource, Inc. HIPAA Transaction Electronic Data Interchange (EDI) Implementation Guide. For Health Care Providers

California Division of Workers Compensation Electronic Medical Billing and Payment Companion Guide

WPS Health Solutions

837P Health Care Claim Professional

HP SYSTEMS UNIT. Companion Guide: Electronic Data Interchange Reports and Acknowledgements

Horizon Blue Cross and Blue Shield of New Jersey

835 Health Care Remittance Advice

837I Health Care Claims Institutional

820 ANSI X12 Version

Administrative Services of Kansas

Xerox EDI Direct Claims Gateway Communication Document for ASC X12N 837 Health Care Claim Transaction Submission

Standard Companion Guide Version Number: 0.1

835 Health Care Claim Payment/Advice Companion Guide

GEORGIA MEDICAL BILLING AND REIMBURSEMENT FOR WORKERS COMPENSATION

HIPAA Transactions and Code Set Standards As of January Frequently Asked Questions

Key Highlights of the Final Rule

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

Early Intervention Louisiana Early Steps Louisiana Early Steps HIPAA Testing Plan

824 Application Advice

IAIABC Workers Compensation Electronic Billing and Payment National Companion Guide

Oregon Workers Compensation Division Electronic Billing and Payment Companion Guide. Release 1.0 January 1, 2015

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

Subject: Changes for the 834 Benefit Enrollment and Maintenance Companion Document

Introduction. Companion Guide to X12 Transactions version 5010

837 Professional Health Care Claim

Georgia State Board of Workers Compensation Electronic Billing and Payment National Companion Guide (Based on ASC X and NCPDP D.

ANSI X12 version Planning Schedule with Release Capability

FMH Benefit Services, Inc.

Georgia Department of Community Health (DCH) HIPAA Transaction Standard Companion Guide

CMS. Standard Companion Guide Transaction Information

Communications and Connectivity

MOLINA MEDICAID SOLUTIONS. Louisiana Medicaid 835 Health Care Claim/Payment Advice Companion Guide. Based on ASC X12N Version X221A1

How To Use Ansi X12N For A Business

837 I Health Care Claim Institutional

HIPAA Transaction Standard Companion Guide 834 Eligibility Enrollment and Maintenance

835 Health Care Claim Payment/Advice Functional Group=HP

AmeriHealth Administrators

AmeriHealth (Pennsylvania Only)

HIPAA X 12 Transaction Standards

Clearinghouse Screen Instructions for ANSI837

Detail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header

BlueCross BlueShield of Tennessee Electronic Provider Profile

837 Professional EDI Specifications & Companion Guide

EFT and ERA Enrollment Process White Paper

DY574_261023_br. OMPP MMIS HIPAA 5010 /Edifecs Project. Overview

HIPAA - ASC X12N Outbound EDI 835 Electronic Remittance Advice Transaction

APEX BENEFITS SERVICES COMPANION GUIDE 837 Institutional Health Care Claims. HIPAA Transaction Companion Guide 837 Institutional Health Care Claim

Transcription:

Geisinger Health Plan Companion Guide for the 820 Payroll Deducted and Other Group Premium Payment for Insurance Products Refers to the Implementation Guides Based on X12 version 004010A1 Version Number: 1.05 Revised October 25, 2005 1

Preface This is a Companion Guide to the ASC X12N Implementation Guides adopted under the Health Insurance Portability and Accountability Act (HIPAA). It should be used when interacting with Geisinger Health Plan (GHP). This document describes the data element requirements of GHP s trading partners for submission of EDI HIPAA compliant transactions. This guide is not meant to replace HIPAA s Implementation Guides but should be used in conjunction with them. Disclosure Statement Geisinger Health Plan and Geisinger Indemnity Insurance Company are affiliates of Geisinger Health System Foundation. Geisinger Health Plan and Geisinger Indemnity Insurance Company shall be collectively referred to as Health Plan. All pages within this document are the property of Health Plan and/or its subsidiaries and affiliates. The content of this document was specifically prepared for use by the trading partner affiliates of GHP only. 2003 Geisinger Health Plan. All rights reserved. The specific trading partner of GHP may copy this document only for internal use. 2

Table of Contents 1. Introduction...4 1.1 Scope...4 1.2 Overview...4 1.3 References...4 2. Certification and Testing Overview...5 3. Connectivity / Communications...6 4. Contact information...6 4.1 Health Plan EDI Technical Contact...6 4.2 Available Websites...6 5. Requirements, Payer Specific Business Rules and Limitations...7 5.1 Minimum and Maximum Requirements...7 5.2 Headers...8 5.3 Detail...9 6. Acknowledgements and or Reports...11 6.1 Report Inventory...11 Appendix...12 Summary of Changes...12 3

1. Introduction In an effort to reduce the administrative costs of health care across the nation, the Health Insurance Portability and Accountability Act (HIPAA) was passed in 1996. This legislation requires that health insurance payers in the United States comply with the electronic data interchange (EDI) standards for health care, established by the Secretary of Health and Human Services (HHS). For the health care industry to achieve the potential administrative cost savings with EDI, standard transactions and code sets have been developed and need to be implemented consistently by all organizations involved in the electronic exchange of data. The ANSI ASCX12N820 Payroll Deducted and Other Premium Payment for Insurance Products implementation guides provide the standardized data requirements to be implemented for all 820 submissions. HIPAA does not require that a group submit premium remittance information electronically. Groups may continue to submit remittance information on paper. However, if the group elects to conduct business electronically, HIPAA does mandate the use of the standard transactions and code sets. 1.1 Scope This Companion Guide explains the procedures necessary for trading partners of the Health Plan to transmit Electronic Data Interchange (EDI) for the 820 Payroll Deducted and Other Premium Payment for Insurance Products transaction. This Companion Guide is not intended to replace, contradict or exceed the X12N Implementation Guides; rather it is intended to be used in conjunction with them. 1.2 Overview The first part of this Companion Guide explains its purpose and the trading partner s role working with the Health Plan. It also provides important information on the communication process and detailed Health Plan contact information. 1.3 References This Companion Guide should be used in conjunction with the Implementation Guides, which can be obtained from the Washington Publishing Company by calling 1-800-972-4334 or are available for download on their web site at www.wpc-edi.com/hipaa/. Other important websites: Workgroup for Electronic Data Interchange (WEDI) http://www.wedi.org United States Department of Health and Human Services (DHHS) http://aspe.hhs.gov/admnsimp/ Centers for Medicare and Medicaid Services (CMS) http://www.cms.gov/hipaa/hipaa2/ Designated Standard Maintenance Organizations (DSMO) http://www.hipaa-dsmo.org/ National Council of Prescription Drug Programs (NCPDP) http://www.ncpdp.org/ National Uniform Billing Committee (NUBC) http://www.nubc.org/ Accredited Standards Committee (ASC X12) http://www.x12.org/ 4

2. Certification and Testing Overview The Workgroup for Electronic Data Interchange (WEDI) and the Strategic National Implementation Process (SNIP) have recommended seven types of HIPAA compliance testing, these are: 1. Integrity Testing This is testing the basic syntax and integrity of the EDI transmission to include: valid segments, segment order, element attributes, numeric values in numeric data elements, X12 syntax and compliance with X12 rules. 2. Requirement Testing This is testing for HIPAA Implementation Guide specific syntax such as repeat counts, qualifiers, codes, elements and segments. Also testing for required or intra-segment situational data elements and non-medical code sets whose values are noted in the guide via a code list or table. 3. Balance Testing This is testing the transaction for balanced totals, financial balancing of claims or remittance advice and balancing of summary fields. 4. Situational Testing This is testing of inter-segment situations and validation of situational fields based on rules in the Implementation Guide. 5. External Code Set Testing This is testing of external code sets and tables specified within the Implementation Guide. This testing not only validates the code value but also verifies that the usage is appropriate for the particular transaction. 6. Product Type or Line of Service Testing This is testing that the segments and elements required for certain health care services are present and formatted correctly. This type of testing only applies to a trading partner candidate that conducts the specific line of business or product type. 7. Implementation Guide-Specific Trading Partners Testing This is testing of HIPAA requirements that pertain to specific trading partners such as Medicare, Medicaid and Indian Health. Compliance testing with these payer specific requirements is not required from all trading partners. If the trading partner intends to exchange transactions with one of these special payers, this type of testing is required. The WEDI/SNIP white paper on Transaction Compliance and Certification and other white papers are found at http://www.wedi.org/snip/public/articles/index%7e12.htm. 5

3. Connectivity / Communications The Health Plan has a communication server with secure Internet access for transmitting and receiving EDI transactions. Please contact our EDI Technical Contact listed in Section 4 for the account set up and software requirements. 4. Contact information 4.1 Health Plan EDI Technical Contact If you have any questions or need additional EDI information, please contact the Health Plan s Information Technology Department at the following: Contact Name: EDI Technical Contact 100 N. Academy Avenue Danville, PA, 17822-8005 Telephone: 570-271-5633 Fax: 570-271-5162 Email Address: editechnical@thehealthplan.com Weekdays 8:00am 5:00pm. 4.2 Available Websites For on-line EDI information, including the Health Plan s companion guides, access www.thehealthplan.com. 6

5. Requirements, Payer Specific Business Rules and Limitations 5.1 Minimum and Maximum Requirements The level of information sent affects the structure of the 820 transaction. The 820 transaction consists of 3 tables: the Headers the Detail, and the Trailers Headers Table 1 (Header) contains information related to the total payment. Detail Table 2 (Detail) can contain one of two data structures. The Health Plan has chosen to require the use of the Individual Remittance approach section 2.2.2.2 of the Implementation Guide for those employer groups who are Self-billed or for those who received a bill, but are paying a premium amount that is different from the amount on their bill. Only those employer groups who are paying exactly the amount billed will use the Organization Summary Remittance approach section 2.2.2.1 of the Implementation Guide. Trailers Table 3 (Trailer) contains only the SE segment. This segment indicates the end of the transaction set and provides a count of the transmitted segments in the 820 transaction. Notes 1. The Health Plan will not post the payment until the funds are received. 7

5.2 Headers ISA Interchange Control Header Loop: N/A To start and identify an interchange of zero or more functional groups and interchange-related control segments ISA05 I05 Interchange ID Qualifier M ID 2/2 Code Name ZZ Mutually Defined ISA06 I06 Interchange Sender ID M AN 15/15 ISA07 I07 Interchange ID Qualifier M ID 2/2 Code Name 30 U. S. Federal Tax Identification Number ISA08 I08 Interchange Receiver ID M AN 15/15 The Health Plan prefers the Interchange Control Header required data elements to be formatted in the ISA segment as follows: ISA05 is set to ZZ (Mutually Defined) ISA06 is set to mutually agreed upon sender identification number ISA07 is set to 30 (U.S. Federal Tax Identification Number) ISA08 is set to the Health Plan s U.S. Federal Tax Identification Number of 23-2311553 GS Functional Group Header Loop: N/A To indicate the beginning of a functional group and to provide control information. GS03 124 Application Receiver s Code M AN 2/15 The Health Plan prefers the Functional Group Header required data elements to be formatted in the GS segment as follows: GS03 is set to the Health Plan s U.S. Federal Tax Identification Number of 23-2311553 8

DTM Coverage Period Loop: N/A To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail DTM05 1250 Date Time Period Format Qualifier X ID 2/3 DTM06 1251 Date Time Period X AN 1/35 N1 Premium Payer's Name Loop: 1000A To identify a party by type of organization, name, and code N103 66 Identification Code Qualifier C ID 1/2 Code Name 65 National Employer Identification N104 67 Identification Code M AN 15/15 The Health Plan prefers the Premium Payer s Name data elements to be formatted in the N1 segment as follows: N103 is set to 65 (National Employer Identification) N104 is set to your National Employer Identification number (should be the same as your IRS tax ID) Note : The use of this code becomes mandatory on 07/30/04 5.3 Detail SLN Member Count Loop: 2315A To specify product subline detail item data 9

SLN04 380 Quantity X R 1/15 SLN05 C001 Composite Unit of Measure C Comp 355 Unit or Basis for Measurement Code M ID 2/2 Code Name 10 Group IE Person PR Pair The Health Plan prefers the Member Count data elements to be formatted in the SLN segment as follows: SLN04 is sent once for each code below SLN05 is set to 10 - Represents the number of contract holders not included in IE and PR SLN05 is set to IE - Represents the number of contract holders with Individual coverage SLN05 is set to PR - Represents the number of contract holders with Self and Spouse Only coverage ENT Individual Remittance Loop: 2000B To designate the entities which are parties to a transaction and specify a reference meaningful to those entities ENT03 66 Identification Code Qualifier X ID 1/2 Code Name 34 Social Security Number ENT04 67 Identification Code X AN 2/80 NM1 Individual Name Loop: 2100B To supply the full name of an individual or organizational entity NM103 1035 Name Last O AN 1/35 NM104 1036 Name First O AN 1/25 NM105 1037 Name Middle O AN 1/25 NM106 1038 Name Prefix O AN 1/10 NM107 1039 Name Suffix O AN 1/10 RMR Individual Premium Remittance Detail Loop: 2300B To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail 10

RMR04 782 Monetary Amount O R 1/18 DTM Individual Coverage Period Loop: 2300B To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail DTM05 1250 Date Time Period Format Qualifier X ID 2/3 DTM06 1251 Date Time Period X AN 1/35 6. Acknowledgements and or Reports 6.1 Report Inventory The Health Plan supports the following response transactions and acknowledgements to the 820 Payroll Deducted and Other Premium Payment for Insurance Products Transaction: 997 Functional Acknowledgement Proprietary Detailed Error Reporting 11

Appendix Summary of Changes Date of Change: 08/13/2003 Initial Publication 05/04/2004 Version 1.01 Revised Section 6.2 Added GS, Functional Group Header 05/07/2004 Version 1.02 Revised Section 6.2 Revised IS loop and N1 loop 05/13/2004 Version 1.03 Revised Section 7.1 added proprietary report statement 06/08/2004 Version 1.04 Revised Section 6.1 removed note on coverage level 10/25/2005 Version 1.05 Removed Section 3 This Section had information pertaining to the use of a Web based validation tool. 12