Pain Point, Solved 4.9 ★★★★★ Google Rating

How Do Practices Track Medicare’s In-Person Visit Requirement for Mental Health Telehealth?

Practices track Medicare’s in-person visit requirement for mental health telehealth by putting the last in-person visit date on every telehealth patient’s chart and running a monthly lookback report that flags anyone approaching the deadline, because the rule is enforced at claim adjudication, not at eligibility. Medicare conditions telehealth mental health payment on a non-telehealth visit within a set window before the first session and at least once every twelve months after, and the eligibility response never carries that clock. The fix has four moves: add an in-person-visit date field to every Medicare telehealth chart, run a monthly report of patients nearing the twelve-month mark, schedule the compliance visit sixty days before it lapses, and hold denied sessions against the correct visit date rather than writing them off. We run those moves inside the systems you already use, so a covered patient stays a paid patient. The table of contents maps the whole method; the moves after it are the detail.

What Actually Keeps Medicare Telehealth Claims From Denying on the In-Person Rule

The goal is simple: every Medicare telehealth patient has a current in-person visit on record before their session bills, and nobody finds out they lapsed from a denial. Here is what does that, move by move.

1. Put the In-Person Visit Date on Every Telehealth Chart

You cannot track a date you never captured. The first move is a dedicated field on every Medicare telehealth patient’s record that holds the last in-person visit date, entered at the start of care and updated every time a compliance visit happens. Eligibility responses do not carry this, so it has to live somewhere your team controls. Once the date is captured consistently, the whole rest of the method becomes a report instead of a scramble; without it, every denial is a surprise you learn about too late to prevent.

2. Run a Monthly Lookback Report Against the Deadline

Once the dates are captured, run a monthly report that lists every Medicare telehealth patient and how close they are to the twelve-month mark. The patients to act on are the ones inside sixty days of expiry, not the ones who already lapsed. Thirty minutes of report review a month replaces the annual pile of surprise denials, because you are now looking forward at who is about to fall out of compliance instead of backward at who already did.

3. Schedule the Compliance Visit Before It Lapses

A patient flagged sixty days out gets a real in-person visit on the calendar, not a reminder that sits in a queue. That visit resets the clock and keeps the telehealth sessions payable. For patients who genuinely cannot make an in-person visit, Medicare allows the clinician to document the reason it would pose a hardship or risk, so that exception is captured in the note rather than left to chance. The point is that the visit is booked on purpose, ahead of the deadline, not reconstructed after a denial.

4. Hold and Rework the Denials Against the Right Visit Date

When a denial does land, it is not automatically a write-off. The session is checked against the actual in-person visit date on file, and if a qualifying visit existed, the claim is corrected and resubmitted with that date documented rather than absorbed. Tracking every denial, its patient, and the visit date that answers it in one place is what keeps a rule enforced at adjudication from quietly turning delivered care into unpaid care.

5. Hand the Tracking to a Dedicated Team

Practices that stop losing telehealth sessions to this rule do it by handing the whole loop to a dedicated team: remote specialists who own the date field, run the monthly report, flag the sixty-day list, and rework the denials, live in 1 to 2 weeks. The clinicians go back to seeing patients, a trained backup covers every gap, and the compliance clock stops being the thing nobody was watching. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“Eligibility came back active every single time, so we had no reason to think anything was wrong. Then a block of telehealth claims denied at once in the winter, all for the same reason, and every one of them was a patient whose last in-person visit had quietly aged past a year.” – billing lead, behavioral health practice

“The rule is not checked when you verify benefits. It is checked when the claim goes in, months after the session, so by the time you see the denial the visit that would have fixed it is long gone. We were finding out about lapses the worst possible way.” – practice administrator, group therapy practice

“We were writing these off as uncollectible because nobody knew where the in-person date lived. It was not in the eligibility response, it was not flagged anywhere, it was just missing until a denial made it a problem.” – revenue cycle lead, behavioral health group

“Our clinicians are doing telehealth all day and they are not thinking about a compliance visit clock in the background. That is not their job, and it should not be. But somebody has to be watching that date, and for a long time nobody was.” – office manager, counseling practice

