HomeComprehensive Medication Review SimulatorMedication Therapy Management Billing Simulator

📋 Medication Therapy Management Billing Simulator

This simulation helps healthcare professionals document and bill for medication therapy management services. It covers the process of tracking, evaluating, and managing a patient's medication regimen to optimize therapeutic outcomes while ensuring accurate billing practices.

Comprehensive Medication Review Simulator2DModerate60 FPS
mtm-billing-simulator ↗ Open standalone

Medication Therapy Management Is a Distinct, Billable Clinical Service

Medication Therapy Management (MTM) is not the same thing as answering a quick question at the pharmacy counter. It is a structured, patient-specific clinical service — comprehensive or targeted medication review, assessment of therapy problems, and documented recommendations — that payers recognize and reimburse under specific billing codes. Treating MTM as billable from the outset, rather than as an informal add-on to dispensing, is what connects the clinical encounter to an actual revenue pathway.

  • 99605–99607: Common MTM billing codes (pharmacist time-based CPT codes)
  • ~0%: Informal counseling billed (ad-hoc counseling is rarely reimbursable)
  • $75–125: Illustrative reimbursement / CMR (varies widely by payer and plan)
  • ~25–30%: Medicare Part D MTM-eligible (of Part D beneficiaries, illustrative)

Why MTM must be treated as a service line, not a courtesy

Pharmacists answer medication questions constantly — dosing clarifications, side-effect concerns, refill timing. Almost none of that is billable, because it lacks the structure, scope, and documentation that payers require to recognize a reimbursable clinical encounter.

MTM is different by design. It is delivered as a defined encounter type — often a Comprehensive Medication Review (CMR) or a Targeted Medication Review (TMR) — with a beginning, a scope of work, and an expected set of deliverables (a personal medication list, a medication-related action plan, documented recommendations to prescribers). That structure is precisely what makes it billable: payers are not reimbursing "a conversation," they are reimbursing a defined clinical service with a verifiable output.

Treating MTM as a billable service line from the start changes operational behavior: encounters get scheduled deliberately, time gets tracked, and documentation gets built to satisfy claims requirements rather than assembled after the fact.

The single biggest gap between clinical value and financial sustainability in pharmacy practice is not a lack of clinical impact — it is under-documentation and under-billing of services that were, in fact, delivered.

Connecting the clinical encounter to a billing pathway

Every billable MTM encounter needs a clear path from "service delivered" to "claim submitted." That pathway typically has four checkpoints, each covered in a later stage of this simulator:

1. Confirm the patient is eligible for the specific MTM program or benefit being billed 2. Track and document the actual time spent on the encounter 3. Capture the required documentation elements the payer expects to see 4. Assemble and submit the claim, then track whether it was reimbursed

Skipping any checkpoint does not just create administrative rework — it can mean clinically valuable work goes completely unreimbursed, which undermines the case for staffing and sustaining MTM services at all.

Confirming Patient Eligibility Before the Service Can Be Billed

Almost every MTM program — Medicare Part D plans, state Medicaid programs, commercial payer MTM benefits — defines its own eligibility criteria. Before an encounter can be billed under a given program, the patient's eligibility must be confirmed against those criteria. Skipping this check is one of the most common reasons MTM claims are denied.

  • ≥2–3: Typical chronic condition threshold (program-defined minimum count)
  • ≥5–8: Typical chronic medication threshold (maintenance medications, illustrative)
  • 5–10 min: Eligibility verification time (per patient, chart/claims review)
  • ~10–20%: CMR completion among eligible (illustrative program participation rate)

What eligibility criteria usually check

While exact thresholds vary by program, eligibility determination generally checks a combination of:

• Number of qualifying chronic conditions (e.g., diabetes, hypertension, heart failure, asthma/COPD) — often a minimum count is required • Number of chronic/maintenance medications the patient is taking — programs frequently set a minimum medication count • Estimated annual drug spend for the patient, for some payer-defined programs • Enrollment status in the specific plan or benefit being billed • Program-specific inclusion or exclusion rules (e.g., residency in a long-term care facility, recent hospitalization)

A patient can be clinically appropriate for a medication review and still fail to meet a specific program's billing eligibility criteria — which is why the eligibility gate has to be checked explicitly, separate from clinical judgment.

Why the gate matters before scheduling the encounter

Confirming eligibility before the encounter — rather than after — avoids two costly outcomes: delivering a full clinical service that turns out not to be billable, and delaying reimbursement while eligibility is retroactively verified.

In practice, eligibility determination is usually a quick lookup against plan eligibility files or a documented chronic-condition/medication count from the chart, but it is a required checkpoint, not an optional formality — most payer audits of denied MTM claims cite unmet or undocumented eligibility as a leading cause.

A patient meeting clinical criteria for medication optimization is not automatically "billable" — eligibility determination is a distinct, payer-specific gate that must be checked and documented before the encounter is scheduled as a billable service.

Time-Based Documentation Requirements Drive the Reimbursement Level

A large share of MTM billing codes are structured around time: an initial increment (commonly around 15 minutes) followed by additional increments for further time spent. Because the reimbursement level is tied directly to documented duration and complexity, accurately tracking and recording time spent is one of the most operationally important — and most frequently audited — parts of MTM billing.

  • ≈15 min: Initial encounter increment (illustrative starting code increment)
  • +15 min each: Additional increments (illustrative add-on code structure)
  • Leading: Time documentation as denial cause (frequently cited audit finding)
  • Real-time log: Recommended practice (log time during, not after, the encounter)

Why time has to be tracked, not estimated

Because reimbursement tiers are keyed to time thresholds, an encounter that runs 12 minutes and one that runs 22 minutes may fall into different billing tiers entirely — even though both may have been clinically thorough. Estimating time after the fact ("that felt like about 20 minutes") introduces both compliance risk and revenue risk: overstating time is an audit and compliance exposure, while understating time under-bills a service that was actually more complex than the code reflects.

Best practice is to log start and stop times contemporaneously — during the encounter — rather than reconstructing them afterward. Some MTM platforms timestamp the encounter automatically; where that is not available, a simple real-time log against the encounter note is the safer approach.

Complexity and time are usually documented together

Time alone rarely justifies a billing tier on its own — most payers expect the documented complexity of the encounter (number of medication-related problems addressed, number of interventions made, coordination with prescribers) to be consistent with the amount of time billed. A 45-minute encounter with a single, simple recommendation may draw more audit scrutiny than a 45-minute encounter addressing five interacting medication problems across two prescribers.

This is why time-based documentation and the "required documentation elements" covered in the next stage are closely linked: the time log substantiates the billing tier, and the documented problem/intervention/outcome substantiates that the time was clinically justified.

Reimbursement level depends on both service duration and complexity — a time log without a documented rationale for that time is exactly the pattern payer audits flag first.

Assembling the Documentation Elements a Claim Requires

Successful billing depends on assembling specific documentation elements into a claim that satisfies payer requirements: the medication-related problem identified, the intervention the pharmacist performed, the time spent delivering the service, and the outcome or resolution achieved. A claim missing any one of these elements is a common cause of denial or delayed reimbursement.

  • 4: Core documentation elements (problem · intervention · time · outcome)
  • ~25–35%: Claims denied for missing elements (illustrative audit finding)
  • Structured note: Common documentation format (SOAP-style or program template)
  • Recommended: Prescriber communication record (supports the intervention element)

The four elements, and what payers look for in each

1. Problem identified — the specific medication-related problem (drug interaction, therapeutic duplication, non-adherence, untreated indication, dosing concern) stated clearly enough that a reviewer can independently understand what was found.

2. Intervention — the specific action the pharmacist took: recommendation communicated to the prescriber, patient education provided, medication regimen adjustment suggested, adherence tool introduced. Vague language ("discussed medications") is a common denial trigger; specific, actionable language is not.

3. Time spent — the documented duration, consistent with the billing tier claimed (Stage 3), ideally logged contemporaneously.

4. Outcome — what happened as a result: prescriber accepted/declined the recommendation, patient adherence improved, problem resolved or remains open with a follow-up plan. Payers increasingly want to see that the loop was closed, not just that a recommendation was made.

Assembling elements into a claim-ready record

In practice, these four elements are usually captured in a structured template — often SOAP-style (Subjective / Objective / Assessment / Plan) or a program-specific MTM documentation form — rather than free-text narrative. Structured templates make it easier to verify, before submission, that all four required elements are actually present and internally consistent (e.g., the time logged matches the billing tier claimed; the outcome references the intervention documented).

A useful pre-submission check is simply asking, for each encounter: can a reviewer who was not there read this note and independently identify the problem, the intervention, the time, and the outcome? If any one of those is missing or ambiguous, the claim is not yet ready for submission.

A clinically excellent encounter with an incomplete note is, from a billing standpoint, indistinguishable from an encounter that never happened — documentation completeness is what makes the clinical work legible to the payer.

Claim Submission and Reimbursement Tracking Sustain the Service

Once documentation is complete, the claim is submitted through the appropriate billing pathway — pharmacy claims system, medical claims (CMS-1500), or a program-specific MTM platform. Tracking what happens after submission — accepted, denied, reimbursed, at what rate, and how long it took — is what turns individual encounters into evidence that the MTM service line is financially sustainable, not just clinically valuable.

  • ~15–25%: Initial claim rejection rate (illustrative industry range)
  • 30–45 days: Typical reimbursement timeline (payer-dependent, illustrative)
  • $1 : $3–12: Cited MTM cost-avoidance ratio (illustrative literature range)
  • Growing: Reimbursement tracking maturity (increasingly treated as a core metric)

From completed note to submitted claim

A claim-ready encounter (eligibility confirmed, time documented, all four required elements present) is coded with the appropriate billing code and submitted through the relevant channel. Depending on the payer and program, this may run through standard pharmacy claims adjudication, a medical claim form, or a dedicated MTM vendor platform that aggregates and forwards claims to the plan.

Common reasons a technically complete claim is still rejected at this stage include: eligibility mismatches discovered at adjudication (the plan's records disagreeing with the pharmacy's), coding errors, and timing issues (claims submitted outside the payer's filing window).

Why reimbursement tracking matters beyond the individual claim

Tracking reimbursement outcomes over time — submission-to-payment lag, denial rate and denial reasons, average reimbursement per encounter type — serves two purposes. Operationally, it identifies recurring failure points (a particular eligibility check that is frequently wrong, a documentation gap that repeatedly triggers denials) so they can be fixed upstream rather than re-litigated claim by claim.

Strategically, aggregated reimbursement data is the evidence base for demonstrating that MTM is not just clinically beneficial but financially sustainable — which is often what determines whether a service line gets continued staffing, expanded hours, or investment in supporting technology.

A single unbilled or denied MTM encounter is a minor loss. A pattern of unbilled or denied encounters, invisible without reimbursement tracking, is what quietly makes an otherwise valuable clinical service look financially unsustainable.
⚙ Under the hood

This simulation helps healthcare professionals document and bill for medication therapy management services. It covers the process of tracking, evaluating, and managing a patient's medication regimen to optimize therapeutic outcomes while ensuring accurate billing practices.

CanvasBiomedicine

2D · HTML5 Canvas 2D · 60 FPS target · runs fully client-side, no install

What did you find?

Add reproduction steps (optional)