Overview
This article explains a known issue where remaining deductible and remaining out-of-pocket values returned by pVerify for Aetna policies are not displayed in the Dazos CRM iVerify VOB UI. If you are running an insurance verification for an Aetna policy and only see annual values — but not remaining values — this article applies to you.
Symptom
When running an insurance verification (VOB) for an Aetna policy in the CRM, the results screen displays annual deductible and out-of-pocket values but does not show remaining values, even when those values are present in the pVerify response payload.
Specifically, the following fields are returned by pVerify but are not rendered in the CRM UI:
Remaining Deductible (Individual)
Remaining Deductible (Family)
Remaining Out-of-Pocket (Individual)
Remaining Out-of-Pocket (Family)
Cause
This is a known UI rendering and field mapping issue specific to how Aetna policy responses from pVerify are displayed in the CRM. It is not a data availability issue — pVerify is correctly returning both annual and remaining values at the networkBenefits and healthBenefitSummary levels. The CRM UI is simply not mapping and rendering those remaining value fields.
This issue is not instance-specific. It affects all CRM instances when verifying Aetna policies through iVerify.
What the pVerify Response Includes (But the UI Does Not Show)
The pVerify API returns remaining values in both the Network Benefits and Health Benefit Summary sections. For example:
networkBenefits:
Deductible → Annual: $0.00 | Remaining: $0.00
OutOfPocket → Maximum: $3,750.00 | Remaining: $0.00
healthBenefitSummary:
Family Calendar Year Deductible (In-Network): $3,300.00
Family Remaining Deductible (In-Network): $0.00
Individual Calendar Year Out of Pocket (In-Network): $3,750.00
Family Remaining Out of Pocket (In-Network): $1,611.70
Individual Remaining Out of Pocket (In-Network): $1,690.98
All bolded fields above are present in the pVerify response but are currently not displayed in the CRM UI.
Workaround
There is currently no workaround available within the CRM UI for this issue.
⚠️ Important: This issue has been escalated to the Dazos development team with high priority. Updates will be communicated once a fix is available.
When to Contact Support
You do not need to contact support to report this issue — it is already known and under active investigation. However, please reach out to Dazos Support if:
You need confirmation of the remaining values from the raw pVerify response for a specific patient record.
You are unsure whether your case is related to this known issue or a different VOB problem.
You require an update on the status of the development fix.
💡 Tip: When contacting support, provide the VOB record ID and patient name so the team can review the specific pVerify response and confirm the returned values.