A PDMP, or prescription drug monitoring program, is a state-level electronic database that tracks controlled-substance prescriptions dispensed to patients. For telehealth operators, it is a compliance and clinical-decision layer separate from EPCS: an e-prescribing system may satisfy the technical requirements for electronically transmitting a controlled-substance prescription, but the prescriber still has separate state-specific obligations to review a PDMP.
That distinction matters most when a telehealth provider treats patients in multiple states. PDMP rules are not uniform nationwide. States can differ on which prescriptions trigger mandatory review, when a query must occur, whether repeat checks are required, and which professionals can access the database or delegate access.
The practical question is therefore not simply, "Does our e-prescribing system support controlled substances?" It is also: "For this provider, this patient, this medication, and this state, does a PDMP review need to happen before prescribing?"
What Is a PDMP?
A prescription drug monitoring program is an electronic database containing information about controlled-substance prescriptions dispensed within a jurisdiction.
The CDC describes PDMPs as electronic databases that track controlled-substance prescriptions and can help inform clinical decision-making. The agency identifies them as an important state-level intervention to improve prescribing practices and protect at-risk patients.
The emphasis on dispensed prescriptions matters. A PDMP is not simply a list of every prescription a clinician has considered or entered into an e-prescribing interface. Pharmacies and other required dispensers report covered dispensing activity to the applicable database according to jurisdiction-specific rules.
A prescriber reviewing a patient's PDMP history may therefore see information indicating that the patient recently received controlled medications from other clinicians or pharmacies.
Depending on the jurisdiction and database, relevant information can include:
- Controlled substances previously dispensed
- Dispensing dates
- Prescribing clinicians
- Dispensing pharmacies
- Drug and quantity information
- Refill or other dispensing information
- Patterns involving multiple prescribers or overlapping controlled-substance therapy
The purpose is not to turn a database response into an automatic prescribing decision. PDMP information provides another source of clinical context that the prescriber can evaluate alongside the patient's history, current medications, diagnosis, and other relevant information.
A PDMP Is a History Check, Not an Approval System
The language around PDMPs can sometimes make them sound like a system that approves or rejects a prescription.
That is not what they do.
A PDMP provides prescription-dispensing information to authorized users. The clinician uses that information to help evaluate the prescribing decision.
For example, a query may reveal that a patient has recently received another controlled medication from a different clinician. That does not automatically indicate inappropriate behavior or require denying another prescription. An entirely legitimate explanation may involve coordinated care, a recent specialist visit, or another clinical circumstance.
The clinician still needs to interpret the information appropriately.
That distinction matters for telehealth workflows because software should not turn a PDMP result into an unexplained binary flag. The information belongs inside clinical decision-making, not in place of it.
How PDMPs Differ From EPCS
PDMP and EPCS requirements often appear in the same controlled-substance workflow, which makes them easy to confuse.
They solve different problems.
EPCS, or electronic prescribing for controlled substances, concerns the systems and processes used to create, authenticate, sign, and electronically transmit controlled-substance prescriptions in accordance with applicable requirements.
A PDMP, by contrast, is a database containing controlled-substance dispensing history that an authorized prescriber may review as part of the prescribing process.
| EPCS | PDMP |
|---|
| Concerns electronic prescribing of controlled substances | Concerns reviewing controlled-substance dispensing history |
| Focuses on prescription creation, authentication, and transmission | Focuses on information available before or during the prescribing decision |
| Includes federal technical and security requirements | Operates primarily through jurisdiction-specific programs and requirements |
| Is built into or connected to prescribing technology | May be accessed through a state portal or integrated clinical system |
| Does not replace a required PDMP query | A PDMP query does not replace EPCS requirements |
Bask's existing guide to EPCS compliance for telehealth covers the electronic-prescribing side in more detail.
For operators, the key takeaway is simple: an EPCS-capable prescribing workflow does not, by itself, prove that every applicable PDMP obligation has been satisfied.
What Happens During a PDMP Check?
The exact workflow depends on the jurisdiction and the technology the clinician uses, but conceptually the process is straightforward.
A prescriber identifies the patient, accesses the relevant PDMP information, reviews applicable controlled-substance history, and considers that information before making the prescribing decision when review is required or clinically appropriate.
A simplified workflow can look like this:
| Step | Controlled-Substance Workflow |
|---|
| 1. Patient evaluation | Provider evaluates the patient and determines whether controlled-substance treatment is being considered |
| 2. Jurisdiction check | Workflow identifies the state-specific PDMP requirement that applies |
| 3. PDMP query | Authorized user accesses the patient's controlled-substance dispensing history |
| 4. Clinical review | Provider considers relevant prescribing history and potential safety concerns |
| 5. Prescribing decision | Clinician determines whether and how to prescribe |
| 6. EPCS | Prescription is electronically authenticated and transmitted when applicable |
| 7. Dispensing and reporting | Pharmacy processes the prescription, and covered dispensing activity may subsequently enter the PDMP. |
The PDMP query and the electronic transmission happen at different points for different purposes.
That separation is why telehealth operators need to design controlled-substance workflows around more than an e-prescribing button.
What a Prescriber Is Looking for in PDMP Data
PDMP data can help clinicians identify prescribing history relevant to safety or care coordination.
The CDC notes that PDMP information can help clinicians identify patients who may be at risk for overdose and can be useful when medication history is otherwise unavailable. Its clinical PDMP guidance specifically advises clinicians prescribing opioids to review other controlled medications and consider whether combinations such as opioids with benzodiazepines may increase risk.
A prescriber might therefore review the database for issues such as:
- Controlled medications from multiple prescribers
- Overlapping prescriptions
- Concurrent medications that may create additional risk
- Recent controlled-substance dispensing that was not otherwise visible in the chart
- Patterns that warrant clarification with the patient or coordination with another clinician
That does not mean every instance of multiple prescribing is inappropriate.
A patient may have multiple legitimate treating clinicians. PDMP records can also require clarification if demographic data, dispensing history, or other information appears inconsistent with the patient's account.
The database provides information to investigate, not a diagnosis of misuse.
Why PDMP Requirements Are Especially Complicated in Telehealth
A local medical practice can build its controlled-substance procedures around one state's rules.
A multi-state telehealth business may not have that luxury.
The same provider may treat patients located in multiple jurisdictions during a single workday, and the applicable PDMP process can change depending on where the patient is located and what is being prescribed.
That creates a workflow problem that looks similar to other state-variable telehealth requirements, including CPOM, professional licensure, and collaboration agreements.
Federal rules add a separate layer. HHS notes that DEA telemedicine flexibilities for prescribing controlled substances without a prior in-person evaluation have been extended through December 31, 2026, subject to conditions. Those federal flexibilities govern whether a telehealth prescription can be issued at all. They do not replace state PDMP obligations.
The software interface may remain identical while the legal requirements underneath it change from one encounter to another.
State PDMP Requirements Vary
There is no reliable nationwide rule stating that every prescriber must query a PDMP before every prescription for every controlled substance.
The CDC specifically notes that some states require providers to check the state PDMP before prescribing certain controlled substances and in certain circumstances.
That wording is important.
Depending on the jurisdiction, requirements may differ based on factors such as:
- Controlled-substance schedule
- Type of medication
- Initial prescription versus continuation
- Frequency of repeat prescribing
- Length of therapy
- Provider or facility type
- Emergency circumstances
- Other statutory exceptions
A telehealth company should therefore avoid coding one simplified national rule into its prescribing workflow unless that rule intentionally exceeds all applicable requirements and has been appropriately reviewed.
Instead, operators need a way to determine which requirement applies to each prescribing event.
The Patient's Location Can Change the Workflow
Telehealth turns geography into workflow logic.
A prescriber may be sitting in one state while the patient receives care in another. The provider may be licensed in several jurisdictions and use the same clinical platform for all of them, but controlled-substance rules can still differ by state.
That means the platform needs reliable patient-location and provider-authorization information before the prescribing workflow reaches its compliance checkpoints.
For a telehealth operation, useful questions include:
- Where is the patient located at the time of care?
- Which state license is the clinician practicing under for that encounter?
- Which PDMP applies?
- Does that jurisdiction require a query for this prescription?
- Can the provider access the applicable database?
- Can access be delegated under that state's rules?
- Does the workflow document that the required review occurred?
These are operational questions before they become prescribing problems.
A platform that waits until the provider reaches the final prescription screen to discover that they cannot complete a required state database review has already introduced unnecessary friction into the clinical workflow.
PDMP Data Is Not Always Truly Real-Time
Another important operational detail is data freshness.
The term "monitoring program" can imply that every controlled-substance dispensing event appears in the database immediately. In practice, reporting intervals can differ.
The CDC explains that pharmacies submit controlled-substance dispensing data to state PDMPs at varying intervals, ranging from longer reporting periods to daily or near-real-time submission. More timely reporting gives clinicians access to more recent prescription history.
For clinicians, this creates an important limitation: the absence of a prescription from a PDMP does not necessarily prove that no recent dispensing event occurred.
PDMP information should therefore be considered alongside other clinical information rather than treated as an infallible, instantaneous record of every relevant medication event.
For telehealth operators, the practical lesson is that integrating access to a PDMP can make the workflow easier, but it does not eliminate the limitations of the underlying data.
Why PDMP Integration Matters Operationally
One of the biggest barriers to effective PDMP use is not the concept of checking the database. It is the friction involved in doing it repeatedly.
A clinician may otherwise need to:
-
Leave the clinical record.
-
Open a separate state portal.
-
Sign in.
-
Search for the patient.
-
Review the history.
-
Return to the telehealth platform.
-
Document whatever the workflow requires.
-
Continue prescribing.
Multiply that process by multiple patients and multiple states, and a small compliance step can become a substantial provider-workflow burden.
The CDC identifies integration of PDMP access into electronic health record systems as one practice that can make the databases easier to use.
For telehealth businesses, that creates an important technology-selection question:
Does the clinical workflow make required PDMP access practical, or does it force clinicians to reconstruct the compliance process manually for every prescription?
Integration can reduce friction, but operators should distinguish between several different capabilities:
- Providing a link to the correct state PDMP
- Allowing single sign-on or embedded access
- Returning PDMP information inside the clinical interface
- Documenting that a query occurred
- Determining when a query is legally required
- Automatically performing a query
Those are not the same feature.
When a vendor claims "PDMP support," ask exactly which of those functions it provides.
What the Evidence Says About PDMPs
PDMPs are widely used as public-health and clinical decision-support tools, but the evidence should be described carefully.
The CDC calls PDMPs among the more promising state-level interventions for improving opioid prescribing, informing clinical practice, and protecting patients at risk. At the same time, the agency notes that study findings have been mixed. Evaluations have found changes in prescribing behavior and use of multiple providers, but results vary across implementations and outcomes.
That nuance matters.
It would be too strong to say that simply creating or checking a PDMP automatically prevents misuse, overdose, or inappropriate prescribing.
The usefulness of the system depends on several things:
- Whether clinicians actually access it
- Whether the data are sufficiently current
- Whether relevant information is easy to interpret
- Whether PDMP access fits into the clinical workflow
- How clinicians respond to the information they find
The CDC's clinical guidance reinforces this point by advising clinicians to use PDMP data alongside other clinical information rather than letting the database replace professional judgment.
PDMP Results Should Not Become an Automatic Denial
This point deserves particular attention in software design.
A PDMP may expose a prescribing pattern that warrants further review, but that information should not automatically label a patient or determine the outcome of care.
A clinician may need to discuss the information with the patient, confirm prescriptions that came from other providers, review the clinical context, or coordinate care.
In other words:
PDMP flag → clinical review → patient discussion when appropriate → prescribing decision
not:
PDMP flag → automatic rejection
This matters for telehealth systems using automated rules or decision support. Automation can surface information, but the workflow should preserve the clinician's responsibility to interpret it appropriately.
Building PDMP Requirements Into a Multi-State Telehealth Workflow
For a national telehealth operator, the hard part is not understanding what PDMP stands for. The hard part is ensuring the right check happens for the right patient without asking every provider to memorize dozens of state rules.
A useful operating model separates four questions.
1. Is a PDMP Query Required?
Determine whether the patient's jurisdiction requires a database review for the specific prescribing event.
This decision may depend on the substance, schedule, treatment context, and other statutory factors.
2. Which Database Must Be Queried?
The provider needs access to the appropriate jurisdiction's system or an authorized integration that can retrieve the relevant information.
Interstate data sharing can complicate this further, so operators should confirm what information is actually available through the systems their clinicians use.
3. Who Can Perform the Query?
Some jurisdictions permit certain forms of delegated access; others impose specific registration or user requirements.
The business should not assume that administrative staff, NPs, PAs, pharmacists, physicians, and other users all have identical permissions.
4. How Is the Review Documented?
Where applicable, the organization should understand what evidence it needs to retain showing that a required check occurred.
That may involve workflow records, audit information, clinical documentation, or another mechanism depending on the system and legal requirement.
These four questions create a more reliable framework than a single checkbox reading "PDMP compliant."
A Practical PDMP Workflow Checklist
Before launching controlled-substance prescribing in another state, telehealth operators can review the workflow across several areas.
| Area | Question to Verify |
|---|
| Patient jurisdiction | Do we reliably know where the patient is receiving care? |
| Provider authority | Is the clinician authorized to prescribe the controlled substance in that jurisdiction? |
| PDMP mandate | Does this prescribing event trigger a required PDMP check? |
| Database access | Can the clinician or authorized delegate access the correct PDMP? |
| Data review | Can the provider review relevant dispensing history before prescribing? |
| Documentation | Can the organization demonstrate that the required workflow occurred? |
| EPCS | Can the resulting prescription be transmitted through the applicable EPCS workflow? |
| Policy updates | Who monitors changes to state PDMP requirements? |
The sequence matters.
EPCS comes near the end because technical prescription transmission doesn't answer the earlier question of whether the clinician completed the required database review and clinical decision steps.
How Bask Health Fits Into PDMP-Related Compliance
Bask Health provides the infrastructure around the controlled-substance workflow, not the state database itself. Provider-facing systems, EMR and e-prescribing, patient records and management, and security controls run inside one platform, so the steps described above happen in a connected environment instead of across disconnected tools.
Several parts of that infrastructure matter directly for PDMP-related work:
- Access and audit controls. Bask's security infrastructure includes SOC 2 Type II controls, multi-factor authentication, audit logging, and HIPAA safeguards. Controlled-substance workflows depend on knowing which authorized user accessed what, and when.
- Synchronous and asynchronous care. Bask supports both live and asynchronous encounters, so brands can route prescriptions that require a real-time visit under applicable rules into a synchronous workflow while keeping other treatment lines asynchronous.
- Customizable treatment pathways. Intake and treatment flows can be configured per service line, which lets operators build jurisdiction and medication checkpoints into the pathway before a prescription reaches the prescriber.
- Integrated doctor networks. Every Bask plan includes access to integrated doctor groups, which reduces the clinical-network infrastructure a brand needs to assemble on its own.
Bask does not replace the prescriber's professional and jurisdiction-specific obligations. The responsible clinical organization still needs to confirm which PDMP checks apply to the care it delivers and that its prescribers complete them. Operators planning controlled-substance service lines can review what Bask includes in its plans.
FAQs
What Is a PDMP?
A PDMP, or prescription drug monitoring program, is an electronic database containing controlled-substance prescription dispensing information.
Authorized healthcare professionals can use PDMP information to review a patient's controlled-substance history and incorporate that information into prescribing and care decisions.
The precise data, access rules, and reporting requirements vary by jurisdiction.
How Is a PDMP Different From EPCS?
A PDMP provides access to controlled-substance dispensing history.
EPCS is the electronic prescribing process used to create, authenticate, and transmit controlled-substance prescriptions under applicable technical and regulatory requirements.
They can appear in the same workflow but perform different functions. A provider may need to review a PDMP before using EPCS to transmit the resulting prescription.
Do All States Require a PDMP Check Before Every Controlled-Substance Prescription?
No.
PDMP mandates vary by jurisdiction. The CDC notes that some states require a check before prescribing certain controlled substances and under certain circumstances, rather than establishing one universal requirement applying to every controlled-substance prescription nationwide.
Telehealth operators should verify the current requirement for the patient's jurisdiction, medication, provider type, and prescribing circumstances.
What Happens if a Prescriber Does Not Check the PDMP Where Required?
Failing to perform a legally required PDMP review can create compliance and professional-licensing exposure.
The exact consequences depend on the jurisdiction and circumstances. State laws and licensing-board requirements can differ, so telehealth organizations should not rely on a single national penalty model.
The safer operational approach is to design the prescribing workflow so required checks can be completed and documented before the prescription progresses.
Does a PDMP Tell a Prescriber Whether They Should Prescribe?
No.
A PDMP provides controlled-substance dispensing information that can inform the clinician's decision. The provider still needs to interpret the data in the context of the patient's history, current medications, clinical condition, and other relevant information.
PDMP data should support professional judgment, not replace it.
Conclusion
PDMPs are a separate compliance and clinical-decision layer inside controlled-substance prescribing. They give authorized clinicians access to controlled-substance dispensing history, while state law determines when and how to review that information.
For telehealth operators, the complexity comes from scale. One provider can encounter different PDMP requirements as patients move across jurisdictions, even when every prescription is written through the same EPCS system.
That is why PDMP compliance should be treated as a workflow question rather than a portal-login task. The organization needs to know which check applies, who can perform it, how the provider reviews the information, and how the process is documented.
EPCS can securely transmit the prescription. A PDMP helps inform what happens before that transmission. A compliant controlled-substance workflow may need both, but satisfying one does not automatically satisfy the other.
References
1. Centers for Disease Control and Prevention. (2024). Prescription drug monitoring programs (PDMPs). https://www.cdc.gov/overdose-prevention/php/interventions/prescription-drug-monitoring-programs.html
2. Centers for Disease Control and Prevention. (2024). Prescription drug monitoring programs (PDMPs): What clinicians need to know. https://www.cdc.gov/overdose-prevention/hcp/clinical-guidance/prescription-drug-monitoring-programs.html
3. Telehealth.HHS.gov. (2026). Prescribing controlled substances via telehealth. https://telehealth.hhs.gov/providers/telehealth-policy/prescribing-controlled-substances-via-telehealth
