Reimbursement and the Rules That Shape the Product

This is engineering guidance, not legal advice. Confirm specifics with qualified counsel.

Why this matters

If you are scoping a telemedicine product, reimbursement decides your revenue per visit, which states you can operate in, and which visit types are financially viable — before a single architecture decision is made. Product teams routinely discover, months after launch, that their platform cannot produce the records a payer demands, and every claim from day one is at risk of denial. The October 2025 lapse — 42 days during which Medicare's telehealth rules reverted to their 2019 defaults — showed that the rules move faster than product roadmaps. This article gives you the 2026 map of US reimbursement rules, the non-obvious vocabulary (originating site, modality requirements, parity), and the specific product features each rule forces. It is the last article in our foundations block, and the bridge into the compliance block that follows.

The payer is the silent product manager

Every telemedicine product has three possible revenue engines. The first is fee-for-service insurance billing: Medicare (the US federal program for people 65 and older), Medicaid (the state-run programs for low-income patients), and commercial insurers pay a fee for each visit that meets their rules. The second is contract revenue: an employer or hospital pays a subscription or a per-member-per-month fee, and individual visits are not billed to insurance at all. The third is cash-pay: the patient pays directly, as in most direct-to-consumer subscription services.

Why does this matter to an engineer? Because only the first model requires your platform to prove every visit to a third party — and that proof is a data structure. A billable telehealth visit is not "a video call happened." It is a record showing who the clinician was, where the patient was located, which technology carried the visit, how long it lasted, what was decided, and that the patient consented. If your platform cannot produce that record, the visit happened clinically but not financially.

The two non-payment rulebooks — state licensing and federal prescribing law — apply to all three revenue models. A cash-pay product escapes billing codes, but it does not escape the requirement that the clinician hold a license in the patient's state, or the federal rules on prescribing controlled medications remotely. We cover both below, because they shape the same product surfaces: routing, scheduling, and the visit record.

Figure 1. Four rulebooks govern one product — and two of them (licensing, prescribing) apply even when no insurance claim is ever filed.

Four rulebooks, one product

US telemedicine reimbursement is not one body of law. It is four, written by different authors on different clocks.

The practical consequence: "is this visit reimbursable?" is a function of at least four variables — payer, patient location, clinician type, and modality — and the answer carries an expiry date. Hold that thought; it becomes an architecture requirement at the end of this article.

The vocabulary: originating site, distant site, modality

Three terms from Medicare regulation do most of the work in any reimbursement conversation, and all three translate directly into data fields.

The place where the patient is during the visit is called the originating site. The place where the clinician is is the distant site. Historically, Medicare paid for telehealth only if the originating site was a medical facility in a rural area — the patient drove to a clinic to be connected to a remote specialist. The pandemic-era flexibilities suspended that, and through December 31, 2027 the patient's home, or anywhere in the US, qualifies (CMS Telehealth FAQ, updated 2026-02-26). When the originating site is a qualifying facility, that facility can bill a small hosting fee — HCPCS code Q3014, set at $31.85 for CY 2026.

Your claim tells the payer where the patient was through a place of service (POS) code: POS 10 means telehealth delivered to the patient in their home; POS 02 means telehealth delivered anywhere else. The distinction is money, not trivia — since January 1, 2024, Medicare pays home-based telehealth (POS 10) at the higher non-facility rate (CY 2024 PFS final rule). So the question "where are you right now?" at check-in is not UX politeness. It selects the code, the rate, and — as we will see under licensing — the law.

Modality requirements define which technology counts as a visit. Medicare's statutory default is an interactive, two-way, real-time audio-video connection. Audio-only visits are payable for patients at home through December 31, 2027 — and for behavioral health, permanently — but with a condition that surprises engineers: the clinician's system must be capable of video, and the record must reflect that the patient could not or did not consent to use it. Audio-only claims carry modifier 93 (a two-character code appended to the billing code identifying an audio-only service); synchronous video claims to commercial payers typically carry modifier 95. A modifier is an attestation, and your platform is the witness: if the call fell back from video to audio, the visit record should say so, and why.

