What It Means That CareHub Is an Approved DMAS Service Center

Virginia DMAS has approved CareHub as a Service Center for electronic remittance advice (the EDI 835 transaction). If you are a Virginia DD waiver provider and you have ever asked an EHR vendor whether they handle Medicaid payment information directly, you already know how rare a "yes" actually is.

This post explains what that approval is, what it changes for providers, and what does not change yet.

What is a DMAS Service Center?

When Virginia Medicaid pays a provider, the payment is accompanied by an electronic file called an 835 Electronic Remittance Advice. The 835 tells you exactly which claims were paid, which were denied, the adjudicated amount on each line, and the reason codes for anything that was adjusted. It is the document your billing person posts to your books.

DMAS does not send 835s directly to every provider. Most providers route them through a Service Center, a third party that DMAS has approved to receive 835 files on the provider's behalf and make them available to the provider's billing system. Clearinghouses do this for hospitals. EHR vendors do it for medical practices. Until recently, very few IDD-focused systems were on the list at all.

CareHub now is.

Why this matters for DD waiver providers

Most Virginia DD waiver providers reconcile Medicaid payments by hand. The check or ACH deposit lands in the bank, then someone in billing logs into a payer portal, downloads the remittance, opens a spreadsheet, and walks each line back to a claim that was submitted weeks earlier. Denials are easy to miss. Underpayments are easier to miss. Recoupments from prior periods are the hardest of all, because by the time a finance team sees them they have already affected three months of cash flow.

A Service Center fixes the routing problem. The 835 lands in the same system your billing team already uses, line items tie back to the claims they answer, denials surface as a queue, and prior-period adjustments are visible the day they happen instead of the day someone notices.

For an IDD provider running residential supports under Building Independence, FIS, or Community Living, that visibility matters in three concrete ways:

• Faster posting. The bottleneck is usually not the work, it is the lag between deposit and reconciliation. A Service Center cuts it.
• Denial recovery. Many DD waiver denials are technically correctable (a wrong service authorization, an off-by-one date, a missing modifier). Seeing them inside a queue rather than at the bottom of a downloaded PDF means more of them actually get worked.
• Audit defensibility. DMAS recoupment lookbacks routinely cover several years. An organized digital remittance trail is the difference between a clean response and a frantic file hunt.

What changes for providers, and when

DMAS approval is the first step. The remaining steps are:

1. FAS testing. DMAS's Financial Application Services team runs a controlled testing window where CareHub processes sample 835 files against DMAS's spec. Standard, no provider action required.
2. Provider NPI association. Once we are live, each Virginia provider who wants 835 ERAs to flow through CareHub will associate their NPI with the CareHub Service Center ID on the MES Provider portal. If a provider is currently associated with another Service Center for 835, they will need to terminate that association first. DMAS has a short walkthrough video on the MES site that covers the steps.
3. Inside CareHub. Once a provider's NPI is associated, 835 data flows into the existing CareHub Claims module. Posting, denial queues, and reconciliation reports go from "log into a portal and download" to "open CareHub and work the queue."

We will email Virginia customers directly with the CareHub Service Center ID and the association instructions as soon as FAS testing wraps. Nothing for customers to do today except keep an eye out for that email.

Why CareHub pursued this

Most IDD EHRs stop at documentation, daily notes, MARs, incidents, and plans. Claims and remittance are punted to a separate billing vendor, which is the right call for a generalist EHR but creates real seams for DD waiver providers whose service-authorization logic and waiver-specific billing rules are tightly coupled to the rest of the record.

We pursued the Service Center designation for the same reason we built MAR per service type and incident reporting with CHRIS deadline tracking: when a documentation system understands the specific regulatory and payment shape of Virginia DD waivers, the work is faster, cleaner, and more defensible. Cutting one more handoff between the chart and the books is consistent with that direction.

What is next

FAS testing is in motion. Once that wraps, every Virginia DBHDS provider on CareHub will get a direct email with their next steps. New customers signing up after that point will have the option to enable 835 routing during onboarding.

If you operate a Virginia DD waiver service and want to be on the list when 835 routing turns on, the easiest path is to start a free 7-day trial at carehub.mydsplife.com. Free data migration is included during the trial. Once we are live with DMAS, your NPI association becomes a two-minute task instead of an integration project.

DSPlife™ Collaborative Group supports DD waiver providers with compliance tools, training, and now electronic remittance routing, all built by people who have done the work. Visit carehub.mydsplife.com to learn more.