- expiring_appeals / slow_payer / underpayment no longer get the denial-spike
charts sliced by payer alone (one bar per department x code)
- weekly and recovery rows folded to their chart grain
- replayed mornings show only the trend, cut at the replay date
- new charts: payer speed (slow_payer) and appeal scorecard
- y-axis ticks no longer clipped at two digits
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The review now cuts by procedure and by provider, and checks paid vs allowed
for short-payments. The Run review page lists the checks and the thresholds
that apply to each.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Every user-facing string rewritten from a narrator's voice into an
application's. "What she wants you to approve" is now "Recommended actions";
"Her evidence" is "Query log"; "Watch how she did it" is "Activity trace";
"The full story" is "Analysis"; "Ava is reviewing" is "Review in progress";
"Nothing needs your attention this morning" is "No findings". Chart captions
state what the chart shows ("Gray: 8-week baseline · Blue: last 6 weeks")
instead of commenting on it ("One insurer moved").
The AI is an attribution — "AI analysis · Ava · Confidence 97%" — not a
character the page talks about. Labels are nouns, hints are facts, and the
queue and action names use the workflow's own vocabulary (Approve actions,
Request changes, Resume review, Close case).
Same treatment on the exported slides: Summary, Trend, Comparison, Recovery,
Recommended actions, Method.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Recommendation titles were cut at the first period, so "$1.56M billed"
rendered as a title of "$1" and a body starting "56M". The split now breaks
only on a period followed by a space, a colon, or a newline — decimals and
codes like CO-197 survive.
Her evidence counted every attempt on the case: a run that failed to submit
leaves its queries in the trace beside the run that succeeded, and 16 + 20
read as "36 database queries". The panel now scopes to the attempt whose
decision was submitted (trace events carry decision_id), so the count is
what she actually did to reach these findings.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A case now carries pictures, and a button that turns it into a deck.
THE CHARTS (Briefing.tsx) answer the same three questions the page does,
visually: the spike (the flagged slice's weekly denials, with the payer's
rule change drawn as a line — weeks after it in the accent, before in gray),
where it sits (denial rate by insurer, baseline vs now), where the money
stands (the slice's denied dollars by what can still happen to them), and
appeals about to expire by insurer. Every chart has a table twin.
Data comes from six pre-aggregated Databricks views (sm2/…/chart_views.py)
read through the ordinary record-view API, filtered by the slice Ava now
records in four structured fields (slice_payer, slice_department,
slice_reason_code, spike_start). Nothing is computed from raw claims in the
browser.
COLOUR WAS COMPUTED, NOT EYEBALLED. The palette is the dataviz reference
set (blue 1, orange 2, green 6, violet 7, gray) run through
validate_palette.js against this console's own surfaces, both themes — all
checks pass. Two things the validator caught: the brand teal fails the
chroma floor and would read as gray on a chart, so it is never a data hue;
and red beside orange in the recovery stack fails adjacent-pair separation
even for normal vision (ΔE 7.1), so "lost on appeal" is violet.
THE SLIDES (lib/slides.ts) are six native-chart PowerPoint slides built in
the browser with pptxgenjs from the same rows: what happened, the spike,
where it sits, the money, the recommendations, the method. Text is Ava's
verbatim. Lazy-imported so the 700 KB library is paid for only on click.
Backend counterpart: sm2/custom-apps/denials-investigator/10_briefing.sql.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Case 58325 died submitting findings: the submit_decision call arrived with
no `data` at all. The final model reply was exactly 4,096 output tokens —
the service's cap — so the JSON was cut off mid-call. Asking Ava to paste
16 full SQL statements into sql_log, on top of a summary, root cause, five
recommendations and a scanned-summary, is what pushed one tool call past
the limit and lost the whole investigation.
The platform already records every statement the agentic tool sends,
verbatim, with Databricks' own SUCCEEDED/FAILED and the row count. So
SqlEvidence now renders from the trace and treats sql_log as a one-line
index per step. Her charter gained hard per-field character limits to
match (sm2/custom-apps/denials-investigator/05_ai_employee.sql).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Rebuilt the two screens for a person with ninety seconds, not an analyst.
Every screen now answers, in order and at descending size: what happened
(one sentence, 21px), how much (three numbers you can read across a
table — claims denied, money at stake, still recoverable with its first
deadline), and what she wants approved (the ranked list, with the decision
buttons directly under it). The full analysis, her SQL and the live trace
sit behind disclosures — one click for the reviewer who wants to check,
zero clutter for the manager who does not.
The queue opens on a briefing strip: "1 decision waiting for you —
$1,091,000 recoverable". A manager who reads only that line has the day.
Cards lead with the verdict sentence and the recoverable figure; a waiting
case says "Needs your decision", not "Awaiting Review".
Jargon translated where a business reader meets it: "data reconciled"
became "Numbers checked against Finance"; "97% confident" became "Ava is
97% sure"; the trace steps read "Asked the data" and "Thought about it".
Ava's SHOUTED recommendation headings are sentence-cased.
While Ava is still working, the trace is the page — there is nothing else
to show yet, and watching her query is the demo.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Start Investigation is gone. The daily review is the only way a case is
born — "she isn't asked" should not ship with a button for asking her. A
person still steers Ava, but only about something she already found:
Send Back to Ava carries the note.
Removed the ask-a-question screen, route and ghost button; the case page's
"request" card now says how the review came to exist (live, or a replay of
a past morning) instead of echoing a question nobody typed.
Backend counterpart: sm2/custom-apps/denials-investigator/09_one_front_door.sql.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The primary action is now "Run daily review": no form, no question. It
starts the new INIT door dni-act-review, which is the same activity a
scheduler performs at 6am; the button exists so a room does not have to
wait until 6am. Ava sweeps every payer, department and front desk against a
materiality bar and, if nothing clears it, records "nothing to report" and
closes the case herself — it never reaches a desk. "Ask a question" stays,
demoted to a ghost button, for the follow-up path.
A second button replays a quiet morning: the demo data is static, so every
live sweep would flag the same August spike. Anchoring one run on
2026-07-26 lets it genuinely come back empty, and the contrast — one quiet
morning beside one $1.09M morning — is the pitch.
Queue cards and the case page now carry the sweep outcome: what she
reviewed, how many patterns she flagged, and what kind (payer rule change,
front desk, expiring appeals, …). A closed quiet case reads "Nothing to
report" rather than "Closed", because those are different outcomes.
Backend counterpart: sm2/custom-apps/denials-investigator/08_daily_review.sql
and the sweep-first charter in 05_ai_employee.sql.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The operator console for Northlake Health's Denials Investigator (dev, org
900000109 / app 900000102). A revenue-cycle manager asks why claim denials
rose; Ava — an AI employee — investigates the hospital's Databricks lakehouse
and comes back with a cause, a dollar figure and a recommendation. He approves,
and she re-checks on her own two minutes later.
THE POINT OF THE SCREEN is that her work is checkable. Anyone can be told an
agent analysed their denials; AvaLive shows the actual SQL she sent to
Databricks, in order, with what came back and how long each query took — and it
does NOT hide a query she got wrong and corrected, because that is the most
convincing thing on the page.
Two decisions worth knowing about:
* Her trace does not come from the AI-employee monitor API. That endpoint needs
an org-scoped studio token and answers "no organization scope on this
account" for every user of this console. It comes instead from two views
(northlake_app.ava_trace / ava_decisions) exposed as ordinary rdbms record
views, behind a login role that cannot read the aiemployee schema at all.
Seeded by sm2/custom-apps/denials-investigator/07_console_views.sql.
* Ava's own activities — Record Findings, Confirm Recovery, Flag Still
Elevated, Escalate — are deliberately absent from STAGE_ACTIONS. Putting them
on screen would only let a person sign in as the agent and press its button,
which is a person impersonating an agent rather than an agent working.
Violet is the AI and nothing else is violet; amber is the one queue a human
owns. No API URL is compiled in — config.js carries it at placement time.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
