New DDS eBilling Field for Remote Services: What Regional Center Vendors Must Do Starting July 2026
July 31, 2026
If your organization delivers any services remotely to Regional Center consumers — telehealth sessions, virtual behavior support, remote independent living skills training, or any other DDS-funded service provided outside a traditional in-person setting — a regulatory change is coming that will directly affect your claims.
Starting July 2026, the California Department of Developmental Services (DDS) will require vendors to populate a new designated field in the eBilling system to indicate whether a service was delivered remotely. Billing claims that omit or incorrectly populate this field may be rejected or flagged for audit. For organizations that have been delivering remote services since the pandemic-era flexibilities and never fully updated their billing workflows, this is a wake-up call — not a distant concern.
This post explains what the new requirement involves, why it matters operationally, and what your billing and compliance teams need to do right now.
Why DDS Is Adding a Remote Services Field
The expansion of remote service delivery under California's pandemic-era waivers revealed a significant gap in DDS's claims data: the system had no reliable, structured way to distinguish whether a given unit of service was delivered in person or remotely. That distinction matters for several reasons.
First, DDS and the Department of Health Care Services (DHCS) need accurate data to evaluate the cost-effectiveness and clinical appropriateness of remote versus in-person delivery across service types. Second, Regional Centers are under increasing pressure to ensure that Purchase of Service (POS) expenditures reflect the actual modality of service — particularly as remote delivery can carry different overhead costs than in-person care. Third, as CalAIM and related managed care integrations continue to evolve, having clean modality data in the DDS billing system will be essential for cross-program reporting.
The new DDS eBilling remote services 2026 requirement is, in short, a data integrity initiative with real compliance teeth.
What the New Field Actually Requires
While DDS has not yet released the final technical specifications in its eBilling companion guide (expected in early 2026), the directional requirements have been communicated through vendor bulletins and Regional Center provider relations channels. Here is what your team should expect:
A Mandatory Modality Indicator
Vendors will be required to include a service modality indicator on claims for covered service codes. The field will distinguish at minimum between:
- In-person (face-to-face, at a service location or consumer's home)
- Remote/telehealth (synchronous video or audio delivery)
- Hybrid (partially remote, partially in-person within the same service event, for applicable service types)
For certain service codes — particularly those tied to behavior support, independent living services, and supported employment — DDS may require additional detail about the platform or documentation of consumer consent for remote delivery.
Not All Service Codes Are Affected Equally
DDS is not applying this requirement uniformly across all billing codes. Service types that are inherently in-person — such as residential facility supports or certain day program codes — will not require remote modality documentation. Your billing team needs to map your active service codes against the DDS bulletin guidance to identify which claims will be affected.
This is not a task to delegate entirely to your software vendor. Your clinical and program staff need to confirm, at the service authorization and scheduling level, which services are being delivered remotely — because that information has to flow into your billing system accurately before the claim is ever generated.
The Operational Risk Your Organization Needs to Manage
The single biggest risk for Regional Center vendors under DDS eBilling remote services 2026 is not technical — it is workflow. Here is the failure pattern that leads to claim rejections and audit exposure:
- A direct support professional or clinician delivers a service remotely.
- The service note is entered in your EHR or billing platform without a modality field, or with a default "in-person" value that was never updated.
- The claim is submitted with incorrect or blank modality data.
- DDS flags the claim, or worse, pays it — and it surfaces in a post-payment audit.
That last scenario is the one that creates real liability. An incorrectly coded claim that is paid is not a billing error you can simply correct quietly. It can trigger a repayment demand, a compliance review, and in some cases a corrective action plan with your Regional Center.
What Your Team Needs to Audit Before July 2026
- Service documentation templates: Does your current progress note or session note capture service modality? If not, update the template now so staff document it at the point of care.
- Scheduling and authorization records: Are remote services flagged differently in your scheduling system? They should be.
- Billing system configuration: Can your current eBilling platform — whether that is the DDS web portal, a clearinghouse, or a practice management system — accept and transmit the new field? If you are still manually entering claims into the DDS portal, this is an opportunity to assess whether your current workflow is sustainable.
- Staff training: Front-line staff and supervisors need to understand that "how the service was delivered" is now a billing-relevant data point, not just a clinical one.
Preparing Your Billing System for the Change
If your organization uses a purpose-built platform for DDS billing, your vendor should be communicating a timeline for updating their system to support the new field. Ask your software vendor directly:
- When will the remote service modality field be available in the system?
- Will it auto-populate based on scheduling or session data, or will staff need to manually select it?
- Will there be claim validation that flags missing or inconsistent modality data before submission?
If you are receiving vague or non-committal answers, that is a signal to evaluate whether your current platform can keep pace with California's regulatory cadence. DDS eBilling remote services 2026 is not an isolated change — it is part of a broader DDS initiative to modernize claims data, and more structured fields are likely to follow.
Regional Center Coordination Is Also Required
Do not assume your Regional Center's service coordinator or contract manager is proactively reaching out about this change. Some Regional Centers have been more communicative than others in distributing DDS vendor bulletins. Your organization's compliance lead should be directly reviewing DDS Vendor Bulletins and attending any vendor training webinars DDS offers in the months leading up to July 2026.
Additionally, if your organization has a Vendor Agreement that specifies service delivery modality, review it now. If your agreement authorizes in-person delivery only and you have been delivering services remotely without an amendment, the new billing field will make that discrepancy visible in a way it has not been before. Get ahead of any authorization amendments before the field goes live.
The Bottom Line
The DDS eBilling remote services 2026 requirement is a targeted but consequential change for any California Regional Center vendor with remote service delivery in its model. The organizations that will handle this transition smoothly are the ones that treat it as a cross-functional workflow problem — not just a billing department task — and begin their internal audits and system updates now, rather than in June 2026.
Your documentation practices, your scheduling workflows, your billing platform configuration, and your staff training all need to be aligned before the first claim under the new requirement is submitted. That alignment takes time, and July 2026 is closer than it feels.
If you want to see how purpose-built software can help your team manage DDS billing compliance — including upcoming field requirements — See How CareAutomate Works for DDS Providers.