Resource brief · NC Senate Health Care Committee

Level the Playing Field
AI in Medical Coding & Claims

A non-partisan briefing on how artificial intelligence shapes both sides of every medical bill — providers coding claims, and payers reviewing them. Built to help policymakers see the whole system before drawing a line through part of it.

📍 Durham, NC ⏱️ 12-minute read 🔗 Shareable & printable 📚 35+ cited sources

Section 01The 90-Second Picture

AI is now embedded on both sides of every medical claim. A bill that addresses only one side leaves the other unchecked — and may make the imbalance worse.

🩺 What providers' AI does
Where it lives Inside the EHRElectronic Health Record. The system clinicians use to chart patient care and submit claims. Examples: Epic, Cerner/Oracle, athenahealth. and ambient documentation tools. Suggests diagnosis codes, surfaces E/MEvaluation and Management. The codes (99202–99215) that describe the complexity of an office visit and largely determine physician payment. levels, prompts for unspecified details.
What it can do well Reduce documentation burden, capture genuine clinical complexity that hand-charting misses, surface chronic conditions that affect care.
What goes wrong Code-suggestion nudges drift upward over time. Revenue-cycle dashboards reward higher codes. Captures diagnoses that were never treated.
Who watches OIG audits, False Claims ActFederal law (31 U.S.C. §§ 3729–3733) imposing treble damages and per-claim penalties on those who knowingly submit false claims to the government. Whistleblowers can sue on the government's behalf (qui tam). liability, CMS Recovery Audit Contractors, payer Special Investigation Units, state Medicaid Fraud Control Units.
📋 What payers' AI does
Where it lives Inside claims adjudication and prior authorizationA requirement that an insurer approve a service before it is delivered. Increasingly automated; ~53M Medicare Advantage determinations in 2024 alone. systems. Auto-flags claims as "not medically necessary," predicts length-of-stay, recommends denials and downcodes.
What it can do well Fast-track clearly covered services. Detect billing fraud and duplicate claims. Route complex cases to human reviewers.
What goes wrong Auto-denies in 1.2 seconds (Cigna PXDX). Predicts post-acute stays with ~90% reversal rate on appeal (UnitedHealth nH Predict). Silently downcodes without formal denial.
Who watches Limited federal oversight (CMS guidance for Medicare Advantage only). Six states have AI prior-auth laws. North Carolina currently has none.

The Core Insight

Provider AI use largely emerged as a response to payer AI use. As insurers automated denials, downcodes, and prior-auth gates, providers turned to AI to keep up with the volume and complexity. Banning one side without addressing the other doesn't level the playing field — it tilts it further.

Section 02Provider AI & Upcoding

What the evidence actually shows about how clinicians and hospitals use AI to influence the codes that get submitted.

What "upcoding" actually means

Every medical service is translated into a code. Diagnoses use ICD-10International Classification of Diseases, 10th revision — the standard system for coding diagnoses on medical bills.; procedures and office visits use CPTCurrent Procedural Terminology — the AMA's code set for procedures and services. CPT codes determine most physician payment.; hospital stays roll up into DRGsDiagnosis-Related Groups — the bundled payment categories Medicare uses to pay hospitals for inpatient stays. Higher-severity DRGs pay more.; Medicare Advantage uses HCCsHierarchical Condition Categories — diagnosis groupings CMS uses to risk-adjust Medicare Advantage payments. More documented chronic conditions = higher capitated payment. to risk-adjust monthly capitated payments. Each code carries a payment level. Upcoding is submitting a code that pays more than the service actually delivered or the documentation actually supports. It can be deliberate fraud, careless overstatement, or — most commonly with AI — a pattern of optimistic interpretation at scale.

How AI upcoding actually works — a step-by-step walkthrough

To engage meaningfully on this issue, it helps to know exactly where AI plugs into a clinician's day. There are four pressure points where AI influences a code on its way to a payer:

Step 1 · The Visit

Ambient AI scribes capture the encounter

