← Portfolio Working prototype

r3f3r

The referral follow-up tracker for one busy coordinator: log specialist referrals, see what is overdue at a glance, and chase every follow-up from one compact workbench.

Context
Personal project, public since Sep 2026. Built for the coordinator workflow: referrals come in, follow-ups slip, the overdue ones must stare back at you.
Stack
Vue 3.5, Vite, Spring Boot 3.5, Java 21, Oracle Database Free or H2. Fictional data only.
Role
Sole author
Repository
github.com/HeyItWorked/r3f3r (Public)

At a glance

Prototype
Status: working prototype
JUnit
Backend tests: controller and referral-rules suites
4
Due views: all dates, overdue, today, next 7 days
26 Sep 2026
Made public
01

What it is

r3f3r tracks specialist referrals for a single busy coordinator. You log a referral with its due date, and the workbench shows what is overdue, due today, or due in the next 7 days — stacked with text search and status filters so one view answers "what do I chase right now".

Day counts come from the backend, so the browser's timezone cannot move a referral between views. The whole thing is styled like a late-90s desktop workbench, on purpose.

02

What is implemented

  • Referral records with due dates, statuses, find search, and a single Due filter stacking all three.
  • Create, save and refresh toolbar against a Spring Boot REST API over Oracle Free, with H2 for local runs.
  • Overdue rows flagged in red at a glance; fictional seed data only, so the demo never touches real patients.
  • JUnit suites cover the controller and the referral rules on the backend.
03

Screens

The full r3f3r workbench: referral table with overdue rows flagged in red, filters, and the Create, Save and Refresh toolbar.
From the repository README: the full workbench with overdue rows flagged in red.
04

Verification

Checked on 26 Sep 2026 from the public repository: the backend ships ReferralControllerTest and ReferralRulesTest JUnit suites, and the README documents the local run against Oracle Free or H2. No frontend test suites ship yet.

05

Limitations

  • Single-coordinator scope: no multi-user roles, no authentication.
  • Frontend has no automated tests; coverage is backend-only.
  • Seed data is fictional, so there is no real-world overdue history to show.
GitHubr3f3r: source and READMEOpen ↗