BRIT Accuracy

A second scoring pass runs after all rate sources — Benchmarks, Raw, Imputations, and Transformations — are merged into one wide table per ROID. Each provider/rate type gets its own accuracy SQL with type-specific outlier bounds and scoring logic.

Why a Second Pass?

Raw accuracy scores all payer and hospital rate columns immediately after combined_raw is built — before imputations or benchmarks exist. BRIT accuracy re-scores everything after combined_brit merges all four layers, so imputation columns get scored for the first time, and previously scored raw columns can be re-evaluated with more context (e.g., benchmark columns now available for comparison).

BRIT Accuracy Tasks

Six type-specific tasks run in parallel, each reading from tmp_int_combined_brit and writing to its own table. Medical is split into three sequential sub-steps:

1

Drugs

Drug-specific outlier bounds (0.8–10× Medicare for payer; 0.8–4× for hospital). DPR exception: payer drug rates up to 1000% of Medicare allowed. CDF scoring disabled (is_drug_code=true → CDF=0).

→ tmp_int_accuracy_brit_drugs

2

Labs

Tight bounds: 0.2–4.5× Medicare. Lab rates cluster near Medicare, so the narrow window is appropriate. CDF scoring active.

→ tmp_int_accuracy_brit_labs

3

Medical — Rates

Scores all payer and hospital raw+transformation columns for non-IP (0.5–30×) and IP (0.9–10×) medical codes. Builds payer_rates_array and hospital_rates_array for counterparty checking.

→ tmp_int_accuracy_brit_medical_rates

4

Medical — Imputations

Scores imputation columns for medical ROIDs separately. Imputed rates use a different score ceiling (max score 4, not 7) — they can never beat a validated raw rate.

→ tmp_int_accuracy_brit_medical_imputations

5

Medical — Join

Combines medical rates + medical imputations into the final medical accuracy table. All columns (raw, transformed, imputed) with their validation scores in one row per ROID.

→ tmp_int_accuracy_brit_medical

6

Physician Groups

PG-specific: anesthesia codes get a hard dollar cap ($1–$200) in addition to the 0.5–5.5× Medicare multiplier bound. Scores PG-specific columns from core_rates_physician_groups.

→ tmp_int_accuracy_brit_physician_groups

7

DME

DME codes: 0.5–5.5× Medicare bounds. Scores DME rate columns.

→ tmp_int_accuracy_brit_dme

8

Urgent Care

Urgent care ROIDs scored separately. Applies standard medical bounds within the urgent care provider type.

→ tmp_int_accuracy_brit_urgent_care

9

BRIT Union

All 6 type-specific tables unioned into the final BRIT accuracy table.

→ tmp_int_accuracy_brit

What Changes Between Raw and BRIT Accuracy?

Dimension	Raw Accuracy	BRIT Accuracy
Input table	tmp_int_combined_raw	tmp_int_combined_brit
Columns scored	Payer + hospital raw columns only	Raw + transformed + imputed + benchmark columns
Chunking	By payer	By rate/provider type (parallel)
Counterparty arrays	Built here — used for raw score 7	Rebuilt with full data — final validated scores
Type-specific logic	None — one SQL for all types	Separate SQL per type (drugs, labs, medical, PG, DME, UC)

Medical 3-step design

Medical rates and medical imputations are scored separately before joining. This lets the imputation scoring use different score ceilings (imputed rates cannot reach score 7) without complicating the main rates SQL. The join step assembles the complete per-ROID picture for rate selection.

Output feeds rate selection

tmp_int_accuracy_brit is the final wide table with every rate column and its _validation_score for every ROID. Rate selection reads this table and picks the column with the highest score.