“Once we started running a monthly lookback and calling patients in sixty days before their year was up, the denials basically stopped. The whole thing turned out to be a tracking problem, not a coverage problem.” – practice manager, behavioral health practice

Our Answer

Here is what we actually do. A dedicated remote specialist puts the last in-person visit date on every Medicare telehealth patient’s chart, runs a monthly lookback report, and pulls the list of patients inside sixty days of the twelve-month deadline so a compliance visit gets booked before it lapses. When a denial does land, they check it against the real visit date on file and rework it with that date documented rather than let it become a write-off. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses and pharmacists, working inside your EHR and scheduling tools, with AI drafting the first-pass report and a human verifying every flag before it goes to your schedulers. This is our eligibility and benefits verification paired with an AI-first workflow, aimed at the one rule your eligibility check never shows you.

Why This Keeps Happening

If eligibility says the patient is covered, why do the claims still deny? Because Medicare’s in-person requirement is a condition of payment that lives outside the eligibility response. Effective October 1, 2025, under guidance from the Centers for Medicare and Medicaid Services and HHS, most Medicare behavioral telehealth requires an in-person, non-telehealth visit within six months before the first telehealth session and at least one in-person visit every twelve months after. The eligibility file tells you the patient has the benefit; it does not tell you whether the visit that keeps the benefit payable is still current. That gap is the whole problem.

The second half is timing. The rule is enforced at adjudication, not at the front end, so the failure is invisible until the claim is already submitted, often weeks after the session was delivered. By then the twelve-month window has closed and the fix, an in-person visit, cannot be applied retroactively to a session that already happened. A practice running dozens of Medicare telehealth patients has no way to feel a lapse coming unless someone is deliberately watching the date. This is exactly the blind spot a disciplined insurance eligibility verification workflow is built to close.

And the cost is not one claim. Because the lapses cluster, when a panel of patients crosses the twelve-month mark around the same time, a whole block of delivered sessions denies together, and telehealth is a high-volume, repeat-visit service. That is care your clinicians already gave, documented, and now cannot easily bill. The American Medical Association has long documented how much administrative burden these coverage conditions add to practices, and a rule you find out about only through denials is that burden at its most expensive.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the lapse you learn about from a denial. Because the in-person clock is invisible in the eligibility response and only tested when the claim adjudicates, a patient can fall out of compliance in the background while every session still looks covered on the front end. You keep seeing them by video, the claims keep going in, and then a block of them denies at once, all for visits already delivered. Unless someone is watching the date forward and booking the compliance visit before the window closes, the most damaging denials are the ones for care you already gave and can no longer make payable.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

What you tried What actually happened Who ended up doing the work
Trusted the eligibility check to catch it Eligibility said active every time; the in-person clock is not in that response, so nothing flagged until the claim denied The eligibility system, which never had the data
Left the compliance clock to the clinicians Clinicians are seeing patients, not watching a payment-condition calendar; the date drifted with nobody owning it Nobody, really
Wrote off the denied telehealth sessions Delivered care went uncollected because the in-person date lived nowhere the biller could check The bottom line
Gave the tracking to a dedicated remote specialist Date on every chart, monthly lookback, sixty-day flag, compliance visit booked before it lapses, denials reworked against the real date Someone whose whole job it is

The Solution

So what does “someone whose whole job it is” look like on the in-person rule? The specialist starts where the practice usually cannot: making sure the last in-person visit date is captured on every Medicare telehealth chart, then running a monthly lookback that lists exactly who is inside sixty days of the twelve-month deadline. That list goes to your schedulers with enough lead time to book a real visit, not a reminder that ages. Most of these denials are a tracking-and-scheduling problem, and that is precisely what dedicated eligibility and benefits verification is built to solve before it ever becomes a denied claim.

