Data problem

Candid::Errors::ClientError

{"errorName":"HttpRequestValidationError","errorInstanceId":"<secret>","content":{"fieldName":"organization_name","humanReadableMessage":"Either organization_name or first + last name must be set"}}

FailedCandidClaimResubmissionJob@billing463 events · 0 users first seen 105 d agolast seen 9 h ago

In one line

Candid rejected a claim because a provider on it has neither an organization name nor first and last name, and this comes from provider data in Candid.

Checked against the code

What happened

Candid rejected the encounter with a validation error: either organization_name or first + last name must be set.
The mapper builds the billing provider and rendering provider from live Candid provider records, and drops any blank fields with .compact.
A provider record with no organization_name, or with no first/last name, therefore goes out without a name.
1181 events over 105 days is a steady trickle that repeats on retries, which fits a few specific bad provider records. A code bug on every claim would produce far more events.

What to do next

Check In the Candid dashboard, open the provider for the program's claims_billing_provider_uuid and the rendering NPIs on the failing entries. Fill in organization_name, or first and last name, wherever it is missing.
Query Lists the rendering NPIs in use, so you can spot one that is an organization or has no individual name. Check the table and column names against db/schema.rb first, because they were not verified.
```
SELECT rendering_provider_npi, COUNT(*) FROM billing_items GROUP BY rendering_provider_npi ORDER BY 2 DESC;
```

Queries are shown, never run. Check them before using them on production.

Ask a follow-up

Continues the same session, so it still remembers the error and the code it read.

Analysed 1 h ago · claude-sonnet-5-5 · $0.04