D.C. Medicaid Uses Sandata for EVV.
A Separate Program from Maryland and Virginia.

Washington D.C. operates a distinct Medicaid program through DHCF. It is not administratively connected to Maryland's or Virginia's Medicaid programs despite geographic proximity. A home care agency that serves clients across all three jurisdictions — D.C., Maryland, and Northern Virginia — is operating under three completely separate Medicaid systems with three different EVV requirements.

D.C.'s Hybrid model uses Sandata as the aggregator. Agencies choose their capture method. All visit data must reach Sandata before DHCF processes the corresponding claim.

Unlike Maryland (which uses ISAS and mandates direct use of the state system) and Virginia (which uses a Provider Choice model with no single aggregator), D.C.'s Sandata requirement is similar in structure to many other states — but it is a separate Sandata enrollment and configuration from any Maryland or Virginia setup. A Sandata account configured for another state does not automatically cover D.C.

CareBravo manages the D.C. Sandata exception queue as part of its daily delivered operations, tracking D.C.-specific enrollment and billing requirements separately from any adjacent jurisdiction the agency may also serve.

D.C. is an urban environment with strong cellular coverage — the connectivity-related exceptions that affect rural states aren't a factor here. But missed clock-ins, GPS discrepancies from dense urban environments with GPS signal interference from buildings, and authorization mismatches all generate Sandata exceptions that must be resolved before billing. For a 25-patient D.C. agency, a week's exception backlog typically represents $700–$1,400 in delayed revenue. CareBravo resolves exceptions daily.