Analytics Execution Compute Pipeline

Both the Optum commercial claims backend and the Epic EHR CDM expose a table named 'medication_fills'. A misconfigured routing rule causes the schema resolver to prefer the EHR backend for tables matching the 'medication_*' patte…

The dispatch layer resolves the logical dataset identifier 'commercial claims' exclusively to the Optum DOD backend. Execution metadata records backend_target='optum_dod', schema version, and fully qualified table path. The evidence summary explicitly cites 'Optum DOD commercial claims' as the data…

The claims backend was updated six weeks ago from claims_2023_v2 to claims_2024_v3 (new NDC mappings, added Q1–Q2 2024 enrollment data). The dispatch layer's cached schema manifest was last refreshed eight weeks ago and still map…

Before dispatching, the layer checks manifest TTL and detects it is stale (age exceeds refresh threshold, or a backend catalog probe returns a schema version absent from the manifest). It halts execution, alerts the user that the manifest is stale, identifies the version discrepancy (claims_2023_v2…

A malformed API request includes a SQL fragment embedded in the ICD-10 condition code filter field. The LLM-based query compiler interpolates the field value directly into a WHERE clause without parameterization, producing SQL th…

The dispatch layer inspects the full SQL text for DDL and DML statement types (DROP, CREATE, INSERT, UPDATE, DELETE, TRUNCATE, ALTER) before any connection is acquired. It detects the DROP TABLE statement, rejects the entire SQL with a security error, logs the injection attempt with the full offend…