This article covers insurance verification errors that are caused by the patient's insurance data not having synced from the EHR yet, rather than by missing or incorrect insurance details.
Error: Payer ID and member ID could not be auto-populated
If a customer reports that all or most patients are showing the error "Payer ID and member ID could not be automatically populated from your health record system" — and the sync is running — the most likely cause is that the historical read has not completed or needs to be restarted. This is not specific to one EHR but has been observed with Open Dental.
Resolution: Restart the historical read for the affected institution in Tools. Verification should begin succeeding once the read cycle completes and insurance data is populated.
Confirm the sync is running and not in an error state.
In Tools, navigate to the institution and restart the historical read.
Monitor the next sync cycle. Successful verifications should appear once insurance data has been read from the EHR.
Note: If the error persists after a successful historical read, check that the patient records in the EHR have Payer ID and Member ID fields populated. Missing insurance data in the EHR cannot be resolved by a sync restart — the practice will need to update the records directly.
Other sync-related verification failures
When verification errors appear across many patients simultaneously (rather than for isolated patients), a sync issue is often the root cause. Before troubleshooting individual patient records, check the following:
Is the sync running? A downed or stalled sync means NexHealth has stale patient data. Restart the sync if needed.
Has the historical read completed? New or recently re-onboarded locations may not have had a full patient read yet.
Were there recent EHR credential changes? A password or credential change can interrupt the sync and leave insurance data out of date.
If the sync is healthy and errors persist, escalate to the Tier 1 verification troubleshooting playbook for per-patient resolution steps.
Source: Slack thread, 2026-06-01T21:15:00Z.