One patient journey. Four points of view.
A prescription passes through several hands before it reaches the patient, and each person needs different information and a clear next step. The platform brings them into one application, where every role sees only what it should.
- Product
- A healthcare platform for patients, doctors and pharmacies
- My role
- Co-founder. I lead the product and direct the build.
- Languages
- English, Italian and Greek
- Status
- In development. Not yet open to the public.
Build and test inventory, September 2026. Tests show what was checked, not clinical outcomes.
Sees only their own requests and where each one stands.
Sees a patient's request only while there's an active link between them.
Sees only the requests assigned to it, routed by country and by what it can supply.
Works in its own workspace, alongside its prescribers and patients.
Three rules the whole product is built on.
Healthcare software fails when people see too much, too little, or can't tell whose turn it is. These rules answer all three.
Access follows the relationship.
A doctor sees a patient's request only while there's an active link between them. A pharmacy sees only the requests assigned to it. The application only shows each role the records linked to its work.
Access rules are built into the application and checked through testing.
Every next step has an owner.
A request moves through a fixed set of stages. Each stage identifies who is responsible for the next action.
Some of the stages a request can reach
One application, several views.
Patients, prescribers, clinics and pharmacies each get their own workspace. Routing adapts to the country and to what each pharmacy can actually supply.
A small team, with AI as the engineering department.
I designed the workflows, directed AI to write and check the software, and tested each role's journey with made-up patients, doctors and pharmacists before a real one came near it. More than 500 automated tests back it up, including 15 that walk a whole journey the way a patient, doctor, clinic or pharmacy would. A licensed pharmacist co-founder keeps the product grounded in how pharmacies really work.
Clinical and dispensing decisions always stay with licensed professionals.
If your work passes between several people, the same approach applies.
I used AI to help build this software. What carries over to your business is the method: map the hand-offs, give each step an owner, and control who can see and change each record. It suits orders, claims, approvals and similar workflows that cross teams or companies.
Tell me one task your team hates doing.
In a free 15-minute call, we'll work out whether AI can take it on and what a sensible first step would be. If the answer is no, I'll say so.
Free · 15 minutes · you'll talk to me, not a sales team.
