USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270

Similar documents
West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270

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

Medical Associates Health Plans and Health Choices

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

DentaQuest HIPAA Transaction Standard Companion Guide

Assurant Health HIPAA Transaction Standard Companion Guide

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

Standard Companion Guide

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

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

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

Alameda Alliance for Health

Standard Companion Guide

837 Health Care Claim Companion Guide. Professional and Institutional

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

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

COMMONWEALTH CARE ALLIANCE CCA COMPANION GUIDE

Administrative Services of Kansas (ASK)

Eligibility Gateway Companion Guide

Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837

EMBLEMHEALTH HIPAA Transaction Standard Companion Guide

Cabinet for Health and Family Services Department for Medicaid Services

Standard Companion Guide

SHARES 837P Companion Guide

ASC X X220A1)

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

Integration Guide for Data Originators of Claim Status. Version 1.1

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

Inland Empire Health Plan

Partnership HealthPlan of California

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

Administrative Services of Kansas (ASK)

Sanford Health Plan HIPAA Transaction Standard Companion Guide

Indiana Health Coverage Programs

Blue Cross Blue Shield of Louisiana

Florida Blue Health Plan

HIPAA Transaction 278 Request for Review and Response Standard Companion Guide

276 Health Care Claim Status Request Educational Guide

Florida Blue Health Plan

834 Companion Document to the 5010 HIPAA Implementation Guide

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

837 Health Care Claim Professional, Institutional & Dental Companion Guide

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

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

98 - Professional (Physician) Visit - Office

MassHealth. Health Care Eligibility/Benefit Inquiry and Information Response (270/271) Standard Companion Guide

BLUE CROSS AND BLUE SHIELD OF LOUISIANA INSTITUTIONAL CLAIMS COMPANION GUIDE

BLUE CROSS AND BLUE SHIELD OF LOUISIANA PROFESSIONAL CLAIMS COMPANION GUIDE

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

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

EMBLEMHEALTH. HIPAA Transaction Standard Companion Guide

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

Standard Companion Guide

837 Dental Health Care Claim

Electronic Transaction Manual for Arkansas Blue Cross Blue Shield

Texas Medicaid. HIPAA Transaction Standard Companion Guide

835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1

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

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

Anthem Blue Cross and Blue Shield. 834 Companion Guide

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

Blue Cross Blue Shield of Delaware

Pennsylvania PROMISe Companion Guide

271 Health Care Eligibility Benefit Inquiry Response Educational Guide

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

837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE

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

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

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

Standard Companion Guide

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

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

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

X A1 ADDENDA COMPANION DOCUMENT PROFESSIONAL (004010X098A1)

MOLINA MEDICAID SOLUTIONS

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

Standard Companion Guide

Blue Shield of California

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

Unsolicited 277 Trading Partner Specification

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

ANSI ASC X12N 277 Claims Acknowledgement (277CA)

Horizon Blue Cross and Blue Shield of New Jersey

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

Standard Companion Guide

837 Professional Health Care Claim

834 Benefit Enrollment and Maintenance

Appendix A Vendor Specifications for. State of Idaho MMIS

Specialty Benefits Dental. Standard Companion Guide

HIPAA X 12 Transaction Standards

HIPAA X 12 Transaction Standards

EDS SYSTEMS UNIT. Companion Guide: 837 Dental Claims Transaction

HIPAA X 12 Transaction Standards

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.

Indiana Health Coverage Programs

MOLINA MEDICAID SOLUTIONS. Louisiana Medicaid 837 Health Care Claim-Institutional Companion Guide. Based on ASC X12N Version X223A2

Medicare-Medicaid Encounter Data System

Provider EDI Reference Guide for Blue Cross Blue Shield of Delaware

837D Health Care Claim: Educational Guide

ANSI ASC X12N 837 Healthcare Claim Companion Guide

Transcription:

USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270 Date of Publication: 12/04/2012 Version: 1.1

DISCLAIMER The DXC Technology Companion Guide for USVI Medicaid is subject to change prior to January 1, 2013 or at the instruction of the Department. Therefore, it is the responsibility of the trading partner to ensure that the latest version of this guide is used when designing\building NX12 5010 EDI transactions. The trading partner should frequently check for updates to the companion guide. DXC Technology accepts no liability for any costs that the trading partner may incur that arise from or are related to changes to the companion guide. December 2012 005010 1 2

Preface This Companion Guide to the v5010 ASC X12N Implementation Guides and associated errata adopted under HIPAA clarifies and specifies the data content when exchanging electronically with DXC Technology. 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. December 2012 005010 1 3

