All case studies

[ Case Study — Healthcare ]

AWEB Client & Module Store

Modular desktop platform and module store for AWEB — quentis' cloud-based practice software.

< 2 s

hardware login at the workstation

Industry
Healthcare
Services
Desktop Platform, Module Infrastructure
Stack
Electron, Next.js, TypeScript, PostgreSQL, Redis
Timeline
Ongoing project
01

The challenge

AWEB — the practice management software by quentis — runs entirely in the browser: appointments, patient records and billing are cloud-based, no server needed at the practice. But in day-to-day practice work that's exactly where integration breaks down: the browser has no line to the physical workstation.

Hardware keys for fast user switching, document scanners via WIA/TWAIN, the GDT device interface of lab and diagnostics equipment, local folders and structured mail communication — all of it is out of reach for a web app. The task: close this gap without touching the web app itself — it stays with quentis.

02

Our approach

Instead of a browser plugin or a monolithic desktop port, we built a modular desktop platform. AWEB Client is an Electron runtime for Windows that embeds the web app and extends it via a plugin system: modules load dynamically, declare their permissions through a capability model and bring their own UI overlays — panels, sidebars, widgets, full-screen views.

Alongside it sits the AWEB Module Store as the central distribution platform: module catalog, license models per station, user or tenant, an admin dashboard with a role system and audit log, plus a self-service portal where tenants activate and configure modules without IT support.

The critical part was distribution: every module package is signed server-side and delivered encrypted per station. The client verifies signature and key before loading — extensibility stays controlled without turning the store into a single point of failure: if it's unreachable, the client keeps running under grace periods.

03

The outcome

The platform runs in production at medical practices: stations register themselves with the store, modules are licensed and rolled out centrally, and new features ship as modules rather than on-site update appointments. iButton login takes under two seconds; scans land directly in the record.

What started as a desktop extension for a web app is now the module and licensing infrastructure behind AWEB workstations — and documented as a standalone in-house product on this website: AWEB Client.

[ Delivered ]

Delivered

  • Electron desktop client with plugin runtime & overlay UI
  • AWEB Module Store (module catalog, licenses, rollout)
  • Signed, per-station-encrypted module distribution
  • Capability-based permission model for modules
  • 8 production modules (iButton login, scan & GDT, mail, etc.)
  • Station management with self-registration
  • Admin dashboard & self-service portal for tenants
  • Offline operation with grace periods
  • Audit log & role system

[ Contact ]

Planning something similar?

Tell us what you want to build — we will walk you through how we would deliver it.

Discuss your project