BlueBee: A Local-First EHR for Orthopedic Clinics

A local-first desktop electronic health record for orthopedic clinics — patient records, longitudinal joint and lab assessments, scheduling, configurable forms and statistics, all stored on the clinic's own machine.

A local-first desktop electronic health record for orthopedic clinics — patient records, longitudinal joint and lab assessments, scheduling, configurable forms and statistics, all stored on the clinic's own machine.

🐝 BlueBee: Clinical Records That Never Leave the Clinic

An orthopedic clinic runs on continuity: the same patient, the same joints, measured again and again over months. Cloud-first software charges a subscription for the privilege of holding that history somewhere else. BlueBee takes the opposite position. It is a desktop electronic health record that keeps every record on the machine in front of the doctor — offline, instant, and answerable to no one but the clinic.

What it does

  • Patient records. Demographics, presenting history, HLA-B27 and smoking status, and a structured comorbidity panel, captured in one place.
  • Longitudinal assessments. Per-visit entries for joint involvement, general symptoms, and the activity indices clinicians actually use — BASDAI and BASFI — alongside lab values and current medications. New visits clone the previous one so the common case is a few edits, not a blank page.
  • Scheduling. A calendar line, upcoming and missed appointments, and a next-appointment picker.
  • Search built for the waiting room. Filter by active, upcoming or missing, narrow by date range, and configure which columns appear in the results table.
  • Statistics. A chart page for tracking a practice or a cohort over time.
  • A form designer. Assessment sections and fields are defined in editable JSON, so a clinician can shape the intake form to the clinic's own protocol without a developer.

Local-first is an architecture, not a feature

The application shell is Electron, and the data boundary is drawn at the IPC seam: the main process owns storage, configuration and export, and the renderer reaches them only through a small bridged API. That keeps file access out of the UI, makes the desktop build the real product rather than a wrapper, and means the app keeps working when the internet — or the practice's patience for another SaaS invoice — runs out. The assessment layout is data: the same config drives both the form the clinician fills and the columns the search page shows.

Tech stack

TechnologyRole
ElectronDesktop shell and file-system owner
React + TypeScriptTyped renderer and UI
MantineComponent system, dates and notifications
ZustandLightweight application state
ViteFast dev server and builds

The result

BlueBee reached a working, feature-rich prototype with the full clinical loop — record, assess, schedule, search, chart — running entirely on-device. It is the studio's clearest statement that the right place for a clinic's data is the clinic.

Project Details

Year

2024

Also known as

بلو بي: نظام سجلات طبية محلي لعيادات العظام

Tags

HealthcareDesktopLocal-firstEHR

Tech Stack

ElectronReactTypeScriptMantineZustandVite

Achievements

  • Config-driven assessment forms, editable in-app
  • Longitudinal BASDAI/BASFI scoring over time
  • Fully offline, on-device records — no cloud required

Start a project

Get in touch and let us help build your next project.

Start a conversation ابدأ المحادثة