An ambient AI scribeAI tools that listen to patient-clinician conversations and generate draft clinical notes. Examples: Abridge, Nuance DAX, Suki, Ambience. Duke Health is deploying Abridge to 5,000 clinicians. listens to the conversation and generates a draft clinical note. It can capture chronic conditions a clinician would otherwise forget to chart (legitimate value), but it can also surface diagnoses the patient never confirmed, list symptoms that were ambiguous, and produce more detailed notes than hand-charting would have.

Step 2 · The Note

NLP tools read the note and propose codes

Computer-Assisted CodingNatural language processing tools embedded in the EHR that read clinical documentation and recommend ICD-10 or CPT codes for billing. Most major EHR vendors include this functionality. tools — built into Epic, Cerner/Oracle, athenahealth — read the documentation and recommend ICD-10 and CPT codes. The model is trained on past coding decisions, so it tends to reproduce the patterns it has seen, including any historical bias toward higher-paying codes.

Step 3 · The Nudge

Revenue-cycle dashboards flag "missed" revenue

Practice management and revenue-cycleThe business processes that translate care into paid claims — coding, billing, collections, denial management. Revenue cycle is where most provider-side AI lives. tools surface visits that "look like" they could be coded higher based on the documentation. A clinician sees a prompt: "This visit may meet criteria for level 4." Pre-AI, this conversation happened with a human coder — and was often appropriate. With AI, it happens at scale, for every visit, every day.

Step 4 · The Risk Pool

HCC mining for Medicare Advantage

In Medicare Advantage, plans get paid more for sicker members. AI mines clinical notes, claims history, and in-home assessments for additional HCCHierarchical Condition Categories — diagnosis groupings used to risk-adjust Medicare Advantage payments. diagnoses. Per the HHS OIG, about 70% of those mined diagnoses are not supported in the medical record — and per Sen. Grassley's 2024 investigation, this accounted for $8.7B in inappropriate UnitedHealth payments in a single year.

The key technical insight

AI doesn't decide to upcode the way a person does. It optimizes for the objective its operator sets. When the operator's metric is "revenue captured per visit," the model finds revenue. The same model, with the same training data, deployed by a payer with the metric "claims to question," would find claims to question instead. The behavior follows the incentive, not the technology. That's why constraining the technology without constraining the incentive structures on both sides rarely changes outcomes.

Talking points for committee

The evidence on upcoding

~20%
Increase in highest-severity Medicare inpatient stays, FY2014–2019, even as length of stay decreased
HHS OIG, 2021
$14.6B
Estimated 2019 payments tied to hospital upcoding across 5 states (vs. 2011 coding patterns)
Health Affairs / RAND, 2024
$54B
Annual Medicare Advantage overpayment attributable to coding intensity
MedPAC, March 2024
$8.7B
UnitedHealth Group inappropriate-diagnosis payments in a single year (2021)
Sen. Grassley report, Oct 2024

The legitimate counterargument

Not every upward code shift is gaming. Patient acuity has genuinely risen. The 2021 AMA E/M revision intentionally allows higher coding when medical decision-making complexity is documented. AI scribes can surface chronic conditions that hand-charting misses. The peer-reviewed RAND study controlled for acuity and still found roughly two-thirds of the growth unexplained — but providers' point that pre-AI charts undercoded elderly and chronic patients deserves a fair hearing.

Why a blunt ban is hard to draft — and who pays for it

Every modern EHR contains code-suggestion features. Banning "AI to upcode" without surgical definitions risks catching (a) ambient scribes that legitimately reduce clinician burnout, (b) compliant Clinical Documentation Improvement programs, and (c) small and rural practices that depend on AI to navigate payer complexity.

The disparate impact is the most overlooked policy harm. A 67-hospital system has dedicated revenue-cycle teams, in-house coders, compliance attorneys, and dedicated denial-management staff. A rural primary-care office or an independent physical therapy clinic has a front-desk staffer doing all of it between patients. When the rules tighten, the system absorbs the cost; the small practice closes the doors or stops accepting the patients the rules were meant to protect. Provider AI restrictions disproportionately burden the practices least able to comply — and the patients those practices serve.

