Medication therapy management has historically been defined as pharmacist-led work — comprehensive medication reviews, therapy assessments, and care plan development all sit squarely in the pharmacist’s clinical judgment. But as MTM volume grows under Medicare Part D and state-level programs, a growing number of boards have started carving out defined technician support roles inside that workflow. Here’s how the division of labor actually works, and why “technician does MTM” is more nuanced than it sounds.
What MTM technicians actually do
No state licenses technicians to perform clinical MTM independently. What’s changed is that some states now explicitly authorize technicians to handle the administrative and data-gathering layer that surrounds an MTM encounter, freeing the pharmacist to focus on the clinical assessment itself. Typical technician-eligible tasks include:
- Identifying and enrolling MTM-eligible patients based on payer criteria
- Collecting medication histories, including OTC and supplement use, before a pharmacist review
- Scheduling comprehensive medication review (CMR) appointments
- Preparing personal medication lists and standardized documentation templates
- Following up with patients on logistics (appointment reminders, form completion) after a pharmacist has set the care plan
- Data entry into MTM platforms and claims/billing documentation support
What remains pharmacist-only in every state: the actual therapy assessment, identifying and resolving drug therapy problems, making recommendations to prescribers, and clinical sign-off on the care plan. The technician role is structured as pre-visit and post-visit support, not clinical decision-making.
Why this distinction matters for scope compliance
The risk for pharmacies isn’t usually intentional overreach — it’s scope creep that happens gradually as MTM volume increases and technicians become more experienced. A technician who’s been collecting medication histories for two years may start flagging what look like drug interactions or making informal recommendations during patient calls. That’s a scope violation even if the technician is highly competent, because the authority to identify and resolve a drug therapy problem is defined by license type, not by skill level.
State variation in how this is authorized
Some states address technician MTM support through general technician scope-of-practice regulations — the same rules that govern pharmacy technician scope expansion more broadly — without a dedicated MTM provision. Others have issued specific guidance or board policy statements addressing technician roles in MTM platforms and CMR logistics. A smaller number have stayed silent on the topic entirely, in which case the default assumption is that technician tasks must fall within the general technician scope framework already in place.
This inconsistency means a technician support model that’s compliant in one state may not be automatically transferable if your organization operates across state lines. Multi-state chains and MTM vendor platforms often build their technician workflows to the most conservative applicable state standard, then loosen tasks in states with broader authorization — but confirm your state’s current position before assuming a workflow used elsewhere applies.
Certification and training expectations
Most states that formally address technician MTM support also expect the technician to hold current state certification (national certification through PTCB or NHA is typically required as baseline technician credentialing already) and — depending on the pharmacy’s internal policy — completion of MTM-platform-specific training. Certification requirements for technicians generally are covered in more depth in our piece on technician national certification versus state requirements, which is worth reviewing since MTM task delegation typically sits on top of, not instead of, baseline certification requirements.
Some MTM platforms (particularly those used for Medicare Part D CMR delivery) have their own training modules for support staff, separate from state licensing requirements. Completing platform training doesn’t expand legal scope of practice — it’s a competency layer on top of whatever the state already authorizes.
Documentation matters as much as the task itself
Even for tasks squarely within technician scope, documentation should make clear who did what. If a technician collects a medication history and a pharmacist later reviews and signs off on the assessment built from it, the record should reflect that division — not read as though the pharmacist independently gathered and assessed everything, and not blur into implying the technician made a clinical judgment. This matters for audit purposes with payers as much as for board compliance; MTM billing to Medicare Part D plans is increasingly subject to documentation review, and unclear role attribution in the chart can create billing exposure independent of any scope-of-practice question.
Where this intersects with CDTM
In states with collaborative practice agreement or collaborative drug therapy management frameworks, MTM and CDTM sometimes overlap operationally — a pharmacist may be modifying therapy under a CPA in the same encounter where MTM services are billed. Technician involvement in that hybrid encounter still follows the same rule: administrative and data support only, no participation in the clinical decision itself. See the glossary entry on CDTM and collaborative practice agreement for more on how that authority is structured.
Bottom line
Technician involvement in MTM is expanding, but the boundary is consistent everywhere it’s been addressed: technicians support the process, pharmacists own the clinical content. Requirements, allowed tasks, and certification expectations vary by state and can change as boards update technician scope regulations — confirm the current rule with your state board before building or expanding a technician-supported MTM workflow.
RxByState tracks technician scope-of-practice rules and regulatory updates across all 50 states, so you’re not left checking board bulletins manually. Start a free 14-day trial →