Skip to main content
Glama

Pbm Compensation Rollup

pbm_compensation_rollup
Read-onlyIdempotent

Sums Form 5500 Schedule C direct + indirect compensation for a named PBM across one or more plan years. Every aggregate runs SERVER-SIDE in SQL over the whole matching population; the per-provider-name and per-plan-year rows the total is made of ride the answer, and each alias spelling carries its own measured attribution. M-6 alias chain resolves OptumRx -> OPTUMRX + OPTUM RX + Catamaran (post-2015 acquisition), Express Scripts -> ESI / ESI MAIL PHARMACY, CVS Caremark -> all variants; a name that is NOT a registered alias_form says so instead of silently searching one literal string.

Reference demo (re-measured live 2026-08-01): OptumRx plan year 2023 -> $1,461,686,909 direct comp across 295 plan-filings and 295 provider rows, attributed OPTUMRX $1,036,556,258 / OPTUM RX $425,110,391 / Catamaran $20,260.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pbm_nameYes
year_maxNo
year_minNo
detail_limitNo
acknowledge_era_breakNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitNo
as_ofNo
valueYes
sourceYes
statusNocomplete
caveatsNo
failureNo
qualityNo
refusalNo
vintageNoas_restated
audit_idYesUUID; ties to medicare_silver.audit_log row.
signatureNo
tenant_idNoCalling tenant slug, resolved by the binding and stamped via the per-call tenant context. Defaults to the bootstrap 'internal' tenant for local/in-process callers.
timestampYes
confidenceNo
data_as_ofNo
request_idYes
methodologyNo
snapshot_setYes{table_fqn → iceberg_snapshot_id (int64)}. Per M-2 §2.2.
tool_versionYes
response_hashYesSHA-256 of canonicalized form per M-2 §2.4.
result_statusYes
vintage_basisNodefault_unmeasured
as_of_assertedNo
as_of_observedNo
parse_revisionNo
as_of_effectiveNo
freshness_stateNounknown
methodology_eraNo
confidence_basisNo
semantic_versionYes
invariants_appliedNo
finality_confidenceNo
cms_vintage_sequenceYes
parser_artifact_hashYes
methodology_blend_factorsNo
parser_artifact_hash_basisNonot_evaluated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources