Clinical Informatics 8 min read

Demystifying Digital Medicine Coding -- A Physician-Developer's Guide to Sustainable Telehealth Workflows

A practical breakdown of 2025 CPT telehealth codes, RPM billing thresholds, and the workflow engineering required to make digital medicine financially sustainable.

By Dr. Chukwuma Onyeije, MD, FACOG

Maternal-Fetal Medicine Specialist & Medical Director, Atlanta Perinatal Associates

Founder, Doctors Who Code · OpenMFM.org · CodeCraftMD · · 8 min read

Listen to this post

Demystifying Digital Medicine Coding -- A Physician-Developer's Guide to Sustainable Telehealth Workflows

0:00
Physician at a desk at night reviewing telehealth billing codes on dual monitors

I built a remote blood pressure monitoring workflow before I fully understood CPT 99454. The clinical side worked. My nurses were calling patients, readings were coming in, gestational hypertension was being managed between visits. Then the first billing cycle ran. Several patients had not hit the 16-day transmission threshold within the 30-day window. The work was done. The reimbursement did not follow.

That gap between clinical effort and captured reimbursement is where digital medicine workflows succeed or fail.

Why the Coding Architecture Comes First

Technical literacy is professional self-defense. If you do not understand how digital medicine is coded and reimbursed, you will build workflows that are clinically sound but financially unstable.

The American Medical Association has recognized the permanent shift toward digitally enabled care. For 2025, the CPT Editorial Panel introduced a new series of telemedicine codes (CPT 98000-98016) that replace the temporary pandemic-era guidelines [1][2]. These codes mirror the structure of traditional Evaluation and Management (E/M) codes, allowing physicians to report services based on either Medical Decision Making (MDM) or Total Time [2].

The 2025 Telemedicine Code Updates

Previously, virtual visits were billed using standard E/M codes appended with modifiers: 95 for audio/video or 93 for audio-only encounters [2]. The 2025 system creates distinct codes for each modality, removing the modifier dependency.

Table 1: 2025 Telemedicine E/M Codes (New Patients)

Level of MDM / TimeAudio/Video CodeAudio-Only CodeCorresponding In-Person E/M
Straightforward (15 min)980009800899202
Low (30 min)980019800999203
Moderate (45 min)980029801099204
High (60 min)980039801199205

Table 2: 2025 Telemedicine E/M Codes (Established Patients)

Level of MDM / TimeAudio/Video CodeAudio-Only CodeCorresponding In-Person E/M
Straightforward (10 min)980049801299212
Low (20 min)980059801399213
Moderate (30 min)980069801499214
High (40 min)980079801599215

The Work RVUs for these codes are generally equivalent to their in-person counterparts. The Total RVUs are lower for audio/video and lower still for audio-only, reflecting the reduced overhead of virtual delivery [2].

CPT 98016 covers brief communication technology-based services of 5-10 minutes for established patients. It replaces the Medicare G2012 virtual check-in code [2]. If you run quick hypertension follow-ups or medication questions that do not rise to a full E/M visit, this is the code you need.

One operational step before you switch: verify with your specific payers whether they have adopted the 98000-series codes or still require the traditional E/M code with modifier. Medicare has published adoption timelines, but commercial payers vary significantly [2]. Billing the wrong code to the wrong payer is not a rounding error.

Engineering the RPM Workflow

Remote Patient Monitoring is where continuous digital care becomes clinically and financially viable. For an MFM practice managing gestational hypertension or diabetes, RPM is not supplementary. It is central to how we extend clinical oversight between visits.

The core RPM codes map to distinct phases of the monitoring process:

  • CPT 99453 covers the initial setup of the FDA-defined medical device and patient education. It is a one-time charge per episode of care [3].
  • CPT 99454 covers device supply and the continuous transmission of daily recordings. It requires at least 16 days of data transmission within a 30-day period to be billable [3].
  • CPT 99457 covers the first 20 minutes of clinical staff time directed by a physician or qualified healthcare professional per calendar month. Interactive communication with the patient or caregiver is required [3].

That 16-day threshold for 99454 is the one that catches practices off guard. It means your monitoring workflow needs to track transmission days in real time, not at the end of the billing cycle. If your EHR is not surfacing this data automatically, you will lose revenue on patients who were clinically well-monitored but administratively under-documented.

Self-Measured Blood Pressure

