FyzioDesk
Software for running a physiotherapy practice, built for Slovakia and Czechia. The calendar and online booking, client records and medical notes, exercise plans with video and adherence, invoices, and a portal where clients book, see their plan and message the clinic. An AI assistant drafts replies, notes and exercise plans for the therapist to check.
- Client
- My own product
- My role
- Product, design and all of the code
- Timeline
- August 2026 to now
- Status
- Live at app.fyziodesk.sk with a presentation site at fyziodesk.sk, mobile apps in progress
- Stack
- Node.js (Fastify), Next.js 16, React 19, Prisma 7, PostgreSQL 18, Redis, BullMQ, MinIO, Expo, Zod, Stripe, Claude API
- Web
- fyziodesk.sk


Why I built it
Physiotherapists in Slovakia and Czechia juggle a booking tool, a spreadsheet of clients, paper notes and exercise sheets printed from the internet. Before writing code I compared nine products, from local ones to Cliniko, Jane and Physitrack. None combined native apps for both client and therapist, photo documentation from the treatment table, and exercise adherence as the number that matters.
FyzioDesk is that product. A clinic, its rooms and therapists live in one tenant; each role sees only what it should.
The first clinics now find it through fyziodesk.sk, a presentation site in Slovak, Czech and English where anyone can ask for a demo practice of their own. Before settling on prices and the next features, I’m running a survey with practising physiotherapists in Slovakia and Czechia. I invited practices directly, and the questions go where a product usually guesses: what they use today and how happy they are with it, how many hours a week admin takes, how many clients don’t show up, what they couldn’t work without, what would stop them from switching, and at what monthly price it would start to feel too cheap or too expensive. Answers are saved after every step, so a half-finished survey still counts. The results only appear on the site once there are enough of them to mean something; until then there is no number at all, not an estimate.

Client record with a pain map
Structured notes from templates, contraindications that stay on top, and a body chart where the therapist marks where it hurts and how much. Medical records can’t be edited once saved: a correction is a new version that points to the old one.

Online booking
Clients pick a service, a time and enter their details. Confirmations go out with an .ics file, reminders 24 and 2 hours before.

Exercise plan
A home programme with video for each exercise. Clients tick exercises off and log pain; adherence is calculated, never stored, so it can’t go stale.

Reports
What was invoiced and what wasn’t, how much time no-shows cost, late cancellations and utilisation per therapist.
What came after the launch
- Client messages. Clients write from the portal and pick a topic; worsening symptoms go to the top of the queue. Replies can carry photos, PDFs or a saved template. The clinic can offer up to three free slots in a message, and the client confirms one with a tap.
- An AI assistant. In Messages it sums up the request, finds free slots that match what the client wrote and drafts the reply, so booking takes one click. For therapists it turns dictation into a structured note, summarises the client before a visit and drafts an exercise plan that the client sees only after the therapist publishes it.
- A tablet and phone app for staff, still in progress: several therapists can share one tablet, each with their own PIN, and the visit card has check-in, photos, notes, the body chart and exercise plans.
- Team and data. The owner manages the team and can download everything the clinic has (clients, appointments, records, invoices, plans, consents, messages) as a ZIP of CSV files. The download is written to the audit log.
- Subscriptions through Stripe. Monthly or yearly plans, a seven day trial without a card, and AI paid in credits per action.

AI assistant on the presentation site
The site walks a therapist through a day in the practice, compares FyzioDesk with a paper diary, shows the AI assistant on real screens and explains security in four parts: data in the EU, encryption, a record of every sign-in, and data that stays the clinic’s, with a processing agreement for each practice.

Home page
The calendar in the hero can be clicked. Visitors can book a 20 minute call or ask for their own demo practice, which runs for 24 hours.

On a phone
Visitors pick a version for solo therapists, clinics or massage therapists, and the opening picture changes with it.
Decisions worth mentioning
- Two layers of tenant isolation.Guards check membership in the app, and every table with a
tenant_idhas a PostgreSQL row-level security policy. The API connects as a role without superuser orBYPASSRLS, and refuses to start if that ever changes. - Double booking is impossible, not just unlikely.GiST exclusion constraints over time ranges stop a therapist or a room from being booked twice. A test fires 20 simultaneous bookings for the same slot and expects exactly one to succeed; it found deadlocks between the two constraints, now handled with retries and jitter.
- Medical notes are append-only.A database trigger rejects any change to the content of a saved record. Only the deletion flag may change.
- Č sorts after C.Name columns use an ICU collation for Slovak, so the client list is in the order a Slovak reader expects.
- Photos only with consent, links that expire.Files sit in private MinIO buckets. Uploads and downloads use presigned URLs that last ten minutes and are issued only after a permission check.
- An AI receptionist that can’t reach medical records.An MCP server gives an AI assistant six tools: find a client, today’s appointments, free slots, book, cancel, unpaid invoices. It uses the public API with an API key and has no route to medical records.
- The AI model never learns who the client is.The client’s name is not sent at all; the greeting is filled in on our side after the draft comes back. Emails, phone numbers, Slovak birth numbers and IBANs are stripped from the text, and so is the name in its declined forms (Zuzane, Zuzanou). Photos and attachments never go out. The assistant is off until the owner switches it on, nothing reaches the client or the calendar without a click, and each use is logged in the audit without its content.
- AI is paid per action, not per token.A reply draft costs one credit, a summary or a plan three. Credits are taken for the actual call and returned if it fails, and the same request asked twice comes from cache for free.
In numbers
- More than 20 API modules with over 340 routes, 87 database models and 95 migrations.
- 145 test files with more than 1,900 test cases, running against real PostgreSQL and MinIO in containers.
- Shared Zod contracts: availability, invoice status, adherence and QR payments are the same code in the API, the web app and the mobile app.
Invoices come with Pay by square and SPAYD QR codes and ISDOC export. Subscriptions and AI credits are paid through Stripe Checkout. Payment gateways for clients, SMS and push are wired and waiting for merchant accounts.