Section 03Payer AI: Downcoding & Denial

The under-examined other half of the equation. Same technology, same incentives — flipped.

How payer AI actually works — three pressure points

Payer AI operates at three sequential points in the life of a claim. At each one, algorithms can deny outright, recommend a lower payment level (downcodingWhen a payer reassigns a claim to a lower-complexity code, paying less than the provider billed. Often done silently, without a formal denial.), or cut off coverage already approved.

Stage 1 · Before care

Prior authorization

Before a service can be delivered, the payer's AI screens the request. Algorithms compare the request against utilization patterns, predicted length of stay, and probability of approval. Companies like EviCore process prior auths for ~100M Americans. Denials at this stage prevent care from happening at all.

Stage 2 · During care

Concurrent review

For inpatient and post-acute stays, AI models like UnitedHealth's nH Predict project a "right" length of stay based on millions of past cases. Case managers were pressured to keep stays within 1% of the algorithm's projection — even when the bedside physician disagreed.

Stage 3 · After the bill

Claims adjudication & downcoding

When a claim arrives, AI compares it against the payer's policies. It can deny outright (Cigna PXDX flagged 300K claims in two months at 1.2 seconds each) or silently reassign a higher-complexity code to a lower-paying one — the practice of downcoding. Downcoding is often not formally appealable because no formal denial was issued.

Talking points for committee

The big investigations

Cigna

PXDX: 1.2 seconds per claim

Cigna's PXDX system routed flagged claims to medical directors who signed off in batches without opening files. One director denied 60,000 claims in a month.

300,000+

Denials in two months in 2022, averaging 1.2 seconds each — ProPublica, 2023

UnitedHealth

nH Predict: 90% reversed

Algorithm predicted Medicare Advantage post-acute stays; case managers were pressured to stay within 1% of its projection.

90%

Of nH Predict denials reversed on appeal — STAT News, 2023

EviCore

"The Dial" — tunable denials

Cigna-owned EviCore handles prior auth for ~100M Americans across Aetna, UHC, BCBS plans. Internal tool can be tuned to raise denial rates; pitches a 3-to-1 ROI to insurers.

3x

Arkansas denial rate vs. Medicare Advantage average — ProPublica/CNN, 2024

Senate PSI

Bipartisan staff report

UnitedHealthcare, Humana, and CVS/Aetna investigated. Post-acute denial rates 3x–16x higher than other care types. CVS projected $77.3M in 3-year AI savings.

16x

Humana post-acute denial rate vs. other care — Senate PSI, Oct 2024

Aggregate scale

53M
Medicare Advantage prior auth determinations in 2024
KFF, 2025
80.7%
Of appealed MA denials are overturned — but only 11.5% of denials are ever appealed
KFF, 2025
1 in 4+
Physicians report prior auth led to a serious adverse event — hospitalization, disability, or death — for a patient
AMA Prior Authorization Survey
13%
Of MA prior auth denials likely would have been approved under traditional Medicare rules
HHS OIG, April 2022

Documented Patient Harm

Court filings and journalism document specific cases: Gene Lokken (91), denied skilled nursing despite a fractured leg, family paid $150K out of pocket, died shortly after. Dale Tetzloff (74), stroke survivor, rehab cut off at 20 days based on algorithm. JoAnne Barrows (86), rehab cut at 14 days despite a 6-week non-weight-bearing order. The pattern is not exceptional — the AMA survey found nearly 1 in 3 physicians has personally reported a patient harmed by prior auth.

Section 04How AI Actually Fails

The same models, the same failure modes — but the consequences flip depending on who's using the tool and what outcome they're optimizing for. A bill that doesn't name these risks can't actually constrain them.

AI in healthcare coding and claims is not a single thing. It's a stack of statistical models — natural language processing, predictive algorithms, and increasingly large language models — trained on historical data, deployed inside business workflows, and tuned toward whoever is paying for the system. That last point is the one most often missed in policy debate: AI optimizes for the objective its owner sets. A model deployed by a payer to flag "questionable" claims will find them. A model deployed by a provider to surface "missed" diagnoses will find those. Both can be technically accurate and systematically biased at the same time.

