Endpoint Overview

/v1/eligibility/search

Supported Methods: POST

The RTE /search endpoint is used for the initial onboarding search to check if a patient is eligible for 98point6 services. This endpoint uses patient information to match partner data to eligibility records at 98point6.

Two types of checks are performed against this endpoint:

• Preliminary Search: The request contains firstName, lastName, and birthDate only. The response should only contain matchFound and canDisambiguate, indicating whether a final search is needed. No actual member data should be sent back (i.e. the members array should be empty). Because no patient information is being exchanged at this stage, we recommend partners use generous/fuzzy matching on the name fields (i.e. disregarding hyphenation, suffixes, etc) to identify candidate matches.

• Final Search: The request contains firstName, lastName, birthDate and at least one confirmation field (last4Ssn, email, memberId). The response should contain member information (including dependents) assuming there is an exact match. Depending on the uniqueness of the confirmation field, implementing partners may want to continue using fuzzy matching on the name fields, as long as the DOB and confirmation field are exact matches.

Required Arguments: firstName, lastName, birthDate

Optional Arguments: last4Ssn, email, memberId

/v1/eligibility/check

Supported Methods: POST

The RTE /check endpoint is used for follow-up checks to confirm that a patient is still eligible for coverage after they have onboarded. This endpoint does not require sending any patient personal information and should be used once a patient’s memberId has been returned from a search result.

The /check endpoint should return the same response as the /search endpoint.

Required Arguments: memberId