EDITOR'S NOTE This page is blank because major sections of a book should begin on a right hand page. December 2012 005010 1 4

Table of Contents Table of Contents... 5 INTRODUCTION... 7 SCOPE... 8 OVERVIEW... 8 REFERENCES... 8 ADDITIONAL INFORMATION... 8 GETTING STARTED... 8 Please visit http://www.vimmis.com for information... 8 TRADING PARTNER REGISTRATION... 8 CERTIFICATION AND TESTING OVERVIEW... 9 TESTING WITH THE PAYER... 9 CONNECTIVITY WITH THE PAYER/COMMUNICATIONS... 10 PROCESS FLOWS... 10 TRANSMISSION ADMINISTRATIVE PROCEDURES... 11 RE-TRANSMISSION PROCEDURE... 11 PASSWORDS... 11 CONTACT INFORMATION EDI CUSTOMER SERVICE... 11 EDI TECHNICAL ASSISTANCE... 11 PROVIDER SERVICE NUMBER... 11 APPLICABLE WEBSITES/E-MAIL... 11 CONTROL SEGMENTS/ENVELOPES... 11 ISA-IEA... 12 GS-GE... 13 ST-SE... 14 PAYER SPECIFIC BUSINESS RULES AND LIMITATIONS... 15 ACKNOWLEDGEMENTS AND/OR REPORTS... 15 REPORT INVENTORY... 15 TRADING PARTNER AGREEMENTS... 15 TRADING PARTNERS... 15 TRANSACTION SPECIFIC INFORMATION... 16 Transmission constraints... 16 270 Transaction -- Eligibility Benefit Inquiry Transaction... 16 APPENDICES... 19 December 2012 005010 1 5

1. Implementation Checklist... 19 2. Business Scenarios... 19 3. Transmission Examples... 20 4. Frequently Asked Questions... 20 5. Change Summary... 20 December 2012 005010 1 6

INTRODUCTION This section describes how ASC X12N Implementation Guides (IGs) adopted under HIPAA will be detailed with the use of a table. The tables contain a row for each segment that DXC Technology has something additional, over and above, the information in the IGs. That information can: 1. Limit the repeat of loops, or segments 2. Limit the length of a simple data element 3. Specify a sub-set of the IGs internal code listings 4. Clarify the use of loops, segments, composite and simple data elements 5. Any other information tied directly to a loop, segment, composite or simple data element pertinent to trading electronically with DXC Technology In addition to the row for each segment, one or more additional rows are used to describe DXC Technology s usage for composite and simple data elements and for any other information. Notes and comments should be placed at the deepest level of detail. For example, a note about a code value should be placed on a row specifically for that code value, not in a general note about the segment. The following table specifies the columns and suggested use of the rows for the detailed description of the transaction set companion guides. December 2012 005010 1 7

SCOPE This companion guide documents the transaction type listed below and further defines situational and required data elements that are used for processing eligibility inquiries/responses for programs administered by USVI Medicaid. This document is not the complete EDI transaction format specifications.. Eligibility Benefit Inquiry and Response ASC X12N 270/271 (005010X279A1) Eligibility Benefit Inquiry and Response ASC X12N 270/271 (005010X279A1) OVERVIEW Data elements, segments, and loops not included in this guide are not used for processing transactions by USVI Medicaid, but must still be sent if the information is required for compliance with the ASC X12N version 5010A1 format. USVI Medicaid requires two of the following data elements for request processing: o Date of Birth o Social Security Number o Medicaid Member ID USVI Medicaid will be returning limitations information if available for the procedure code. USVI Medicaid will process eligibility requests with Dates of Service fields that contain date values greater than the current date. USVI Medicaid will not use Procedure Modifiers when processing requests. USVI Medicaid will not process eligibility requests for dates greater than 24 months in the past. REFERENCES Please refer to the 5010 Technical Report Type 3 Guide for information not supplied in this document, such as code lists, definitions, and edits. ADDITIONAL INFORMATION This section, completed by the payer, includes other information useful to the reader. For example: Assumptions regarding the reader Advantages / benefits of EDI GETTING STARTED WORKING WITH DXC Technology Please visit http://www.vimmis.com for information For any questions, or to begin testing, please contact the DXC Technology EDI Helpdesk at 1-855-248-7536 or email us at VIEDIHelpdesk@molinahealthcare.com. TRADING PARTNER REGISTRATION This section describes how to register as a trading partner with DXC Technology. A trading partner is defined as any entity with which DXC Technology exchanges electronic data. The term electronic data is not limited to HIPAA X12 transactions. USVI Medicaid s Health PAS system supports the following categories of trading partner: December 2012 005010 1 8

