Skip to main content

Regression testing SavingsDate

Testing Feedback2026 Claim Spec Update Queue

Feedback from Greg

“The attached file downloaded from CEDARS shows the SavingsDate field at the end of the Claims table. The SavingsDate field is no longer part of the 2026 input spec but will be added to the record-level output file.”

Claims_2026_Inputs.csv

32 KB• Spreadsheet

Investigate if the SavingsDate output is behaving as expected for 2026

Environment
Staging cedars-2
Select user type
Posted by cedars team ·
Status: Completed4 comments

Log in to comment and vote

Comments4

  • cedars team

    Team•

    Aug 5

    Hi @ggreen,

    This fix has been deployed to cedars-2.

    I believe this feedback came from you, so I’m hoping you can help us test this again and verify that the SavingsDate behavior is working as intended.

    Could you please verify that:

    • SavingsDate no longer appears on the Claims Specification Data Rules page and in the “Download All Rules” file.

    • SavingsDate no longer appears in the “Download Claim Inputs” file on the Active Dashboards.

    • SavingsDate is available in the “Download CET Output” file on the Active Dashboards (the CET will need to be run again on a new upload to see this change).

    • SavingsDate is available in the “Record-level Measure Input and Cost Effectiveness Output” file on the Confirmed Dashboards.

    • Guidance on SavingsDate is visible and clear on the Claims User Guide.

    Thank you,

    Erika

    • cedars team

      Team•

      Aug 6

      Hi @Roopa Reddy,

      As you’re also listed as an up-voter on this ticket, could I ask for you to verify that the SavingsDate behavior is working as intended?

      In addition to cedars-2, this work has also been deployed to cedars-3 if you’d prefer to test it along with the Participant replacement work.

      Could you please verify that:

      • SavingsDate no longer appears on the Claims Specification Data Rules page and in the “Download All Rules” file.

      • SavingsDate no longer appears in the “Download Claim Inputs” file on the Active Dashboards.

      • SavingsDate is available in the “Download CET Output” file on the Active Dashboards (the CET will need to be run again on a new upload to see this change).

      • SavingsDate is available in the “Record-level Measure Input and Cost Effectiveness Output” file on the Confirmed Dashboards.

      • Guidance on SavingsDate is visible and clear on the Claims User Guide.

      Thank you,

      Erika

  • cedars team

    Team•

    Jul 29

    • SavingsDate will be removed from the Claim specification table

    • It will be added to the output file on the active dashboard

    • We have also drafted some additional guidance for the user guide

    Claim.SavingsDate is a value CEDARS generates, not a field you submit. It represents the date used in validation logic, plus the name of the field which that date came from. CEDARS derives it from the relevant date field on the Claim input table (ShipmentDate, SalesDate, PermitIssuanceDate, ComplianceCertDate, ApplicationDate, or InstallationDate, depending on the Measure.DeliveryType). You can find it in the CET Output file on the active dashboards after running the CET on your claims, or in the Record-level Measure Input and Cost Effectiveness Output on the confirmed dashboards.

  • cedars team

    Team•

    Jul 22

    I’d like to confirm with PAs

    If SavingsDate should remain documented within the Claim Specification.

    Considerations:

    • SavingsDate is a CEDARS-generated field rather than a stakeholder-submitted input.

    • The field currently appears on the Claims table specification.

    • Determine whether it should instead be documented as an output-only field or removed from the specification entirely.