Case: a gynecology clinic, its care flows and its website
Torn Studio builds websites, products and content with AI tooling, from Sweden. Projects run in weeks.
Short answer
A Swedish women’s health clinic opened its physical and digital practices at once. The care flows in the platform came before the website: visit types, questionnaires, booking and fees were ready for opening day on 15 December 2023, and the website was rebuilt over the three months that followed. The order was a decision that cost visibility during the launch.
The client is a Swedish care provider in gynecology and women’s health, comprising three clinics. The engagement ran from late October 2023 to mid-March 2024, at roughly half time, some years before the studio took its current name. The starting position: two founders who owned the care and the business, a digital care platform bought and unconfigured, premises being fitted out, and an opening date.
What the engagement covered
- Technical lead-up to opening: equipment, accounts, domain and email, and a walkthrough of the premises against hygiene and accessibility requirements.
- The patient flows in the digital care platform: visit types, questionnaires, booking, video visits, fees, and the rules for rescheduling and cancellation.
- The connections between the systems, so that booking, medical records, questionnaire answers and messages held together as a single path for the patient.
- The website: information architecture, design, technical SEO, and articles on the clinic’s own subject areas.
Why the care flows came before the website
A clinic that opens needs, above all, to be able to receive a patient. A website describing a practice that receives nobody yet is a brochure. So the first six weeks went to the platform and the premises, and the website stood still. The clinic opened on 15 December 2023 with a site that had the wrong content and no keyword structure, and it was rebuilt from January to March.
That was a deliberate choice with a known cost. An opening date can be missed in a way that costs rent, salaries and credibility; a website can launch six weeks later and costs visibility during the launch. The trade-off was written down when it was made, which is why it can be described here.
The questionnaires were product work
Every visit type has its own questionnaire, and the questionnaire is the first thing a patient meets. The platform’s default texts became a starting point, and each visit type then got its own version: what happens when the case is submitted, what the visit costs, how quickly the clinic gets back in touch, which rules apply on cancellation, and the question of whether clinical staff may read the patient’s records.
A document of a few pages took four weeks of calendar time. Every phrase had to match what the clinic could actually deliver, and be reviewed by a midwife or a gynecologist before it went live. That is the pace the work keeps when the copy is part of the care, and it is worth planning for.
The systems that had to hold together
A digital practice runs on several systems that each work on their own and together leave gaps: booking on the web and in the app, medical records, questionnaire answers, video meetings, SMS confirmations, and the region’s own channels. The work was to draw the whole patient path, name which system owns each step, and remove the steps where staff had to copy details across by hand.
One concrete example: the platform’s automatic notifications sent several messages per booking. They were cut back in February 2024 to those that carried information the patient needed. The decision has a downside — fewer reminders raises the risk of no-shows — and trade-offs of that kind are what a flow is made of.
The website: structure before copy
The rebuild started in January 2024 with the information architecture: which pages should exist, what each one answers, and which search question it owns. The clinic’s subject areas — endometriosis and women’s health broadly — are things patients search for in their own words long before they search for a clinic. The articles were written against those words, and the visual language was developed with an external illustrator.
What would be done differently
Two things. The website’s structure could have run in parallel with the platform work back in November, since structure can be settled before the content exists; that would have pulled the launch six weeks forward at almost no extra cost. And measurement was set up too late, which is why the engagement can be described in decisions and dates while lacking figures on traffic and bookings.
The second lesson is the more expensive of the two, and it shows in this article: an engagement with no measurement from day one can be described but never proven. Every engagement since starts with measurement in place before the first page is built.
Evidence
What this article rests on — a measurement we took, a dated source, or a decision we made and what it cost.
- Decision
Configure the patient flows in the care platform before rebuilding the website, so the clinic could receive patients on opening day.
What it cost: The website stood still for six weeks, and the clinic opened with a site that had the wrong content and no keyword structure.
- Decision
Rewrite the platform’s questionnaires as bespoke copy per visit type, reviewed by clinical staff before going live.
What it cost: Four weeks of calendar time for a document of a few pages, and every new visit type needs the same review round.
- Decision
Cut the platform’s automatic notifications back to the messages that carried information the patient needed.
What it cost: Fewer reminders per booking raises the risk of no-shows.
Common questions
- How long did the engagement run?
- From late October 2023 to mid-March 2024, at roughly half time. The clinic opened six weeks into the engagement, and the website was rebuilt over the three months that followed.
- Who did what?
- The clinic’s two founders owned the care and the business. The engagement owned the digital side: the platform, the connections between systems, the website, and the technical advice. Illustration and part of the visual language were brought in externally.
- Was the digital care platform built from scratch?
- No. The platform was bought as a service. The work was to configure it — visit types, questionnaires, booking rules, fees, notifications and permissions — and to connect it to the clinic’s other systems.
- How much of the work was technical?
- Less than half. Most of it was deciding what should happen at each step, phrasing it in Swedish a patient understands, and having it reviewed by clinical staff before it went live.
- Why are no result figures reported?
- Measurement was set up too late in the engagement, and data that was never collected cannot be reconstructed afterwards. So the article describes decisions, dates and trade-offs, all of which can be checked.
- Does the same approach work in another industry?
- Yes, anywhere a service is delivered through several systems and a customer has to travel through them in sequence. The order — flow first, website second — holds as long as the business needs to be able to deliver before it markets itself.
Sources
- Curoflow
The digital care platform the clinic uses, with booking, medical records and video meetings in one system.
Next steps
Read next
- Deciding what to build nextThe method that takes a backlog to a decision: the questions that separate proposals, how the decision is written down, and how often it is redone.
- When a design system pays for itselfWhat a design system is made of, how the build check keeps it true, and at what size it earns back the time it cost to build.
- AI website agency vs traditional agencyThe two models differ in where the time goes: coordination between specialists, or the standard itself. Timelines, revision loops, and when each fits.
Go deeper