00technology / measured 2026.10.03
Technology
buildpassingframeworknoneanalyticsga4 onlyfontsself-hostedapi/api/v1a11yreduced-motion
We build our own software and change it every day. Every number and chart on this page is measured directly from our internal repository.
changes to our software
6,500+
Changes merged into our software since 2026.03.20. Each one passed review before going into production.
2026.03.20 — 2026.10.03
as of 2026.10.03 · source: internal repository · automated changes excluded
- #12610docs2026-10-03merged into main
- #12609feat2026-10-03merged into main
- #12607fix2026-10-03merged into main
- #12606docs2026-10-03merged into main
- #12604chore2026-10-03merged into main
- #12602docs2026-10-03merged into main
- #12601feat2026-10-03merged into main
- #12600fix2026-10-03merged into main
- #12595docs2026-10-03merged into main
- #12593fix2026-10-03merged into main
- #12591chore2026-10-03merged into main
- #12589feat2026-10-03merged into main
- #12588chore2026-10-03merged into main
- #12587docs2026-10-03merged into main
- #12583feat2026-10-03merged into main
- #12581feat2026-10-03merged into main
- #12577feat2026-10-03merged into main
- #12575feat2026-10-03merged into main
- #12574feat2026-10-03merged into main
- #12573feat2026-10-03merged into main
- #12571feat2026-10-03merged into main
- #12568feat2026-10-03merged into main
- #12567feat2026-10-03merged into main
- #12565feat2026-10-03merged into main
- #12564feat2026-10-03merged into main
- #12561fix2026-10-03merged into main
- #12560feat2026-10-03merged into main
- #12556feat2026-10-03merged into main
- #12555feat2026-10-03merged into main
- #12554feat2026-10-03merged into main
- #12553chore2026-10-03merged into main
- #12550docs2026-10-03merged into main
- #12546fix2026-10-03merged into main
- #12543docs2026-10-03merged into main
- #12542fix2026-10-03merged into main
- #12541feat2026-10-03merged into main
- #12539fix2026-10-03merged into main
- #12537feat2026-10-03merged into main
- #12536chore2026-10-03merged into main
- #12534docs2026-10-03merged into main
01process
With AI, the people who build and the people who use become the same team.
Until now, the companies that built healthcare software and the medical institutions that used it were separate. Builders had to prioritize features common to many institutions, and users who asked for specific changes often waited a long time to see them.
AI has sharply reduced the cost and time of building software, so the people who know the front line can now build systems around how they actually work. At PreMed, every employee is an FDE (Forward Deployed Engineer). We develop as a small team working with AI agents, and what we notice when test-booking on a smartphone, or what front-line staff say after looking at a screen, usually reaches the staging environment the same day.
02one os, not point solutions
Some things point-solution SaaS cannot reach.
Booking, intake questionnaires, medical records, patient messaging, acquisition metrics — the work of a medical facility is connected, yet most systems so far have covered only one slice of it. PreMed builds all of these as a single OS, in the same team as the front line. clinic os, built for clinics, runs in the group's clinics, and hospital os, built for hospitals, is in development.
- 01
No manual work left at the seams
When systems are separate, copying and checking data between them remains a human job. With a single OS, the seams themselves disappear.
- 02
Fitted to our operations, not to the average
Products built for many institutions have to prioritize common features. We build around how the group's clinics work, and can fix things the same day.
- 03
One continuous view of the numbers
From the first point of patient acquisition through booking to the visit itself, everything sits on the same data and can be followed on a single screen.
- 04
The more clinics, the better the OS
Clinics that join through succession and newly opened clinics all run on the same OS. An improvement found at one clinic reaches every clinic.
- 05
Updated daily, and embedded on the front line
The front line changes every day. Updating once every few months is, in our view, already too slow. We update our software every day (6,500+ changes since 2026.03.20). What matters is building an organization that can embed each change on the front line, and the execution to see it through.
03galapagos
Galapagos, our booking system
An AI-native booking system for medical facilities, built in-house by a small team working with AI agents — people who know clinical practice first-hand. It goes into use at Kids Clinic Marumaru, opening in November 2026, and will then be extended to the group's other clinics, including gynecology and fertility care.
- 01
Patients book entirely within a LINE chat
Booking, rescheduling, cancelling, joining a waitlist, adding family members and filling in the questionnaire can all be done without leaving LINE. Patients can tap through buttons, or simply write “Tomorrow morning” or “I’d like to cancel Friday’s appointment.” When a patient makes a request in free text, AI checks availability and suggests options; a booking is confirmed only when the patient presses the button themselves.
- 02
AI handles first response; only unanswered inquiries reach staff
AI answers questions sent through LINE within the information the clinic has prepared. Only what AI could not answer, or what needs a staff decision, reaches the admin screen — and once staff add an answer, AI can answer it next time. It never answers symptom questions on its own judgment, and when it detects urgent wording it directs the patient to call 119 or the clinic.
- 03
AI agents carry out detailed admin settings
Most settings — opening hours, the number of booking slots, services, questionnaire items, notices to patients — can be changed by asking an AI agent, without opening the admin screen. A questionnaire of over 100 questions can be registered at once from a table. What an AI agent can do is governed by role-based permissions, and every change is logged with who made it.
- 04
Bookings and questionnaires sync automatically with the claims system and EMR
New patients are registered in the claims system as soon as their booking is confirmed, so their patient ID is set before the visit. Reception actions are reflected in the claims system too, and questionnaire answers flow automatically into the electronic medical record. Reception and consultation rooms no longer need to copy the same information by hand.
- 05
Automated messages before and after each appointment
Day-before reminders, waitlist promotions and return-visit messages for patients who haven’t come in for a while are sent automatically. Each message checks that the booking is still valid just before sending, so people who have cancelled never receive a reminder the day before. For families, every registered guardian receives it.
- 06
Works for any specialty, with features added for each
Services, consultation durations, questionnaires and notices to patients are set freely by each clinic. Features are added to fit the way each specialty works, and clinics can switch off the ones they don't use. Pediatrics, where it goes into use first, is one example: services shown by the child's age in months or years, last-minute slots for sudden symptoms, combined bookings for siblings or parent and child, vaccine stock linked to bookings, vaccination records entered by parents, age-based notices, fever charts and growth curves.
- 07
Acquisition tracked all the way to the visit
For each entry point — ads, website and others — it records how far each patient got through booking and whether they actually visited, in one continuous record. For LINE bookings it also shows where people dropped out and how many could not book because slots were full, so “bring in more patients, or add booking slots?” can be decided on the numbers.