For hypertension management, SMBP coding provides a targeted path. CPT 99473 covers initial education, training, and device calibration. CPT 99474 covers ongoing collection and interpretation of the data [4]. These codes ensure the cognitive work of analyzing blood pressure trends is captured, not just the device provision itself.

Building a System That Captures the Work

The codes exist. The question is whether your workflow generates the documentation to support them.

I audit my digital medicine workflows the same way I audit a clinical protocol. Where is the data actually being generated? Where does it get recorded? Where is the gap between the work being done and the work being billed?

For telehealth, that means confirming that MDM documentation or time documentation is present on every virtual encounter. The 2025 codes do not raise the documentation standard. They change how you report it.

For RPM, that means your EHR tracks transmission counts by patient, not just that a device was issued. Before building any RPM program, verify that your system can produce a report showing which patients have hit the 16-day threshold in the current billing cycle. If it cannot produce that report, the workflow is incomplete before a single patient is enrolled.

For 99457, that means a documentation workflow for nursing time that is connected to the physician record. Clinical staff time spent under general supervision can be billed incident-to the physician. But only if it is documented, linked, and auditable.

The principle I keep coming back to here is one I write about separately: logs before intelligence. You cannot build a sustainable digital medicine practice on monitoring data you are not reliably capturing. Fix the foundational data discipline first, then add the sophisticated workflows on top of it.

The Honest Assessment

I did not build my first RPM workflow poorly because I lacked clinical judgment. I built it poorly because I treated the billing architecture as someone else’s problem.

The honest question is not whether digital medicine is worth doing. It is whether you are willing to own the system behind it. If you outsource the understanding of how your work is coded and reimbursed, you are building on a foundation you do not control. That foundation will shift.

Build the workflow. Learn the codes. Then rebuild the workflow with the codes in mind from the start.


Related: Logs Before Intelligence: Why Data Discipline Must Precede AI Insight

References

[1] American Medical Association. “How the AMA Meets Need for New Telehealth CPT Codes.” AMA Practice Management. https://www.ama-assn.org/practice-management/cpt/how-ama-meets-need-new-telehealth-cpt-codes [2] Society for Maternal-Fetal Medicine. “New 2025 Telehealth CPT Codes.” SMFM News. https://www.smfm.org/news/new-2025-telehealth-cpt-codes [3] ThoroughCare. “2025 Remote Patient Monitoring CPT Codes: 99457, 99453, 99454.” ThoroughCare Blog. https://www.thoroughcare.net/blog/remote-patient-monitoring-billing-rules [4] AAPC. “CPT Code 99473 - Digitally Stored Data Services/Remote Physiologic Monitoring.” AAPC Codes. https://www.aapc.com/codes/cpt-codes/99473

telehealth billing CPT codes remote patient monitoring workflow physician-developer
Share X / Twitter Bluesky LinkedIn

Newsletter

Enjoyed this post?

Get physician-developer insights delivered weekly. No hype. No filler.

Powered by beehiiv

Related Posts

InboxDetox dashboard showing AI-categorized email subscriptions on a dark interface displayed on a monitor
Technology Featured

I Built InboxDetox in Two Evenings — This Is What Disposable Software Looks Like

InboxDetox is an AI-powered email unsubscribe manager built in two evenings and deployed to Railway. It is on GitHub. Take it.

· 5 min read
disposable softwarephysician-developerNext.js
Pregnant woman sitting alone on a dark couch late at night, her face lit by the glow of her phone as she types a medical question into a chatbot
AI in Medicine Featured

Your Patients Are Already Using ChatGPT to Decide Whether to Call You

They are not asking it for fun. They are asking it because the triage line puts them on hold for 45 minutes. The threat is not the technology. The threat is the system that made the technology necessary.

· 10 min read
patient safetyclinical AIphysician-developer
Hospital IT conference room with vendor AI presentation on screen, physicians at the table, one with a code editor open
AI in Medicine

The EHR Vendor Wants You to Stay a Consultant

Physician passivity in health tech is not an accident. It is a business model. Understanding the structural incentives is the first step to building outside of them.

· 6 min read
EHRhealth techphysician-developer
Chukwuma Onyeije, MD, FACOG

Chukwuma Onyeije, MD, FACOG

Maternal-Fetal Medicine Specialist

MFM specialist at Atlanta Perinatal Associates. Founder of CodeCraftMD and OpenMFM.org. I write about building physician-owned AI tools, clinical software, and the case for doctors who code.