Skip to main content
bluespaceSTUDIODiscuss a project

CASE STUDY / LABLINK

LabLink: Clinic-facing lab report portal

A Softr portal connected to Airtable for clinic-facing report access and internal record management.

BLUESPACE STUDIO / SOFTWARE ENGINEERING
01 / THE PROBLEM

What needed to work.

Clinic users needed access to reports while the operating team maintained patient, clinic and report records.

02 / WHAT WE BUILT

The delivery.

Clinic-facing report and patient views, separate administrative views and operating guidance for the underlying Airtable data.

The work behind report access

LabLink coordinates laboratory reports for clinics. Its internal team needs to maintain patient, clinic and report records. Clinic users need a useful place to find information associated with their own work.

The engagement brought those needs into a clinic-facing portal and a separate administrative workflow, rather than attempting to replace every part of the operating process.

What we implemented

We configured a Softr portal connected to Airtable, with report lists and detail views, clinic-level access and distinct clinic/admin presentation.

The two audiences had different responsibilities: clinic users needed to find relevant reports, while the internal team maintained the source records that powered the interface. Portal launch and subsequent operating discussions included clinic-user access and the way records were updated.

A source-data decision that mattered

The team needed a dependable boundary between internal data-management work and the interface clinics used. We separated the working views used internally from those relied on by the portal. Both still depended on the shared source data being kept accurate.

Delivered scope and later improvements

The original delivery covered the portal, its clinic-facing report access, administrative presentation and connection to source records.

After the original delivery, the team discussed ways to make new reports easier to find, improve notifications and reduce manual uploading. Those ideas were considered for a further phase, separate from the portal delivered.

Planning a client-access workflow?

The useful questions begin with who owns the records, who should see them and how the team will keep them current. A client portal is only as useful as those rules and the operating process behind it.

Discuss a client portal · Explore client portal services

START A CONVERSATION

Need something similar?

Tell us about your users and workflows. We'll discuss fit and what a useful first phase could look like.