For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
SandboxDashboard
DocumentationAPI ReferenceChangelog
  • Getting Started
    • Overview
    • API Client
      • Installation
      • Setup
      • Payer Autocomplete
      • Eligibility Input
      • Soft Check
      • Hard Check
      • Existing Patients
      • Analytics
  • Concepts
    • Eligibility
    • Providers
    • Patients
    • Notes
    • Services
    • Revalidation
    • Consent
  • Eligibility
    • Soft Eligibility
    • Hard Eligibility
    • Policy Errors
    • Conditional Patient Responsibility
  • Guides
    • Enrollment Status
    • Monitoring Payer Health
    • Webhook Behavior
  • Integrations
LogoLogo
SandboxDashboard
Getting StartedReact SDK

Existing Patients

Was this page helpful?
Previous

Analytics

Next
Built with

Existing Patients (who have a Policy associated), do not need to resolve their policy with a payer again. This check can be done using the same functions and hooks available in the full hard check process.

This guide assumes familiarity with the full new patient hard check, and describes the differences.

1

Create a Session

When creating the Hard Eligibility Session, include the Policy ID value.

1createHardEligibilitySession({
2  policyId: "pol_xxx",
3  serviceTypeIds: ["svt_xxx"],
4})
2

Form Input

The existing Policy already contains patient information, so the only input required for the eligibility check is the state.

If the UI has a component for the patient to select it, drive it in the same way as the full check.

If the UI does not have a component, and the value is already known, pass the value as the 2nd argument in the field hook.

1useEligibilityInputField("state", "CA")

Patients may travel, and best practice is to confirm their location before each visit to comply with licensing requirements.

3

Handling the Result

When a Policy is provided upfront, several steps and possible error-states are bypassed. The final resulting object is the same shape as with a new user check.