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

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

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

Medical Associates Health Plans and Health Choices

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

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

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

837 Dental Health Care Claim

BLUE CROSS AND BLUE SHIELD OF LOUISIANA PROFESSIONAL CLAIMS COMPANION GUIDE

997 Functional Acknowledgment (Inbound)

USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270

BLUE CROSS AND BLUE SHIELD OF LOUISIANA INSTITUTIONAL CLAIMS COMPANION GUIDE

Assurant Health HIPAA Transaction Standard Companion Guide

Florida Blue Health Plan

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

837 Health Care Claim Companion Guide. Professional and Institutional

Integration Guide for Data Originators of Claim Status. Version 1.1

West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270

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

Florida Blue Health Plan

276 Health Care Claim Status Request Educational Guide

SHARES 837P Companion Guide

270/ /271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time. Basic Instructions. Companion Document

Partnership HealthPlan of California

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

Cabinet for Health and Family Services Department for Medicaid Services

Standard Companion Guide

Alameda Alliance for Health

837 Professional Health Care Claim

270/ /271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time. Basic Instructions. Companion Document

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

837 Health Care Claim Professional, Institutional & Dental Companion Guide

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

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

997 Functional Acknowledgment

837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE

270/ /271 Health Care Eligibility, Coverage, or Benefit Inquiry 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

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

HIPAA X 12 Transaction Standards

X A1 ADDENDA COMPANION DOCUMENT PROFESSIONAL (004010X098A1)

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

HIPAA X 12 Transaction Standards

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

834 Companion Document to the 5010 HIPAA Implementation Guide

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

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

Inland Empire Health Plan

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

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

Administrative Services of Kansas (ASK)

Electronic Transaction Manual for Arkansas Blue Cross Blue Shield

VERSION FUNCTIONAL ACKNOWLEDGEMENT 1 OF 10

Health Care Claims: Status Request and Response (Version 1.12 January 2007)

997 - Functional Acknowledgment. Caterpillar Inc.

Anthem Blue Cross and Blue Shield. 834 Companion Guide

ASC X12N 270/271 (004010X092A1) Health Care Eligibility Benefit Inquiry and Response Companion Guide

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

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

DSW Designer Shoe Warehouse

835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1

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

ASC X X220A1)

DentaQuest HIPAA Transaction Standard Companion Guide

X A1 ADDENDA COMPANION DOCUMENT INSTITUTIONAL (004010X096A1)

855 Purchase Order Acknowledgment

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

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

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

HIPAA Transaction 278 Request for Review and Response Standard Companion Guide

ADOBE Inbound 997 ANSI X Version: 1.0

990 Response to a Load Tender

EDI Functional Acknowledgment

834 Benefit Enrollment and Maintenance

Standard Companion Guide

COMMONWEALTH CARE ALLIANCE CCA COMPANION GUIDE

X A1 Addenda Companion Document - Professional (004010X098A1) - EFFECTIVE 05/23/07

Functional Acknowledgment - 997

Blue Shield of California

Functional Acknowledgment

X A1 Addenda Companion Document - Institutional (004010X096A1) - EFFECTIVE 05/23/07

Optum/Care Improvement Plus Healthcare Claim: 837 Companion Guide. Versions: X222A X223A2

278 Health Care Service Review and Response

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

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

Sanford Health Plan. HIPAA Transaction Standard Companion Guide. Refers to the Technical Report Type 3 (TR3) Implementation Guides

Ver 2 Rel 2 Envelope Segments -

Eligibility Gateway Companion Guide

Functional Acknowledgment - 997

990 Response to a Load Tender

270/271 Companion Document ASC X12N. Health Care Eligibility and Benefit Inquiry and Response Version 4010A1 Addenda October 2002

990 Response to a Load Tender

997 Functional Acknowledgment

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

EMBLEMHEALTH HIPAA Transaction Standard Companion Guide

BlueCross BlueShield of VT. Vermont

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

Customer EDI Guidelines 997 Functional Acknowledgment

997 Functional Acknowledgement X12 Version 4010

832 Price Sales Catalog

Transcription:

ASC X12N 270/271 (004010X092A1) Health Care Eligibility Benefit Inquiry and Response Companion Guide Notes The ISA segment terminator, which immediately follows the component element separator, must consist of only one character code. This same character code must be used as the segment terminator for each segment in the ISA-IEA segment set. It is recommended not to exceed 99 patient requests per Information Receiver Loop (2000B). The following data elements are required: Loop 2100A NM101 should be PR NM102 should be 2 NM108 should be PI NM109 should be 00390 (Institutional) or 00890 (Professional) Include at least one TRN segment in either the subscriber or dependent loop (2000C, 2000D respectively). Include at least one EQ segment in either the subscriber or dependent loop (2110C, 2110D respectively). Any Service Type Code submitted in the EQ01 segment that is not listed as accepted will be converted to a 30 type for processing. If the patient is the subscriber, the following data elements are required: Loop 2100C Patient Last Name (NM103) Patient First Name (NM104) Patient Member ID (NM109, with NM108 = MI ) Patient Date of Birth (DMG02) Patient Gender (DMG03) If the patient is NOT the subscriber, the following data elements are required: Loop 2100C Subscriber's Member ID (NM109, with NM108 = MI ) Loop 2100D Patient Last Name (NM103) Patient First Name (NM104) Patient Date of Birth (DMG02) Patient Gender (DMG03) Rev. 12/14/2006 1

