A behavioral health group ran a claims audit last quarter and found 214 telehealth encounters billed with the office place-of-service code and a telehealth modifier, because that was the workflow someone built in 2020 and nobody revisited. Two payers had already recouped. The fix was not complicated, but it required retraining three schedulers, editing a template, and re-opening a conversation about what the practice stores when it asks a patient where they are sitting. This is a practice-operations guide to POS 10 in medical billing: what the code means, who captures the information, what your documentation has to show, and the privacy and vendor obligations that ride along with it.

If you sign payer contracts, manage a billing team, or own the compliance file, this is your lane. Coding decisions belong to your coders and providers working from payer policy — what follows is how practices build the process around those decisions.

What POS 10 in Medical Billing Means

POS 10 is the place-of-service code for telehealth provided in the patient's home. It tells the payer that at the moment of the encounter, the patient was in a private residence rather than a hospital, clinic, or other facility. CMS added it to the place-of-service code set effective January 1, 2022, and Medicare began accepting it on claims April 1, 2022. Its companion, POS 02, covers telehealth provided somewhere other than the patient's home.

The code describes the patient's location, not the provider's. A physician sitting in an exam room and a physician sitting in a home office both bill based on where the patient was. The full descriptors live in the CMS place of service code set, and that page is the reference your billing team should cite in internal policy rather than a screenshot from a webinar.

POS 10 vs. POS 02 in Practice

The operational distinction is narrow and it trips up staff constantly. A patient joining from their apartment, a relative's house they are staying in, or temporary lodging generally sits on the home side. A patient joining from a nursing facility, a hospital room, or an originating-site clinic sits on the POS 02 side. A patient who took the call from their car in a parking lot is a judgment call your coding policy should address in advance, not at 4:50 p.m. on a Friday.

Money follows the distinction. CMS has priced POS 10 at the non-facility rate and POS 02 at the facility rate, so a swapped digit moves reimbursement on every affected line. Verify current values against the Medicare Physician Fee Schedule before you build any internal expectation, and never assume a commercial payer mirrors Medicare — several still require POS 02 across the board, and some direct practices to bill the physical office location with a telehealth modifier. Get each policy in writing and file it with the contract.

The Intake Script That Produces a Defensible Place of Service

You cannot code the patient's location if nobody asks. Build the question into the encounter opening, assign it to a role, and require an answer before the clinical portion starts.

A workable script for the person launching the visit: "Before we begin, I need to confirm where you're located right now — are you at home, or somewhere else?" If the answer is anything other than home, the follow-up is the type of location, not the street address. "A skilled nursing facility" is what the coder needs. The building's suite number is not.

Three role assignments make this stick:

  • Scheduler or intake coordinator: asks the location question during the reminder call and flags anticipated non-home visits in the appointment note.
  • Provider or clinical support staff: confirms location at the start of the encounter and records it in the designated chart field, because the anticipated location and the actual location diverge often.
  • Billing lead: owns the crosswalk from the recorded location to the place-of-service code, applies payer-specific rules, and works the denial queue.

Do not let the provider guess from context. "It looked like her kitchen" is not documentation.

The Documentation Trail an Auditor Will Ask For

When a payer audits telehealth claims, the reviewer generally wants to see four things tied to each encounter: the patient's location during the service, the provider's location, the modality used, and the consent to receive care by telehealth. Your template should capture all four in discrete, searchable fields rather than free text buried in a narrative.

Modality matters because audio-video and audio-only encounters are reported differently. Modifier 95 has been used to identify synchronous audio-video telehealth; modifier 93 identifies audio-only. Which modifier a payer expects alongside POS 10 in medical billing varies by payer and by code, so your coders need current payer policy, not tribal memory. Document the modality the clinician actually used, and let the coder select the reporting combination from policy.

Consent documentation is separate from the HIPAA authorization question and is frequently a state-law requirement. Record the date, the person who obtained it, and the method. Annual re-consent is a reasonable internal standard for ongoing telehealth patients.

Asking Where a Patient Is Sitting Creates New PHI

The moment you collect and store the patient's physical location at the time of service, that location becomes part of the designated record set. It shows up in the chart, in appointment notes, sometimes in the telehealth platform's session logs, and occasionally in a scheduling comment field that four staff members can read.