Provider Billing Agency Clearinghouse Other DXC Technology will assign trading partner IDs to support the exchange of X12 EDI transactions for providers, billing agencies and clearinghouses, and other health plans. To obtain a trading partner ID please visit our website at: http://www.vimmis.com Or contact us at 1-855- 248-7536. CERTIFICATION AND TESTING OVERVIEW This section provides a general overview of what to expect during any certification and testing phases. All trading partners must be authorized to submit production EDI transactions. Any trading partner may submit test EDI transactions. The Usage Indicator, element 15 of the Interchange Control Header (ISA) of an X12 file, indicates if a file is test or production. Authorization is granted on a per transaction basis. For example, a trading partner may be certified to submit 837P professional claims but not certified to submit 837I institutional claim files. TESTING WITH THE PAYER This section contains a detailed description of the testing phase. Trading partners must submit three test files of a particular transaction type, with a minimum of fifteen transactions within each file, and have no failures or rejections to become certified for production. Users will be notified via E-mail and the Trading Partner Status page of Health PAS-Online when testing for a particular transaction has been completed. December 2012 005010 1 9

CONNECTIVITY WITH THE PAYER/COMMUNICATIONS PROCESS FLOWS This section contains process flow diagrams and appropriate text. December 2012 005010 1 10

TRANSMISSION ADMINISTRATIVE PROCEDURES This section provides DXC Technology s specific transmission administrative procedures. X12 files can be uploaded via Health PAS-Online File Exchange X12Upload. Acknowledgments and Responses to transactions submitted via Health PAS-Online can be accessed by selecting Download/Responses under the File Exchange menu. Trading Partners who have submitted X12 transactions via Secured FTP may retrieve acknowledgements and responses from their designated secured FTP Pickup location RE-TRANSMISSION PROCEDURE This section provides DXC Technology s specific procedures for re-transmissions. ISA13 Interchange Control Number needs to be unique to each file and Trading Partner ID. COMMUNICATION PROTOCOL SPECIFICATIONS This section describes DXC Technology s communication protocol(s). PASSWORDS This section describes DXC Technology s use of passwords. Trading Partner s create their own password at time of registration and are required to update it every 60 days as per the Health PAS-Online requirements. CONTACT INFORMATION EDI CUSTOMER SERVICE This section contains detailed information concerning EDI Customer Service, especially contact numbers. DXC Technology EDI Helpdesk at 1-855-248-7536 or email us at VIEDIHelpdesk@molinahealthcare.com. EDI TECHNICAL ASSISTANCE This section contains detailed information concerning EDI Technical Assistance, especially contact numbers. DXC Technology EDI Helpdesk at 1-855-248-7536 or email us at VIEDIHelpdesk@molinahealthcare.com. PROVIDER SERVICE NUMBER This section contains detailed information concerning the payment of claims, especially contact numbers Provider Services 1-340-715-6929 or vimmis@dhs.vi.gov APPLICABLE WEBSITES/E-MAIL This section contains detailed information about useful web sites and email addresses. Website -- http://www.vimmis.com EDI Support VIEDIHelpdesk@molinahealthcare.com Provider Services vimmis@dhs.vi.gov Provider Enrollment vimmis@dhs.vi.gov CONTROL SEGMENTS/ENVELOPES USVI Medicaid does not require the use of specific values for the delimiters used in electronic transactions. The suggested values are included in the specifications below. December 2012 005010 1 11

Valid Delimiters for USVI Medicaid Definition ASCII Decimal Hexadecimal Segment Separator ~ 126 7E Element Separator * 42 2A Compound Element Separator : 58 3A ISA-IEA This section describes DXC Technology s use of the interchange control segments. It includes a description of expected sender and receiver codes, authorization information, and delimiters. Page # Loop ID Referenc e Name Codes Length Notes/Comments C.4 ISA01 Authorization Information 00 2 ISA02 Authorization Information [space fill] 10 ISA03 Security Information 00 2 ISA04 Security Information [space fill] 10 ISA05 Interchange ID ZZ 2 ISA06 Interchange Sender ID Insert with the unique number found on your USVI Transaction Information Form. 15 C.5 ISA07 Interchange ID ZZ 2 ISA08 Interchange Receiver ID VI_MMIS_4MOLINA 15 Payer ID ISA09 Interchange Date YYMMDD 6 December 2012 005010 1 12

