837I Institutional Health Care Claim

Transcription

1 Section 2B 837I Institutional Health Care Claim Companion Document Basic Instructions This section provides information to help you prepare for the ANSI ASC X12N 837 Health Care transaction for Institutional claims. The tables in this document provide information about 837 segments and data elements that require specific instructions to efficiently process through Anthem Blue Cross and Blue Shield, Indiana, Kentucky, Ohio, Missouri, and Wisconsin (Central Region) systems. Use this companion document in conjunction with both the Transaction Set Implementation Guide Health Care Claim: Institutional, 837, ASC X12N 837 (004010X096), May 2000, and the subsequent Addenda (004010X096A1), October 2002, published by the Washington Publishing Co. EDI Transmission Structure Communications Transport Protocol Interchange Control Header (ISA) Functional Group Header (GS) Functional Group Header (GS) Communications Session Interchange Control Wrap Functional Group 1 Wrap Functional Group 2 Wrap Transaction Set Transaction Set Transaction Set Transaction Set Transaction Set Header (ST) Detail Segment 1 Transaction Set Trailer (SE) Transaction Set Header (ST) Detail Segment 2 Transaction Set Trailer (SE) Functional Group Trailer (GE) Functional Group Header (GS) Transaction Set Header (ST) Detail Segment 1 Transaction Set Trailer (SE) Transaction Set Header (ST) Detail Segment 2 Transaction Set Trailer (SE) EDI Transaction Structure Envelope Envelope Envelope Interchange Control Header (ISA) Functional Group Header (GS) Transaction Set Header (ST) Header Detail Summary Transaction Set Trailer (SE) Functional Group Trailer (GE) Interchange Control Trailer (IEA) Functional Group Trailer (GE) Interchange Control Trailer (IEA) Communications Transport Protocol Anthem Blue Cross and Blue Shield - Central Region Page 1 of 21

2 1 Central Region Products (as indicated on member s ID card) HMO/EPO/POS/PPO/TRAD: Refers to the following products in Indiana, Kentucky, Ohio, Missouri and Wisconsin: Blue Preferred Primary/Blue Priority (HMO), Blue Preferred Primary ASO (Ohio EPO), Blue Preferred Primary Blue (POS); Blue Access (PPO), and Blue Traditional (TRAD). Federal Employees Program (FEP): Refers to product Government-Wide Service Benefit Plan. BlueCard Program: Enables members who obtain health care services while traveling or living in another Plan s service area to receive the same benefits of their contracting Blue Cross and Blue Shield Plan and access to BlueCard providers and savings. It also links participating providers and the independent Blue Cross and Blue Shield plans across the country through a single electronic network for claims processing and reimbursement. National Accounts (NASCO): Refers to products BlueCard PPO, BlueCard Traditional, BlueCard POS, BlueCard HMO (Including Away from Home Care and Guest Membership), Bluecard Worldwide 2 X12 and HIPAA Compliance Checking, and Business Edits Level 1. X12 Compliance: Central Region returns a 997 Functional Acknowledgment to the submitter for every inbound 837 transaction received. Each transaction passes through edits to ensure that it is X12 compliant. If it successfully passes X12 syntax edits, a 997 Functional Acknowledgement is returned indicating acceptance of the transaction. If the transaction fails X12 syntax compliance, the 997 Functional Acknowledgement will also report the Level 1 errors in the AK segments and, depending on where the error occurred, will indicate that the entire interchange, functional group or transaction set has been rejected. Level 2. HIPAA IG Compliance - Sets: HIPAA Implementation Guide edits are strictly enforced. The Central Region will return a Level 2 Status Report to the submitter indicating if a transaction set has been accepted or rejected. If the transaction set has been rejected, this report will indicate the Level 2 HIPAA compliance error(s) that occurred. 3 HIPAA Compliant s Follow the 837 Institutional IG precisely. Use HIPAA-Compliant codes from current versions of the sources listed in the 837 Institutional IG, Appendix C: External Sources. Acceptance of HIPAA standard codes or modifiers will not alter the Central Region s covered benefits or current payment policies, guidelines or processes. Anthem Blue Cross and Blue Shield - Central Region Page 2 of 21

