I build systems where the record has to be right — and I run Trippy Solutions.
Most of my work comes down to the same thing: information that people depend on, living somewhere it can't be trusted. A patient's history scattered across paper files at three different clinics. Twenty years of business rules locked inside software nobody dares touch. In both cases the cost isn't the technology — it's that nobody can see the whole picture when they need it.
A cloud platform for clinics and medical centres across Egypt.
A patient's medical journey usually lives in fragments: a paper file at one clinic, a prescription photographed on a phone, a lab result nobody kept. Every visit starts from scratch, and the doctor in front of you works from whatever you remember to mention.
Trippy Med puts that journey in one continuous record, and connects everyone who touches it — patients, doctors, nurses, reception staff and centre owners in a single system.
For patients Their history follows them: allergies, chronic conditions, medications, lab results with trend charts showing how something like blood sugar or blood pressure moves over time, e-prescriptions with verifiable QR codes, invoices and past appointments — all from their phone. They book with the right doctor at the right centre, get a queue token for walk-in visits, and are alerted the moment something needs attention.
For the clinical team A complete, up-to-date picture before the consultation begins. Follow-ups that don't fall through the cracks. Every record tied back to its source.
Why it matters Continuity and safety. Because it follows a patient over time rather than one visit at a time, it gives patient and doctor a shared, trustworthy source of truth — instead of repeated tests, conflicting treatment, and a history reconstructed from memory.
Microservices: Spring Boot · Angular · React Native / Expo. Patient privacy is the first design constraint, not a later pass — it holds people's health data.
Open-source tooling for organisations stuck on Oracle ADF.
ADF applications still run payroll, licensing and case management at banks, ministries and telcos. The people who wrote them have moved on, and the first question is always "how much of this can we actually move?" — an answer that used to cost a consultant three weeks of reading XML.
adfmig answers it in about a minute, entirely on your own machine: nothing uploaded, no network calls. The assessment half is MIT licensed and complete — no limits, no account, nothing withheld.
github.com/trippysolutions/adfmig
Give the free thing away properly. If someone only ever needs to understand the size of their problem, they shouldn't have to pay me to find out. What's free is genuinely free, not a demo with the useful parts removed.
Be honest about what something can't do. Every tool has an edge. I'd rather say where it is up front and lose a bad-fit customer early than have an unhappy one later.
Build for the people doing the work, not for the demo. Real defects come from running software against real data and comparing the result — never from reading the code and assuming it's fine.
Leave people able to carry on without me. No lock-in waiting a year out, and nothing that stops working when someone stops paying attention to it.
I work with clinics and medical centres that want their patient records to hold together, and with teams facing a modernisation they've been postponing for years.
If either sounds like you, I'd like to hear about it.
Trippy Solutions — healthcare platforms and enterprise modernisation · Egypt