With over 60 clinics operating across 16 European countries, FutureLife is a leading pan-European fertility provider – yet patients had almost no digital access to their own clinical data.

Before Bean, patients depended on clinic staff for basic tasks such as checking appointments, accessing invoices, or reviewing treatment information. The EMR (eBase) contained everything, but it was locked behind internal systems and processes. This created friction for patients, constant interruptions for clinic teams, and made it harder to drive adherence in long treatment cycles.

Bean is a secure patient portal that brings this data to patients in a usable way. Through a mobile‑optimised web app, patients can manage appointments, view medications, download documents, review invoices and pay them online. The platform integrates directly with FutureLife’s eBase EMR, synchronising data in near real time across multiple clinics and countries. The first production rollout happened within six months, and the platform has been continuously evolving since then.

Turn an internal EMR ecosystem into a patient‑centric service without compromising security or clinical workflows.

FutureLife had a mature EMR (eBase) holding appointments, invoices, medications, lab results and documents – but it was built for internal use, not patient consumption. The portal had to integrate with this without destabilising existing workflows, while delivering a modern, responsive experience.

Reliability was non‑negotiable. Patients need accurate information across devices and time zones. If an appointment changes in the EMR, it must reflect in the portal immediately. If a payment succeeds, both finance and the EMR must stay in sync.

Strategically, FutureLife wanted full ownership and independence. That meant transparent, documented architecture that their team could extend. It also required thinking ahead to internationalisation (including Czech language features), multi‑currency payments, and the ability to scale to new clinics by configuration – not re‑implementation.

WDF designed and engineered Bean as a complete platform – from architecture and UX to EMR integration and payments.

Bean is built as an API‑first platform. The backend exposes RESTful services that abstract eBase into patient‑friendly concepts: appointments, documents, invoices, medications. A React frontend consumes these APIs and renders a responsive, component‑based interface designed to feel straightforward to patients.

Key design priorities were ownership and long‑term maintainability. Integrations like Stripe and eBase sit behind abstraction layers so they can evolve without rewriting the portal. Webhook‑based payment flows avoid brittle polling logic. A dedicated notification subsystem supports different event types with clear state transitions.

On the frontend, the team focused on patient‑centred simplicity. Core flows – login, appointment overview, invoice payment, document downloads – work seamlessly on mobile. A Storybook‑based component library keeps the UI consistent as features are added.