Phoenix Reviewer

Settings

The Supabase URL/anon key are hardcoded in the CONFIG object at the top of the script — that key is designed to be public, protected by row-level security, same as always. The AI provider key is NOT here anymore — it lives server-side as a Supabase Edge Function secret (supabase/functions/ai-extract), so it's never exposed to anyone viewing this page's source.

AI Configuration — Routing Thresholds

Controls which confidence score sends a field to Auto-Accept, Fast-Confirm, or Full Manual review. Tune these once you have real accuracy data — no code changes needed, saved to this browser.

Straight-Through Processing

When ON, a page where every field cleared the Auto-Accept bar above — AND nothing was flagged (possible duplicate, possible same-patient page still in queue, low-confidence diagnosis) AND the patient was matched with no ambiguity — is saved automatically, with zero clicks. Everything else still lands in the queue for review exactly as before. Off by default: this changes what gets written to a patient's record without a human looking at it, so it starts disabled until you turn it on deliberately.

Diagnosis and medication are treated more cautiously than other fields, since they're the two most consequential to get wrong silently. With the setting below OFF, a page containing either always goes to manual review no matter how confident the AI was. With it ON, a diagnosis/medication field can still qualify for auto-save, but only when it ALSO matches an entry in the learned vocabulary dictionary — confidence score alone is never enough for these two field types.

Scan or Upload

Uploading only happens from inside a patient's folder — this keeps every document tied to the right person and carton from the moment it's captured, instead of sorting that out afterward.

Scan or Upload

Queue

Review —

Original Enhanced

Patients

Patient Record —

Visit Timeline

Clinical Knowledge Graph

Relationships this patient's record forms across visits — recurring diagnoses, medication continuity, and known diagnosis↔medication pairings — not just a flat list of what happened on each date.

Source Pages

Accuracy Snapshot

Accuracy by Field Type

Today's Activity

From the workflow event log — every upload, extraction, and review is timestamped there.

Team Productivity

Infrastructure

CPU, GPU, memory, and service-availability metrics need a server-side monitoring agent — this is a browser-based client and genuinely can't see that. What it can tell you honestly: storage consumed by scanned images in this facility, below.

Recent Cases

Branches

Who can sign in to this facility

Unmapped Fields

Fields the AI found but couldn't categorize — each has its own printed label on the form. Resolve each one below by mapping it to an existing category, or promoting it to a genuinely new one. Resolving retroactively reclassifies every field already collected under that label — not just new ones going forward.

AI Case Findings

What the AI Case Manager noticed while reviewing — pages it automatically bundled into the same visit, and patient records created despite a flagged name-similarity warning. Acknowledge each once you've seen it; acknowledging doesn't undo anything, it just clears it from this list.

Your Facilities

Facilities where you hold admin access. Creating a new one makes you its first admin automatically, with a Main Branch pre-created.