Orientation · before Baseline Week

Meet the Prior Auth Portal

For the next two weeks this system is your workplace. A member's procedure needs approval; a score decides its path; a clock starts either way. Here's the whole machine — and what you personally will do to it.


01 · One auth, start to finish

Four screens, one decision

1 · SUBMIT
PA PortalProvider: Lakeview Ortho
New request — MRI, lumbar spineMember M-3382 · CPT 72148 · attachments: 2 clinicals
STANDARD · 72Hor mark EXPEDITED
Intake. A provider submits; urgency sets the clock. Clean wizard, deliberate friction where regulation demands it. (React · pap-web)
2 · SCORE
Decision engine41 seconds later
Confidence score: 0.87
0.60threshold 0.850.99
AUTO-APPROVEDmember + provider notified
The threshold. Score ≥ 0.85 auto-approves; below it, a human decides. This one number is the system's soul — and the villain of several cases. (Spring Boot · pap-api)
3 · REVIEW
Reviewer consoleQueue: 14
45h
Knee arthroscopy · 0.79needs clinical criteria check
3h
EXPEDITED · cardiac cath · 0.81SLA breach at 14:00
The queue. Every case wears its SLA as a shrinking ring. Nothing in this course is more honest than that little clock — Perf pack certifies it, the capstone cuts it to 24h.
4 · ACCOUNT
OperationsThis week
Denial rate8.4% ▲
SLA met96.1%
p95 auth-history query2.9s
The ledger. Where the business reads the system — and where your work shows up. That 2.9s is a planted defect three different roles will meet from three different directions.

02 · Feel the soul of it

You be the decision engine

Drag the confidence score
0.87 AUTO-APPROVED · 41s
Above the 0.85 line: no human touches it. Speed for the member — and total dependence on the scorer being right.

Hold that trade-off. It's the same one you'll manage all course long with AI itself: automation above a confidence line, human judgment below it, and everything depending on where the line sits and who verified the scorer.


03 · The machine room

Five repos, one estate

provider / member │ submit · poll · review ▼ pap-web React portal — submitter + reviewer console │ REST ▼ pap-api Spring Boot 4.1 · scoring · routing · SLA clocks │ SQL ▼ pap-db PostgreSQL 16 · 2M synthetic rows · zero real PHI ───────────────────────────────────────────── pap-perf-rig NeoLoad · LoadRunner TruClient · k6 shadow pap-workroom requirements · memos · ADRs · runbooks

Written like a real team wrote it — mixed styles, old TODOs, a git history with moods. Twenty-four planted artifacts hide in there, and at least eight of them will be visited by more than one role. Your role sees its lens; the cohort sees the whole.


04 · What you will walk out with

By the last stamp

QA / Test

A generated-then-mutation-proven suite covering the auth flow, and the review standard to sign off any agent's tests.

FILED: suite + mutation report + review checklist

Performance

NeoLoad scenarios and TruClient journeys that certify the SLA — then re-certify it at 24h in the capstone.

FILED: workload model + certification report

SQL / Data

That 2.9s p95 cut to milliseconds with defended EXPLAIN evidence, and migrations that survive the rollback drill.

FILED: optimization dossier + migration runbook

Architect

A spec and ADR set an agent can build from, governance that runs in CI, and the exec brief that wins the room.

FILED: spec + ADRs + guardrail policy

Engineer

Prior-auth agentic build and review fluency — then the bridge hands you to the full 10x Toolkit.

FILED: reviewed feature PR + hand-off map
And one number that's yours alone.

Baseline Week starts tomorrow: you'll do your role's tasks with no AI at all, on the clock. At the end of your pack you'll face the same tasks again, with everything you've learned. The delta — time, defects, rework — is measured, not promised. That's your evidence, in your numbers.

BEGIN BASELINE WEEK →