On September 6, 2026, the American Medical Association named Jennifer Goldsack, founder and CEO of the Digital Medicine Society (DiMe), as senior vice president and inaugural leader of the AMA Center for Digital Health and AI. It’s a notable hire for an organization whose influence over medical coding runs through a much older, much narrower body: the CPT Editorial Panel. For coders and compliance teams watching how AI intersects with billing policy, the question isn’t whether the AMA is building AI infrastructure — it clearly is — but whether this new center ever gets a seat at the table where codes actually get written.
A DiMe Veteran Takes the AMA’s New AI Seat
Goldsack isn’t a coding insider. DiMe is a nonprofit best known for standardizing how digital biomarkers and remote patient-monitoring data get validated for clinical and regulatory use — work that sits closer to FDA-adjacent evidence standards than to CPT nomenclature. Her appointment signals that the AMA wants the center to lead on trust, validation, and workflow integration for AI tools broadly, not to function as a coding body with its own agenda.
That distinction matters. The AMA has spent the past two years expanding CPT’s AI vocabulary — the Clinically Meaningful Algorithmic Analyses (CMAA) framework that classifies AI services as assistive, augmentative, or autonomous being the clearest example — and all of that work has run through the CPT Editorial Panel and CPT/RUC advisory process, not through a digital-health strategy office.
What the Center for Digital Health and AI Is Built to Do
The center itself isn’t new; the AMA launched it in October 2025 under CEO John Whyte with a mandate to give physicians a stronger voice in how AI and digital tools get integrated into clinical workflows, and to help “forge connections across medicine, tech, policymakers and regulators to shape benchmarks for safe, effective use of AI.” Until this month, though, it had been operating without a permanent leader. Goldsack’s hire is the AMA converting a policy ambition into an actual staffed function.
Not the CPT Editorial Panel
Nothing in the AMA’s public description of the center’s mission mentions CPT codes, billing, or reimbursement. Its stated priorities — clinical workflow integration, physician education, AI trust benchmarks, and cross-industry collaboration — sit upstream of coding, not inside it. The CPT Editorial Panel, which votes on new and revised codes, and the RUC, which recommends relative values, remain the bodies that actually determine how an AI-assisted service gets billed. For now, the center’s authority appears to be advisory and reputational rather than procedural.
Why This Matters to Coders and Compliance Teams Anyway
Even without direct code-setting authority, a well-resourced AI center inside the AMA is likely to shape the inputs that feed CPT policy over time — the benchmarks it defines for “trustworthy” AI, the workflow evidence it collects from health systems, and the physician sentiment it aggregates could all become reference points the next time the CPT Editorial Panel or RUC evaluates a new AI-related code proposal.
The CPT Monopoly Question in the Background
This appointment also lands against an already tense backdrop: CMS issued a request for information this month scrutinizing the AMA’s exclusive control over CPT code licensing and maintenance. A new, high-profile AI center staffed by an outside digital-health leader gives the AMA a visible counter-narrative — proof that it’s investing in modernization — at the same time its core coding franchise is facing outside scrutiny. Compliance teams tracking that RFI should treat the center’s early output as part of the same story, not a separate one.
Practically, none of this changes a single code definition today. But it does create a new venue worth monitoring, especially for organizations trying to anticipate where AI-related billing policy heads next.
What to Watch Next
- Formal ties to the CPT process. Watch for any announcement that gives the center a defined advisory role with the CPT Editorial Panel or RUC, rather than a purely educational mandate.
- AI trust benchmarks. Any framework the center publishes for evaluating AI tool accuracy or safety could become a reference point cited in future CPT proposals, the way clinical validity standards already are.
- Overlap with the CMS CPT RFI. CMS’s inquiry into AMA’s CPT licensing model is a separate proceeding, but the center’s public messaging is likely to be shaped by it.
- Staffing beyond Goldsack. Who she hires under her — particularly anyone with a coding, RUC, or health-information-management background — will be the clearest early signal of how close to billing policy the center intends to get.
- First public output. A published framework, workflow guideline, or public comment tied to a CMS rule will show whether the center is operating as a coding-adjacent policy shop or staying focused on clinical workflow education.
None of this is a reason to change coding practice today, but it is a reason to add the AMA Center for Digital Health and AI to the list of venues worth watching alongside the CPT Editorial Panel itself. Teams that want AI-assisted coding built on a system designed for accuracy and auditability from the ground up, rather than layered onto legacy workflows, can see how that looks in practice with Medikode’s automated medical coding platform.