Back

LinkLog

Reduced time spent on year-end reporting, shipped in 6 days.

Applying service design concepts, we built a working CRM for older-adult healthcare workers and admin to improve tedious and time-consuming workflows in the service.

I led the actual build, but also assessed the service end-to-end to see where design improvements could be made.

LinkLog Making Reports Easy banner
Role
Service Designer + Builder
Tools
Codex, Claude, Gemini, Figma
Team
4 (UofT course)
Duration
6-day sprint
Overview

What is Social Prescribing?

Social prescribing is a structured way to route people from a clinical encounter to non-clinical community supports such as housing, fitness, food security, and social connection.

A Link Worker is the human liason connecting people to the community supports, often working in a SALC.

A SALC is a community centre that provides social prescribing services.

OACAO is the provincial body that funds the centres and collects their year-end data.

The Problem

Every SALC did their year-end report by hand.

In interviews, Link Workers described having to cross-reference paper binders and Excel sheets for patient data, taking days to do the report.

The Challenge

How do we reduce the time spent on the year-end reporting for link workers, while giving OACAO's high quality data for funding grants?

One source of truth for client data

Link workers can import any spreadsheet into a standardized Client Directory, ending the duplicate and manual entry across local files.

Video thumbnail
A client-directory that fits your data

Auto-populated year-end reports

Form fields fill themselves from the Client Directory, so Link Workers go from reconstructing a year of work to reviewing it in minutes.

Video thumbnail
Forms that auto-populate

Admin reporting dashboard

OACAO sees aggregated outcomes across every SALC on the platform; exportable as CSV, viewable as interactive charts, and ready for funding renewals.

Video thumbnail
Program level metrics for admins
Discovery

Every centre tracks differently.

Interviewing 10 SALCs, each described a different way of managing clients, but OACAO's year-end report asked for data they didn't keep in one place, or didn't keep at all.

"I don't know if you know all about the reporting process, but it's, it's like a three-day event to try and do the final report."

A Constraint

The service dealt with PHI

Personal health information in Ontario is governed by two laws: PHIPA, which regulates how health information custodians collect, use, and disclose patient data, and PIPEDA, Canada's federal private-sector privacy law. Our designs had to comply with both, or OACAO could not proceed with our work.

Video thumbnail
The built Client Directory with its follow-up queue, normalized from whatever sheets a worker imported.
Video thumbnail
The CTT review, generated from existing client records rather than a blank form.
Video thumbnail
The OACAO dashboard: aggregated, de-identified outcomes across centres, exportable for funding renewals.
Video thumbnail
Codex writing the backend, Claude Code reviewing its pull requests, privacy requirements checked against policy in Gemini Deep Research.
Outcomes

Currently in cosideration to build

Of all the demos presented (in class), ours was deemed most impactful, ready to implement, and will be piloted in the next fiscal year with 3 SALCs.

Takeaways

The service design mindset

Learning to look at problems more wholistically helps me better surface the intent and purpose behind future design desicions. I look forward to taking this mindset to future problems i tackle.

AI as a conversation starter

With only six days, we could have stopped at a prototype. However building it with AI meant OACAO could log in and react to something real which led to the conversation of piloting at future SALCs. With restraint and careful execution, I plan on building more, and showing how my design solutions could be implemented in real settings.