Real-Time Eligibility with Seamless SSO

Use this page if both of the following apply to your integration:

• Eligibility option: Real-Time Eligibility. MD Live verifies your members in real time with a 270/271 eligibility transaction or the Real Time Eligibility API.
• Registration mode: Seamless SSO. No SSO registration page is displayed, so the contact and address attributes are required.

If you use Including Registration instead, see Real-Time Eligibility with Including Registration. For all options, see SAML Attributes.

Attributes

Attribute values are case-insensitive unless marked Case-sensitive. For the supported attribute name formats, see Attribute Name Formats.

Attribute	Requirement	Description	Format and Example
ou	Required	Organization Unit. MD Live issues one ou value for each client landing page. It decides which landing page ineligible members see.	Value issued by MD Live
firstname	Required	Member's legal first name.	Text
lastname	Required	Member's legal last name.	Text
gender	Required	Member's gender.	M or Male for Male F or Female for Female U, N or Non-binary for Non-binary gender
birthdate	Required	Member's birthdate.	DD-MM-YYYY Example: August 12, 1999 is 12-08-1999
subscriberid	Required	Customer ID, Member ID or Subscriber ID. The same ID that is sent in the 270 request to verify the member's real-time eligibility.	Maximum 20 characters
memberid	Optional	GUID / UUID from the client side. It should not change during the lifetime of the account on the client side.	Maximum 36 characters
phone	Required	Member's phone number.	10-digit phone number Example: 8004006354
email	Required	Member's email.	Must be a valid email address Example: test@mdlive.com
address1	Required	Member's address, line 1.	Text
city	Required	Member's address city.	Text
state	Required	Member's address state. Case-sensitive.	2 upper-case state abbreviation Example: FL, NY, CA
zip	Required	Member's address ZIP code.	5-digit ZIP code Example: 33325

Dependent Members

When the member is a dependent, the attributes above describe the dependent. Also send the following attributes about the primary member:

Attribute	Requirement	Description	Format and Example
relationship	Required	Relationship code of the dependent to the primary member. Case-sensitive.	Only Spouse, Child or Other Adult
primaryfirstname	Required	Primary member's legal first name.	Text
primarylastname	Required	Primary member's legal last name.	Text
primarygender	Required	Primary member's gender.	M or Male for Male F or Female for Female U, N or Non-binary for Non-binary gender
primarybirthdate	Required	Primary member's birthdate.	DD-MM-YYYY Example: August 12, 1999 is 12-08-1999
primarysubscriberid	Required	Primary member's Customer ID, Member ID or Subscriber ID. The same ID that is sent in the 270 request to verify real-time eligibility.	Maximum 20 characters