Corporate

March 26, 2015

Inpatient Rehabilitation Facility - Patient Assessment Instrument (IRF – PAI)

The IRF-PAI is used to gather data to determine the payment for each Medicare Part A fee-for-service and Medicare Part C (Medicare Advantage) patient admitted to an inpatient rehabilitation unit or hospital.

jIRVEN (Inpatient Rehabilitation Validation and Entry system) is a free java-based application that allows IRFs to collect and subsequently submit the IRF PAI data to the CMS National Assessment Collection Database. The software runs the data from the PAI through grouping software that generates a case-mix group based on clinical characteristics and expected resource needs to be used on the IRF claim via a Health Insurance Prospective Payment System (HIPPS) code. Separate payments are calculated for each group, including the application of case and facility level adjustments.

To prevent inaccurate payments, the Fiscal Intermediary Shared System (FISS) suspends claims with HIPPS codes and creates a finder file of claim information on the mainframe at each MAC's Enterprise Date Center (EDC). A file exchange mechanism transmits these files to the data center where the assessments are housed. There, the corresponding assessment information will be found in the Quality Improvement and Evaluation System (QIES) and an updated file returned to the EDC for further FISS processing.

Submission Date and Claims Processing: Scenarios

IRF claims submitted to FISS will suspend to status/location SMFRX0 with reason code 37069. FISS then communicates with the CMS National Assessment Collection Database to request a match of the claim with the assessment. Each nightly cycle, the status/location changes the last digit until four nightly cycles are completed (SMFRX0 – SMFRX4).

If no return file is received after the fourth nightly cycle, the claim will Return to Provider (RTP) with reason code 37096. If your claim RTPs:

  • Ensure the IRF-PAI finalized at the CMS National Assessment Collection Database prior to submitting your claim. If not, F9 or submit a new claim.
  • Verify that the following information on the claim is an exact match to the information on the IRF- PAI:
    • Beneficiary's HIC number (IRF-PAI item 2);
    • Beneficiary's date of birth (IRF-PAI item 6);
    • Provider Transaction Access Number (PTAN) (IRF-PAI item 1B);
    • Claim statement covers through dates (IRF-PAI item 40);
    • Claim admission date (IRF-PAI item 12);
    • HIPPS Code (UB-04 Form Locator code (FL) 44);
    • Occurrence code 50 date (UB-04 FL 31-36); and
    • Patient status other than 30 (UB-04 FL 17)
  • If an error is found, correct and F9 or submit a new claim. If no errors are found, F9 or submit a new claim.

If a return file is received by CGS and a match is found, the following scenarios are possible:

  • If the PAI is transmitted more than 27 calendar days from (and including) the date the beneficiary is discharged, the IRF's payment rate for the applicable case-mix group will be reduced by 25 percent.
  • If the submission date in the assessment response matches the occurrence code 50 date on the IRF claim, CGS will release the claim for processing.
  • If the submission date in the response information is later than the occurrence code 50 date, no condition code D2 is present, and the submission date is more than 27 days from the discharge date, CGS will release the IRF claim for processing but apply the late submission penalty.

Reference:

  • Additional processing scenarios are listed CMS MLN Matters article SE1342External PDF, "Systematic Validation of Payment Group Codes for Prospective Payment Systems (PPS) Based on Patient Assessments."

Two Vantage Way, Nashville, TN 37228 © CGS Administrators, LLC. All Rights Reserved