Page # Loop ID Referenc e Name Codes Length Notes/Comments ISA10 Interchange Time HHMM 4 ISA11 Repetition Separator ^ 1 Suggested value ISA12 Interchange Version Number 00501 5 ISA13 Interchange Control Number Assigned by Sender 9 Pad Left with Zeros must be identical to interchange trailer IEA02 C.6 ISA14 Acknowledgement Requested 1 - Interchange Acknowledgment Requested 1 ISA15 Usage Indicator T= Test Data 1 P = Production Data ISA16 Component Element Separator : 1 Page # Loop ID Referenc e Name Codes Length Notes/Comments C.10 IEA01 Number of Included Functional Groups 1 1/5 IEA02 Interchange Control Number Must be identical to the value in the ISA13 9 GS-GE This section describes DXC Technology 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 DXC Technology expects functional groups to be sent and how DXC Technology will send functional groups. These discussions will describe how similar transaction sets will be packaged and DXC Technology s use of functional group control numbers. December 2012 005010 1 13

Page # Loop Reference Name Codes Length Notes/Comments ID C.7 GS01 Functional Identifier Code HS 2 Eligibility, Coverage or Benefit Information GS02 Application Sender's Code 2/15 Must be identical to the value in the ISA06 GS03 Application Receiver's Code VI_MMIS_4MOLINA 2/15 GS04 Date CCYYMMDD 8 C.8 GS05 Time HHMM 4/8 Time based on a 24-hour clock GS06 Group Control Number Assigned by Sender 1/9 Must be identical to the value in the GE02 GS07 Responsible Agency Code X 1/2 GS08 Version / Release Code 005010X279A1 1/12 Page # Loop ID Reference Name Codes Length Notes/Comments C.9 GE01 Number of Transaction Sets Included 1 1/6 GE02 Group Control Number Must be identical to the value in the GS06 1/9 ST-SE This section describes DXC Technology s use of transaction set control numbers. Please refer to the tables below for the ST-SE specific information for the 270 and 271 transactions. Page # Loop ID Reference Name Codes Length Notes/Comments 61 ST01 Transaction Set Identifier Code 270 3 ST02 Transaction Set Control Number 4/9 Must be identical to SE02 62 ST03 Implementation Convention Reference 005010X279A1 1/35 December 2012 005010 1 14

Page # Loop Reference Name Codes Length Notes/Comments ID 200 SE01 Number of Included Segments 1/10 (Total Number of ST thru SE segments) SE02 Transaction Set Control Number Must be identical to ST02 4/9 PAYER SPECIFIC BUSINESS RULES AND LIMITATIONS This section describes DXC Technology s business rules, for example: 1. Billing for specific services such as DME, Ambulance, Home Health 2. Communicating payer specific edits 3. CORE Level of Certification Please refer to the tables below for the business rules specific information for the 270 and 271 transactions. ACKNOWLEDGEMENTS AND/OR REPORTS This section contains information and examples on any applicable payer acknowledgements Please see Appendix_A_Vendor_Specs-5010.docx. REPORT INVENTORY This section contains a listing/inventory of all applicable acknowledgement reports. Please see Appendix_A_Vendor_Specs-5010.docx. TRADING PARTNER AGREEMENTS This section contains general information concerning Trading Partner Agreements (TPA). An actual TPA may optionally be included in an appendix. TRADING PARTNERS An EDI Trading Partner is defined as any DXC Technology customer (provider, billing service, software vendor, employer group, financial institution, etc.) that transmits to, or receives electronic data from DXC Technology. Payers have EDI Trading Partner Agreements that accompany the standard implementation guide to ensure the integrity of the electronic transaction process. The Trading Partner Agreement is related to the electronic exchange of information, whether the agreement is an entity or a part of a larger agreement, between each party to the agreement. For example, a Trading Partner Agreement may specify among other things, the roles and responsibilities of each party to the agreement in conducting standard transactions. December 2012 005010 1 15

