Skip to main content

IQ CPT Code Service Name Limitations with Payer-Specific Billing (IQ)

Overview: Dazos IQ currently cannot assign different service names to the same CPT/Rev code combination across different payers, which can affect billing accuracy and Low Payment calculations.

Why This Matters

Some payers, particularly Medicaid, use the same CPT/Rev code to represent different service types. For example:

  • The same code may be classified as PHP (Partial Hospitalization Program) for one payer

  • The same code may be classified as RTC (Residential Treatment Center) for another payer

This creates setup challenges since IQ requires a single service name per CPT/Rev code combination.


How the System Currently Works

IQ groups claim service types by the service name configured for each CPT code. When you configure a CPT/Rev code in Administration β†’ CPT Codes, that service name applies to all claims using that code, regardless of payer.

Impact on Low Payment Calculations

  • All claims using the same CPT/Rev code are treated as the same service type

  • Claims from different payers are compared against each other incorrectly

  • RTC payments may be compared to PHP contracts (or vice versa)

  • This can result in inaccurate Low Payment flags

Current Limitations

⚠️ No Current Workaround: There is no way to configure payer-specific service names for the same CPT/Rev code combination in the current system.

As a result:

  • The system uses whichever service name is configured in CPT Codes

  • All claims with that code are treated as the same service type

  • Cross-payer payment comparisons will be inaccurate

  • Low Payment detection may flag claims incorrectly

Future Enhancement

Resolving this limitation will require a feature update to support:

  • CPT code configuration by payer

  • Separate service name assignment per payer

  • Updated Low Payment calculation logic for payer-specific service types

πŸ’‘ Tip: If you encounter this situation, document the specific payers and service types affected. This information helps prioritize future feature development requests.

Did this answer your question?