01 / ContextThe question
behind the work.
Radiology AI is often presented as a model score, while the harder operational questions remain unanswered: who reviews the output, how versions are traced, what happens after an override, and how quality and governance are measured over time.
My role
I designed and built the complete MVP: product specification, FastAPI backend, PostgreSQL schema, worker orchestration, imaging-model paths, review workspace, audit and feedback systems, SQL marts, Power BI package, tests, and documentation.
03 / In detailA workflow around evidence
I designed Radiology Value Pipeline around the work that follows an imaging prediction. A study enters through a normalized ingestion contract, moves through an ordered pipeline, and leaves behind structured findings, urgency suggestions, report drafts, feedback events, final reports, discrepancy records, and audit history.
FastAPI handles the product APIs, PostgreSQL holds the operational state and lineage, and a database-backed worker claims jobs with row locking. The modular-monolith design keeps the system runnable and understandable while preserving clean boundaries for ingestion, pipeline services, reporting, feedback, governance, and dashboard marts.
MRI evidence boundary
The MRI evaluation includes 20 real public CUDA volumes from the public MSD Task01 BrainTumour dataset. Those runs cover prediction conversion, scoring, review overlays, and candidate cards. The 120,000 deterministic robustness, acceptance, conversion, and contract evaluations are separate engineering checks across synthetic failure modes and workflow gates; together the tracked engineering total is 123,020 case-evaluations.
The public MRI cohort ran with a 240 x 240 x 160 ROI. It completed with mean whole-tumor Dice of 0.9202, mean region macro Dice of 0.8411, mean whole-tumor HD95 of 7.3455 mm, and mean whole-tumor 2 mm surface Dice of 0.2970. The 2D held-out benchmark macro AUC was 0.9828. Every candidate card remains reject_for_more_evidence.
The product surface
The browser workspace gives a reviewer the study context, image preview, candidate findings, model posture, evidence references, draft report, feedback controls, discrepancy events, agent ledger, and audit trail in one review surface. Structured findings come before the human-readable report text, which keeps the information usable downstream.
I also built SQL-first marts and Power BI outputs for operations, clinical quality, governance, model inventory, and agent lineage. The portfolio run processed 76 studies, stored 129 candidate findings, recorded 304 workflow-agent runs, and produced 858 dashboard fact rows.