The more information provided in your request, the more accurate the response will be. If a 270 transaction with multiple inquiries is submitted, multiple 271 response transactions will be generated and distributed. It is also possible the 271 transaction may take up to 48 hours to be generated and distributed. We strongly recommend the use of upper case alpha-characters. This will ensure data lookup compatibility. Rev. 12/14/2006 2

ISA and GS Data Elements Definitions for Trading Partners 270: Health Care Eligibility Benefit Inquiry (004010X092A1) Outbound for Submitters ISA01 Authorization Information Qualifier always 00 ISA02 Authorization Information always spaces ISA03 Security Information Qualifier always 00 ISA04 Security Information always spaces ISA05 Interchange ID Qualifier (Sender) usually ZZ must match Trading Partner (TP) ISA06 Interchange Sender ID must match TP (usually Tax ID) ISA07 Interchange ID Qualifier (Receiver) ZZ must match TP ISA08 Interchange Receiver ID 00390 must match TP ISA09 Interchange Date YYMMDD provided by your software ISA10 Interchange Time HHMM provided by your software ISA11 Interchange Control Standards Identifier U ISA12 Interchange Control Version Number 00401 ISA13 Interchange Control Number assigned by your software (usually sequential integer) ISA14 Acknowledgement Requested 1 ISA15 Usage Indicator T Test (Certification) or P Production after BlueCross BlueShield of Tennessee approval ISA16 Component Element Separator (delimits components within a data element) provided by your software GS01 Functional Identifier Code HS (for 270 transactions) GS02 Application Sender s Code must match TP (usually Tax ID) GS03 Application Receiver s Code 00390 must match TP GS04 Date CCYYMMDD provided by your software GS05 Time HHMM provided by your software GS06 Group Control Number assigned by your software (usually sequential integer) GS07 Responsible Agency Code X GS08 Version/Release/Industry Identifier Code 004010X092A1 must match TP Rev. 12/14/2006 3

ISA and GS Data Element Definitions for Trading Partners 271: Health Care Eligibility Benefits Response (004010X092A1) Inbound for Submitters ISA01 Authorization Information Qualifier always 00 ISA02 Authorization Information always spaces ISA03 Security Information Qualifier always 00 ISA04 Security Information always spaces ISA05 Interchange ID Qualifier (Sender) ZZ ISA06 Interchange Sender ID 00390 ISA07 Interchange ID Qualifier (Receiver) will match Trading Partner (TP) ISA08 Interchange Receiver ID will match TP (usually Tax ID) ISA09 Interchange Date YYMMDD date processed ISA10 Interchange Time HHMM time processed ISA11 Interchange Control Standards Identifier U ISA12 Interchange Control Version Number 00401 ISA13 Interchange Control Number from TP record based on TP internal ID ISA14 Acknowledgement Requested 0 on 997 acknowledgements ISA15 Usage Indicator T Test (Certification) or P Production after BlueCross BlueShield of Tennessee approval ISA16 Component Element Separator provided by your software GS01 Functional Identifier Code HB (for 271 transactions) GS02 Application Sender s Code 00390 (Sender) will match TP GS03 Application Receiver s Code will match TP (usually Tax ID) GS04 Date CCYYMMDD date processed GS05 Time HHMM - time processed GS06 Group Control Number assigned number (usually sequential integer) GS07 Responsible Agency Code X GS08 Version/Release/Industry Identifier Code 004010X092A1 will match TP Rev. 12/14/2006 4

997 FUNCTIONAL ACKNOWLEDGEMENT 270: Health Care Eligibility Benefit Inquiry (004010X092A1) A 997 Functional Acknowledgement is generated for every complete incoming transaction received. The 997 transaction validates the compliancy of the transaction received, and identifies any issues that need to be corrected within the file. This acknowledgement will be distributed to the client s mailbox within two hours after receipt of a successful transaction. Below is an example of a 997. We will be using delimiters as defined in the ISA segment to separate elements, components and segments. The element separator will be found immediately following the Interchange Control Header. The component element separator will be found in the ISA16 segment, and the segment terminator will be found at the end of the ISA segment. Please refer to the HIPAA Implementation Guide for documentation on how to read this transaction. You may download this guide from the following Web site: http://www.wpc-edi.com/hipaa/. ISA*00* *00* *ZZ*SENDER ID *ZZ*RECEIVER ID *060719*1113*U*00401*000000173*0*P*> GS*FA*SENDER ID*RECEIVER ID*20060719*111307*173*X*004010 ST*997*173001 AK1*HS*100000001 AK2*270*200000001 AK5*A AK9*A*1*1*1 SE*6*173001 GE*1*173 IEA*1*000000173 Rev. 12/14/2006 5