Implementation 17 min read

California Clinic Compliance Checklist (2026): Telehealth, CURES, E-Prescribing, and Ops Controls

California has specific operational requirements around telehealth, controlled substances, and prescribing workflows. This checklist translates those requirements into execution steps for clinic operators and multi-site leadership teams.

Compliance + Vendor Evaluation Links

Key California Dates and Triggers

  • October 2, 2018: CURES consultation mandate became effective after statewide certification.
  • January 1, 2022: Mandatory e-prescribing requirements began for California prescribers, with specified exceptions.
  • August 1, 2024: CURES reporting required ASAP version 4.2B format for dispensers.
  • January 1, 2025: Additional opioid risk discussion requirements took effect under SB 607 before first opioid prescription in a single course of treatment.

DEA Proposed Rule for Controlled Substance Prescribing and Telehealth

Checklist 1: Telehealth Practice Controls

  • Confirm every telehealth service line has a documented standard-of-care policy equal to in-person expectations.
  • Map telehealth documentation requirements by specialty and encounter type.
  • Implement explicit consent and privacy workflow controls inside intake and scheduling.
  • Define escalation path for visits requiring in-person evaluation.
  • Audit telehealth encounter closure time and coding quality monthly.

California Control Matrix for EHR Configuration

Control EHR Configuration Audit Evidence
Telehealth Consent, modality, patient location, emergency contact, provider location, and escalation flag. Telehealth encounter report by clinician, location, consent status, payer, and note-close time.
CURES Prescribing prompt, documented check, exemption reason, delegate use, and recurring review cadence. Controlled-substance audit log with prescriber, date/time, CURES status, and exception reason.
E-prescribing Default electronic prescribing, failure workflow, paper exception reason, and EPCS role controls. E-prescribing exception report and failed-transmission remediation log.
Opioid risk discussion Required discussion field before first opioid prescription in a course of treatment where applicable. Medication-specific documentation report with missing-risk-discussion exceptions.
Privacy and release Role-based access, release-of-information workflow, amendment request tracking, and access logs. Access review, ROI log, privacy incident register, and corrective-action tracker.

Checklist 2: CURES and Controlled-Substance Workflow

California Medical Board guidance describes mandatory CURES consultation expectations, including first-time controlled-substance prescribing and recurring review cadence where controlled substances remain part of treatment.

  • Embed CURES check in prescribing workflow before order sign-off.
  • Track documented exemptions with rationale and reviewer.
  • Run monthly audit for missing CURES checks and remediation actions.
  • Ensure delegation workflows are policy-compliant and auditable.
  • Monitor recurring controlled-substance therapy so follow-up consultation cadence does not depend on prescriber memory.

Checklist 3: E-Prescribing and Failure Procedures

  • Default all prescribing to eRx where required.
  • When technological/electrical failures occur, enforce failure documentation SLA in the record.
  • Maintain contingency process for compliant paper/alternate workflows where exceptions apply.
  • Train prescribers and staff on controlled-substance EPCS requirements and local exception handling.

Checklist 4: Leadership Governance and Audit Cadence

  • Weekly: review controlled-substance exception log and aged note closures.
  • Monthly: review CURES compliance rate and telehealth documentation quality score.
  • Quarterly: refresh policies, staff attestations, and workflow training artifacts.
  • Semiannual: legal/compliance review for new California policy or board updates.

What to Ask EHR Vendors in a California Demo

  1. Show a telehealth intake from scheduling to signed note with consent, patient location, privacy notice, and billing output visible.
  2. Show a controlled-substance refill request with CURES check documentation, eRx workflow, exception handling, and audit export.
  3. Show how the system handles a technology failure during e-prescribing and what documentation is required before closing the task.
  4. Show a privacy investigation: who accessed the chart, what was disclosed, and how the record can be exported for review.
  5. Show a monthly compliance dashboard that a regional operator can review without custom reporting support.

30-60-90 Day Execution Plan

  • First 30 days: baseline CURES/eRx adherence and telehealth chart quality.
  • Days 31-60: patch workflow gaps in EHR order paths and role permissions.
  • Days 61-90: run live audits and formalize governance dashboard.

Common Failure Patterns

  • Policy-only compliance: the policy says CURES should be checked, but the prescribing workflow does not require evidence.
  • Telehealth ambiguity: charts do not consistently capture consent, patient location, or escalation when an in-person visit is needed.
  • Unowned exceptions: paper prescribing, transmission failures, and controlled-substance exceptions sit in inboxes without SLA ownership.
  • Weak auditability: leadership cannot quickly prove who did what, when, and why across sites.

Bottom Line

California compliance gets safer when clinic policy becomes EHR behavior. Build the required checks into scheduling, telehealth, prescribing, documentation, and audit reporting so leaders can see exceptions before they become board complaints, payer problems, or patient-safety events.

Primary Sources

Editorial Standards

Last reviewed:

Methodology

  • Mapped California telehealth, CURES, e-prescribing, opioid-risk discussion, privacy, and audit topics to operational EHR controls.
  • Prioritized workflows that clinic leaders can configure, train, monitor, and audit across multi-site teams.
  • Used California Medical Board, DCA, DHCS, and related primary sources for regulatory context.

Primary Sources