3 4 Taxonomy s (PRV) The Healthcare Provider Taxonomy code set divides health care providers into hierarchical groupings by type, classification, and specialization, and assigns a code to each grouping. The Taxonomy consists of two parts: individuals (e.g., physicians) and non-individuals (e.g., ambulatory health care facilities). All codes are alphanumeric and are 10 positions in length. These codes are not assigned to health care providers; rather, health care providers select the taxonomy code(s) that most closely represents their education, license, or certification. If a health care provider has more than one taxonomy code associated with it, a health plan may prefer that the health care provider use one over another when submitting claims for certain services. It is strongly recommended that the taxonomy be populated in Loops 2000A and 2310A PRV segment for all applicable claims that you are filing. Refer to the CMS website for a listing of codes, 5 Uppercase Letters All alpha characters must be submitted in UPPERCASE letters only. 6 Delimiters The Central Region accepts any of the standard delimiters as defined by the ANSI standards. The more commonly used delimiters include the following: Data Element Separator, Asterisk, (*) Sub-Element Separator, Vertical Bar, ( ) Segment Terminator, Tilde, (~) These delimiters are for illustration purposes only and are not specific recommendations or requirements. 7 Coordination of Benefits Specific 837 data elements work together to coordinate benefits between the Central Region and Medicare or other carriers. The tables in the section that follow (Loop 2320, 2330A, and 2330B), identify the data elements that pertain to Coordination of Benefits (COB) with Medicare (Provider-to- Payer-to-Payer COB model) and with other carriers (Payer-to-Provider-to-Payer COB model). The Central Region recognizes submission of an 837 to a sequential payer populated with data from the previous payer s 835 (Health Care Claim Payment/Advice). Based on the information provided and the type of policy, the claim will be adjudicated without the paper copy of the Explanation of Benefits from Medicare or the primary carrier. When more than one payer is involved on a claim, payer sequencing is as follows: If a secondary payer is indicated, then all the data elements from the primary payer must also be present. If a tertiary payer is involved, then all the data elements from the primary and secondary payers must also be present. If these data elements are omitted, the Central Region will fail the particular claim. Anthem Blue Cross and Blue Shield - Central Region Page 3 of 21