TRANSACTION SPECIFIC INFORMATION This section describes how ASC X12N Implementation Guides (IGs) adopted under HIPAA will be detailed with the use of a table. The tables contain a row for each segment that DXC Technology has something additional, over and above, the information in the IGs. That information can: 1. Limit the repeat of loops, or segments. 2. Limit the length of a simple data element. 3. Specify a sub-set of the IGs internal code listings. 4. Clarify the use of loops, segments, composite and simple data elements. 5. Any other information tied directly to a loop, segment, composite or simple data element pertinent to trading electronically with DXC Technology. Transmission constraints A. Only one Interchange per transmission B. Only one transaction type per interchange C. Maximum of 5,000 inquiry transactions per transmission D. Single transmission file size must be less than 5MB In addition to the row for each segment, one or more additional rows are used to describe DXC Technology s usage for composite and simple data elements and for any other information. Notes and comments should be placed at the deepest level of detail. For example, a note about a code value should be placed on a row specifically for that code value, not in a general note about the segment. The following table specifies the columns and suggested use of the rows for the detailed description of the transaction set companion guides. 270 Transaction -- Eligibility Benefit Inquiry Transaction Page # Loop ID Reference Name Codes Length Notes/Comments 64 BHT02 Transaction Set Purpose Code 65 BHT06 Transaction Type Code 69 2100A NM101 Entity Identifier Code 70 2100A NM102 Entity Type 2100A NM103 Last Name or Organization Name 71 2100A NM108 Payer Identification 2100A NM109 Identification Code 13 2 Request NOT USED PR 2 Payer 2 1 Non Person Entity 1/60 VI_MMIS_4MOLINA PI 2 Payer Identification 2/80 VI_MMIS_4MOLINA December 2012 005010 1 16

Page # Loop ID Reference Name Codes Length Notes/Comments 75 2100B NM101 Entity Identifier Code 1P Provider 80 Hospital FA Facility 2 76 2100B NM102 Entity Type 1 Person 2 Non-Person Entity 1 2100B NM103 Last Name or Organization Name Provider s Last Name Or 1/60 Organization Name 2100B NM104 First Name Provider s First Name 1/35 77 2100B NM108 Identification Code XX National Provider ID or 1/2 SV Service Provider Number 78 2100B NM109 Identification Code 2/80 When using XX use National Provider ID 88 2000C HL04 Hierarchical Child Code When using SV use VI Medicaid Provider ID 0 No subordinate 1 HL segments in this hierarchical structure 93 2100C NM103 Last Name or Organization Name Subscriber Last Name 1/60 As it appears on their USVI Medicaid Card 2100C NM104 First Name Subscriber First Name 1/35 As it appears on their USVI Medicaid Card 94 2100C NM108 Identification Code MI 2 Member Identification Number December 2012 005010 1 17

Page # Loop ID Reference Name Codes Length Notes/Comments 96 2100C NM109 Identification Code Subscriber Primary Identifier USVI Medicaid 15 digit A/N Member ID 7/10 Please Note: If the MI is missing, SSN and DOB are required. 98 2100C REF01 Reference Identification SY 2 Subscriber SSN 99 2100C REF02 Reference Identification 1/50 9 digits Subscriber SSN 108 2100C DMG02 Date Time Period 8 Subscriber Date of Birth 123 2100C DTP01 Date/Time 291 3 for Plan 2100C DTP02 Date/Time Period Format RD8 3 2100C DTP03 Date Time Period 17 Date requested for eligibility verification 125 2110C EQ01 Service Type Code 2 See appendix 2 for values December 2012 005010 1 18

APPENDICES This section contains one or more appendices. 1. Implementation Checklist This appendix contains all necessary steps for going live with DXC Technology. Register for a Trading Partner ID Test with DXC Technology 2. Business Scenarios This appendix contains free format text descriptions of typical business scenarios. The transmission examples for these scenarios are included in Appendix 3. Service Type Code Description 1 Medical Care 30 Health Benefit Plan Coverage 33 Chiropractic 35 Dental Care 47 Hospital 48 Hospital Inpatient 50 Hospital Outpatient 86 Emergency Services 88 Pharmacy 98 Professional (Physician) Visit Office AL MH UC Vision (Optometry) Mental Health Urgent Care December 2012 005010 1 19

3. Transmission Examples This appendix contains actual data streams linked to the business scenarios from Appendix 2. Example of a request for the values listed in Appendix 2 EQ*1~ 4. Frequently Asked Questions This appendix contains a compilation of questions and answers relative to DXC Technology and its providers. Typical question would involve a discussion about code sets and their effective dates. See http://www.vimmis.com for answers to Frequently asked Questions. 5. Change Summary This section describes the differences between the current Companion Guide and previous guide(s). The companion guide was updated to comply with the CORE companion guide format and rules. December 2012 005010 1 20