fluview API: State-level data missing for epiweek: 202514 despite presence of national data

[dhuynh97]

Endpoint: fluview (https://api.delphi.cmu.edu/epidata/fluview/)

Issue Description:

We are observing a discrepancy in data availability for epiweek: 202514 between the national (nat) level and specific state/sub-regional levels via the fluview API endpoint.

The fluview_meta endpoint correctly reports latest_issue: 202514 and latest_update: "2025-04-11". Consistent with this, national-level data is available for epiweek: 202514. However, when querying for specific states (e.g., tx), data for epiweek: 202514 appears to be missing from the results associated with the same issue: 202514 / release_date: 2025-04-11.

Steps to Reproduce:

1. Query National Data (Success):

   • URL: https://api.delphi.cmu.edu/epidata/fluview/?regions=nat&epiweeks=202511-202514
   • Result: Returns "result": 1 and the "epidata" array contains an object where "epiweek": 202514. (See full response snippet below)

2. Query State Data - Range (Partial Success, Missing Latest):

   • URL: https://api.delphi.cmu.edu/epidata/fluview/?regions=tx&epiweeks=202511-202514
   • Result: Returns "result": 1, but the "epidata" array only contains data up to "epiweek": 202511. Data for 202512, 202513, and crucially 202514 is missing for region tx. (See full response snippet below)

3. Query State Data - Focused Range (Failure):

   • URL: https://api.delphi.cmu.edu/epidata/fluview/?regions=tx&epiweeks=202513-202514
   • Result: Returns "result": -2, "message": "no results", epidata: []. (See full response snippet below)

Expected Result:

We expected the state-level queries (like for tx) in steps 2 and 3 to also return data for epiweek: 202514, given that national data exists for this week in the same data release (issue: 202514, release_date: 2025-04-11) and fluview_meta reports 202514 as the latest_issue.

Actual Result:

Data for epiweek: 202514 is missing for state-level regions tested (e.g., tx), leading to either incomplete results or "result": -2 ("no results").

Supporting Response Snippets:

• National Success (Step 1 Response Snippet):

  {
    "epidata": [
      // ... entries for 202511, 202512, 202513 ...
      {
        "release_date": "2025-04-11",
        "region": "nat",
        "issue": 202514,
        "epiweek": 202514,
        "lag": 0,
        "num_ili": 58543,
        "num_patients": 2351254,
        // ... other fields ...
        "ili": 2.48986
      }
    ],
    "result": 1,
    "message": "success"
  }

• Texas Partial Success (Step 2 Response):

  {
    "epidata": [
      {
        "release_date": "2025-03-21", // Note: Older release date for this specific data point
        "region": "tx",
        "issue": 202511,
        "epiweek": 202511,
        "lag": 0,
        // ... other fields ...
        "ili": 4.39669
      }
      // *** No entries for epiweek 202512, 202513, 202514 ***
    ],
    "result": 1,
    "message": "success"
  }

• Texas Failure (Step 3 Response):

  {
    "epidata": [],
    "result": -2,
    "message": "no results"
  }

Question:

Is this discrepancy between national and state-level data availability for epiweek: 202514 known or expected (e.g., due to CDC reporting/ingestion delays for specific states)? Or does it potentially indicate an issue with the data ingestion for this release cycle?

Thank you for maintaining this valuable API.

[melange396]

Thanks for your thorough report! This is known but not expected, and is in the process of being corrected with #1638

[melange396]

This should be fixed now. Please reopen this issue or create a new one if you have further concerns!