"Where's My Auth?" answers the one question a patient actually asks: what happened to my prior authorization?
When your doctor's office sends a prior-authorization request under the CMS-0057 Prior Authorization API, the payer answers with a FHIR ClaimResponse. That answer is machine-readable — but "machine-readable" is not the same as "readable." This tool takes that ClaimResponse and reads it back in plain language: approved, partially approved, denied, pended (still under review), or — honestly — no status stated yet.
The honest part is the point. A prior-auth decision can arrive three ways, and they are not equally trustworthy:
- as a coded review action (an X12 306 decision code) — the strongest signal, a structured field the payer set on purpose;
- as free text in the response's disposition — the payer's wording, which the tool shows you verbatim instead of paraphrasing it as fact;
- or as nothing decisive at all — in which case the tool says "no status stated," never a guessed approval.
It always tells you which of those it used, and points at exactly where in the payload it read it. A denial is a denial; a maybe is a maybe; a blank is a blank.
This is a teaching tool. It reads a synthetic FHIR ClaimResponse you paste and runs entirely in your browser — it does not contact any payer, and it does not send your data anywhere. Try it with a built-in synthetic example: Where's My Auth?.
Under the hood it reads the inquiry-response side of the same PAS plumbing the FHIR Analysis Workbench validates — one corner of the CMS-0057 four APIs. If you are new to why any of this exists, start with what prior authorization means when you're the patient.