Payer graph · resolver
A claims system does not send a payer's name. It sends a path — TRUSTMARK SMALL BUSINESS - AETNA SIGNATURE ADMINISTRATORS (PPO) — in which the provider contracted with Aetna and the money comes from Trustmark. Type one and watch it come apart.
The box above is plain JavaScript over a 11.5k-key index, which is why it answers instantly on a phone. This panel loads a real DuckDB into the browser and points it at the same three Parquet files, withsilver.name_core() installed — the same macro the pipeline uses. Eight megabytes of engine to query 278 KB of data is a bad trade for the common path and a good one for proving the pack is a database and not a bespoke lookup.
How it works
Strip the trailing (PRODUCT). Match the whole string against the 59 payer codes a claims system writes instead of a name (BCBS-IL, GWH-CIGNA). Split the rest on - and : — a hyphen without spaces is part of a name. Drop product and program qualifiers, which are never parties. Normalise each remaining segment and look it up among 9,279 refs. Rank the readings: the leased network outranks the payer, and both outrank whoever administers the paperwork, because the question is who did the provider contract with. Every reading tied for the best role is an answer — Pennsylvania has three Blues territories and the code names none of them, so three answers is correct and picking one is not.