It should be this simple
Some systems became something else
Voices from the field
I klik seven taims for opening one patient. SEVEN TAIMS! My finger is now like maratton runner. Wery atletik finger. Rest of me, not so mats. De system is not helping me, it is training me. But in rong direktion.
De old system vas updating. Tree hours. I drink vone kahvi. Den anoder kahvi. Den I start knitting. I finish hole sokk before de system finish loading. Now I haff wery nice sokks but patients are still vaiting.
Dey said new system is koming. Dat vas 2015. Den 2017. Den "soon." My dotter vas born, vent to skool, and learned to kode faster dan dis deployment. She offered to help. Dey said no. Of kourse dey said no.
I press save. Nossing happen. I press again. Nossing. I press törd taim — now I haff tree same preskriptions. Patient gets enaf antibiotiks for hole village. Wery effisient. In rong direktion.
De training vas two viiks. TWO VIIKS! For writing notes! I vent to medikal skool six years and it vas easier to understand de human body dan dis user interfeis. At least de body makes some sense, you know.
Samvone asked me how mats de system kost. I told dem. Dey tought I vas talking about a brits. No no, I said, brits vould be tsiper. And de brits you kan aktually kross to de adder side.
These are fictional characters. Any resemblance to your actual Tuesday morning is purely coincidental.
The architecture
A doctor takes an oath to keep your secrets. Then the architecture makes it impossible to honor. Kotletti is built on an identity-first model — patient data exists only where the patient has explicitly shared it. No central database. No honeypot. The math enforces the oath.
Read the full architecture documentOpen source
Healthcare software handles lives. The code should be open to every developer, auditor, clinician, and citizen who wants to look. Not because we're idealistic. Because it's irresponsible not to be.
Don't like a decision we made? Fork it. Improve it. Run your own. No permission needed. No license fee. No phone call to a sales team that doesn't pick up.
Every commit is public. Every decision has a trail. When someone asks "why does it work this way?" — the answer is never "we'll get back to you."
Why "Kotletti"
A kotletti is straightforward. You know what's in it. You know what it costs. It doesn't need a brand strategy or a twelve-month onboarding program. It's just good, honest, ordinary food.
Healthcare software should be the same. Not a seven-course mystery menu. Not a molecular gastronomy experiment funded by taxpayers. A cutlet.
Also, we're Finnish. We like naming things after food. Don't overthink it.
Talkoot
In Finland, when something needs building, the neighbours show up. No contracts. No procurement rounds. You bring what you know. Someone brings coffee. The work gets done.
That's how Kotletti is built. Not by a vendor. By people who use healthcare systems, build healthcare systems, or simply believe they should work better than they do.
Write code. Review code. Break things in staging so they don't break in production.
Tell us what's wrong. Not with the code — with the workflow. You know where it hurts.
Make seven clicks into one. Make the important thing visible. Make the screen feel calm.
Translate. Document. Test. Ask hard questions. File issues that start with "why does it—" We need those most.
Read the code. Open an issue. Or just say hello.