Click any card to expand examples of how the risk plays out on each side.

⚖️

Bias

Models inherit the patterns in their training data. If the data reflects historical underdocumentation, overdocumentation, or population-level inequities, the AI replicates them at scale.

How it shows up
Provider side AI trained on charts from well-resourced systems may overcode common conditions to match those patterns when deployed on rural or under-documented populations.
Payer side Algorithms trained on claims history can deny more often for populations where prior denials succeeded — a self-reinforcing loop that disproportionately affects low-appeal communities.
📉

Drift

A model that worked when deployed slowly degrades as clinical practice, coding rules, payer policies, and patient populations change. Without monitoring, performance silently decays.

How it shows up
Provider side A coding-suggestion tool calibrated against 2022 E/M guidelines keeps recommending codes that no longer match 2026 documentation requirements.
Payer side A length-of-stay model built on pre-COVID data continues cutting off post-acute care for patients with longer modern recovery curves — exactly the nH Predict pattern.
💭

Hallucination

Generative AI can produce confident, fluent output that is partly or wholly fabricated. In documentation and claim adjudication, hallucinated content is hard to detect because it reads like the real thing.

How it shows up
Provider side Ambient AI scribes have been documented inserting symptoms, exam findings, or diagnoses the clinician never said — and those phantom details can land in the bill.
Payer side AI-generated denial rationales can cite policy provisions or clinical guidelines that don't exist or don't apply — clinicians appealing have caught fabricated references.
🪞

Sycophancy & objective alignment

Modern AI is tuned to agree with and serve its user. If the user is incentivized to find upcoding, the model will find it. If incentivized to find reasons to deny, it will find those too. The model isn't neutral — it mirrors the goal it's pointed at.

How it shows up
Provider side Revenue-cycle dashboards prompt clinicians: "This visit looks like it could be a level higher." The AI isn't lying — it's optimizing for the metric its operator chose.
Payer side EviCore's internal "dial" can be tuned to raise denial rates. The model surfaces denial rationales because that's what success looks like to its operator.
🕳️

Opacity

Most healthcare AI is a vendor product. Clinicians and patients see the recommendation, not the model card, validation data, or training population. Even regulators rarely see them.

How it shows up
Provider side A small practice using a third-party coding assistant typically cannot audit what the tool actually recommends across encounters — they see one suggestion at a time.
Payer side Patients and providers receiving denials almost never learn whether AI was involved, what model, what version, or what data trained it. NC has no requirement to disclose this.
♻️

Feedback loops

When AI shapes the data it later trains on, errors compound. The system can't distinguish "what's true" from "what we've been doing for years."

How it shows up
Provider side If AI-suggested codes become the new charting norm, future AI versions train on those charts and treat the inflated pattern as ground truth.
Payer side Denied claims are rarely reversed in the training data. The model learns that denial is the right answer because past denials weren't appealed — even though 80%+ that are appealed get overturned.

What this means for policy

A bill can't ban "bias" or "hallucination" — those are properties of how the technology works. But a bill can require the things that surface and constrain these risks: ongoing performance monitoring, third-party validation, transparency about the model's objective function, human review of consequential decisions, and audit trails. The risks are technical. The remedies are governance.

Section 05The Asymmetry Problem

Identical technology, used by both sides, in pursuit of opposite financial outcomes — but only one side faces serious oversight today.

🩺 If providers use AI to upcode
Liability Federal False Claims Act exposure (treble damages, per-claim penalties)
Enforcement OIG audits, DOJ qui tam suits, CMS Recovery Audit Contractors, ZPICs
State action NC Medicaid Fraud Control Unit; AG settlements (e.g., $8.8M Bethany Medical, 2025)
Private enforcement Payer Special Investigation Units; payer prepayment review
Track record DOJ recovered $5.7B in FY2025 healthcare FCA cases
📋 If payers use AI to downcode or deny
Liability Generally no statutory liability beyond contract / bad faith claims
Enforcement CMS guidance for Medicare Advantage only; no federal commercial rule
State action NC has no AI prior-auth law. CA, IL, TX, AZ, MD, NE, IN do.
Private enforcement Individual patient appeal — used by only ~11.5% of denied beneficiaries
Track record 80%+ overturn rate on appeal — meaning most denials were wrong but never challenged

