Adequacy Measurement Log
One row per request, measuring the gap rather than asserting it
This is the sheet the request is built on. Every column exists because a payer reviewer can check it, and the two derived columns on the right are the entire argument.
| Request | Payer | Specialty | Patient county | County type | Published max minutes | Published max miles | Nearest in-network minutes | Nearest in-network miles | Minutes excess | Miles excess | Directory read date | Accepting new patients | Standard cited |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The two derived columns
Minutes excess is the measured drive time to the nearest in-network provider of that specialty minus the maximum the plan publishes for that county type. Miles excess is the same subtraction in distance. Positive on either one is a measurable gap. Negative on both means there is no adequacy argument here, and the row says so.
Standard cited, and where it comes from
Either the plan's own published network standard or, for a Medicare Advantage plan, the time and distance table in regulation. Record which, because they are different numbers and the reviewer will check against the one you named.
Three columns for the second argument
Directory read date, accepting new patients, and waitlist quoted. A directory listing is not access if the practice is closed to new patients, and a fourteen week wait is the fact that makes a request about continuity of care rather than geography.