Controlled substance workflow
ModMed Pain Controlled Substance Intake: AI-Assisted New-Patient Screening, PDMP Checks, and Opioid Agreement Workflow
New-pain-patient intake calls involving controlled substances are the highest-stakes calls a pain practice handles. One careless promise of a refill, one missed PDMP cue, one undocumented prior-prescriber detail, and the practice is exposed to DEA scrutiny, state monitoring program flags, and potential drug-seeking behavior. MedReception AI runs these calls inside the guardrails ModMed Pain (EMA) clinicians actually need: structured data capture, opioid agreement awareness, and a hard rule against ever committing to a controlled substance prescription on the phone.
Baseline intake time
41 min
Average new-pain-patient intake call without AI structure
With AI structured fields
12 min
Human time per intake after AI handles structured capture
Shopping call detection
89%
Of the 23% of new-pain-patient calls that are drug-shopping behavior
Refill promises made
0%
100% of controlled substance promises avoided on every call
The intake challenge
Why New-Pain-Patient Intake on Controlled Substances is the Hardest Call in the Practice
A new patient calls asking to be seen for chronic pain and mentions they are on opioids, benzodiazepines, or stimulants from a prior prescriber. That single sentence triggers a cascade of compliance, clinical, and operational requirements that a standard front-desk script is not built to handle. ModMed Pain practices in particular sit under heightened DEA and state monitoring program scrutiny, and the intake call is where the documentation trail starts.
DEA and Regulatory Exposure
- • DEA scrutiny on new-patient onboarding documentation
- • State prescription drug monitoring program checks required before first prescription
- • Mandatory opioid disclosures vary by state and substance
- • Insurance plans flag practices with poor intake documentation
- • Board of medicine complaints often trace back to weak intake records
Clinical Protocol Requirements
- • Opioid treatment agreement required before any controlled substance prescription
- • Urine drug screen protocol set by clinician at first visit
- • Prior prescriber records must be in chart before bridging therapy
- • Imaging and diagnostic workup expectations set on intake
- • Realistic timeline disclosure about evaluation versus prescription
Shopping Behavior Patterns
- • Caller pressuring for early appointment specifically to refill
- • Vague or shifting answers about prior prescriber identity
- • Requesting specific medication, dose, and quantity by name
- • Recent multiple-pharmacy or multiple-prescriber pattern hints
- • Refusal to consent to release of prior records
Front-Desk Risk Without Structure
- • Untrained staff may inadvertently promise continued prescribing
- • Free-text intake notes miss the structured fields ModMed expects
- • Inconsistent disclosures across staff create legal vulnerability
- • Shopping callers detected only after multiple visits
- • Prior prescriber details captured incompletely on the phone
What the AI captures
Structured Fields the AI Collects on Every Controlled Substance Intake
The AI runs through a clinician-approved intake script that mirrors the discrete fields ModMed Pain expects in EMA. Every field below is captured as structured data, not free text, so it pushes cleanly into the chart and is auditable end to end.
Current Medication List
- • Each controlled substance name, dose, and frequency
- • Prescribing pharmacy name and city for each medication
- • Last fill date and remaining supply
- • Non-controlled medications and over-the-counter use
- • Reported allergies and prior adverse reactions
Prior Prescriber and Records
- • Prior prescriber full name and clinic
- • Prior prescriber DEA number if patient can provide
- • Reason for transferring care
- • Consent to request prior records and PDMP review
- • Last appointment date and pending workup
UDS and Agreement Willingness
- • Willingness to provide urine drug screen at first visit
- • Understanding that an opioid agreement will be required
- • Acknowledgment of single-prescriber, single-pharmacy expectation
- • Willingness to follow tapering or adjuvant therapy plans
- • Understanding of random pill counts when applicable
Treatment Goals and Function
- • Pain location, duration, and prior workup
- • Functional goals stated in patient words
- • Prior interventions tried such as injections or PT
- • Surgical history relevant to pain etiology
- • Behavioral health context if disclosed by patient
Hard limits
What the AI Never Does on a Controlled Substance Intake Call
The guardrails are as important as the captures. The AI is configured to refuse the categories of statements that create DEA exposure or set patient expectations the clinician cannot honor. Every refusal is structurally enforced inside the call flow, not just suggested in the prompt.
Never Promise Refills
- • Will not say the patient will be prescribed any controlled substance
- • Will not say the practice continues prior prescriptions as bridging
- • Will not commit to refill timing of any kind
- • Will not confirm a specific clinician will or will not prescribe
- • Redirects all refill questions to the new-patient evaluation
Never Quote Dosages
- • Will not state typical doses, schedules, or maximums
- • Will not confirm or deny a dose the patient names
- • Will not suggest the clinic prescribes specific medications
- • Will not name brand or generic preferences
- • Captures the patient-reported dose only as a data field, not a clinical comment
Never Pre-commit to a Plan
- • Will not tell the patient a UDS will be waived
- • Will not tell the patient the opioid agreement is optional
- • Will not assert that prior records can be skipped
- • Will not promise a particular imaging or referral plan
- • Frames every step as decided by the clinician at the first visit
Schedules the Evaluation Only
- • Books the new-patient evaluation visit and nothing more
- • Captures consents required to begin records request
- • Explains what to bring including ID and prior records
- • Flags shopping-behavior signals for clinician review pre-visit
- • Triages medically urgent presentations to the clinical line
ModMed Pain integration
How the Intake Lands in EMA and the Practice Workflow
Capturing the right data is half the job. Pushing it into ModMed Pain in a usable shape is the other half. The AI is wired to deliver every structured field where the clinician already looks, and to coordinate the surrounding work that the front desk would otherwise have to chase.
Intake Form to EMA Push
- • Structured fields populate the EMA intake template
- • Medication list pre-populates so reconciliation begins before visit
- • Prior prescriber block sets up the records request task
- • Shopping flags surface in the chart pre-visit summary
- • Audit trail of the call recording and transcript attached to the encounter
PDMP Screenshot Coordination
- • Generates the PDMP request task in EMA for staff to run
- • Standardizes naming of the PDMP screenshot upload
- • Cross-references reported medications against PDMP at the desk
- • Flags discrepancies before the patient is in the room
- • Confirms PDMP attestation matches state requirements
Opioid Agreement Workflow Status
- • Marks agreement as required but unsigned on chart open
- • Coordinates with patient portal to deliver the agreement pre-visit
- • Tracks acknowledgment and signature status
- • Surfaces unsigned status to the rooming workflow
- • Holds prescribing actions until agreement is on file
First-Visit Setup
- • UDS collection slot added to the rooming checklist
- • Imaging review block surfaced if patient has prior imaging
- • Insurance authorization pre-checked for first-visit codes
- • Pharmacy of record captured for future ePrescribing
- • Behavioral health referral pathway flagged when indicated
Call flow timeline
From Inbound Call to Documented Intake in Three Phases
Minutes 0 to 3: Triage and Disclosures
AI greets, confirms identity, and surfaces the structural realities of a new-pain-patient evaluation up front so the caller knows what to expect.
Minutes 3 to 9: Structured Capture
AI runs the medication, prior prescriber, UDS willingness, and treatment goal sections as discrete fields, never as free text.
Minutes 9 to 12: Booking and Handoff
AI books the evaluation visit, confirms what to bring, sets the agreement and records tasks, and posts shopping-signal flags for clinician review.
Why pain practices choose AI here
The Calls You Cannot Afford to Wing
Pain practices live and die on documentation. Controlled substance intake calls are where the documentation either starts cleanly or starts behind. Running these intakes through a structured AI workflow tied directly to ModMed Pain gives the practice a defensible record from minute one.
See the Intake Flow in ActionPair with refill and PA workflows
Intake is the Start of the Controlled Substance Lifecycle
Once the patient is established, the same guardrails extend to refill and prior authorization calls. The structured fields captured at intake become the spine of every downstream controlled substance interaction the practice handles.
Prescription Refill CallsPricing and adjacent workflows