When a denial does slip through, the specialist takes the write-off off the table. They pull the session, check it against the actual in-person visit date on file, and if a qualifying visit existed, correct and resubmit the claim with that date documented rather than absorb it. For patients who cannot make an in-person visit, they make sure the clinician’s hardship or risk exception is captured in the note the way Medicare allows, so a legitimate exception is not read as a lapse. The delivered care gets paid instead of quietly disappearing into an aged-claim bucket.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow reads the panel, builds the lookback report, and flags the sixty-day list; a person confirms each flag is real and owns the outreach to your schedulers. Every security control that protects the patient data moving through that tracking is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving Medicare beneficiary records through an eligibility workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team track this rule better than your own staff? Because watching a payment-condition calendar across an entire Medicare telehealth panel is their whole day, not the thing they squeeze between check-ins. The people running your tracking are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US eligibility, telehealth billing, and Medicare compliance workflows. They know the difference between the eligibility response and the in-person clock, how to read a lookback report, and how to document a hardship exception correctly. That is not a generalist task handed to whoever is free; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so the compliance clock keeps getting watched even when the one person who usually watches it is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

✓ What stops happening: What stops happening: the block of telehealth claims that denies all at once in the winter. The lapse you find out about from a denial instead of a report. The delivered sessions written off because the in-person date lived nowhere the biller could check. The clinician quietly expected to watch a payment-condition calendar they were never meant to own. The Medicare patient who looks covered on eligibility right up until the claim adjudicates and says otherwise.
2-Week Free Trial

Ready to Stop Losing Telehealth Sessions to This Rule?

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented tracking workflow: where the in-person visit date lives on every Medicare telehealth chart, when the lookback report runs, what the sixty-day threshold is, who gets the flag, and how a denial is reworked against the real visit date. Before we track a single patient for a new practice, we chart your Medicare telehealth panel and find where the in-person dates are missing or stale, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than tribal knowledge in one coordinator’s head. It records how the date is captured, how the report is run, how the sixty-day list reaches your schedulers, how a hardship exception is documented, and how a denied session is corrected and resubmitted. It is written down, kept current as CMS guidance changes, and owned by the team. When your specialist is out, a trained backup runs the same report the same way, so a patient’s twelve-month clock never lapses because one person was away.

That is the difference between reworking this winter’s block of denials and fixing the process for good, and it is what a dedicated eligibility and benefits verification partner actually buys you. A coordinator leaving used to mean the tracking fell apart and lapses started stacking up again. Under this model the report keeps running, the playbook stays, the backup steps in, and Medicare’s in-person rule stops being the thing that quietly costs you delivered sessions.

The Whole Thing in Four Sentences

Practices track Medicare’s in-person visit requirement for mental health telehealth by capturing the last in-person visit date on every telehealth chart and running a monthly lookback that flags patients approaching the twelve-month mark, because the rule is enforced at adjudication and the eligibility response never carries the clock. Trusting eligibility, leaving the clock to clinicians, or writing off the denials all fail the same way. The fix is a captured date field, a monthly report, a compliance visit booked sixty days before expiry, and denials reworked against the real visit date. A behavioral health group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop losing telehealth sessions to this rule? Try us risk free: two weeks, your real Medicare telehealth panel, a dedicated specialist tracking the in-person date and reworking the denials, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Transparent Weekly Pricing

One Flat Weekly Rate. 45 Hours of Coverage.

No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.

Single
$399/ week

One dedicated remote specialist tracking the in-person visit date on every Medicare telehealth patient and flagging the ones approaching expiry, single-site behavioral health practice

Enterprise
$299/ week

10+ remote specialists, multi-location behavioral health network, MSO, or PE-backed platform tracking the in-person rule across many providers and patient panels

  How Pricing Works

45 hours of coverage for less than others charge for 40.

Standard US full-time year: 40 hrs x 52 weeks = 2,080 hours, the federal basis for computing hourly pay per the U.S. Office of Personnel Management. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour. Typical US market rates for healthcare virtual assistants run $9.50 to $13.00 per hour for 40 hours of coverage.

Trained backup VA Dedicated success manager Monthly training updates HIPAA-certified staff $5M E&O and cyber liability

