Telehealth Billing: Fix POS 02 and POS 10 Before Year-End

A physician conducts two video visits from the same office, using the same platform and the same documentation template. One patient joins from home; the other joins from a workplace. The encounters look almost identical on the schedule. For traditional Medicare professional billing, however, the patients’ locations point to different place-of-service codes—and potentially different payment calculations. If the practice management system assigns both visits the office’s default location, a clean-looking claim can still be wrong.

As practices prepare January schedules and review year-end revenue in October 2026, telehealth deserves a more precise check than “Is this visit covered?” Federal coverage provisions, Medicare payment instructions, state requirements, and commercial payer policies operate on separate tracks. A change on one track does not automatically change the others. The practical task is to build claims from what actually happened: where the patient was, how the encounter occurred, what service was furnished, and which rules applied on that date. Start with POS 02 and POS 10, then follow the information through scheduling, documentation, claim creation, and payment.

1. Separate Coverage Eligibility From Claim Mechanics

Telehealth policy discussions often collapse several questions into one. Is the service eligible for remote delivery? May this patient receive it at this location? Is this practitioner eligible to furnish it? Which code, modifier, and place of service belong on the claim? A favorable answer to one question does not settle the others.

This distinction matters during year-end planning. Medicare telehealth availability can depend on statutory provisions as well as CMS regulations. A service’s appearance on the Medicare telehealth services list does not, by itself, establish that every patient location or communication method is permitted. Likewise, the existence of POS 10 does not make every service furnished to a patient at home payable.

Use a date-specific coverage check before applying billing instructions. Review the applicable CMS telehealth guidance, the Medicare telehealth services list, Medicare Administrative Contractor instructions, and the payer’s current provider manual. For commercial insurance and Medicare Advantage, identify the actual product; a payer’s corporate name alone is not enough.

Avoid building January 2027 schedules around an assumed extension, expiration, or universal rollback. Record what the governing source says and when the team checked it. If a future provision remains unsettled, flag the affected appointments for review rather than silently converting an assumption into a scheduling rule.

2. POS 02 and POS 10 Describe the Patient’s Location

For professional telehealth billing, POS 02 identifies telehealth provided other than in the patient’s home. POS 10 identifies telehealth provided in the patient’s home. The deciding fact is the patient’s location—not the physician’s office address, the billing company’s location, or the place where the video platform’s equipment sits.

Under the Medicare Physician Fee Schedule policy implemented in 2024, covered telehealth services billed with POS 10 are paid using the nonfacility rate, where applicable. POS 02 generally points to the facility rate. This distinction can affect the allowed amount even when the service code and clinician are unchanged. It does not mean every code has two different rates or that every payer follows Medicare’s payment methodology.

Consider an established-patient video visit that otherwise supports 99214. If the patient participates from home, POS 10 is the relevant telehealth location code. If the patient participates from a workplace, POS 02 describes that location category—but the practice must still establish that the service is covered under the applicable originating-site rules or exceptions.

Do not substitute POS 11 simply because the physician is sitting in an office. Also, do not apply professional-claim POS logic indiscriminately to institutional claims, rural health clinics, or federally qualified health centers. Those settings have additional billing structures and instructions.

3. Capture Location at the Encounter, Not Just at Registration

A home address in the registration file establishes where a patient receives mail. It does not establish where the patient was during Tuesday’s appointment. Patients join visits from relatives’ houses, workplaces, parked vehicles, and facilities. Some travel across state lines without realizing that the change can affect both clinical authorization to practice and insurance coverage.

Ask the patient to confirm the physical location at the start of the encounter. Capture enough detail to distinguish home from another setting and to identify the state. Clinical teams may also need the actual address for emergency response. The claim should receive the appropriate location category without relying on a biller to interpret a vague note.

Keep the question neutral: “Where are you physically located for today’s visit?” is better than “You’re at home, correct?” A patient temporarily staying elsewhere may require clarification. A nursing facility or hospital should not automatically become “home” merely because the patient currently resides there.

Make location changes visible. If scheduling records home but the clinician confirms a workplace, the encounter-level information should control the billing review. Never overwrite the patient’s permanent mailing address just to make the telehealth claim work.

• Document the patient’s actual location and state for the encounter.
• Record the communication method actually used, not merely the scheduled visit type.
• Flag institutional settings and unclear locations for review.
• Route out-of-state encounters for appropriate licensure and payer-policy checks.

4. Treat Audio-Only as a Different Billing Decision

A failed video connection is not just an IT problem. It can change the billing analysis. A visit scheduled as audiovisual may end up entirely by telephone, or the connection may fail after part of the service. The final claim must reflect the encounter that occurred, subject to the payer’s rules for that service and modality.

CMS has established specific circumstances in which audio-only communication can satisfy Medicare telehealth requirements. These are not blanket permission to bill every telephone encounter as a video visit. Check the service, patient location, applicable coverage conditions, and documentation requirements for the date of service.

Modifiers are another source of false confidence. Modifier 95 generally identifies synchronous audiovisual telemedicine when required by the relevant billing instructions. Audio-only services may require modifier 93 or, in defined Medicare circumstances, FQ. Do not select among them by habit or assume they apply identically across payers. A modifier cannot turn an ineligible service into a covered one.

Give clinicians a structured way to document technology failure, the method used afterward, and any policy-relevant reason video was not used. Avoid a universal attestation that patients “could not use video” when that was never established. If the facts do not support billing, send the encounter for review before releasing a claim.

5. Replace the Universal Telehealth Template With a Payer Matrix