Documentation requirements round out the vocabulary: payers expect documented patient consent for telehealth, the patient's and the clinician's locations, the modality used, and — for time-based codes — the duration. None of these fields exist in a generic video-call platform. All of them must exist in yours.

Medicare 2026: the current map and its expiry dates

Here is the state of Medicare telehealth as of June 2026, with the dates that matter.

Extended through December 31, 2027 (Consolidated Appropriations Act, 2026 — H.R. 7148, signed February 3, 2026): no geographic or originating-site restriction, so patients can be served at home anywhere in the US; an expanded practitioner list, including physical therapists, occupational therapists, speech-language pathologists, and audiologists; audio-only visits for patients at home; Federally Qualified Health Centers and Rural Health Clinics billing as distant sites (HCPCS G2025); and a waiver of the in-person-visit requirement for tele-mental-health.

Permanent, no expiry: behavioral and mental health telehealth at home, with no geographic restriction and with audio-only allowed (made permanent by the Consolidated Appropriations Act, 2021); the removal of frequency limits on subsequent inpatient and nursing-facility telehealth visits and critical-care consultations (CY 2026 PFS final rule, effective January 1, 2026); and virtual direct supervision — a supervising physician may now be "present" through real-time audio-video, excluding audio-only, for most services that do not carry a surgical global period (CY 2026 PFS final rule).

The January 1, 2028 cliff: unless Congress acts again, non-behavioral telehealth reverts to the statutory baseline — the patient must be in a medical facility in a rural area; therapists drop off the eligible-practitioner list; and the in-person-visit rule for tele-mental-health activates (an in-person visit within 6 months before the first tele-mental-health service, then every 12 months; patients established before 2028 skip the 6-month gate).

Figure 2. The expiry calendar. Every flexibility carries a date — and the October 2025 lapse shows the dates are enforced.

If that cliff sounds theoretical, October 2025 already rehearsed it. Congress missed the September 30, 2025 funding deadline, the government shut down, and the telehealth flexibilities lapsed with it. For 42 days — October 1 to November 12, 2025 — Medicare telehealth law reverted to the 2019 rules, and CMS instructed its claims processors to hold telehealth claims rather than deny them. The continuing resolution signed November 12, 2025 restored the flexibilities retroactively through January 30, 2026, and the CAA 2026 then extended them to the end of 2027 (CMS Telehealth FAQ Q16; APTA, November 2025).

Walk through what a lapse like that does to a provider's cash. Take a 12-clinician group running 2,000 Medicare telehealth visits a month at an illustrative average allowed amount of $75 per visit:

2,000 visits × $75 = $150,000 of claims per month 42 days ≈ 1.4 months → 1.4 × $150,000 ≈ $210,000 held, unpayable until Congress acted — retroactively payable only because Congress said so.

The product lesson is not "panic." It is that eligibility logic, payer rules, and even whether a visit type is billable at all are time-dependent variables outside your control. Products that hard-code them break twice a year. Products that store them as effective-dated configuration absorb a lapse — or a windfall — as a data update.

One more boundary worth knowing: services that are not a substitute for an in-person encounter — chronic care management, behavioral health integration, and remote patient monitoring — are not "Medicare telehealth" at all in the statutory sense, so the originating-site rules and expiry dates above do not apply to them (CMS Telehealth FAQ Q13). That single sentence of regulation is why an RPM product has no December 2027 cliff on its roadmap and a video-visit product does.

The codes your platform must support

In 2025 the American Medical Association replaced the old telephone-visit codes with a dedicated telemedicine family in CPT, the standard catalog of billable medical services: codes 98000–98007 for synchronous audio-video visits, 98008–98015 for synchronous audio-only visits that involve more than 10 minutes of medical discussion, and 98016 for a brief 5–10-minute "virtual check-in" with an established patient.

