A: This was a workflow issue in Dazos where the insurance company name updated immediately but the payer code had a delay of approximately one day. The system was designed to update insurance fields only under specific conditions, but the primary insurance company field was updating even when the parent record already had a value, causing the payer code mismatch.
​

​

A: Since EMR systems like Kipu rely on the payer code rather than the insurance company name, this delay caused incorrect insurance information to be sent to your EMR. The mismatch would persist until the payer code eventually updated automatically.
​

A: Yes, this issue has been fixed by the Dazos development team. The payer code now updates immediately when you change the Primary Insurance Company during a full VOB submission, ensuring data consistency between Dazos and your EMR integration.
​

A: If you continue to see delays in payer code updates after changing insurance information in a full VOB, please contact Dazos support immediately as this should no longer occur.
​

If you need assistance with VOB submissions or EMR integrations, please contact our support team for additional help.