Clinic platform
Internal tool. Screens recreated for confidentiality. No public link.
The clinic makes the insoles and stays their manufacturer. The platform is the tool it designs them with, and I don’t market it as a medical device.
Sites and software for clinics, by someone who has built a clinic platform.
Patient records, 3D tooling in the browser and a line to the 3D printer, in one multi-clinic platform I designed and built. I’ll show you how it works, and say plainly what needs a compliance check.
The drawing is live. Drag the cutting plane through the insole.
- From the heel
- 118 mm
- Width at the cut
- 57 mm
- Highest point
- 17.8 mm
What I have built
A platform that takes a clinic from a scan to a finished insole.
Features only. What a clinic does with them is the clinic’s decision.
One workspace per clinic
Each clinic has its own space, its own staff and two roles. An admin invites people; nobody sees another clinic.
Patient and project records
A patient has projects. A project has its scans, its designs and a status. Records are archived, never silently lost.
3D insole design in the browser
A pair of foot scans goes in. The practitioner sets heights, widths and pads with sliders and sees the shape change as they drag. The software does what it is told and decides nothing.
A line to the 3D printer
A small program on the clinic’s own computer picks up a finished design and prepares it for the printer. A mill is supported too.
Settings for the clinic’s own paperwork
The clinic keeps its standard texts and company details in one place, so the documents it has to produce for its own regulatory file come out the same every time.
What I build for clinics
Three things, at the same prices as for anyone else.
There is no health surcharge. Compliance documents are quoted separately.
A patient-facing site
What you do, who it is for and how to book, written to be read on a phone in a waiting room. Booking and intake forms that ask for no more than they need.
from €16k
3–5 weeks
How that works: a patient-facing siteA clinic tool
Records, planning or production, built around how your clinic already works. One workflow first. A larger system is the product scope.
from €18k
3–5 weeks
How that works: a clinic toolAn app
For patients or for staff, on iOS and Android from one codebase.
from €32k
6–10 weeks
How that works: an app
Allow one to two extra weeks for your clinic’s own review. Prices excl. VAT.
Four ideas I’ve drawn for clinics
- Concept
A request desk
Incoming requests land in one queue, sorted by rules the clinic wrote, each with the reason it was put there. A person at the desk decides. It makes no clinical call.
- Concept
A document reader
Letters and forms are read into fields, with every field pointing at the words it came from. Unsure fields stay marked until someone checks them.
- Concept
A production board
What is being designed, what is printing and what is ready to fit, on one board, so nobody walks to the printer to ask.
- Concept
A no-show and recall manager
A cancelled slot is offered to the people on the waitlist it fits, and refills. Slots at risk carry a reason, never a score.
Concepts I drew to show the idea. They are not client work. See them in Explorations
How I handle data
Where patient data lives, and who can see it.
Samples, with made-up patients. Yours are drawn in week one.
The browserA practitioner’s or a patient’s deviceStoredNothing after sign-outWho sees itOnly what that person’s role allows
EU hostThe app and its database, in a region you chooseStoredRecords, files and the access log, encrypted at restWho sees itClinic staff, by role
BackupEncrypted copies, also in the EUStoredA daily copy, kept for a period set in the DPAWho sees itNobody in normal use. A restore is logged
MeThe person who builds itStoredMade-up patients onlyWho sees itLive data only under the DPA, for a stated reason, logged
From the browser to the EU host, then into an encrypted backup. It does not leave the EU.
I build on made-up patients. My line to live data is dashed: only under the DPA, for a stated reason, and the log shows it.
A sample for a clinic tool. Yours is drawn in week one and goes into the data processing agreement.
- Sheet
- H-01
- Title
- Data flow
- Status
- Sample
| What | Where it lives | Who can see it | Kept for |
|---|---|---|---|
| Patient records | Database, EU host | Clinic staff, by role | As long as your retention rule says |
| Files, such as 3D scans | File storage, EU host | Clinic staff, by role | With the record they belong to |
| Access log | Database, EU host | Clinic admins | A period set in the DPA |
| Backups | Encrypted, EU | Nobody in normal use | A period set in the DPA |
| Sign-in session | The browser | The person signed in | Until sign-out |
| Made-up patients | My machine and the test site | Me, and whoever reviews | For the length of the build |
I give you the data map for your DPIA. The assessment is yours to sign.
- Sheet
- H-02
- Title
- Data map
- Status
- Sample
- 09:14PractitionerOpened recordDemo patient 014
- 09:15PractitionerEdited projectDemo patient 014
- 10:02Front deskOpened recordDemo patient 031
- 11:40Clinic adminExported the access listAll staff
- 13:05Builder (DPA)Opened record. Reason: bug report 27Demo patient 031
My own access is a line in the log like anyone else’s. The clinic can also print the list of who has access to what.
Access by role, a log of who opened which record, and encryption in transit and at rest.
- Sheet
- H-03
- Title
- Access log
- Status
- Sample
Where the database runs is a setting. You pick it, and I show you where it is set.
- Frankfurtpicked in this sample
- Paris
- Ireland
- Stockholm
The four EU regions one database host offers today (Supabase (opens in a new tab)). On some hosts, server functions run in the US unless a region is set (Vercel (opens in a new tab)). I set it.
Hosted in an EU region you choose, on providers that publish their security attestations.
- Sheet
- H-04
- Title
- Hosting region
- Status
- Sample
Made-up patients
I build, and you review, on demo data. Nothing real is needed to judge the tool.
DPA signed
Before real dataReal data
Only now, in your system, by role, with every opened record written to the log.
What the agreement holds me to
- I work with the data only on your written instructions.
- Anyone who touches it is bound to confidentiality.
- When the work ends, I delete it or hand it back. Your choice.
- If something goes wrong, I tell you without delay.
I build the software. Your clinic stays the data controller, and we sign a data processing agreement before I see real patient data.
- Sheet
- H-05
- Title
- Order of signing
- Status
- Sample
What I will not claim
No badges. Here is what I say instead.
I’m one person who builds software, not a certified body. A lawyer should read anything you rely on.
I won’t sayWhat I say instead
“GDPR compliant” or “HIPAA compliant”, as a label on me or on what I ship.
I build the software. Your clinic stays the data controller, and we sign a data processing agreement before I see real patient data. I haven’t done US patient-data work yet. If you need a BAA, raise it on the call and we settle it before anything else.
“MDR compliant”, “CE marked”, “medical-grade” or “clinically validated”.
Whether a feature makes software a medical device depends on what it is meant to do. I check that with you feature by feature, before I build it. Where it helps, it has fields and exports that support your own MDR paperwork.
ISO 27001, ISO 13485 or SOC 2 as my own. Hosting providers hold those. I don’t.
Hosted in an EU region you choose, on providers that publish their security attestations.
“Secure”, as if it were a yes or a no.
Access by role, a log of who opened which record, and encryption in transit and at rest.
Software that makes a clinical call.
AI features are labelled as AI, a person decides, and they make no clinical calls.
A DPIA done for you.
I give you the data map for your DPIA. The assessment is yours to sign.
“WCAG compliant” or “EAA compliant”. That takes an audit.
Built to WCAG 2.2 AA and tested with a keyboard and a screen reader. You can measure this page yourself, below.
Accessibility, measured on this page.
Saying a site is accessible is easy. So here is a button that measures this one, in your browser, and draws what it finds on top of the page. If something fails, you’ll see it in red.
Nothing measured yet. The numbers appear here, and on the page, when you press the button.
FAQ
Questions clinics ask first.
In an EU region you choose, on providers that publish their security attestations. I show you where the region is set, and the data map lists what sits where.
Your clinic. I build the software. If I need access to real patient data I am a processor, and we sign a data processing agreement first. Until then I work on made-up patients.
Whether a feature makes software a medical device depends on what it is meant to do. I check that with you feature by feature, before I build it, and with a regulatory adviser when it is close.
Yes to a data processing agreement, before I see real patient data. I haven’t done US patient-data work yet. If you need a BAA, raise it on the call and we settle it before anything else.
Only where you ask for it, and never to make a clinical call. AI features are labelled as AI and a person decides. An assistant that talks to patients says that it is one.
I build to WCAG 2.2 AA and test with a keyboard and a screen reader. I don’t call it compliant, because that word needs an audit. The button further up measures this page, so you can check my work on the spot.
The same as any project of that size: a patient-facing site from €16k, a clinic tool from €18k, an app from €32k. Compliance documents are quoted separately. Allow one to two extra weeks for your clinic’s own review.
A 20-minute call, then week one: I map the workflow, draw the data flow for your case and build a first version on made-up patients. You can stop at the end of that week and I refund it.
Guarantees
Four promises, in writing.
Fixed price
No overrunsThe price on the quote is the price. If I underestimated, that is my cost.
Staged payments
Stop after any stageYou pay per stage and can stop after any stage.
Week one
Refunded if you stopWeek one is a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full.
Revisions
Until you sign offChanges inside the agreed scope of a stage are included until you sign it off.
A clinic tool starts at €18k. Week one costs €3,000, and you get it back if you stop there.
Book a 20-min call