Telehealth equipment reimbursement sounds straightforward: help employees get the basics, maybe a headset, a camera, and a blood pressure cuff, so virtual care is actually usable at home.
But in real benefit programs, this “small” idea creates outsized friction. The reason is simple: telehealth equipment sits at the intersection of plan design, payroll, tax rules, privacy, and vendor administration. Pick the wrong path and you don’t just waste money; you create a compliance headache and erode employee trust.
But when it’s designed as a system (not a one-off policy), telehealth equipment support becomes a practical tool for prevention-first care and, over time, claims avoidance.
Decide the money rail and the data rail before the device list
Most employers start by asking, “What equipment should we reimburse?” That’s the wrong first question.
The two decisions that matter most are invisible:
- The money rail: Are you paying through payroll, an HRA, the health plan, an FSA/HSA-compatible route, or by providing company-owned equipment?
- The data rail: What information are you collecting to approve the request: just a receipt, an attestation, or something that reveals medical details?
Pick the wrong rails and your program either becomes too hard to use (so no one participates) or too risky to manage (so it becomes a constant exception process).
Start by categorizing “equipment” (because it’s not one category)
A single reimbursement policy for “telehealth equipment” usually fails because the items people request don’t behave the same way under tax rules, plan rules, or operational reality. In practice, you’re juggling multiple buckets:
1) Connectivity and home setup
Broadband upgrades, mobile hotspots, routers, lighting, or noise-canceling headsets. These may be essential to access, but they’re often the hardest to justify as a medical expense. This is where programs drift into “general convenience” spending.
2) General-purpose hardware
Tablets, phones, laptops, and webcams are typically dual-use. The cost isn’t the problem. The problem is governance: who owns it, what happens when it breaks, and whether it’s being used for the intended purpose.
3) Medical-adjacent peripherals
Digital blood pressure cuffs, pulse oximeters, connected scales (sometimes), and similar tools tend to be more defensible because they directly support preventive care and condition management.
4) True medical equipment (DME-like)
When the item is clearly medical equipment tied to diagnosis or treatment, it often belongs in a health plan or clinical vendor workflow, not a manual HR reimbursement process.
The tax test behind the buckets: primarily for medical care
The reason some items clear the bar and others do not is a single rule. Under 26 U.S.C. section 213(d), an expense is medical care only when it is primarily for the diagnosis, cure, mitigation, treatment, or prevention of disease, or for affecting a structure or function of the body. The IRS reads that test strictly: an expense that merely benefits general health does not qualify.
That one sentence does most of the sorting for you. A blood pressure cuff or pulse oximeter measures a physiological function, so it is easier to defend. Broadband, a router, or a laptop is a general-purpose tool; it fails the test no matter how much easier it makes a video visit. That is also why general-purpose hardware usually belongs on the taxable stipend or company-owned rail, not the FSA/HSA rail.
The practical effect is to stop spending compliance effort trying to squeeze connectivity gear into a tax-advantaged bucket. Spend it on substantiating the monitoring peripherals and true medical items, where the tax treatment holds and the preventive value is real.
The compliance trap: you can accidentally create (or expand) a group health plan
Here’s the part that rarely gets discussed plainly: a telehealth equipment reimbursement program can unintentionally become a group health plan feature depending on how it’s structured.
When employers reimburse items as “medical care” without a clean administrative structure, the program can pull in expectations and obligations tied to ERISA, COBRA, and privacy practices that resemble HIPAA-grade handling (especially if medical details start flowing into HR).
The most common failure pattern looks like this:
- An employee asks for reimbursement.
- HR requests “proof” (often a note from a provider or medical necessity language).
- That documentation lands in an HR inbox or ticketing system.
- Payroll reimburses it.
Good intent aside, you’ve just built a process where the employer is collecting and storing sensitive medical context. That is a trust problem first and a risk problem second.
The fix is structural. Fund the item through a route where someone else performs the medical substantiation, or pay it as plainly taxable compensation so the amount never carries medical meaning.
Pick the right funding approach (and be honest about the trade-offs)
Employers fund this in a few common ways. The key is to match the approach to the type of item and your tolerance for administration.
A) Taxable stipend through payroll
Operationally, this is the simplest. It scales fast and doesn’t need receipt police. The catch? It’s taxable compensation, and employees may not experience it as a true healthcare benefit.
B) Provide company-owned equipment
This often works best for dual-use hardware like tablets or laptops. It also helps with standardization and IT/security controls. The trade-off is logistics: shipping, replacements, and support.
C) Let employees use FSA/HSA dollars (when eligible)
This can be clean because it keeps the employer out of the medical-substantiation loop. The trade-off is that not everything qualifies, and not every employee has available funds (which can create uneven adoption).
D) Use an HRA or medical reimbursement arrangement
HRAs can be effective, but they require careful administration and thoughtful design. If you’re not already set up to manage substantiation and plan governance well, this is where complexity can multiply.
E) Route fulfillment through the health plan or clinical vendor
For items that are clearly medical, this is often the safest from a governance and privacy standpoint. The trade-off is implementation speed and dependence on partner capabilities.
The part most programs miss: substantiation is the product
Telehealth equipment reimbursement lives or dies on substantiation. If it’s too strict, employees disengage. If it’s too loose, you invite waste and create uncomfortable edge cases.
A smarter approach is to substantiate the preventive action, not the device.
Instead of asking employees to justify a device (which invites medical detail), you can tie support to verified steps like:
- Completing an annual preventive visit or screening
- Following through on labs and a documented follow-up
- Completing a chronic care check-in cadence
- Meeting adherence or monitoring milestones tied to a plan of care
This shifts the program from “receipt review” to prevention enablement. It’s easier to measure, easier to explain to finance leaders, and far less intrusive for employees.
Equity matters: reimbursement can quietly favor the people who already have access
On paper, reimbursements look fair: the same cap for everyone. But in real life, they can tilt toward employees who already have stable internet, private space, and enough cash flow to buy equipment upfront.
If your workforce includes frontline, hourly, rural, or shared-housing employees, consider adding options that reduce those barriers:
- Provide standardized kits rather than reimbursements for certain roles
- Offer private telehealth spaces on-site for employees who need them
- Use an approved catalog to reduce shopping friction and out-of-pocket timing issues
- Reward care completion (a behavior) rather than purchases (a financial capacity test)
Keep medical details out of HR inboxes
If your process requires employees to send diagnosis notes or medical necessity letters to HR, pause. That creates unnecessary data retention risk, inconsistent access controls, and employee discomfort.
A simpler design is to send substantiation through the right administrator or vendor so HR/payroll only sees the minimum: approved/denied and amount. Employees get the benefit without feeling like they’re sharing medical context with their employer.
Measure it like a benefits strategy, not a purchase program
The ROI story here isn’t “a webcam saves money.” The real value is what better access changes: earlier detection, reduced avoidable utilization, better chronic control, fewer delayed-care blowups.
So measure what actually moves cost over time:
- Utilization shifts (virtual vs. in-person vs. urgent care)
- Preventive care completion rates
- Follow-up adherence (labs, check-ins, medication routines)
- Downstream claims patterns over renewal cycles
A practical checklist to implement without creating a mess
If you’re building (or cleaning up) a telehealth equipment reimbursement program, this sequence prevents most problems:
- Define the objective (access, prevention uptake, chronic management, retention).
- Segment eligible items into connectivity, hardware, peripherals, and DME-like equipment.
- Choose the right funding rail for each bucket (stipend vs. company property vs. tax-advantaged routes vs. plan/vendor fulfillment).
- Design substantiation around actions (what was done) rather than diagnoses (why it was needed).
- Minimize sensitive data exposure so HR isn’t storing medical details.
- Build equity into delivery (kits, spaces, catalogs, upfront barriers).
- Track leading and lagging metrics tied to preventive behavior and claims outcomes.
Done right, it stops being a fringe policy and becomes a practical way to remove friction from prevention-first care, with no tax surprises, no privacy scares, and no admin sprawl.
This guide is for general information only and is not legal, tax, or medical advice. Employers should consult their own advisors.