Skip to content
English
Sign in
  • There are no suggestions because the search field is empty.

Dentical / Medi-Cal Eligibility: Best Practices for Running Verifications

Context: "Patient Not Found" errors on Dentical / Medi-Cal are often linked to a payer-side database sync window that runs end-of-day. Verification calls made during this period may fail even for fully active patients. Following the scheduling guidance below can significantly reduce the frequency of these errors. 

Why this helps: Scheduling verifications in the morning — after the payer database has refreshed — reduces the likelihood of sync-related failures. While this does not guarantee zero errors, teams that have adopted this approach report fewer "Patient Not Found" occurrences tied to timing.

Payer Database Refresh

Dentical / Medi-Cal runs a full database refresh at end-of-day. During this window:

  • Patient records may be temporarily inaccessible or in an inconsistent state
  • Eligibility API calls can return "Patient Not Found" regardless of actual coverage status
  • The window duration is payer-controlled and Payer does not indicate the start or end of the refresh
  • Once the sync completes, records return to a consistent state

Observed Behavior

Verification Timing Behavior Likely Outcome
Evening

(during sync window)

 Records temporarily unavailable ❌ "Patient Not Found" error
Morning
(after sync completes)		 Database fully refreshed ✅ Consistent eligibility results

Recommended Configuration

1. Reschedule batch jobs to morning execution

Where possible, schedule eligibility verification batch jobs for this payer to run at the start of the business day. API calls made after the nightly sync has completed are more likely to return accurate, stable results.

// Recommended: schedule after 8:00 AM local time
// Avoid: any job window between ~8:00 PM – 6:00 AM

2. Add Dentical / Medi-Cal to the Same-Day Morning Batch Job

Configure this payer explicitly within the Same-Day Morning Batch Job. This groups it with other payers that require post-refresh execution and ensures consistent behavior across scheduling changes.

Diagnosing a "Patient Not Found" Error

Before escalating, verify the following:

Check How to Verify
What time did the verification run? Check job logs for execution timestamp. If evening, timing is the likely cause.
Does the error repeat in the morning? Re-run the same verification after 8:00 AM. If it resolves, timing was the likely root cause.
Is this isolated or widespread? If multiple patients fail within a window of time, it is likely a db timing issue. If a single patient fails consistently at any time of day, it may be a coverage data issue.
Capture the Correlation ID Log the Correlation ID from the failed response. This is required if the issue needs to be escalated to the Zuub support team.