SSO

To use Platform SSO, partner’s must first create a patient in the EMR, then create a patient account in the consult service. This patient account is what is used to authenticate to the appropriate white label path.

1. Links will automatically expire 5 minutes after they are first used
2. An unused link will be valid for 10 days.
3. When redirected to the white label, the patient is placed in the appropriate place in the white label with no action needed from the partner.
   1. NPA
   2. Select State
   3. Visits
4. If a partner is using SSO, the patient profile section of the white label will be hidden to prevent patients from updating their information in the white labeled platform

Patient Requirements

1. Authenticating a patient to the white label requires the patient to have a unique, valid email address that is not validated by the partner API. If an email is a duplicate or invalid, the patient will see a generic error page for the partnership prompting them to contact support.
2. Partners should only pass patients through sso in the appropriate age range agreed upon for the partnership. If a patient outside of the allowed age range submits a visit request, it will be automatically rejected and the patient will be refunded.

Partner Requirements

1. Partner’s need to provide the login URL for the white label. This link should allow the patient to authenticate to the partner platform and easily redirected into the SteadyMD patient experience. SteadyMD will be used in the following use cases.
   1. To include in our patient sms and email notifications that prompt them to go to their patient portal.
   2. When the patient’s session expires
   3. When the patient selects Logout in the menu

UTM Parameter Tracking & Reporting

SteadyMD can track which UTM source, medium, and campaign patients come from to help determine which marketing efforts are most effective. These analytics are available for patients registering through the SteadyMD white label experience as well as patients coming through SSO.

UTM for SSO

Generate a login link and append custom querystring values. e.g. http://partner-api-gateway/v1/p/34TSqH6cAXgNmFNuwvPbVa?utm_source=test_source&utm_campaign=test_campaign&utm_medium=test_medium&custom1=value1

When the Partner Api redirects to the Fenix landing page then the Fenix landing url should include the UTM parameters in addition to the decrypted payload. Non-UTM parameters are filtered out. e.g. http://fenix/external/land?d=decryptedvalue…&utm_source=test_source&utm_campaign=test_campaign&utm_medium=test_medium