The Symmetry Argument in One Sentence

If AI in coding decisions warrants legislative scrutiny, the principle applies equally to the side that generates the code (providers) and the side that adjudicates the code (payers) — and any well-designed bill should address both, with parallel guardrails and parallel enforcement.

Talking points for committee

Section 06Through Five Lenses

The same facts feel different depending on whose chair you sit in. Toggle through the perspectives the committee will hear from.

The Patient's View

The person whose care, money, and trust are on the line.

Risk from provider AI

A bill they don't understand. A diagnosis on their record that was never explained. Surprise out-of-pocket cost when an AI-elevated code crosses a deductible threshold.

Risk from payer AI

Denied care for a condition their doctor said they need treated. A 90%-wrong algorithm cutting off rehab. Coverage decisions made in seconds, appeals that take weeks. Care delays linked to serious harm.

The Clinician View

Nurses, physicians, PTs, and other licensed clinicians caught between the two algorithms.

Risk from provider AI

Pressure from revenue-cycle dashboards to chart for billing rather than care. Ethical bind when codes don't match clinical reality. But: AI scribes meaningfully reduce documentation burden — nurses spend ~23% of a 12-hour shift in the EHR, and burnout is the top reason RNs leave.

Risk from payer AI

Hours each week fighting denials. Moral distress when an algorithm overrides their clinical judgment. Discharge planning constrained by a model nobody at the bedside has ever seen. Patients harmed while appeals are pending.

The Hospital & Practice View

Institutions running on thin margins in a complex payer environment.

Risk from provider AI

False Claims Act exposure if AI nudges drift into fraud territory. Reputational and AG-level scrutiny. Compliance overhead of validating every AI suggestion. Smaller practices can't afford in-house compliance — they need rules that don't pick winners.

Risk from payer AI

Cash flow disruption from denied claims. AHA reports claim denials up 20%+ over five years. Administrative cost of appeals — care that was delivered but takes months to be paid. Small practices and rural hospitals hit hardest.

The Payer View

Insurers' best-faith case for current practice — and where it breaks down.

View on provider AI

"Provider AI inflates codes; we use AI to catch it. The 80% overturn rate proves we sometimes deny in error, but the alternative — paying every claim — drives premiums up for everyone. CMS already lets us use AI; we follow the rules."

Where it gets harder

The 1.2-second denial review. The 90%-error-rate algorithm. The internal "dial" that tunes denial rates. The lack of any state-level transparency requirement. The pattern of denying expensive care for vulnerable populations, then winning by attrition when only 11% appeal.

The Regulator's View

What it looks like from the state insurance department, AG, and committee dais.

On provider AI

Federal infrastructure already extensive — FCA, OIG, CMS audits. A state ban risks duplicating federal enforcement, triggering preemption challenges, or catching legitimate documentation improvement. Surgical definitions matter.

On payer AI

Federal floor exists only for Medicare Advantage. Commercial and Medicaid managed care AI use is largely unregulated in NC. Six states have moved; NC has not. Patient harm is documented. Enforcement gap is the larger policy problem.

Section 07Ethics & What's Already on the Books

Before drafting new rules, what frameworks and federal requirements already apply.

Ethics frameworks (the common floor)

Every major medical ethics body — AMA, ANA (nursing), NAM, WHO, and the Coalition for Health AI — converges on the same principles: AI in healthcare must augment, not replace human clinical judgment; must be transparent about how it works and what data trained it; must be monitored for bias and drift; and must keep licensed professionals accountable for the decisions made in their name. None recommend outright bans — all recommend governance.

What federal law already does

What other states have done (verified through May 2026)