Track Every In-Person Deadline This Month

You have seen the whole method. The pilot proves it on your own Medicare telehealth panel, with a lookback report your team can watch every month.

Start My 2-Week Free Trial

Request Information

Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.

Frequently Asked Questions

Because Medicare’s in-person visit requirement is a condition of payment that lives outside the eligibility response. The eligibility file tells you the patient has the telehealth benefit; it does not tell you whether the required in-person visit is still current. The rule is checked when the claim adjudicates, weeks after the session, so a lapse stays invisible on the front end until a denial reveals it.
Under guidance from the Centers for Medicare and Medicaid Services, most Medicare behavioral telehealth requires an in-person, non-telehealth visit within six months before the first telehealth session and at least one in-person visit every twelve months afterward. The requirement took effect October 1, 2025 for most providers. It is a payment condition, not an eligibility flag, which is why it has to be tracked separately.
Put the last in-person visit date on every Medicare telehealth patient’s chart, run a monthly lookback report of everyone approaching the twelve-month mark, and schedule the compliance visit for anyone inside sixty days of expiry. Thirty minutes of report review a month replaces the annual pile of surprise denials, because you are looking forward at who is about to lapse instead of backward at who already did.
Yes. Medicare allows the clinician to document that an in-person visit would pose a hardship or greater risk for a specific patient, such as a significant travel burden or a medical contraindication. That exception has to be captured clearly in the note, so a legitimate reason is recorded rather than read later as a lapse. Documenting it correctly is part of the tracking workflow, not an afterthought.
They are not automatically a write-off. Each denied session is checked against the actual in-person visit date on file, and if a qualifying visit existed, the claim is corrected and resubmitted with that date documented. The care was delivered; the goal is to make it payable against the right visit rather than absorb it because the date was never tracked in a place the biller could find.
No. Our specialist works inside the EHR and scheduling tools you already use, so there is no migration and no new platform for your staff to learn. They capture the in-person date where the chart already lives, run the lookback there, and hand the sixty-day list to your schedulers, which is why a typical practice is live in 1 to 2 weeks rather than months.
No. AI drafts the first pass, building the lookback report and flagging the patients approaching the deadline, and a credentialed human verifies every flag before it reaches your schedulers. The judgment about scheduling and documenting exceptions stays with people. Automation removes the repetitive report work so the specialist spends their time on the patients who actually need action, not on rebuilding the same list by hand.
Usually within the first monthly cycle. Once a dedicated specialist has captured the in-person dates and is running the lookback, the patients about to lapse get flagged and scheduled before the window closes, and the block of surprise denials that used to hit in the winter starts shrinking because nobody is falling out of compliance unnoticed anymore.
Your dedicated specialist works a 9-hour day, Monday to Friday, which is 45 hours of coverage each week. The ninth hour is part of the flat weekly rate, not billed as overtime. Over a year that is 2,340 hours of coverage, against the standard US full-time work year of 2,080 hours (40 hours x 52 weeks, the same basis the U.S. Office of Personnel Management uses to compute hourly rates of pay). That is how $399 per week works out to $8.87 per hour.
Dan Nandan, CEO of Staffingly, Inc.

Written By

Dan Nandan
Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From

Sources & References

  • Centers for Medicare and Medicaid Services Telehealth Policy Resources. Guidance on Medicare telehealth payment conditions, including the in-person visit requirement for mental health telehealth services. cms.gov
  • Telehealth.HHS.gov Policy Updates. Federal guidance on Medicare behavioral health telehealth flexibilities and the in-person visit requirement effective dates. telehealth.hhs.gov
  • American Medical Association Practice Management Resources. Physician-practice guidance on administrative burden and coverage conditions tied to telehealth billing. ama-assn.org
  • MGMA Practice Operations and Patient Access Resources. Benchmarks and guidance on eligibility, telehealth compliance, and revenue cycle for medical group practices. mgma.com
  • HFMA Revenue Cycle and Denials Management Resources. Guidance on eligibility-related denials, telehealth billing, and the revenue impact of coverage-condition lapses. hfma.org