Then came the twist that defines telehealth billing in 2026: Medicare declined to pay the new family, judging it duplicative of existing office-visit codes. For Medicare, practices bill the ordinary evaluation-and-management codes 99202–99215 with the right POS code and, for audio-only, modifier 93 — while 98016 is the one new code Medicare does pay. Many commercial payers, meanwhile, accept the 98000-series. One visit, two coding dialects, selected by payer.

Read that table as a requirements document, because that is what it is. The platform needs a per-payer code map maintained as configuration, not constants. It needs an in-call timer, because 98008–98015 hinge on a 10-minute threshold and the evaluation-and-management codes can be selected by total time. It needs the modality-fallback attestation from the previous section, because modifier 93 asserts audio-only and the chart must back it up. And it needs time-stamped consent capture, because payers expect consent in the record. A claims clearinghouse or your customer's billing team handles submission — but they can only submit what the visit record contains. Revenue integrity starts in your data model, which is part of the anatomy of a telemedicine platform.

Figure 3. The billing-grade visit record. None of these fields exist in a generic video-call tool; all of them decide whether the visit is payable.

Parity laws: coverage is not payment

Medicare is federal and uniform. Commercial insurance is regulated state by state, and the operative word is parity — used in two senses that are routinely confused.

A coverage parity (or service parity) law says: if an insurer covers a service in person, it must cover it via telehealth. A payment parity law goes further: the insurer must also pay the same amount as it would in person. As of the Center for Connected Health Policy's Fall 2025 review, 44 states plus DC, Puerto Rico, and the Virgin Islands have private-payer telehealth laws — but only 24 states plus Puerto Rico require payment parity. In a coverage-parity-only state, a telehealth visit can be covered and still reimbursed at, say, 70% of the in-person rate, at the insurer's discretion.

Medicaid multiplies the variation by fifty: every state program covers live video in fee-for-service, but store-and-forward (asynchronous) coverage existed in 40 state programs as of Fall 2025, and remote-monitoring coverage varies in both scope and conditions. The same product feature — an asynchronous photo consult, say — can be revenue in one state and a free amenity in the next.

For a product team this is a unit-economics input, not background reading. A teledermatology product whose business case assumes $120 per asynchronous consult works in a state whose Medicaid program and parity law support it, and quietly loses money in a state where only live video is paid. "Which states do we launch in?" is a spreadsheet of parity rules — build it before the architecture review, and revisit it each legislative season. Our cost-model article shows where per-visit revenue assumptions enter the budget.

Licensing: the state line is a product feature

The default rule of US medicine is blunt: the clinician must hold a license in the state where the patient is located at the time of service. The doctor's location is mostly irrelevant; the patient's is decisive. Cross the line — a New York-licensed physician treating a patient vacationing in Florida — and the visit may be unlicensed practice of medicine, regardless of video quality or clinical excellence.

Three interstate compacts soften this, in two different ways. The Interstate Medical Licensure Compact (IMLC) — 43 states plus DC and Guam as of 2026 — is an expedited application pathway: a physician still ends up holding (and paying for) a separate license in each state. The Psychology Interjurisdictional Compact (PSYPACT, 43 jurisdictions) and the Nurse Licensure Compact (NLC, 43 jurisdictions) use a privilege model: one home-state license grants the right to practice into every member state. Same word — "compact" — two product realities: under IMLC your provider directory tracks many licenses per physician; under PSYPACT it tracks one license plus a compact-privilege flag.

The product surface this creates is routing. At visit start, the platform captures the patient's current state — asked explicitly, not inferred silently from GPS or billing address, though geolocation makes a good cross-check. The scheduling and waiting-room logic then matches the patient only to clinicians licensed (or privileged) for that state, and the visit record stores both locations for the claim and for the audit. A license-state matrix with expiry dates per provider, a state captured per visit, and a hard guard in the matching engine: that is licensing law, rendered as three database tables. The state and specialty rules article goes deeper.

Figure 4. One question — "where is the patient right now?" — gates licensing, payer rules, and the code path.

Prescribing: the DEA clock