4 8 Sending Attachments to Support a Claim Loop 2300 PWK segment is required when paper documentation (attachments) supports a claim. To expedite processing of a claim: Mail the attachment the same day the claim is submitted Do not send a copy of the claim with the attachment. Send the completed PWK Attachment Face Sheet with the attachment. Anthem Mid-West (IN, KY, OH, MO, WI) Attachment Face Sheet Claim Supplemental PWK; Loop 2300 Original Service Line Number PWK; Loop 2400 Line Supplemental The paper documentation included in this mailing supports the electronically submitted claim. Date Claim Transmitted Line of Business Professional Institutional Member s Contract Number (Prefix Included) Name of Patient Date of Service Name of Provider State Services Were Rendered (Attachment Control #) (If the correspondence is not received in 14 calendar days and is necessary to adjudicate the claim, Anthem will fail the claim. After 14 calendar days, the claim will be reviewed on an inquiry basis only.) Please mail to: Anthem BCBS PO Box Louisville, KY An independent licensee of the Blue Cross and Blue Shield Association. Registered marks of the Blue Cross and Blue Shield Association. The PWK Attachment Face Sheet is located in the appendices on (IN, KY, OH, MO, WI) and includes the following fields: 1) Date Claim Transmitted 2) Line of Business (Professional, Institutional, Dental*) *Refer to 837D Companion Document for appropriate Attachment Face Sheet 3) Member s Contract (Subscriber) Number 4) Patient Name 5) Date of Service 6) Provider Name 7) State Where Services Were Rendered 8). This is the Attachment Control Number, an alphanumeric code created by the provider for his records. Mail the Attachment Face Sheet and supporting documentation to: Anthem BCBS PO BOX Lousiville, KY Anthem Blue Cross and Blue Shield - Central Region Page 4 of 21

5 Claim File received with PWK segment populated Claim Supplement Attachment Face Sheet Institutional Health Care Claim Attachment to Support a Claim By Mail June 8 June 20 June 21 June 22 All documentation must be received within 14 calendar days of the electronic submission. If supporting documentation is not received but is required to process the claim, the Central Region will deny the claim. For example (as shown above): On June 8, a claim is received with the PWK segment populated. On June 22, the 14 day time period expires. The claim will be denied if the attachment has not been received and is required for adjudication. 9 Numeric s, s and Unit Amounts The Central Region pays all claims in US dollars and, therefore, accepts monetary amounts only in US dollars. If codes related to foreign currencies are used, then the claim will be denied. The Central Region recognizes unit amounts in whole numbers only. The claim will also be denied for negative values submitted in any of the three data elements in Loop 2400 SV2 Institutional Service Line (See 837 Institutional IG, P.439): SV203 Line Item Charge Amount SV205 Quantity Service Unit Count SV207 Line Item Denied Charge or Non-Covered Charge Amount Anthem Blue Cross and Blue Shield - Central Region Page 5 of 21

6 Enveloping EDI envelopes control and track communications between you and Anthem. One envelope may contain many transaction sets grouped into functional groups. The envelope includes the following components: Interchange Control Header (ISA) Functional Group Header (GS) Functional Group Trailer (GE) Interchange Control Trailer (IEA) 837 EDI Transaction Structure Interchange Control Header (ISA) Functional Group Header (GS) Transaction Set Header (ST) Envelope Envelope Envelope Header Detail Transaction Set Trailer (SE) Functional Group Trailer (GE) Interchange Control Trailer (IEA) Anthem Blue Cross and Blue Shield - Central Region Page 6 of 21

7 837 Envelope Control Segments Inbound Health Care Claim Interchange Control Header (ISA) The ISA segment is the beginning, outermost envelope of the interchange control structure. Containing authorization and security information, it clearly identifies the sender, receiver, date, time, and interchange control number. Anthem requests that all data entered in the ISA-IEA segment be in UPPERCASE. Segment ISA ISA01 Interchange Auth Info Control ISA02 Header Authorization Info ISA03 Security Info ISA04 Security ISA05 Interchange ID ISA06 Interchange Sender ID ISA07 Interchange ID ISA08 Interchange Rec ID ISA09 Interchange Date ISA10 Interchange Time ISA11 Interchange Control Standards Identifier ISA12 Interchange Control Version Number ISA13 Interchange Cntrl No. Specific to Anthem No Authorization Present (10 Spaces) Enter 10 positions No Security Present (10 Spaces) Enter 10 positions. ZZ (Submitter ID) ZZ ANTHEM (YYMMDD) (HHMM) U ISA14 Ack Requested ISA15 Usage Indicator ISA16 (X) Component Element Separator 837 Institutional Health Care Claim Interchange Control Header (ISA) ZZ - Mutually Defined Format - Fixed length of 15 positions, alphanumeric. Left-justified followed by spaces. Identical to GS02. ZZ - Mutually Defined ANTHEM - Anthem Plans Left-justified followed by spaces. must be a valid date in YYMMDD format. must be a valid time in HHMM format. U - U.S. EDI Community of ASC X12, TDCC, and UCS Draft Standards for Trial Used Approved for Publication by ASC X12 Procedures Review Board through October 1997 (Assigned by Sender) Format - Fixed length 9 positions, numeric. Unique value greater than zero and not used in any HIPAA transmission within last 365 calendar days. Right-justified, filled with leading zeroes. Identical to IEA02. 0, No Acknowledgment Requested 1 - Interchange Acknowledgment Requested P, T Submitter ID must be approved to submit production data (P - Production Data; T - Test Data). X - 1 character contained in Basic or Extended Character set. must not equal A-Z, a-z, 0-9, "space", and special characters which may appear in text data (i.e., hyphen, comma, period, apostrophe). Anthem Blue Cross and Blue Shield - Central Region Page 7 of 21

8 2 837 Health Care Claim Functional Group Header (GS) The GS segment identifies the collection of transaction sets that are included within the functional group. More specifically, the GS segment identifies the functional control group, sender, receiver, date, time, group control number and version/release/industry code for the transaction sets. Anthem requests that all dat in the GS-GE segment be entered in UPPERCASE. Segment 837 Institutional Health Care Claim Functional Group Header (GS) Specific to Anthem GS Functional Group Header GS01 Functional Identifier GS02 Application Sender's GS03 Application Receiver's GS04 Date GS05 Time GS06 Group Control Number GS07 Responsible Agency GS08 Version / Release / Industry Identifier HC HC - Health Care Claim (837) (Submitter ID) ANTHEMIN ANTHEMKY ANTHEMOH ANTHEMMO ANTHEMWI (CCYYMMDD) (HHMM) (Assigned by Sender) X X096A1 Format positions, alphanumeric. Left-justified with no trailing zeroes or spaces. Identical to ISA06. Routing of batched transactions to: ANTHEMIN - IN BCBS Plan ANTHEMKY - KY BCBS Plan ANTHEMOH - OH BCBS Plan ANTHEMMO - MO BCBS Plan ANTHEMWI - WI BCBS Plan must be a valid date in CCYYMMDD format. must be a valid time in HHMM format. Format positions, numeric. Unique value greater than zero and not used in any HIPAA transmission within last 365 calendar days. Left-justified with no trailing zeroes or spaces. Identical to GE02. X - Accredited Standards Committee X12 Operationally used to identify the transaction: X096A1-837 Institutional Claim NOTE. Critical Batching and Editing. **Transactions must be batched Transactions must be batched in separate functional group by Application Receiver s (GS03). ***Group Control Number (GS06) may not be duplicated by submitter. Files containing duplicate or previously received group control numbers will be rejected. Anthem Blue Cross and Blue Shield - Central Region Page 8 of 21

9 3 837 Health Care Claim Functional Group Trailer (GE) The GE segment indicates the end of the functional group and provides control information. Segment 837 Institutional Health Care Claim Functional Group Trailer (GE) Specific to Anthem GE Functional Group Trailer GE01 Number of Transaction Sets Included GE02 Group Control Number (Total Number of Transaction Sets in Functional Group or Transmission) (Control Number) Format positions, numeric. Left-justified with no trailing zeroes or spaces. Format positions, numeric. Left-justified with no trailing zeroes or spaces. Identical to GS Health Care Claim Interchange Control Trailer (IEA) The IEA segment is the ending, outmost level of the interchange control structure. It indicates and verifies the number of functional groups included with the interchange and the interchange control number (the same number indicated in the ISA segment). Segment 837 Institutional Health Care Claim Interchange Control Trailer (IEA) Specific to Anthem IEA Interchange Control Trailer IEA01 Number of Included Functional Groups IEA02 Interchange Control Number (Number of Functional Groups GS/GE Pairs in Interchange) (Control Number) Format positions, numeric. Left-justified with no trailing zeroes or spaces. Format - Fixed length 9 positions, numeric. Unique value greater than zero. Identical to ISA13. Anthem Blue Cross and Blue Shield - Central Region Page 9 of 21

10 837 Institutional Claim Header The 837 Claim Header identifies the start of a transaction, the specific transaction set, and its business purpose. Also, when a transaction set uses a hierarchical data structure, a data element in the header, BHT01 (Hierarchical Structure ) relates the type of business data expected within each level. The following table indicates the specific values of the required header segments and data elements for the Central Region processing. IG Segment Beginning of Hierarchical Transaction P.57 BHT Beginning of Hierarchical Transaction P.60 REF Transmission Type BHT06 Transaction Type REF02 Transmission Type Loop ID 1000A Submitter Name P.61 NM1 Submitter Name P.65 PER Administrative Communications Contact NM109 PER03 Communication Loop ID 1000B Receiver Name P.67 NM1 Receiver Name 837 Institutional Health Care Claim Header NM103 Last Name or Organization Name NM109 CH X096A1 (Submitter Identifier) UPPERCASE TE ANTHEM BLUE CROSS AND BLUE SHIELD All submissions recognized as chargeable. Will not be used to distinguish between test and production. Anthem will determine based on the value in ISA15 only. EDI Assigned Sender ID. Equals the value entered in ISA06 and GS02. TE - Telephone For support purposes, the Central Region requests the telephone number of the submitter be identified. Receiver Name represents Indiana represents Kentucky represents Ohio represents Missouri represents Wisconsin Anthem Blue Cross and Blue Shield - Central Region Page 10 of 21

11 837 Institutional Claim Detail The 837 Claim Detail level has a hierarchical level (HL) structure based on the participants involved in the transaction. The three levels for the participant types include: 1) Source (Billing/Pay-to Provider) 2) Subscriber (Can be the Patient when the Patient is the Subscriber) 3) Dependent (Patient when the Patient is not the Subscriber) Anthem Blue Cross and Blue Shield - Central Region Page 11 of 21

