The following diagram shows the key relationships between the member, subscriber and policy classes that are used to drive the member match, validations, and policy selection logic.

The member data model includes the support for multiple other identifiers, known as the “Member keyring”.

Example ID’s:

• Pega Subscriber
• Pega Member
• Medicaid
• Medicare

All the ID’s associated to a unique member are maintained as a list in the other information section. The Type is configurable and can be repeated within a member keyring.

Search and match logic with Elastic Search can utilize the keyring IDs along with member demographic information to identify the correct member. The search will yield all members associated with the submitted ID. Results are then filtered by date of service. SCE can be configured to select the submitted policy, internally ranked policy, or externally ranked policy based on the desired outcome.

Alternatively, customers can customize the selection process to apply the preferred member ID based on specific business logic.

There are multiple pages that are used to provide information for the member match, validations, and policy selection. These pages will need to be populated for the SCE to perform the necessary lookups and validations.

• Member match frequently used terms