New patient visit CPT codes look simple on paper. In practice, they sit at the intersection of documentation, time, payer policy, and growing audit scrutiny. Small errors, such as misunderstanding the 3 year “new patient” rule or over relying on AI generated notes, now translate quickly into denials, downcoded claims, and in some cases payer investigations.
For independent practices, hospital employed groups, and billing companies, 2026 is a turning point. Payers are aligning more tightly around the revised office and outpatient E M guidelines, using analytics to flag outlier use of codes 99204 and 99205, and tightening rules on telehealth. At the same time, physicians expect coding teams to support AI tools and hybrid in person / virtual workflows without slowing them down.
This guide explains how to operationalize new patient visit CPT codes (99202–99205) in 2026. It focuses on what matters to revenue cycle leaders: financial impact, coding and documentation risk, and workflow design that prevents denials before they start.
Clarifying Who Is a “New Patient” in 2026 and Why It Matters to Cash Flow
Every decision about which E M family to bill starts with a deceptively basic question: is this patient new or established to the billing provider or group. The definition has not changed in 2026, but payers are enforcing it more aggressively with cross claim analytics.
A patient is “new” if they have not received any professional services from the same physician or another physician or qualified health care professional of the same specialty and subspecialty in the same group in the past 3 years. That 3 year lookback is based on the date of service, not registration date or referral date.
Why this definition impacts revenue
New patient codes (99202–99205) typically reimburse more than their established patient counterparts (99212–99215) because they are expected to require more work. If your practice is mistakenly billing new patient visits when the patient should be established, payers can:
- Downcode the visit and recoup the difference on post payment review.
- Apply extrapolation for “pattern errors” in a statistically valid sample.
- Flag the provider as an outlier, triggering broader documentation audits.
On the other hand, if staff incorrectly assume a patient is established and bill 99213 instead of 99203, you leave legitimate revenue on the table and depress RVUs for employed providers.
Operational safeguard: The 3 year rule workflow
RCM leaders should not rely solely on manual front desk judgment for patient status. A robust workflow usually includes:
- EHR logic: Configure your practice management or EHR system to look back three years across all providers of the same specialty in the group. Patient status should default to “established” unless there is truly no qualifying visit.
- Multi location visibility: Multi site practices and hospital owned groups must ensure that scheduling and registration staff can see encounters across locations. Silos are a common reason a returning patient is misclassified as new.
- Exception queue: Route edge cases (for example complex mergers, subspecialty questions, or patients who changed plans but not providers) to a central RCM or coding review queue rather than forcing front line staff to guess.
Measure the effectiveness of this process with a simple KPI: the percentage of downcoded or recouped claims due to incorrect “new vs established” status. For most mature organizations, that number should be effectively zero.
Choosing the Right New Patient Code: MDM vs Time in 99202–99205
In 2026, new patient office visit codes 99202–99205 are selected based on either medical decision making (MDM) or total time spent on the date of the encounter. History and exam still must be medically appropriate and documented, but they no longer drive code selection.
Understanding the decision making pathway
Each new patient code aligns with a level of MDM:
- 99202: Straightforward MDM
- 99203: Low complexity MDM
- 99204: Moderate complexity MDM
- 99205: High complexity MDM
MDM levels are determined by three elements:
- Number and complexity of problems addressed.
- Amount and complexity of data to be reviewed and analyzed.
- Risk of complications and or morbidity or mortality.
Revenue leaders should align coding strategy to clinical reality, not to payer fears or productivity pressure. A provider who rarely sees high risk or extensively worked up conditions should not show an unusually high percentage of 99205 visits. That outlier pattern is exactly what payer analytics are tuned to find.
Time based coding and its implications
Time based coding is appropriate when the total time spent on the date of service is the main driver of work. That total can include:
- Preparing to see the patient (reviewing records, test results).
- Face to face time with the patient and or family.
- Ordering medications, tests, or procedures.
- Documenting in the medical record after the visit.
- Communicating with other professionals regarding the patient.
Each code is associated with a time range. As an example framework that many payers reference, 99202 may correspond to a short visit of roughly 15–29 minutes while 99205 may represent 60–74 minutes. There is no single universal table across all payers, so RCM leaders should anchor their operational rules to the current CPT manual and major payer policies.
MDM vs time: a decision framework for coders
To keep your audits defensible and denials low, build a simple decision tree for coding teams:
- If MDM clearly supports a higher level code and documentation is robust, code based on MDM even if time is modest.
- If MDM is low but the physician legitimately spent extended time on counseling, coordination, or complex data review, code based on total time and ensure the note includes total minutes and qualifying activities.
- Do not selectively switch to time based coding only to reach a higher code level. That is exactly the pattern payers will flag.
Audit a monthly sample of new patient visits for each provider, comparing the selected level against both MDM and time. Outliers should trigger education and potentially changes to documentation templates.
Documentation Requirements That Withstand 2026 Audit Scrutiny
Strong documentation is the only meaningful defense if a payer challenges your use of 99204 or 99205. In 2026, payers are less focused on “bullets” for history and exam and more focused on whether the note clearly supports the complexity of the work.
Key elements for MDM based coding
For MDM based new patient visits, RCM leaders should ensure notes routinely address:
- Problems addressed: Use explicit language about acuity, severity, and status. “Worsening chest pain in a patient with known CAD” supports higher risk far better than “chest pain follow up”.
- Data reviewed and ordered: Identify external records, imaging, lab review, and discussions with other clinicians. Specify which tests were ordered and why.
- Risk of management: Document the rationale behind starting high risk medications, ordering advanced imaging, or deciding against hospitalization. Payers read risk from the plan, not the problem list.
Train physicians to think in terms of “audit story” rather than “narrative length”. Dense, clearly structured notes that map to MDM elements are far more defensible than long, auto imported histories that obscure the clinical thinking.
Key elements for time based coding
For time based new patient visits, documentation should always include:
- Total time on the date of service, expressed as a single number of minutes.
- A concise list of the categories of work performed (for example record review, face to face counseling, care coordination, orders and documentation).
- Evidence that the majority of time was spent on E M related activities rather than separately billable procedures or unrelated tasks.
Time statements like “I spent greater than 60 minutes” without detail are increasingly vulnerable to downcoding. Payers are comparing time patterns across providers and specialties. A provider whose average documented time always sits right at or just above the threshold for 99205 is more likely to be audited.
Common documentation failures and how to prevent them
Three failures appear over and over in appeal files for denied or downcoded new patient visits:
- Copy forward problems with no clear indication of what changed or what was addressed today.
- Notes that show high visit levels but minimal or no diagnostic workup or management changes.
- Time based coding with vague or boilerplate time statements that do not tie to the patient’s complexity.
Practical countermeasures include focused provider education, peer review sessions for high level codes, and periodic external coding audits. Practices that adopt a “trust, but verify” approach to documentation usually see fewer denials and less stressful auditor interactions.
Telehealth New Patient Visits and Modifier Strategy in 2026
Many practices now onboard new patients virtually. That trend will continue in 2026, but payers are narrowing telehealth rules and requiring cleaner use of modifiers and place of service codes. Mistakes in this area are a leading cause of preventable denials.
Aligning telehealth E M coding with payer rules
From a CPT perspective, the same new patient codes 99202–99205 can often be used for synchronous video visits when documentation and clinical risk support it. Operational challenges arise because:
- Individual payers may require specific place of service codes to indicate telehealth vs in person services.
- Modifiers like 95 or GT may be required to signal a real time audio video encounter.
- Policies can differ between Medicare, Medicaid, and commercial plans, and many have sunset or modified pandemic era flexibilities.
RCM leaders should maintain an up to date telehealth policy matrix by payer that is accessible to schedulers, clinicians, and coders. The matrix should define:
- Which new patient codes are covered via telehealth for that payer.
- Required place of service and modifier combinations.
- Any documentation language the payer expects regarding modality and patient location.
Using modifiers to reduce denials and add transparency
Beyond telehealth indicators, other modifiers can shape how payers interpret a new patient visit:
- Modifier 25 indicates a significant, separately identifiable E M service on the same day as a procedure. Misuse leads to denials and refund demands, but correct use is essential when a true new patient evaluation accompanies a minor procedure.
- Some organizations now voluntarily tag AI assisted documentation using an internal or external modifier when allowed. That practice can improve transparency with payers and internal auditors.
The key is consistency. Build modest but clear rules about when modifiers should be appended, then embed those rules directly into your charge capture or EHR workflows. Manual modifier selection by hurried front desk staff is a formula for denials.
AI Assisted Documentation: Opportunity and Risk for New Patient Coding
In many practices, new patient notes are now drafted or heavily supported by ambient listening tools and generative AI. This can reduce clinician burnout and improve narrative detail, but it also introduces new coding and compliance risks if not governed properly.
How AI can distort E M levels if left unchecked
AI systems tend to include every problem mentioned, even those that are not addressed today. They can also auto generate rich sounding assessments that imply more data review or greater risk than what was actually considered. If coders use these notes at face value, MDM may appear artificially high, driving more 99204 and 99205 codes.
Payers are already aware of this pattern and are calibrating audits accordingly. If your documentation consistently shows very high complexity for relatively routine conditions, AI may be inflating the apparent work.
Governance framework for AI supported notes
RCM and compliance leaders should put a simple governance framework in place:
- Clinician attestation: Require explicit attestation in the note that AI generated content was reviewed and edited as needed by the rendering provider.
- Problem addressed vs problem listed: Train both clinicians and coders to distinguish between problems that are documented and those that are actually addressed and managed on that date.
- MDM mapping checks: During audits, pay particular attention to new patient visits where AI tools were used. Validate that documented data review and risk align with reality.
Document your AI governance steps in policy. If a payer or regulator questions your documentation practices, being able to show a thoughtful oversight process is crucial.
Preventing Denials and Downcoding: A New Patient Visit Compliance Playbook
Denials and payer recoupments for new patient visits usually cluster around a handful of root causes. RCM leaders should treat these causes as design problems, not individual coder failures. A deliberate playbook can stabilize revenue and reduce rework.
Common failure modes and how to design them out
- Incorrect patient status: Solve at the system level with EHR rules, three year lookbacks, and multi location visibility, rather than asking staff to remember the definition.
- Over concentration of high level codes: Set reasonableness benchmarks by specialty. For instance, a primary care provider with 50 percent of new patients coded at 99205 is almost certainly an outlier.
- Unclear telehealth coding: Use payer specific telehealth templates that pre populate required modifiers and place of service codes.
- Weak appeals: When denials do occur, build appeal templates that explicitly connect documentation to MDM elements or time definitions rather than simply restating the original claim.
Metrics that RCM leaders should track
To keep new patient coding on track, monitor a concise KPI set:
- Distribution of 99202–99205 by provider and specialty, compared to internal peers and available benchmarks.
- Denial rate specific to new patient visit codes, broken down by payer and denial reason.
- Percentage of new patient claims adjusted or refunded after post payment review.
- Audit findings by MDM element (problems, data, risk) and by time documentation sufficiency.
Use these metrics to drive focused interventions rather than generic training. For example, if one payer frequently denies 99205 for lack of “high risk” support, target documentation training on risk statements and management decisions for that payer’s population.
Turning New Patient Coding Discipline Into Strategic Advantage
Precision in new patient visit CPT coding is more than a compliance obligation. It shapes how fast cash moves through your system, how credible your physicians look to payers, and how confident your executives feel when growth strategies rely on accurate RVU reporting.
Organizations that treat 99202–99205 as a strategic area tend to see:
- Higher first pass payment rates and lower appeal volume.
- Fewer disruptive payer audits and recoupments.
- Cleaner productivity reporting for compensation and staffing decisions.
If your internal team is stretched or your audit findings show persistent gaps, it may be time to bring in outside expertise. If your organization is looking to improve billing accuracy, reduce denials, and strengthen overall revenue cycle performance, working with experienced RCM professionals can make a measurable difference. One of our trusted partners, Quest National Services Medical Billing, specializes in full service medical billing and revenue cycle support for healthcare organizations navigating complex payer environments.
Regardless of whether you handle coding in house or with a partner, the next step is the same: review your 2026 new patient visit performance against the frameworks in this guide, identify two or three high impact gaps, and put specific operational changes on the calendar.
If you would like to discuss how these principles apply to your practice, group, or health system, you can contact us for a conversation focused on your data, your payers, and your risk profile.
