Skip to main content

As a PA, I want the Q1/Q2 output files regenerated so the SavingsDate output field is populated

Testing Feedback

The SavingsDate output field was added as part of the Claims Spec update, but the Q1/Q2 output files were generated before that field was in place — we mistimed getting the output out ahead of the Claims Spec deadline. As a result, the existing Q1/Q2 outputs don't have SavingsDate populated.

Which is blocking Eric Corona's testing. This ticket covers regenerating those output files so testing can proceed.

Select user type
Posted by cedars team ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • ecorona1

    •

    Oct 13

    The 2026 record-level data was downloaded from CEDARS and imported into a DB table. The SavingsDate is missing for ~88K claims with MeasImpactType='Deem' and DeliveryType in ('DI', 'Down', 'Mid-Distr', and 'Mid-Retail'). The SavingsDate is also missing in claims with MeasImpactType='Deem-WP' and DeliveryType in ('DI', 'DnDeemDI', 'Down'). There are no eTRM permutations with a 2025 MeasImpactType (Deem-WP) and a 2026 DeliveryType (DI, Down). A valid MeasImpactType/DeliveryType combination should be considered for a CEDARS validation enhancement.