Hard Check

Refer to the Hard Eligibility page for a detailed explanation of what’s happening during this process.

Running a successful eligibility request for a new patient is the most complex integration touch point. Bridge manages the lifecycle of the hard eligibility check and implements best-practice recommendations around failures, retries, and conversion optimization.

For advanced use cases (optimistic soft check, multiple provider types, conditional patient responsibility), see Advanced.

See Existing Patients for patients who already have a Policy, scheduling follow-up visits

Result

1interface HardEligibilitySessionState {
2 status: HardEligibilitySessionStatus;
3 args?: HardEligibilitySubmissionArgs;
4 nextAction?: HardEligibilitySessionAction;
5 error?: HardEligibilityError;
6 policy?: Policy;
7 serviceEligibility?: Record<ServiceTypeId, ServiceEligibility>;
8 patientResponsibility?: HardEligibilityPatientResponsibility;
9 providers?: Provider[];
10 ineligibilityReason?: IneligibilityReason;
11}
StatusDescription/Action
PENDINGInitial form input, nothing has been submitted
SERVER_ERRORUnknown server error, may be retried
TIMEOUTPayer took too long to respond with the Policy, may be retried
WAITING_FOR_POLICYFirst step of the flow, resolving the Policy, is in progress
POLICY_ERRORPolicy was unable to be resolved, there’s an error reason included
WAITING_FOR_SERVICE_ELIGIBILITYPolicy was resolved, second step is in progress
INELIGIBLEEither the patient’s Policy does not cover this service, or there are no providers eligible
ELIGIBLEThe patient’s Policy covers this, and there are Provider’s available

When the session is in an error state, expect error to be defined:

1interface HardEligibilityError {
2 code: HardEligibilityErrorCode;
3 message: string;
4 retryable: boolean;
5 forceMemberId?: boolean;
6}

Display message to the patient. When you reach INELIGIBLE or ELIGIBLE, redirect the patient to the next step.