Two practical consequences. First, location data lands inside records requests. When a patient asks for their chart, encounter notes containing home or facility location go with it, and the response clock runs the same as any other request. Second, minimum necessary applies. A coder needs to know the category of location to select a place-of-service code. A coder does not need a street address, an apartment number, or the note that the patient was staying at a domestic violence shelter. Design the field to accept a category, and train staff not to volunteer specifics into free-text boxes.

Location detail is exactly the kind of data that turns an ordinary disclosure into a sensitive one. A leaked appointment list showing a patient joined a psychiatry visit from an inpatient facility is a materially worse event than a leaked list of office visits. Treat the field accordingly in your access review.

Access Reviews for Telehealth Session Logs

Pull the user list for your telehealth platform this month. Most practices find at least one departed employee, one shared login, and one vendor support account nobody remembers approving. Session logs typically contain participant names, IP addresses, timestamps, and join locations — PHI by any reasonable reading. Put the platform on the same quarterly access-review calendar as the EHR.

Your Telehealth Vendor List Is a BAA List

The pandemic-era enforcement flexibility for telehealth is gone. OCR's Notification of Enforcement Discretion for telehealth remote communications expired with the public health emergency on May 11, 2023, and the 90-day transition period ended August 9, 2023. Since then, a video platform handling PHI on your behalf is a business associate and needs a signed business associate agreement, full stop. HHS maintains telehealth-specific HIPAA guidance that is worth circulating to clinical leadership, because "we used it in 2021" is still a live argument in too many practices.

Inventory everything that touches a telehealth encounter and confirm an executed BAA for each:

  • The video or audio platform, including any consumer-grade tool a clinician uses on the side
  • The scheduling and reminder system that stores the anticipated location
  • Your clearinghouse and any billing service that sees the claim with POS 10 on it
  • Remote scribes, transcription vendors, and AI documentation tools
  • Interpreter services joining sessions
  • Any IT contractor with access to the platform's admin console

If that inventory turns up gaps — and it usually turns up two or three — you need executable paperwork, not a project. You can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX, one-time purchase, which is faster than routing a request through outside counsel for a low-risk transcription vendor. Keep the executed copies in one folder with renewal dates, because the question an investigator asks is not "do you have BAAs" but "show me the one for this vendor."

The Monthly Reconciliation That Catches Place-of-Service Drift

Build a recurring report and give it an owner. Two queries catch most problems.

  1. Telehealth modifier without a telehealth place of service. Any claim carrying 93 or 95 with an office or facility POS gets pulled for review before submission. This is the 2020-era habit that generates recoupments.
  2. POS 10 volume against charted location fields. Sample 20 claims a month and confirm the coded place of service matches what the clinician documented. Track the mismatch rate by provider and address outliers in one-on-ones, not in an all-staff email.

Add a denial-code tally. When a payer starts rejecting POS 10 lines it previously paid, you want to see it in week two, not in a quarterly revenue review. Assign someone to check payer bulletins monthly, because telehealth payment policy — including the Medicare telehealth provisions Congress has repeatedly extended on short timelines — has changed more often than any other area of the fee schedule in the last five years. Confirm current status on CMS's telehealth page rather than relying on a vendor newsletter.

A 30-Day Cleanup for Practices Already Billing Telehealth

Week 1: Pull 90 days of telehealth claims. Count how many used each place-of-service code and how many carried which modifier. Identify who chose the code and from what source.

Week 2: Collect written telehealth billing policy from your top five payers by volume. Build a one-page internal crosswalk. Date it and name an owner.

Week 3: Add or fix the discrete location field in your encounter template. Rewrite the intake script. Train schedulers and clinical support in a 20-minute session and document attendance.

Week 4: Finish the vendor inventory, close BAA gaps, and run the telehealth platform access review. Note the results in your risk analysis — telehealth expanded your data footprint, and the analysis should say so. If your documentation set has not been touched since the platform went live, automating the risk analysis and policy refresh is a faster path than rebuilding it in a spreadsheet.

Handled well, POS 10 in medical billing is a two-second question at the top of a visit and one clean field in the chart. Handled badly, it is a recoupment letter, a records request you cannot answer completely, and a vendor with no agreement on file. Start with the vendor inventory this week — if any name on it lacks a signed BAA, build the agreement and get it signed before your next telehealth block.