NC's own SB 624 (Sen. Mayfield, in Senate Rules) would require providers to disclose AI use in medical-necessity determinations. SB 315 (Sen. Burgin, in Health Care Committee) addresses utilization review transparency. Both are potential vehicles for symmetric, enforceable language.

Where states stand on AI in coding & claims

Status of state laws governing payer AI in utilization review, claims adjudication, and prior authorization. Scored on human-in-the-loop requirement, transparency/disclosure, audit authority, and breadth of scope. Statutes verified against state legislature records.
California
SB 1120 + AB 3030 — in force
Leader
Maryland
HB 820 — audits, quarterly review, in force
Leader
Texas
SB 815 — in force Sep 2025
Strong
Nebraska
LB 77 — in force
Strong
Indiana
HB 1271 — first downcoding law, eff. July 2026
Active
Arizona
HB 2175 — eff. June 2026
Active
Utah
SB 319 — disclosure, eff. Jan 2027
Emerging
North Carolina
SB 315, SB 624, HB 434 — none enacted
Behind

As of May 2026, at least seven states have enacted or signed AI-specific healthcare claims/utilization-review statutes. North Carolina has bills in motion (SB 315 — Sen. Burgin; SB 624 — Sen. Mayfield; HB 434) and the technical infrastructure (NC HealthConnex) to lead. What's missing is enacted, symmetric legislation. (Colorado's general AI Act and Illinois's mental-health AI law are not included in this comparison because neither is a healthcare-claims statute.)

Talking points for committee

Section 08From Ban to Workable Limits

The Senate chairs have said "limit, not ban." That's the right instinct. Here's what a well-designed limit can actually look like — and what each option costs.

The "ban vs. limit" question

A categorical ban on "provider use of AI to upcode" is hard to enforce and easy to evade. Every modern EHR contains coding-suggestion features. The behavior the bill is targeting — gaming codes for revenue — is already illegal under the federal False Claims Act. A ban without surgical definitions risks chilling legitimate documentation tools while doing nothing to constrain the larger, less-regulated payer-side AI behavior.

A well-crafted limit instead does three things: (1) defines the conduct it's targeting with precision, (2) creates auditable obligations on both sides, and (3) gives regulators visibility — not just patients with the energy to appeal.

Six design considerations the committee can explore

1. Human-in-the-loop attestation

Require a licensed clinician to review and attest to any final code submitted (provider side) or any adverse determination issued (payer side). AI can suggest; humans decide.

Trade-off: Operational cost; needs clear "review" standards so attestation isn't rubber-stamping.
Precedent: CA SB 1120; CMS MA FAQ.

2. Algorithm transparency & audit rights

Give NC DOI and Medical Board authority to demand AI model documentation, validation evidence, training-data summaries, and outcome audits — for both provider-side and payer-side AI used at scale.

Trade-off: Trade-secret tension; needs protected-disclosure framework.
Precedent: ONC HTI-1 transparency rule.

3. Public reporting of rates

Require annual public reporting of: AI-influenced code adjustments (providers); denial rates by service line and AI involvement (payers); appeal overturn rates (payers). Sunlight is enforcement.

Trade-off: Definition work — what counts as "AI-influenced" needs clarity.
Precedent: CMS-0057-F (federal MA only).

4. Patient notification

When AI materially influences a coding or coverage decision, the patient gets a plain-language notice — and a clear path to appeal with the algorithm's role disclosed.

Trade-off: Notice fatigue; must be specific enough to be actionable.
Precedent: CA AB 3030; IL HB 1806.

5. Symmetric scope

Apply parallel rules to providers and payers. Equal definitions of "AI use," equal disclosure obligations, equal audit authority. Politically durable and ethically coherent.

Trade-off: Broader scope means broader lobbying. But asymmetric rules are unlikely to survive constitutional challenge in any case.
Precedent: Indiana's 2026 downcoding law mirrors structures used against upcoding.

6. Small & rural practice protection

