Help with Eligibility checks and private-pay fallback
This page focuses on the guide you were reading. Work through the relevant checks below, then send us a question if the issue is still unresolved.
Missing access may be expected. Check its rollout status before treating the absence of a control as a technical fault. Do not submit real protected health information.
Start with your eligibility checks and private-pay fallback setup
These are checks drawn from this feature's own instructions.
- An eligibility response is not a guarantee of payment.
- Coverage checks and 24-hour rechecks are not approved for live use.
Common problems in RL Health
Choose the problem closest to what you are seeing. Each one includes practical checks and a safe next step.
A clinical feature described here is unavailable
- Check the article's development status before assuming the feature has shipped.
- Confirm your organization has been approved for a protected clinical workspace.
- Use only fictional records in any current QA or demonstration environment.
A clinical workflow seems to cross into regular RoveLogics
- Keep charts, notes, patient identifiers, and protected documents within the separate clinical boundary.
- Confirm the planned handoff does not disclose identifying clinical details.
- Report the workflow concept without attaching real medical information.
Still not resolved?
When you contact support, tell us what you expected, what happened instead, the non-sensitive error text (if any), and roughly when it occurred. The form will automatically include Eligibility checks and private-pay fallback as the topic.
Please do not include passwords, security codes, payment card details, client health records, or any other sensitive information.