12 1 837 Health Care Claim Detail: Billing/Pay-to Provider Hierarchical Level The first hierarchical level (HL) of the 837 Claim Detail, Billing/Pay-to Provider HL, identifies the original entity who submitted the electronic claim to the destination payer. IG Segment Loop ID 2000A Billing/Pay-to Provider Hierarchical Level P.71 PRV PRV01 BI BI - Billing Billing/Pay-to Provider Provider Specialty P.73 CUR Foreign Currency PRV03 CUR02 Currency (Provider Taxonomy ) USD Loop ID 2010AA Billing Provider Name P.76 NM1 NM108 XX Billing ID 24 Provider NM109 (Billing Name Provider Primary ID P.82 REF Billing Provider Secondary When using NPI, enter the taxonomy code that applies to the service on the claim that you are filing (NOTE to Clearinghouses - DO NOT DEFAULT). USD - US dollars Monetary amounts recognized in US dollars only. XX - National Provider Identifier 24 - Employer's Number NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers No.) Segment required to accurately identify the Billing Provider. REF01 1A ID EI SY SY - Social Security Number REF02 (Billing Provider Additional ID) Loop ID 2010AB Pay-to Provider Name P.91 NM1 NM108 XX Pay-to ID 24 Provider NM109 (Pay-to Name Provider Primary ID P.97 REF Pay-to Provider Secondary 837 Institutional Health Care Claim Detail Billing/Pay-to Provider Hierarchical Level 1A - Blue Cross Provider Number EI - Employer's Number Provider's Tax ID ('EI') Provider's Social Security No. ('SY') Assigned Provider No. ('1A') - for Exempt Providers XX - National Provider Identifier 24 - Employer's Number NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers No.) Segment required to accurately identify the Pay-to Provider. REF01 1A ID EI SY SY - Social Security Number REF02 (Billing Provider Additional ID) 1A - Blue Cross Provider Number EI - Employer's Number Provider's Tax ID ('EI') Provider's Social Security No. ('SY') Assigned Provider No. ('1A') - for Exempt Providers Anthem Blue Cross and Blue Shield - Central Region Page 12 of 21

13 2 837 Health Care Claim Detail: Subscriber Hierarchical Level The second hierarchical level (HL) of the 837 Health Care Claim Detail is the Subscriber HL. It is strongly recommended that each interchange (ISA-IEA envelope) be limited to 5000 claims for processing efficiency. IG Segment Loop ID 2000B Subscriber Hierarchical Level P.101 SBR Subscriber SBR01 Payer P, S, T Responsibility Sequence Number Loop ID 2010BA Subscriber Name P.108 NM1 Subscriber NM109 (Subscriber Primary Name Identifier) Loop ID 2010BC Payer Name P.126 NM1 NM108 Payer ID NM Institutional Health Care Claim Detail Subscriber Hierarchical Level PI (Payer Primary Identifier) Enter one of the Format Explanation following formats: ***ALL ALPHA CHARACTERS MUST BE IN UPPERCASE LETTERS. Enter the ID Number exactly as it appears on the front of the ID card, including ANY PREFIX. (XXX ) character alpha prefix e.g. YTA (uppercase) followed by 9-character alphanumeric subscriber ID code. (R ) R (uppercase) followed by 8-position e.g. R numeric subscriber ID code. ( ) e.g Usage of 'S' and 'T' accompanies information populated in Loop PI - Payer represents Indiana represents Kentucky represents Ohio represents Missouri represents Wisconsin 9-position numeric subscriber ID code. Anthem Blue Cross and Blue Shield - Central Region Page 13 of 21

14 3 837 Health Care Claim Detail: Patient Hierarchical Level The third hierarchical level (HL) of the 837 Health Care Claim Detail is the Patient HL. it is strongly recommended that each interchange (ISA-IEA envelope) be limited to 5000 claims for processing efficiency. IG Segment Loop ID 2300 Claim P.157 CLM CLM01 Claim Claim Submitter's Identifier CLM02 CLM05-3 Claim Frequency Type P.167 DTP Statement Dates DTP03 Date Time Period P.173 PWK PWK02 Claim Report Supplemental Transmission P.191 REF Original Number (ICN/DCN) P.204 K3 File 837 Institutional Health Care Claim Detail Patient Hierarchical Level (Patient Control Number) (Total Claim Charge Amount) (Third Position of Uniform Billing Claim Form Bill Type) (Statement From or To Date) BM PWK06 (Attachment Control Number) REF01 ID REF02 K301 Fixed Format F8 (Claim Original Number) Maximum of 20 alphanumeric characters. is returned on outbound 835 and other transactions. must equal the total amount of submitted charges for service lines in Loop 2400 SV203. If '7' (replacement) or '8' (void/cancel) then the Original Number (ICN/DCN) data segment (Loop 2300 REF02) is required and must contain Anthem's originally assigned claim no. Determination of valid medical codes based on the "Statement From Date." BM - By Mail All documentation and Attachment Face Sheet must be received within 14 calendar days of the electronic transmission otherwise the claim will be denied. Refer to Basic Instructions for mailing details. Self-assigned attachment control no. (10 alphanumeric characters) on the Attachment Face Sheet. Digits will be drawn beginning from the left to match the Attachment with the appropriate electronically submitted claim. F8 - Original Number Represents the claim no. assigned by Anthem. This value will be returned on 835 and should be submitted when Loop 2300 CLM05-3 = '7' or '8'. K3*POA<value/s>Z~ or K3*POA<value/s>Zvalue~ /s: Y=Yes; N=No; U=Unknown; X or Z = POA terminator; 1=Unreported/Not Used/Exempt; W=Clinically Undetermined; Eff. 1/1/08, Acute Care Hospitals must submit a POA indicator for every principal and other diagnosis on inpatient (TOB 11x and 12x) acute care claims. Eff. 6/27/09, when an E- is submitted in the HI03 (external cause of injury with BN qualifier) the POA values will be submitted after the data terminator. Examples Showing Reporting Structure: K3*POAYNU1Z1~ No exception handling, e-code submitted. K3*POAYNU1Z~ No exception handling, no e-code submitted. K3*POAYNU1XY~ Exception handling, e-code submitted. K3*POAYNU1X~ Exception handling, no e-code submitted. Anthem Blue Cross and Blue Shield - Central Region Page 14 of 21

15 IG Segment Loop ID 2300 Claim (cont'd) P.227 HI HI HI03-2 See Health Care Diagnosis Source 131: ICD-9-CM Loop ID 2310A Attending Name P.321 NM1 NM108 XX Attending ID 24 NM109 (Attending Name Primary ID) P.324 PRV PRV03 (Provider Attending Taxonomy ) Specialty P.326 REF Attending Secondary Include diagnosis information to promote more efficient adjudication and processing of bill type 4XX, 5XX, and 14 transactions. ICD-9-CM Guide requires diagnosis codes to the highest level of specificity. A 3-digit code cannot be used if a 4-digit exists, no 4-digit if a 5-digit code exists, etc. A code is invalid if it has not been coded to the full number of digits required for that code. XX - National Provider Identifier 24 - Employer's Number NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers When using NPI, enter the taxonomy code that applies to the service on the claim that you are filing (NOTE to Clearinghouses - DO NOT DEFAULT) Segment required to accurately identify the Attending. REF01 ID 1A EI SY 1A - Blue Cross Provider Number EI - Employer's Number SY - Social Security Number REF02 (Attending Provider's Tax ID ('EI') Provider's Social Security No. ('SY') Secondary ID) Assigned Provider No. ('1A') - for Exempt Providers Loop ID 2310B Operating Name P.328 NM1 NM108 XX XX - National Provider Identifier Operating ID Employer's Number Name NM109 (Operating Primary ID) NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers P.333 REF Segment required to accurately identify the Operating. Operating Secondary REF01 ID 1A EI SY 1A - Blue Cross Provider Number EI - Employer's Number SY - Social Security Number 837 Institutional Health Care Claim Detail Patient Hierarchical Level REF02 (Operating Secondary ID) Provider's Tax ID ('EI') Provider's Social Security No. ('SY') Assigned Provider No. ('1A') - for Exempt Providers Anthem Blue Cross and Blue Shield - Central Region Page 15 of 21

16 IG Segment Loop ID 2310C Other Provider Name P.335 NM1 NM108 XX Other ID 24 Provider Name P.340 REF Other Provider Secondary NM109 (Other Provider Primary ID) XX - National Provider Identifier 24 - Employer's Number NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers Segment required to accurately identify the Other Provider. REF01 1A ID EI SY REF02 (Other Provider Secondary ID) 1A - Blue Cross Provider Number EI - Employer's Number SY - Social Security Number Provider's Tax ID ('EI') Provider's Social Security No. ('SY') Assigned Provider No. ('1A') - for Exempt Providers Loop ID 2310E Service Facility Name P.349 NM1 NM108 XX XX - National Provider Identifier Service ID Employer's Number Facility Name NM109 (Laboratory / Facility Primary ID) NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers P.357 REF Segment required to accurately identify the Service Facility Location. Service Facility Secondary REF01 ID 1A EI 1A - Blue Cross Provider Number EI - Employer's Number 837 Institutional Health Care Claim Detail Patient Hierarchical Level REF02 (Laboratory or Facility Secondary ID) Provider's Tax ID ('EI') Assigned Provider No. ('1A') - for Exempt Providers Anthem Blue Cross and Blue Shield - Central Region Page 16 of 21

17 IG Segment When Anthem is secondary or tertiary, enter data elements as noted for Loops 2320, 2330A, & 2330B. Loop ID 2320 Other Subscriber P.359 SBR Other Subscriber SBR01 Payer Responsibility Sequence Number P S T P - Primary; S - Secondary; T - Tertiary Represents the other payer(s) level of responsibility for payment of this claim P.365 CAS Claim Level Adjustment P.371 AMT Payer Prior Payment P.372 AMT COB Total Allowed Amount 837 Institutional Health Care Claim Detail Patient Hierarchical Level Use the CAS segments to report prior payer(s) claim level adjustments that cause the amount paid to differ from the originally submitted charge amount. Institutional adjustments recognized at claim level only. CAS01 Claim Adjustment Group CAS02,5,8,11,14,17 Claim Adjustment Reason CAS03,6,9,12,15,18 CAS01 Claim Adjustment Group CAS02,5,8,11,14,17 Claim Adjustment Reason CAS03,6,9,12,15,18 CAS01 Claim Adjustment Group CAS02,5,8,11,14,17 Claim Adjustment Reason CAS03,6,9,12,15,18 Amount AMT02 Amount AMT02 CO - Contractual Obligation CR - Correction & Reversals OA - Other Adjustments Deductible Amount (Adjustment Amount) DEDUCTIBLE PI - Payer Initiated Reductions PR - Patient Responsibility COINSURANCE CO - Contractual Obligation PI - Payer Initiated Reductions CR - Correction & Reversals PR - Patient Responsibility OA - Other Adjustments Coinsurance Amount (Adjustment Amount) CO - Contractual Obligation CR - Correction & Reversals NON-COVERED CHARGES PI - Payer Initiated Reductions PR - Patient Responsibility OA - Other Adjustments (Adjustment Represents the adjustment reason code for noncovered as reported by other Reason ) payer. (Adjustment Amount) C4 (Payer Prior Payment) B6 (Allowed Amount) Represents the deductible as reported by the other payer. Represents the coinsurance as reported by the other payer. Represents the non-covered amount as reported by other payer. C4 - Prior Payment - Actual Represents the Prior Payer Payment. B6 - Allowed - Actual Represents the Allowed Amount. Anthem Blue Cross and Blue Shield - Central Region Page 17 of 21

18 IG Segment When Anthem is secondary or tertiary, enter data elements as noted for Loops 2320, 2330A, & 2330B. Loop ID 2320 Other Subscriber (cont'd) P.373 AMT COB Total Amount T3 T3 - Total Submitted Charges Submitted AMT02 (Total Claim Level Represents the Coordination of Benefits Charges Submitted Chrg.) Total Submitted Charge Amount. P.374 AMT ZZ ZZ - Mutually Defined Diagnostic Amount Related Group (DRG) Outlier AMT02 (Claim DRG Outlier Amount) Represents the Claim DRG Outlier Amount. Amount P.376 AMT N1 N1 - Net Worth COB Total Amount Medicare Paid Amount AMT02 (Total Medicare Paid Amount) Represents the Total Medicare Paid Amount. P.378 AMT KF KF - Net Paid Amount Medicare Paid Amount Amount - 100% AMT02 (Medicare Paid at 100%) Represents the COB Medicare Paid Amount at 100%. P.380 AMT PG PG - Payoff Medicare Paid Amount Amount - 80% AMT02 (Clm Lvl Allowed Chrg. Pd at 80%) Represents the amount that Medicare Paid at 80%. P.382 AMT AA AA - Allocated COB Medicare A Amount Trust Fund Paid Amount AMT02 (Amount Paid by Medicare Part A) Represents the Paid From Part A Medicare Trust Fund Amount. P.384 AMT B1 B1 - Benefit Amount COB Medicare B Amount Trust Fund Paid Amount AMT02 (Amount Paid by Medicare Part B) Represents the Paid From Part B Medicare Trust Fund Amount. P.386 AMT COB Total Non- Amount A8 A8 - Non-covered Charges - Actual Covered Amount AMT02 (Non-covered Clm Represents the amount for the total of Lvl Chrg.) non-covered claim level charges. P.387 AMT COB Total Amount YT YT - Denied Denied Amount AMT02 (Total Claim Level Represents the Claim Total Denied Denied Charges) Charge Amount. P.388 DMG Other Subscriber Demographic 837 Institutional Health Care Claim Detail Patient Hierarchical Level DMG02 Date Time Period DMG03 Other Insured Gender (Other Insured Birth Date) F M U Represents other insured's date of birth. F - Female; M - Male; U - Unknown Anthem Blue Cross and Blue Shield - Central Region Page 18 of 21

19 IG Segment When Anthem is secondary or tertiary, enter data elements as noted for Loops 2320, 2330A, & 2330B. Loop ID 2320 Other Subscriber (cont'd) P.390 OI Other OI03 Yes/No Condition or N Y N - No; Y - Yes (same values as Loop 2300 CLM08) Insurance Coverage Response Indicator OI06 Release of (Release of ) Indicates provider has an authorization of release on file (same value as Loop 2300 CLM09). Loop ID 2330A Other Subscriber Name P.400 NM1 NM101 IL IL - Insured or Subscriber Other Entity Identifier Subscriber NM Person Name Entity Type NM103, NM104 (Other Subscriber Represents the Other Subscriber's First Name Last/Org. Name, Last & First Name) and Last name. Name First NM108 MI MI - Member Number NM109 (Other Subscriber Primary Member ID No.) Represents the Other Subscriber's ID No. as assigned by the Other Payer. Loop ID 2330B Other Payer Name P.410 NM1 NM101 PR PR - Payer (Other) Other Payer Entity Identifier Name NM Non-Person Entity Entity Type NM103 Name Last/Org. Name (Other Payer Org. Name) Represents the Other Payer Last or Organization Name. NM108 PI PI - Payer NM109 P.415 DTP Claim DTP01 Adjudication Date/Time Date DTP02 Date Time Period Format DTP03 Date Time Period 837 Institutional Health Care Claim Detail Patient Hierarchical Level (Other Payer Primary ID No.) If Other Payer is a BCBS Plan, indicate Plan assigned by BCBS Assoc. Required when Loop 2430 is not used & Other Payer has adjudicated the claim Date Claim Paid D8 (Other Payer Adjud. or Payment Date) D8 - Date expressed in format CCYYMMDD Represents date the primary payer adjudicated the claim. Anthem Blue Cross and Blue Shield - Central Region Page 19 of 21

20 IG Segment Loop ID 2400 Service Line P.438 LX LX01 Service Line Assigned Number Number P.445 SV2 Institutional Service Line SV201 Product/Service ID SV202-2 HCPCS Procedure SV HCPCS Modifier 1-4 SV203 SV205 Quantity SV206 Unit Rate SV207 Loop ID 2410 Drug P.480 LIN LIN03 Drug Product/Service ID 837 Institutional Health Care Claim Detail Patient Hierarchical Level Accept claims containing up to 999 line items. (Service Line Revenue ) (HCPCS Procedure ) (HCPCS Modifiers) (Line Item Charge Amount) (Service Unit Count) (Service Line Rate) (Line Item Denied Charge or Non-Covered Charge Amount) (National Drug ) If the value ends in "9", then either Loop 2300 PWK (Claim Supplemental ) or Loop 2300 NTE (Claim Note) is required. Report the corresponding NDC# in Loop 2410 LIN03. For OHAS (Outpatient Hospital Allowance Schedule), HCPCS coding is required. Use the modifiers listed in the UB92 manual. Accept values greater than or equal to zero and less than $999, Sum of Line Item Charges reported must equal Total Claim Charge Amount in Loop 2300 CLM02. cannot exceed 9999 units. Accept values greater than or equal to zero. Accept values greater than or equal to zero and less than $999, NDC# (without hyphens) corresponds to unlisted HCPCS (NOC codes) in Loop 2400 SV201, SV202-2, and the drug and dosage in Loop 2300 NTE02. Example: NDC# is recognized as Anthem Blue Cross and Blue Shield - Central Region Page 20 of 21

21 IG Segment Loop ID 2420A Attending Name P.462 NM1 NM108 XX Attending ID 24 NM109 (Attending Name P.467 REF Attending Secondary XX - National Provider Identifier 24 - Employer's Number NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers Primary ID) Segment required to accurately identify the Attending. REF01 1A 1A - Blue Cross Provider Number ID EI EI - Employer's Number SY SY - Social Security Number REF02 (Attending Secondary ID) Provider's Tax ID ('EI') Provider's Social Security No. ('SY') Assigned Provider No. ('1A') - for Exempt Providers Loop ID 2420B Operating Name P.469 NM1 NM108 XX XX - National Provider Identifier Operating ID Employer's Number Name NM109 (Operating Primary ID) NPI ('XX') for Non-Exempt providers Tax ID ('24') for Exempt providers P.474 REF Segment required to accurately identify the Operating. Operating Secondary REF01 ID 1A EI SY 1A - Blue Cross Provider Number EI - Employer's Number SY - Social Security Number 837 Institutional Health Care Claim Detail Patient Hierarchical Level REF02 (Operating Secondary ID) Loop ID 2430 Service Line Adjudication P.490 SVD Service Line Adjudication SVD02 Payer Responsibility Sequence (Service Line Paid Amount) P.502 DTP DTP03 (Service Service Date Time Period Adjudication Adjudication or Payment Date Date) Provider's Tax ID ('EI') Provider's Social Security No. ('SY') Assigned Provider No. ('1A') - for Exempt Providers When the Central Region is secondary, enter the amount paid by Medicare or the other payer. Represents when the primary payer made payment and is recognized for processing Coordination of Benefits. Anthem Blue Cross and Blue Shield - Central Region Page 21 of 21