How to Choose Telehealth Software for a Cash-Pay Clinic: A 10-Question Scorecard
Last verified: October 30, 2026 · By Ernesto Cullari, Ernesto Cullari Media LLC. An operator's guide, not legal or medical advice.
Quick answer
Score every telehealth platform on ten questions, and give a point only for what the vendor shows you live. The questions cover hosting and the cloud agreement, field-level encryption, the audit trail, staff sign-in, how clinic data is kept separate, AI use, data import, pricing, practice model and whether leads and patients live in one system. Ask the vendor to show each answer working, not describe it.
This guide is for cash-pay TRT, HRT, peptide, GLP-1 and wellness clinics choosing a telehealth platform. If you bill insurance, you need a system built for claims, and this scorecard does not cover that.
How do I score a vendor?
Give each question 0, 1 or 2 points.
0: the vendor showed nothing.
1: the vendor described it or sent a document.
2: the vendor showed it working while you watched.
Ask to see every answer working. A slide describes what a vendor intends. A demonstration shows what the system does.
What are the ten questions?
#
Question to ask
What a good answer looks like
Why it matters
1
Where is patient data hosted, and does the host have a BAA with the vendor?
The hosting provider and region by name, and the business associate agreement between the vendor and that provider.
HHS says a cloud provider that maintains patient data is a business associate even if it holds only encrypted data (HHS FAQ 2076).
2
Which fields are encrypted individually in the database?
A list of fields and the algorithm, not only "encrypted at rest."
Encryption is an addressable Security Rule specification (45 CFR 164.312(a)(2)(iv)), and data encrypted to HHS guidance is not "unsecured" for breach notification (164.402, HHS guidance).
3
How does the audit trail show that someone altered it?
How an administrator verifies the log, and a plain list of the actions it records.
The Security Rule requires audit controls and protection from improper alteration (164.312(b) and (c)(1)).
4
How do staff sign in?
Multi-factor authentication on every staff sign-in, and a unique login for each person.
The data types, the formats, who does the work and who checks the result before go-live.
Patient data must be protected from improper alteration or destruction (164.312(c)(1)).
8
What will I pay in the first month?
Plan prices and the onboarding fee published before a sales call, with a written list of what is not included.
The first-month total, not the monthly rate, is the number to compare.
9
Is the platform built for the way I run my practice?
A plain statement of whether it is built for cash-pay practices or for insurance claims.
A platform built for insurance claims and a platform built for cash-pay practices solve different problems.
10
Do leads and patients live in one system?
A lead becomes a patient in the same system, without re-entering the record.
Re-entering records between tools is where errors and lost follow-ups start.
A total of 20 is the maximum. There is no industry threshold. The scorecard does not list every HIPAA requirement, so have your counsel confirm the full list for your practice.
How do I run the demo?
Send the ten questions to the vendor before the call.
Ask the vendor to create a test patient, then show you the encrypted fields for that patient.
Ask the vendor to show how an administrator verifies the audit trail, and which actions it records.
Ask for the price sheet and the onboarding scope in writing, and add up the first month yourself.
Score each question as you go, not afterward.
How does LUKE answer?
LUKE is built for cash-pay practices. Here is how LUKE answers the questions above. Bring the ten questions to a demo and ask about each one.
Hosting (1): production runs on AWS under AWS's Business Associate Addendum.
Encryption (2): sensitive fields are encrypted individually with AES-256-GCM, including patient identity, intake answers, clinical notes, messages, vitals, prescription dosing and lab results.
Audit trail (3): a hash-chained, tamper-evident record of clinical and administrative actions, which administrators can verify on demand.
Sign-in (4): multi-factor authentication on every staff sign-in in production.
Clinic data (5): each clinic's data is scoped to that clinic.
AI (6): Staff AI runs on AWS Bedrock under the AWS Business Associate Addendum, behind a per-clinic switch, with a daily spend limit. AI use is recorded.
Import (7): Enterprise onboarding includes patient demographics and chart documents from a prior system.
Pricing (8): plan prices and onboarding fees are published at luke.care/#pricing.
Practice model (9): built for cash-pay practices.
One system (10): LUKE is one platform for clinical workflows and a lead CRM, and leads convert to patients.
Legal disclaimer: This article is for informational purposes only and is not legal, regulatory, medical or compliance advice. Rules, enforcement and platform policies change. Consult qualified legal counsel before you act on anything here.
See Each Answer Live
LUKE is a telehealth platform, built HIPAA-first, for clinics offering TRT, HRT, peptide therapy and GLP-1 weight management. Book a demo and bring the ten questions.
Encryption is an addressable specification in the Security Rule (45 CFR 164.312(a)(2)(iv) and (e)(2)(ii)). Addressable means you implement it if reasonable and appropriate, or document an equivalent alternative. Data encrypted to HHS guidance is also not "unsecured" for breach notification purposes (45 CFR 164.402).
If my cloud host cannot read my data, does it still need a BAA?
Yes. HHS says a cloud service provider that stores only encrypted patient data, without the key, is still a business associate (HHS FAQ 2076).
Does a vendor's HIPAA badge or certificate replace a demo?
No. A badge describes the vendor's own assessment. Seeing the control work is the evidence this scorecard counts.
What score is good enough?
There is no industry threshold. Compare vendors on the same ten questions, and treat a 0 on any question as something to resolve before you sign.