Prescribing adds a federal rulebook with its own calendar. The Ryan Haight Online Pharmacy Consumer Protection Act of 2008 requires, with limited exceptions, at least one in-person medical evaluation before a clinician may prescribe a controlled substance — medications like opioids, stimulants for ADHD, or benzodiazepines, scheduled by the Drug Enforcement Administration (DEA). The pandemic suspended that in-person gate, and the suspension has been extended repeatedly: the current Fourth Temporary Extension (DEA and HHS, Federal Register, December 31, 2025) runs through December 31, 2026. It allows prescribing of Schedule II–V medications via audio-video telemedicine without a prior in-person exam, and certain opioid-use-disorder medications via audio-only.

The permanent framework — a proposed "Special Registration for Telemedicine" that would let registered practitioners prescribe remotely as a durable rule rather than a waiver — was published as a proposed rule on January 17, 2025, and has not been finalized as of June 2026. A telepsychiatry or ADHD-care product therefore has a regulatory dependency with an 18-month-old pending rule and a hard expiry date inside its current roadmap.

The product implications: prescribing flows must be schedule-aware (a flag on the medication, checked before the e-prescription is created), able to enforce an in-person-visit linkage if the rules tighten, and integrated with EPCS — electronic prescribing of controlled substances, with its identity-proofing and two-factor requirements — which we cover in the e-prescribing article.

Build the rules as data, not code

Pull the threads together and a single architectural pattern falls out. Every rule in this article is a fact with dimensions — payer, state, modality, clinician type, service — and a validity window. The October 2025 lapse, the December 31, 2026 DEA expiry, the December 31, 2027 flexibility sunset, the January 1, 2028 in-person-visit activation: these are rows with effective dates, not constants in source code.

Common mistake: shipping the rules as code. A team builds in 2026, tests against 2026 Medicare rules, and hard-codes them — audio-only as a boolean, one national provider pool, one code path for all payers. The first December rule change triggers an emergency release; the 2028 cliff triggers a rewrite. The fix costs almost nothing on day one: an effective-dated billing_rules table, a visit record with the nine fields in Figure 3, and a quarterly review tied to the PFS rulemaking cycle (proposed rule each summer, final rule each November, effective January 1; requests to change the Medicare telehealth-services list are due to CMS by February 10 each year).

Outside the US: a short note

The architecture lesson travels even where fee-for-service does not. In England, NHS video consultations are funded through general-practice contracts and block arrangements rather than per-visit claims — the product pressure shifts from claim records toward capacity, triage, and waiting-list management. In the EU, Directive 2011/24/EU gives patients a reimbursement route for cross-border care, explicitly including telemedicine, but each member state sets its own tariffs, prior-authorization rules, and e-health requirements — so "which country pairs do we support?" becomes the analogue of the US state matrix. The constant across systems: somebody pays, that somebody has rules, and the rules end up in your schema.

Where Fora Soft fits in

We build telemedicine platforms with the billing record designed in from the start — patient-location capture, modality and fallback attestation, duration tracking, consent, and effective-dated rules configuration — because retrofitting them after launch is the most expensive way to learn US reimbursement. Since 2005 we have shipped video products across telemedicine, conferencing, streaming, e-learning, and surveillance, and the recurring pattern in healthcare work is exactly this article's thesis: the compliance requirement comes first, then the feature. If you are deciding which states, payers, and modalities your product can afford to serve, that analysis belongs in the first sprint, and we are happy to pressure-test it with you.

What to read next

• Synchronous, asynchronous, and remote patient monitoring — three products, three architectures — how each modality maps to a different Medicare payment category.
• The telemedicine cost model — where per-visit revenue meets build and run cost.
• State and specialty rules: telehealth licensing, prescribing, mental health — the 50-state layer in depth.

Call to action

