A telehealth claim can be clinically sound, fully documented, and still deny because the place of service does not match where the patient received care. That is the practical issue behind POS 10 versus 02. These codes may look like a minor claim-field distinction, but they communicate different patient locations to Medicare, Medicaid programs, commercial payers, and downstream audit teams.
For coders and billing staff, the right answer is not based on where the rendering practitioner sat, where the practice is located, or whether the visit occurred by video. It depends on the patient’s physical location when the telehealth service was furnished. Getting that fact into the workflow before the claim is created is one of the simplest ways to reduce avoidable telehealth edits.
POS 10 Versus 02: The Core Distinction
Place of service code 02 identifies telehealth provided when the patient is located somewhere other than the patient’s home. Place of service code 10 identifies telehealth provided when the patient is in the patient’s home.
The Centers for Medicare & Medicaid Services defines POS 02 as telehealth provided other than in the patient’s home. POS 10 is defined as telehealth provided in the patient’s home. The distinction is intentionally narrow, but the operational effect can be significant because payer reimbursement rules, claim edits, and reporting logic may recognize the two settings differently.
The patient’s home generally means a location where the patient lives. It does not automatically include every nonclinical setting. A patient connecting from work, a school campus, a family member’s house, a hotel, or a parked vehicle is not necessarily receiving the service at home. In those situations, coders should not assume POS 10 merely because the patient was not in a facility.
Likewise, POS 02 is not limited to patients who connect from a hospital or physician office. It can apply when the patient is at another qualifying non-home location. The claim should reflect the patient’s actual location at the time of the encounter, subject to the payer’s telehealth policy.
Why the POS Choice Can Affect Payment and Audit Risk
Place of service reporting is not a cosmetic billing detail. Payers use it to apply coverage edits, determine the appropriate payment methodology, evaluate telehealth requirements, and identify claims for review. A mismatch between the POS code, modifier, documentation, and payer rules can trigger a denial or create a record that is difficult to defend later.
Medicare policy has changed repeatedly since the public health emergency, particularly around originating-site requirements, practitioner eligibility, audio-only services, rural restrictions, and temporary statutory extensions. Commercial payer policies have also varied widely. Some plans distinguish payment for home-based telehealth from telehealth provided when the patient is in another location. Others use separate telehealth indicators, modifiers, or electronic claim instructions that must be applied with the POS code.
That means POS 10 or POS 02 does not independently establish that a service is covered. It also does not replace the need to report a required telehealth modifier, select a covered CPT or HCPCS code, meet modality requirements, or support medical necessity. The POS is one component of a compliant claim, not a substitute for the full billing rule.
For audit purposes, the risk is often a basic inconsistency. The note may state that the patient was “at home,” while the claim reports POS 02. Or the scheduling record may show a facility location, but the note gives no patient location at all. Those gaps invite questions about whether the organization has a reliable telehealth billing process.
Start With the Patient Location, Not the Platform
The telehealth platform does not determine POS selection. A video visit conducted through the practice’s preferred application can be reported with POS 10 or POS 02, depending on where the patient was. The same is true when a payer permits a qualifying audio-only service.
The most reliable workflow starts before the clinician begins the encounter. Registration or intake staff should capture the patient’s physical location for each telehealth date of service, not simply retain the address listed in the patient record. A home address on file does not prove that the patient was home during the visit.
Clinicians should document the patient’s location in language that supports the claim. “Patient located at home in Ohio” is more useful than “telehealth visit completed.” If the patient was at a school, worksite, skilled nursing facility, another physician office, or other site, the note should identify that setting clearly enough for the billing team to apply the correct payer rule.
This step matters for licensure and jurisdictional compliance as well. While the POS code is not a licensure determination, the patient’s documented state location may affect whether the practitioner was authorized to provide the service. Revenue-cycle teams should recognize when a location field has implications beyond claims processing.
Common Errors Coders Should Watch For
One common error is treating POS 02 as the universal telehealth code. That practice may have originated before POS 10 was implemented or during periods of changing payer guidance. It is no longer a safe default when the patient received the service at home and the payer recognizes POS 10.
Another error is selecting POS 10 whenever the patient is outside a healthcare facility. A patient at work or in another non-home location may belong under POS 02, assuming telehealth is allowed and the payer’s instructions support the claim.
A third error is carrying forward the office POS because the provider is working from the clinic. Place of service for telehealth reporting generally centers on the patient’s location under the applicable payer instruction. The provider’s office address, remote workstation, and corporate billing address do not answer the POS 10 versus 02 question.
Teams also create denials when they assume all payers follow Medicare billing instructions. Medicare Advantage plans, state Medicaid agencies, and commercial carriers may adopt, modify, or depart from traditional Medicare guidance. A payer contract, provider manual, current bulletin, or claims-edit response may impose specific reporting rules. When policy language conflicts with a legacy internal cheat sheet, the current payer instruction should control.
Apply the Correct Modifier and Service Rules
POS reporting must be evaluated alongside modifier requirements. Depending on the payer and date of service, a telehealth claim may require modifier 95, modifier GT, modifier GQ, another payer-specific indicator, or no telehealth modifier at all. The correct modifier can also depend on whether the service was furnished through interactive audio-video technology, an approved audio-only pathway, or another modality.
Do not use a modifier as a shortcut around a place of service mismatch. A modifier may identify that the service was furnished through telehealth, but it does not explain whether the patient was at home or elsewhere. Both data elements need to align with the encounter record.
Coders should also verify whether the billed code remains eligible for telehealth under the payer’s current policy. This is especially important for services affected by temporary federal extensions, evolving Medicare rules, or state-specific Medicaid requirements. A correctly reported POS 10 will not cure a noncovered telehealth service, and a covered service can still deny if the claim lacks the required modifier or patient-location support.
Build a Defensible Telehealth Claim Workflow
The strongest control is a structured intake field that requires staff to select the patient’s location at the time of service. The field should distinguish home from other locations and allow meaningful detail when needed. That information should flow to the clinician’s note and be visible to the billing team.
Organizations should then map location responses to POS 10 and POS 02 within their billing system, with payer-specific exceptions maintained in a controlled reference. Coding staff need a clear escalation path for ambiguous answers such as “with family,” “traveling,” or “at a friend’s house.” Guessing is not an audit strategy.
Periodic claim audits should compare the POS, modifier, appointment type, documented modality, and patient-location statement. Focus first on high-volume telehealth specialties, denial-prone payers, and encounters that were corrected after submission. If staff repeatedly choose the wrong code, the solution may be revised intake scripting or system edits rather than repeated individual education.
When a claim has already been submitted with the wrong POS, follow the payer’s correction process promptly. Document the reason for the change and preserve the source record showing the patient’s actual location. A corrected claim is easier to defend when the underlying note was complete on the date of service.
Telehealth policy will continue to shift, but the operational discipline remains stable: capture where the patient was, match that fact to the payer’s current reporting rule, and make sure the claim tells the same story as the record. That is how a two-digit POS decision becomes a more reliable reimbursement process.
