Hard Check
Bridge’s React SDK is in beta! Expect breaking changes, bugs, and missing features. Please talk to us before integrating.
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. Often, the goal is to minimize friction for the patient, while increasing the likelyhood of resolving their policy. Payers are notoriously unreliable, and even those that don’t require Member ID’s, sometimes force us to.
Bridge has a series of API’s that manages the lifecycle of the “hard eligibility check”, and the React SDK packages those up into a clean, single flow. The SDK implements Bridge’s best-practice recommendations around failures, retries, and conversion optimization. The interface for the SDK will remain stable as we release updates that improve these in a way that requires no additional work from you.
There is an example of a full hard eligibility check, implemented with MUI, inside the GitHub repository.
Below is a step-by-step guide on implementing the basic hard eligibility check. For more advanced use cases (such as multiple provider type support, and conditional patient responsibility), see the Advanced section.
Create a Session
Obtain the createHardEligibilityFunction
through the useBridgeSdk
hook.
On first load, create a session, and pass that through into a HardEligibilityProvider
, to child components below.
Form Input
It’s possible that all of the Eligibility Input Fields may be required.
With the useEligibilityInputField
hook, implement each field type.
Drive your “Submit” button with the useHardEligibilitySubmit
hook.
Handling the result
With the useHardEligibilityState
hook, monitor the progress and outcome of the request.
Submission Status
The possible status
values, their meaning and any action to take, are detailed below.
Error Handling
When the session is in any error state, expect the error
object to be defined.
This is mostly information, Bridge will handle allowing a retry, and updating the state of the Member ID input field.
It’s expected that you display the contents of message: string
to the patient.
This is an explanation of what went wrong, or, a specific message returned by the Payer.
Handling the Results
Bridge will handle re-enabling the form, surfacing errors and changing required inputs, based on the response from the Payer.
When a terminal state is reached (INELIGIBLE
or ELIGIBLE
), redirect them to the next step.
Patient Responsibility Estimates
If eligible, the patient responsibility estimate is exposed at patientResponsibility.estimate
. See the conditional patient responsibility page for more on that.
We highly recommend that you refer back to the demo project in GitHub, to see how this functions in practice.