• Talk to a telemedicine engineer — book a 30-minute scoping call to talk through your telehealth reimbursement rules plan.
• See our case studies — 250+ shipped projects across video streaming, WebRTC, OTT, telemedicine, e-learning, surveillance, and AR/VR.
• Download the Telehealth Reimbursement Rule Calendar — One page: every 2026–2028 US telehealth rule date (Medicare flexibilities, DEA waiver, the 2028 cliff, the PFS rulemaking cycle) plus the nine fields of a billing-grade visit record.

References

1. CMS, Telehealth FAQ (updated 2026-02-26) — geographic/originating-site policy through 2027-12-31, POS 02/10, in-person-visit rules, retroactive payment after the FY2026 lapse. https://www.cms.gov/files/document/telehealth-faq-updated-02-26-2026.pdf (Tier 1)
2. CMS, Calendar Year (CY) 2026 Medicare Physician Fee Schedule Final Rule fact sheet (CMS-1832-F, 2025-10-31) — Q3014 originating-site fee $31.85; permanent removal of frequency limits; virtual direct supervision; telehealth-list simplification. https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2026-medicare-physician-fee-schedule-final-rule-cms-1832-f (Tier 1)
3. Federal Register, CY 2026 Payment Policies Under the Physician Fee Schedule (final rule, 2025-11-05). https://www.federalregister.gov/documents/2025/11/05/2025-19787/ (Tier 1)
4. Congress.gov, H.R. 7148 — Consolidated Appropriations Act, 2026 (signed 2026-02-03) — Medicare telehealth flexibilities extended through 2027-12-31. https://www.congress.gov/ (Tier 1)
5. DEA & HHS, Fourth Temporary Extension of COVID-19 Telemedicine Flexibilities for Prescription of Controlled Medications (Federal Register, 2025-12-31; effective 2026-01-01 through 2026-12-31). https://www.federalregister.gov/documents/2025/12/31/2025-24123/ (Tier 1)
6. DEA, Special Registrations for Telemedicine and Limited State Telemedicine Registrations (proposed rule, 2025-01-17; not finalized as of 2026-06). https://www.federalregister.gov/ (Tier 1)
7. Social Security Act §1834(m) and 42 CFR §410.78 — the statutory and regulatory definition of Medicare telehealth, geographic and modality conditions. https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-B/part-410/subpart-B/section-410.78 (Tier 1)
8. Center for Connected Health Policy, State Telehealth Laws and Reimbursement Policies Report, Fall 2025 — 44 states + DC + PR + VI with private-payer laws; 24 states + PR with payment parity. https://www.cchpca.org/resources/state-telehealth-laws-and-reimbursement-policies-report-fall-2025/ (Tier 5 — institutional)
9. American Medical Association, Telemedicine E/M CPT codes 98000–98016 (CPT 2025/2026). https://www.ama-assn.org/practice-management/cpt/how-ama-meets-need-new-telehealth-cpt-codes (Tier 3)
10. Telehealth.HHS.gov, Billing and coding Medicare fee-for-service claims — POS 02/10 and modifier guidance. https://telehealth.hhs.gov/providers/billing-and-reimbursement/billing-and-coding-medicare-fee-for-service-claims (Tier 2)
11. Interstate Medical Licensure Compact Commission; PSYPACT Commission; NCSBN Nurse Licensure Compact — membership as of 2026: IMLC 43 states + DC + Guam; PSYPACT 43; NLC 43. https://www.imlcc.com/ · https://psypact.org/ · https://www.ncsbn.org/nlc (Tier 2)
12. APTA, Government Shutdown Ended: Telehealth Flexibilities Extended Until Jan. 30, 2026 (2025-11-17) — the 42-day lapse, claims holds, retroactive restoration. https://www.apta.org/article/2025/11/17/government-shutdown-ended (Tier 5)
13. Directive 2011/24/EU on the application of patients' rights in cross-border healthcare — telemedicine within the EU reimbursement framework. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32011L0024 (Tier 1)

Where lower-tier summaries disagreed with rule text — for example, vendor billing blogs describing CPT 98000–98015 as universally payable — this article follows the controlling sources: Medicare payment policy per the CY 2025/2026 PFS rules and the CMS Telehealth FAQ.