Skip to main content

Unable to upload claims without ProgramCost table - Update Participant.PrgYear data rule

Testing Feedback2026 Claim Spec Update Queue

When I try to upload a claims file with only the Measure, Claim, Site, ContactClaim, and Participant tables (i.e., without ProgramCost) as an XLSX file, I encounter a server error. I tested this with both the example claims file and some of my PA’s claims.

I didn’t see any issues uploading an XLSX file with all tables or only with the ProgramCost table.

New Update (7/28):

The specific validation rule that triggered the error is:

  • Participant.PrgYear must match a valid ProgramCost.PrgYear.

Update this validation rule to be:

  • Participant.PrgYear is for the current claim year.

  • This matches one of the validation rule applied to Measure.ClaimYearQuarter

Environment
Staging cedars-2
Select user type
Posted by SoCalREN_TEC ·
Status: Completed8 comments

Log in to comment and vote

Comments8

  • cedars team

    Team•

    Aug 4

    Hi @SoCalREN_TEC @Kevin Truong (TEC) @Roopa Reddy,

    This fix has been deployed to cedars-2. Could you please test this again by uploading a claim without the ProgramCost table and verify that it’s working as intended?

    Thank you,

    Erika

    • ktruong_TEC

      •

      Aug 4

      Hi Erika,

      Confirming that I no longer run into the server error when uploading a claims file without the ProgramCost table.

  • cedars team

    Team•

    Jul 23

    Hi @SoCalREN_TEC @Kevin Truong (TEC)

    We've investigated the server error reported when uploading an XLSX claims file containing the Measure, Claim, Site, ContactClaim, and Participant tables, but excluding the ProgramCost table.

    The upload itself is behaving as expected. CEDARS currently allows claims uploads without a ProgramCost table.

    The issue occurs during validation. One of the validation rules checks that every Participant.PrgYear matches a valid ProgramCost.PrgYear. When the ProgramCost table is not included, this validation assumes the table exists and crashes instead of handling its absence gracefully.

    The specific validation rule that triggered the error is:

    • Participant.PrgYear must match a valid ProgramCost.PrgYear.

    • Roopa Reddy

      Team•

      Jul 23

      Hi @cedars team

      Under the current scope, the Participant table was intended to be submitted without program cost data. With that in mind, would there be any concerns with defining the following validation rule as an alternative approach?

      Participant.PrgYear must match a valid year in Measure.ClaimYearQuarter.

      Would this create any issues or unintended impacts, and would it provide meaningful validation?

      Thank you!

      • cedars team

        Team•

        Jul 27

        Hi @Roopa Reddy,

        Since the Measure.ClaimYearQuarter data rule is validated against the current claim year, we're proposing to apply the same logic to Participant.PrgYear as an alternative approach. This would reduce cross-table validation dependencies while still ensuring the program year is valid for the current claim year.

        Current data rule:

        • Participant.PrgYear must match a valid ProgramCost.PrgYear.

        Proposed data rule:

        • Participant.PrgYear is for the current claim year.

        Regards,

        Erika

        • Roopa Reddy

          Team•

          Jul 27

          @cedars team Sounds good to me. Thanks for the update, Erika.

  • cedars team

    Team•

    Jul 22

    Could you please provide us the file you were trying to upload for testing purposes @SoCalREN_TEC

    • ktruong_TEC

      •

      Jul 22

      claim_2026_example_input_noPC.xlsx

      25.5 KB• Spreadsheet

      SCR Q1 2026 DRAFTv2_noPC.xlsx

      61.8 KB• Spreadsheet

      Please see attached.