Skip to content
Hamdosh
Get started
Our story

We built this for our own families first.

A medical memory built for the kitchen table, not the clinic. Because the most important question your doctor asks — 'what did we try last time?' — has no good answer today.

  • Founder-built
  • Family-first
  • Outcomes-driven

A note from the founder

"I built Hamdosh because my mother had a thyroid medication that worked, my sister now has the same condition, and nobody — not us, not the hospital, not any of the four health apps I tried — could connect the two. The information existed. It just had no home. Hamdosh is that home."

— Founder & CTO (placeholder)

Our values

The four lines we won't cross.

Privacy is the product.

A medical record app whose business model depends on selling your data is broken at the foundation. We will never sell PHI. We will never train external models on your records without explicit consent. Period.

Family-first, not patient-first.

You aren't one patient. You're a parent of two kids, a partner, an adult child of aging parents. Health software that treats you as a single ID misses the whole point of caregiving.

Outcomes are mandatory data.

A prescription with no follow-up is dead weight. We nudge gently — and relentlessly — for outcomes. That's what makes a record a memory: knowing what worked, what didn't, and why.

We surface history. We don't prescribe.

Every insight is framed as "last time, X was prescribed, with outcome Y." Never as "you should take X." That's the product position, and the liability shield, and — frankly — the right thing.

Roadmap

Where we are, and where we're going.

Now

Encounter grouping, OCR, outcomes, smart search, family roll-up. Encrypted at rest and in transit.

Next

Semantic search with pgvector. Family sharing via consent grants. Mobile capture app.

Later

HIPAA certification. Provider portal export. Insurance/EOB intelligence. Wearable signals.

If this resonates, come build with us.

We're early. Your feedback shapes the roadmap.