* Screens show fictitious demo data (images from the press release).
04toki — fertility care database
TOKI, an EMR for fertility care
The electronic medical record used every day in the group's fertility care. It brings together what fertility care needs, from treatment cycles to IVF and frozen embryos, on screens each doctor finds easy to read. When something is missing, we build it quickly from the floor's requests.
- 01
One set of data, a screen for each doctor
The same patient data appears in a different UI for each doctor. A doctor who follows the course of treatment line by line gets a single continuous view; a doctor who compares many items at once gets three panes side by side. Everything has its fixed place, and what is needed fits on one screen.
- 02
Every record fertility care needs
Treatment cycles and daily visits, IVF, frozen embryo transfer, semen analysis and self-injections are all handled in one database. Things that are easy to miss, such as embryo storage deadlines and uncollected consent forms, show up in a list.
- 03
Today's work on one screen
Today's outpatients, today's lab, today's self-injections: the patients to see and the tasks to do each fit on a single screen. In the lab, double checks by two people are recorded too.
- 04
Easy to read, easy to enter
Insured and self-pay care are color-coded so they can be told apart at a glance. Small chores in data entry are taken away, and half-written entries are never lost.
- 05
Requests become features quickly
A button at the bottom right of the screen lets users send "it would be nice if…" on the spot. Each request is registered directly as a development issue, and we build it with AI agents. A request sent in the morning has been implemented by early afternoon the same day. In the roughly five weeks since late August 2026, more than 170 changes have gone into TOKI.


* Screens show fictitious demo data.