About orenva

Healthcare, made whole.

orenva began with a frustration anyone who has had to manage their own care has felt: you should not have to be the messenger between six services that never speak to each other. We are building one intelligent platform where consultation, pharmacy, therapy, fitness, insurance and wellness finally share the same context.

Join the waitlist See how it works

The origin

It started with a question that would not let go.

Why does the person at the centre of a care journey end up doing all the carrying? You describe your symptoms to a screening tool. You repeat them to a clinician. You repeat them again to a pharmacist. You explain to insurance what just happened. The system gets paid for the visits — and you are the one who held it together.

We started orenva because the answer is not another single-purpose app on top of an already fragmented stack. It is the connective layer underneath: one health context that every service reads from and writes to. Care stops restarting. The thread finally holds.

The philosophy

Three commitments we will not bend on.

The product changes constantly. These do not.

Mission

One connective layer

Bring consultation, pharmacy, therapy, prevention, insurance and wellness into one intelligent layer that understands the whole person — not six separate fragments of them.

Vision

Healthcare that does not restart

A future where moving between care services feels like one continuous conversation, rather than a series of cold starts where you re-explain yourself every time.

Principle

Advanced, precise, calm

Every interaction is engineered to lower anxiety, not add to it. The technology stays quiet so the care stays clear.

Where we sit

Not another app. The layer beneath them.

orenva is not competing with telehealth, mental-health, pharmacy or insurance apps one by one. It is the layer that makes them stop being islands.

Telehealth apps

They: A single channel of care — usually consultation.

orenva: The connective layer between every channel, including consultation.

Single-purpose pharmacy / mental-health apps

They: One slice of care, in a vertical of its own.

orenva: Every slice, sharing the same record so the thread holds.

Hospital portals & EHRs

They: Care viewed from inside the institution.

orenva: Care organised around the person, across institutions.

Insurance platforms

They: Coverage handled separately from care.

orenva: Claims and coverage drawn from the care that actually happened.

The product

The modules are the surface. The context is the platform.

Any one of the six modules — consultation, pharmacy, diet and fitness, therapy, insurance, store — already exists somewhere as a standalone product. What does not exist is the connective tissue: a single health record that every module reads and writes, with consent baked in. That is the platform. The modules are how you touch it.

See how the context engine works

The founders

Two people. One thesis.

orenva is built by an operator who has spent his career inside healthcare, and an engineer who builds platforms that ship. They share the same conviction: the connective layer is the moat.

Geet Patil

Founder & Chief Executive Officer

Schweinfurt, Germany · originally Mumbai

The architect of the orenva thesis. Geet has spent his career at the intersection of healthcare, partnerships, and product strategy — and started orenva to build the layer the industry has spent a decade going around. He leads strategy, fundraising, and the partner-led launch.

Healthcare partnerships across clinic, pharmacy, and insurance networks
Product and commercial leadership through multiple early-stage builds
Operates between India and Europe — the markets orenva starts in

orenva.health@gmail.com LinkedIn

Jordan Gilbert

Technical Co-Founder & Chief Technology Officer

London area, United Kingdom

Engineer-operator. Built the orenva platform end-to-end — the connective context engine, the HealthGraph thesis-as-object, the design system. Multi-product background: ships, doesn't just specify. Owns architecture, engineering, and product delivery.

Built the public-facing orenva platform on Next.js 14 + TypeScript
Runs UK Web Marketing — a multi-vertical web-platform agency
Has previously shipped Brother Sylvester and Sweatty Limited

orenva.health@gmail.com LinkedIn

Open to clinicians, designers, and engineers who want to help shape what gets built first. orenva.health@gmail.com

The road so far · and next

Where we are, told honestly.

No vanity metrics. Here is the shape of the build, in plain language.

Insight
Naming the problem
A long pattern of friction — re-entered history, lost context between services, ten apps for one body — finally read as a single thing: fragmentation as default.
Foundation
The thesis takes shape
A small team converges around one bet: the connective layer is the moat, not any one module. Clinical pathways and the shared-context engine begin to be built side by side.
Build
Six modules. One record.
AI consultation, pharmacy, diet & fitness, therapy, insurance and the marketplace each begin reading and writing the shared health context. The platform stops being six apps and starts being one.
Pre-launch
Opening the waitlist
The site you are reading. Early members shape what we ship first. Partner conversations open with clinics, pharmacies, insurers and employers.
Next
Private preview
A small first group of members enters the preview. Founding partners integrate. We listen, refine and prepare for public launch.

Where this is going

One layer, every part of care, eventually everywhere.

The starting market is Europe and India — where the team is, and where the gap is most acute. The starting wedge is consultation to pharmacy, because the handoff between those two is the part that bleeds context most plainly. From there the ecosystem fills out around the same shared context — and the same layer can extend to any market with the same problem.

Join the waitlist Talk to the team