Scale compliance obligations to organization size. Independent and rural practices rely on AI scribes and coding assists to keep up with payer-imposed complexity — they cannot carry the same compliance load as a 67-hospital system. Rules that ignore this gap don't level the field; they accelerate consolidation and reduce patient access in exactly the NC counties least able to afford either.

Trade-off: Thresholds invite gaming; better to scale by patient volume than by tax structure.
Precedent: Many state laws use FTE or revenue thresholds.

Enforcement realism check

Any limit needs a credible enforcer. Options NC already has: NC DOI (insurance), NC Medical Board (clinicians), NC AG / Medicaid Fraud Control Unit (fraud), and private right of action (used cautiously). The single most overlooked enforcement asset is NC HealthConnex — as of October 2025, NC Medicaid claims data flows into the state HIE alongside clinical records, creating the technical substrate to audit coding-vs-clinical-reality patterns at scale.

Talking points for committee

Section 09The North Carolina Picture

Why this bill, why now, and what's already happening in the state.

The NC market — major systems and the long tail

The half of NC most policy debates miss

Statewide market debates tend to anchor on the big systems. But a substantial share of North Carolinians get care from small, independent, and rural providers — and that share is concentrated in exactly the counties where access is already most fragile.

~4.6M
North Carolinians live in rural counties — roughly 1 in 3 residents; second-largest rural population in the U.S.
NCDHHS Office of Rural Health
40 / 100
NC counties designated Tier 1 — the state's most economically distressed
NC Department of Commerce
20
Critical Access Hospitals — the smallest rural hospitals, financially most exposed to denials and slow payment
Sheps Center / NC ORH
43
Federally Qualified Health Center organizations serving ~500,000 NC patients — overwhelmingly low-income
NC Community Health Center Assn
85+
Rural Health Clinics in NC — independent or small-group practices serving rural patients
CMS / Sheps Center
23
"Healthcare deserts" in NC — counties with severely limited care infrastructure
RHT Compass / NCDHHS

The Sheps Center and NCDHHS describe rural NC care delivery as "a fragmented network of providers, many working independently." These are the practices that cannot absorb new compliance costs without consequence — and the patients in those communities are the ones who lose access first when small providers exit the market.

What NC already has in motion

Senate Health Care Committee — 2025–2026 Session

Chair
Sen. Burgin
Chair
Sen. Galey
Chair
Sen. Sawrey
Advisory
Sen. Robinson
Member
Sen. Adcock
Member
Sen. Applewhite
Member
Sen. Barnes
Member
Sen. Britt
Member
Sen. Corbin
Member
Sen. Garrett
Member
Sen. Hise
Member
Sen. Hollo
Member
Sen. Johnson
Member
Sen. Lee
Member
Sen. Mayfield
Member
Sen. Moffitt
Member
Sen. Mohammed
Member
Sen. Murdock
Member
Sen. Settle
Member
Sen. Waddell

Source: NCGA Senate Health Care Committee

The NC clinical workforce angle

NC is projected to be short ~12,500 RNs by 2033. In 2023, 1 in 6 RN positions were unfilled. Documentation burden is repeatedly cited as a top driver of clinician attrition — and AI scribes are one of the few tools that have shown measurable burden reduction. Policy that catches legitimate documentation AI in the same net as upcoding gaming will hit the clinical workforce hardest.

From a small-practice owner

"In our private-practice physical therapy clinic here in North Carolina, we've watched prior authorization requirements and denials climb year over year. The administrative burden is material. The moral distress on our clinicians is real. And the people who lose are our patients — North Carolinians who aren't getting the post-acute and rehabilitative care their clinical experts say they need. We can't fight every denial the way a hospital system can. Policy that constrains provider AI without addressing the payer AI driving that volume will push small practices like ours out of the market — and take our patients' access with us."

— Rich G. Kenny, owner, NC physical therapy clinic; former critical care and emergency nurse

Talking points for committee

Section 10Sources & Further Reading

Every claim above traces to a primary source. Listed for staff verification and deeper research.

Provider AI & upcoding

Payer AI: denial & downcoding

Ethics & policy frameworks

North Carolina sources

State AI laws (verified May 2026)