Questions to ask a doctor about your digital health product
An hour with a doctor goes fast. These are the questions that tend to change what founders build, grouped by the five things that decide whether a health product gets used.
By the Hudlyn team · Updated October 10, 2026
1. Workflow: will it actually be used?
- “Walk me through the moment in your day when you'd open this.”
- “What would you stop doing to make room for it?”
- “Who else touches this: a nurse, a medical assistant, the front desk?”
- “Where does the result need to end up so you'd actually see it?”
2. Trust: would you rely on it?
In an AMA survey, physicians named liability coverage as their most important requirement for adopting digital health tools, followed by EHR integration and data privacy.[1]
- “What would you need to see before acting on its output?”
- “If it's wrong, who carries the risk, and would that stop you using it?”
- “Does it have to live inside the EHR, or is a separate screen acceptable?”
3. Payment: does anyone pay for this?
If your product monitors patients remotely, Medicare has specific rules. Remote physiologic monitoring requires an established patient relationship, the device must meet the FDA's definition of a medical device, data must be collected on a set number of days in a 30-day period, and only one practitioner can bill for it per patient in that period.[2] The common codes cover initial set-up and education (99453), the device supply, billed once every 30 days (99454), and the first 20 minutes of the clinician's review and communication each month (99457).[3]
- “Is there a code that pays for this today, or would it come out of someone's budget?”
- “Whose time does it take, and is that time paid?”
4. Regulation: device or not?
The FDA treats “software intended to be used for one or more medical purposes” without being part of a hardware device as software as a medical device.[5] Its clinical decision support guidance explains which decision-support functions fall outside the definition of a device.[4] A doctor can't give you a regulatory opinion, but they can tell you how they'd use your output, and that is what the line depends on.
- “Would you act on this directly, or review the reasoning first?”
- “Could you see why it recommended what it did?”
5. Buying: who has to say yes?
In hospitals, products often pass a value analysis committee of clinicians, supply chain and administrative staff.[6] Technology decisions increasingly need clinical, IT, operational and financial leaders to agree.[7] And purchasers want proof of measurable clinical and economic outcomes, not just engagement metrics.[8]
- “Who in your organization would have to approve this, and in what order?”
- “What outcome would convince them: time saved, admissions avoided, money?”
- “Who would champion it internally, and what would they need from us?”
Hudlyn gets you a one-hour video call with a verified doctor who works where your product will live.
Request an inviteSources
- American Medical Association, Digital health care 2022 study findings
- CMS, Telehealth and remote patient monitoring (MLN booklet, December 2025)
- American College of Physicians, Remote patient monitoring: billing, coding and regulations (2025)
- FDA, Clinical decision support software guidance (updated January 2026)
- FDA, Software as a medical device (SaMD)
- Value analysis committees, Clinical Orthopaedics and Related Research (2024)
- HIT Consultant, reporting KLAS: healthcare IT needs of C-suite leaders (2025)
- Peterson Health Technology Institute, 2025 state of digital health purchasing
This guide is general information for founders, not medical, legal or regulatory advice.