P-5.3. Claim Format

The current telecommunications standard for pharmacy claim transactions is the National Council for Prescription Drug Programs (NCPDP) version D.0. Claim transactions submitted in any other version will reject.

Refer to the pharmacy payer sheets for specific transaction, segment, and field requirements and, for the E1 transaction, detailed messaging returned in the “Additional Message Information” field (526-FQ).

5.3.1. NCPDP Transactions

The transaction codes below are defined according to the standards established by NCPDP. Ability to use these transaction codes will depend on the pharmacy’s software. At a minimum all pharmacy software should have the capability to submit original claims (transaction code B1) and reversals (transaction code B2).

Code Name Support Requirements

B1

Billing

Required

B2

Reversal

Required

B3

Re-bill

Not Supported

C1

Controlled Substance Reporting

Not Supported

C2

Controlled Substance Reporting Reversal

Not Supported

C3

Controlled Substance Reporting Rebill

Not Supported

D1

Predetermination of Benefits

Not Supported

E1

Eligibility Verification

Supported

N1

Informational Reporting

N1 from pharmacies not supported

N2

Informational Reversal

N2 from pharmacies not supported

N3

Informational Re-bill

Not Supported

P1

Prior Authorization Request and Billing

Not Supported

P2

Prior Authorization Reversal

Not Supported

P3

Prior Authorization Inquiry

Not Supported

P4

Prior Authorization Request Only

Not Supported

S1

Service Billing

Not Supported

S2

Service Reversal

Not Supported

S3

Service Rebill

Not Supported

Claims Billing (B1) Transaction

This transaction captures and processes the claim in real time. On payable claims, the system notifies the pharmacy of the dollar amount allowed under the Medicaid reimbursement calculation. If the claim is not payable, the system returns an NCPDP error code. In some cases, a message is included in "Addition Message Information" (field 526-FQ).

The following payer sheets are available:

B1 transactions submitted to HHSC for clients enrolled in Medicaid managed care or CHIP will reject with NCPDP code "AF" (“Patient Enrolled Under Managed Care") and identify the name of the client's MCO. Pharmacy providers should contact the client's specific MCO for details.

Claims Billing Reversal (B2) Transaction

Pharmacies use this transaction to cancel a claim previously processed as paid. The following payer sheets are available:

The following fields must match on the original paid claim and on the reversal request for a successful claim reversal:

  • "Service Provider ID" (201-B1)
  • "Prescription/Service Reference Number" (402-D2)
  • "Product/Service ID" (407-D7)
  • "Date of Service" (401-D1)

Eligibility Verification (E1) Transaction

Pharmacies use this transaction to determine a client's program-specific eligibility, prescription benefits, and managed care enrollment status when applicable. The following payer sheets are available:

Refer to the Eligibility section for information about the Pharmacy Eligibility Verification Portal, an alternate method of verification.

* E1 transactions submitted to HHSC for clients enrolled in CHIP will return a response identifying the name of the client's MCO. Pharmacy providers should contact the client's specific MCO for details.

5.3.2. NCPDP Transaction Segments

Data in the NCPDP standard is grouped together in segments. The current program segment requirements are outlined below.

NCPDP Segment B1 B2 E1 Segment Support Requirements

Header

Mandatory

Mandatory

Mandatory

Required for all transactions

Patient

Required Not Used Required

Required for B1 and E1, not used for B2

Insurance

Mandatory

Not Used Mandatory Required for B1 and E1, not used for B2

Claim

Mandatory Mandatory Not Used Required for B1 and B2, not used for E1

Pharmacy Provider

Not Used Not Used Not Used

Not used

Prescriber

Required Not Used Not Used

Required for B1 only

COB/Other Payments

Optional Not Used Not Used

Required for B1 when other payer exists

Worker’s Comp

Not Used Not Used Not Used

Not Used

DUR/PPS

Optional Optional Not Used

Optional

Pricing

Mandatory Not Used Not Used

Required for B1 only

Coupon

Not Used Not Used Not Used

Not Used

Compound

Optional Not Used Not Used

Required for B1 when claim is for a compound

Prior Authorization

Not Used Not Used Not Used

Not Used

Clinical

Not Used Not Used Not Used

Not Used

Additional Documentation

Not Used Not Used Not Used

Not Used

Facility

Not Used Not Used Not Used

Not Used

Narrative Not Used Not Used Not Used Not Used

5.3.3. NCPDP Transaction Segment Data Elements

The system uses program-specific data elements for each transaction outlined below. The pharmacy’s software vendor must review the HHSC payer sheets before setting up the plan in the pharmacy’s system. This will allow the provider access to the required fields.

The system will not process claims without all the required data elements for the transaction submitted. Required fields may or may not be used in the adjudication process for all transactions.

Code Description

M

Designated as MANDATORY in accordance with the NCPDP

Telecommunication Implementation Guide Version D.0.  These fields must be sent if the segment is required for the transaction.

R

Designated as REQUIRED for this program.

O

Designated as OPTIONAL in accordance with the NCPDP

Telecommunication Implementation Guide Version D.0.  It is necessary to send these fields in noted situations where they are conditional based on data content.

N

Designated as NOT USED in accordance with the NCPDP Telecommunication Implementation Guide Version D.0.

***R*** The “***R***” indicates the field is repeating.