One template for all telehealth claims is convenient until different payers require different treatment. Commercial plans may have their own accepted code sets, modifiers, benefit restrictions, and payment arrangements. Medicare Advantage plans cover Medicare benefits, but that does not make every operational claim instruction or contracted payment term identical to traditional Medicare.

Build a compact matrix around the services your practice actually furnishes. A psychiatry group does not need a sprawling reference file covering every specialty. It needs reliable instructions for its common encounters, relevant patient locations, audiovisual and audio-only options, and payer products.

Whether the work stays in-house or is supported by medical billing services, assign an owner to every rule change. The useful deliverable is not a downloaded policy. It is a tested claim configuration, a staff instruction, and a record of the source and effective date.

Include exceptions rather than hiding them in free-text notes. Behavioral health telehealth has service-specific statutory provisions and requirements that should not be generalized to unrelated care. Where an in-person requirement or exception may apply, verify its operative timing for the service date instead of relying on an old pandemic-era checklist.

• Payer and product, including the applicable line of business.
• Covered service codes and supported communication methods.
• Location eligibility, POS instructions, and required modifiers.
• Authorization, referral, and documentation requirements, where applicable.
• Policy source, effective date, verification date, and internal owner.

6. Test What the Billing System Actually Sends

The note can be correct while the claim is wrong. An encounter may display POS 10 in the electronic health record, then inherit POS 11 when charges cross into the practice management system. A clearinghouse rule may append a modifier to every visit labeled “virtual.” A billing team may correct one claim without fixing the mapping that created the error.

Trace a small set of representative encounters from scheduling through the outbound professional claim. Inspect the transmitted fields, not just the screen used to enter charges. Include a home video visit, a covered non-home encounter, an eligible audio-only encounter, and a visit whose modality changed after scheduling.

For each test, compare the location and modality in the clinical record with the POS and modifier values actually transmitted. Then inspect the payer’s adjudication. Clearinghouse acceptance means the transaction passed certain edits; it does not prove coverage, coding accuracy, or correct reimbursement.

Use exception edits where they can catch meaningful contradictions. A home telehealth encounter mapped to POS 02 deserves review. So does an audio-only note paired with an audiovisual modifier. Do not create an edit that forces staff to choose the financially preferable answer. The edit should demand reconciliation with the facts, not manufacture them.

7. Audit Paid Claims, Not Just Telehealth Denials

Telehealth location errors often survive adjudication. A payer may pay a claim carrying the wrong POS without asking where the patient was. That makes denial reports an incomplete control. The practice needs to examine paid claims for both underpayment and possible overpayment.

Start with a targeted sample rather than an indiscriminate rebilling project. Look for clinicians whose telehealth claims all carry one POS, visits with missing location documentation, and encounters converted from video to telephone. Review allowed amounts, not simply the cash deposited, because deductibles and coinsurance affect how payment is divided.

For traditional Medicare, compare the allowed amount with the applicable fee schedule, locality, service code, and facility or nonfacility basis. For contracted payers, use the agreement and relevant payment policy. Do not assume Medicare’s POS 10 treatment controls a commercial contract.

If the record supports a correction, follow the payer’s corrected-claim or reopening process and applicable deadlines. If the record does not establish location, do not fill the gap by assuming the patient stayed home. Evaluate any identified overpayment under the applicable reporting and return requirements. An audit that only pursues additional reimbursement is not a complete audit.

8. Set Patient Expectations Without Promising Coverage

Patients often hear “telehealth appointment” as a promise that insurance will pay. Front-desk staff should not reinforce that assumption. Scheduling eligibility, benefit verification, authorization, and final payment are related but distinct. A benefit quotation is not a payment guarantee.

Give patients a short, practical explanation before the visit: the practice needs their physical location, the planned communication method matters, and a change may require review. If the patient will be traveling, resolve the question before the appointment where possible. Discovering an out-of-state location after the clinician has completed the service creates avoidable clinical and billing complications.

Do not treat a generic financial-responsibility signature as permission to transfer every telehealth denial to the patient. Medicare beneficiary-liability rules, payer contracts, state law, and the reason for noncoverage all matter. When a Medicare Advance Beneficiary Notice is relevant, it must meet the applicable requirements; it is not a universal waiver for uncertain telehealth billing.

Keep the language usable. “Please tell us if you will be outside your usual home location” is more helpful than a page of unexplained regulatory terms. Staff also need an escalation contact who can answer questions without improvising a coverage promise.

9. Finish the Year With a Telehealth Control You Can Repeat

A useful year-end project should leave the practice with a repeatable process, not a binder that becomes obsolete in January. Choose one clinical lead, one billing lead, and one system owner. Together, they should validate the payer matrix, test claim mappings, and review a sample of recently paid encounters.

Separate historical corrections from prospective changes. A new payer instruction may require a system update for future dates without establishing that every older claim was wrong. Conversely, discovering a longstanding mapping defect may justify a broader lookback. Document why the review period and claim population were chosen.

If external medical billing services handle submission or follow-up, put the control responsibilities in writing. Specify who maintains payer rules, who investigates mismatches, who approves corrected claims, and who reports possible overpayments. Outsourcing claim work does not eliminate the practice’s need for oversight.

Track a few actionable measures: encounters missing location, claims held for modality conflicts, confirmed POS errors, and unresolved payment variances. Review them after configuration changes and whenever relevant policies change. The goal is not to produce more alerts. It is to make the patient’s location and the actual encounter survive every handoff—from the first scheduling question to the final payment posting.