Web Portal - Enrollment

1. The patient creates an account in mscripts pharmacy application in one of the following ways
   • Register a new account on the client portal page and choose a widget (eg menu option, button) to access mscripts. The Identity Provider (IDP) is updated with patient profile and then IDP initiates the SAML form post to mscripts.
   • An alternative route is that patient first goes to mscripts login/home page and selects the sign-in button.  In this case they are redirected to a client portal page along with a Relay State value which is sent back to mscripts in the SAML assertion form post. 
2. If all required data is provided in the SAML assertion form, including unique Email, Mobile #, First Name, Last, DOB and Rx#, the patient account is created. If any of the required data is missing then a 'step-up' page is displayed for data entry.  mscripts requires a combination of First Name, Last Name, Date of Birth and Prescription # to lookup and uniquely identify the patient in the dispensing system.
3. Once patient is successfully identified the mscripts prescriptions landing page is displayed. 

Standard flow for a new patient account creation

Web Portal - Login

1. The patient logs into an account in mscripts pharmacy application in one of the following ways
   • Logs into the client portal page and choose a widget (eg menu option, button) to access mscripts. The Identity Provider (IDP) is updated with patient profile and then IDP initiates the SAML form post to mscripts.
   • An alternative route is that patient first goes to mscripts login/home page and selects the sign-in button.  In this case they are redirected to a client portal page along with a Relay State value which is sent back to mscripts in the SAML assertion form post. 
2. The patient SSO identifier is looked up in mscripts, if patient is successfully identified the mscripts prescriptions landing page is displayed.

Standard flow for patient login

Mobile - Enrollment

1. The patient downloads the mscripts app from the stores (Itunes for IOS or Google Play for Android).
2. The patient then opens the mscripts app and is presented with IDP account creation page inside of a webview. After creating account the IDP initiates the SAML form post to mscripts.
3. If all the required data is provided in the SAML assertion form, including unique Email, Mobile #, First Name, Last, DOB and Rx#, the patient account is created.  If any of the required data is missing then a 'step-up' page is displayed for data entry. mscripts requires a combination of First Name, Last Name, Date of Birth and Prescription # to lookup and uniquely identify the patient in the dispensing system.
4. Once patient is successfully identified mscripts redirects to the landing page.

Standard flow for new patient account creation with mscripts standalone app

Mobile - Login

1. The patient open the mscripts pharmacy app and is presented with IDP account login page inside of a webview. After creating account the IDP initiates the SAML form post to mscripts.
2. An API call is made to the Identity Provider (IDP) for patient verification using SSO identifier and a lookup is made to dispensing system for a match. If patient is successfully identified the mscripts prescriptions landing page is displayed.

Standard flow for patient login on mscripts standalone app

Logout Flow

Logout is implemented by clearing cache/session.  mscripts redirects to a logout URL provided by the client upon which the session on the clients side is cleared

Password Change and Recovery

Password is administered on client side.  

Biometrics 

Biometric with SSO is not supported

App-in-App

Mscripts embeddable pharmacy application (or App in App) is a new product offering wherein we offer the clients an option to embed our web-based pharmacy application within their parent application.

In addition to the normal web pharmacy functionalities, additional integration points are provided such as device location settings, use device camera to refill by scan or to transfer using photos, use parent app’s store locator and use device tokens to enable push notifications.

The mobile flows enrollment and login flows are primarily affected as patient will enter mscripts via the parent client app and as such we will not publish any mobile apps to Apple or Google stores.