3
10 Comments

I built an AI tool that explains prescriptions & lab reports in simple language

Built dawaai.info 🚀 — an AI tool that explains prescriptions & lab reports in simple language.

Upload your report → get clear explanations, side effects & usage.

Goal: make healthcare easier to understand.

Would love feedback 🙏
https://www.dawaai.info

on April 18, 2026
  1. 1

    This is a genuinely high-value use case — medical jargon is one of the biggest sources of patient anxiety. How are you handling the accuracy / liability piece? That seems like the main adoption blocker in the healthcare space.

  2. 1

    I think this is a growing space. Better and faster access to insights is critical. My fiancee works in healthtech and is very passionate about this.

    One piece of contstructive advice - website says a lot of cool stuff but as a cold lead coming on your site, where do I see the value prop vs using my own Claude for insights? A short demo or something like that could help :)

  3. 1

    Have you had any traction yet or still validating?

  4. 1

    This is a solid use case — especially in healthcare where clarity = trust.

    One thing I’d flag though: before users even try it, they judge credibility based on the name + domain.
    Something like .info can actually create friction here.

    Curious — are you planning to upgrade the brand/domain as this grows, or keeping this for now?

    1. 1

      That’s a very fair point—especially in healthcare where trust is everything. Since we’re primarily focused on sharing information (not a commercial service at this stage), we chose a .info domain as a starting point. That said, we do recognize how perception plays a role, and upgrading the brand/domain is definitely on the roadmap as we grow. Really appreciate you calling this out.

      1. 1

        Makes sense — good call starting simple.

        The only reason I brought it up is because in healthcare, the shift from “interesting tool” → “trusted product” often happens earlier than expected.

        Even a small upgrade in name/domain can noticeably improve:
        – first-time conversion
        – willingness to upload sensitive reports
        – perceived reliability

        Not urgent of course, but worth locking in early before users start associating with the current one.

        If you ever explore options, happy to share a few directions that would fit this space well.

  5. 1

    This is a really interesting idea — especially the “explain in simple language” part. I feel like a lot of people struggle with exactly that after getting prescriptions or lab results.

    One thing that came to mind: in products like this, trust is probably everything. If it’s not immediately clear why the explanation is reliable, users might hesitate to rely on it — even if the output is good.

    Also curious how you’re thinking about the first-time experience. Like, when someone lands — is it obvious what they should do first? (ask a question vs upload vs something else)

    Happy to take a deeper look and share more detailed UX feedback if that’s useful.

    1. 1

      This is super insightful—appreciate you taking the time.

      100% agree that trust is the core challenge here. We’re actively working on making reliability more explicit (not just good outputs, but visible reasoning + guardrails).

      On onboarding—great call. It’s something we’re iterating on right now to reduce friction and make the first step obvious.

      Would love your deeper UX feedback—I'll reach out / feel free to dive in and share anything you notice.

      1. 1

        Took a closer look at the medicine checker page — sharing a few specific UX thoughts:

        1. Readability on the first screen
          Some text feels a bit hard to scan quickly (contrast + density).
          For a health-related tool, clarity in the first seconds feels especially important.

        2. First action isn’t obvious enough
          There are multiple things I can do (ask, upload, explore examples), but no single clear starting point.
          Might help to make one primary action dominant.

        3. Trust is present but not visible early
          I noticed the disclaimer, but it reads more like a legal note.
          I think what could really help is showing:
          – how the AI generates answers
          – what it's based on
          – where its limits are closer to the input area.

        4. Output expectation
          Before trying it, I’m not fully sure what kind of result I’ll get.
          A small preview example could reduce friction a lot.

        Overall, the idea is strong — especially simplifying medical info.
        Feels like improving clarity + trust in the first few seconds could significantly increase usage.

  6. 1

    Happy to dive deeper into how it works — AI, tech stack (Python + AI APIs), or any challenges I ran into while building it. Ask me anything 👇

Trending on Indie Hackers
I built a tool that shows what a contract could cost you before signing User Avatar 113 comments The coordination tax: six years watching a one-day feature take four months User Avatar 74 comments My users are making my product better without knowing it. Here's how I designed that. User Avatar 64 comments A simple LinkedIn prospecting trick that improved our lead quality User Avatar 52 comments I changed AIagent2 from dashboard-first to chat-first. Does this feel clearer? User Avatar 39 comments Why I built a SaaS for online front-end projects that need more than a playground User Avatar 17 comments