It’s difficult to think of something that could genuinely help people—and even harder to follow through with it.
Ideas are easy to romanticize. You imagine the impact, the lives changed, the problems solved. But the moment you try to build something real, doubt creeps in. You start asking yourself if it’s even good enough. If it’s too complicated. If you’re the right person to do it.
That’s where I am with PatternMD.
PatternMD is a dream project of mine. At its core, it’s an attempt to map out patterns in medicine—especially in cases where answers aren’t obvious. The idea is simple in spirit but complex in execution: create a system that helps connect symptoms, timelines, lab results, and lived experiences into something more structured. Something that makes it easier to see what might otherwise be missed.
Not to replace doctors. Not to override clinical judgment. But to support it.
Because the truth is, medicine isn’t always straightforward. Patients don’t walk in with neatly packaged diagnoses. Sometimes their labs are normal. Sometimes their symptoms don’t “fit.” Sometimes they get told, directly or indirectly, that nothing is wrong—when something clearly is.
PatternMD is my attempt to sit in that gap.
It’s meant to be a tool that recognizes patterns over time, across individuals, across systems. Something that could help both patients and physicians see connections earlier. Something that might reduce the time it takes to get answers—or at least make the process feel less isolating.
But if I’m being honest, I’m not just thinking about the idea itself. I’m constantly questioning whether I’m capable of bringing it to life.
It feels too big. Too technical. Too ambitious.
There are moments where I look at it and think, “Who do I think I am trying to build something like this?” And other moments where I think, “If I don’t try, what if this could’ve actually helped someone?”
Maybe it is a self-esteem thing. Maybe my standards for myself are so high that nothing I create ever feels like enough. Or maybe I’m just seeing clearly how hard this actually is.
Probably both.
But here’s what I keep coming back to: PatternMD doesn’t have to be perfect to have value.
It doesn’t have to solve everything. It doesn’t have to be fully built out from the start. It just has to begin.
Even if it starts as something small. A collection of mapped pathways. A visual system. A way of organizing information that makes even one concept easier to understand. That’s still something.
PatternMD might never become exactly what I imagine it to be right now. It might evolve into something entirely different. It might take years. It might require help from people I haven’t even met yet.
But I think it has potential.
Rootin for ya,
Edidiong
