54.0.1Smile Portal

Experimental

54.0.1.1Setup

The Smile Portal requires a "Custom Application Configuration" of the following form:

{
	"apps": [
		{
			"label": "PA admin module 1",
			"group": "Group A",
			"url": "https://host/pa-admin1"
		},
		{
			"label": "Custom module 2",
			"group": "Group B",
			"url": "https://host/pa-admin2"
		}
	],
	"apis": [
		{
			"label": "PA admin module 3",
			"group": "Prior Auth",
			"appType": "PRIOR_AUTH",
			"additionalParameters": {
				"fhirRepo": "https://host/pa-admin3"
			}
		},	
		{
			"label": "Custom module 4",
			"group": "Group C",
			"appType": "ANOTHER_APP",
			"additionalParameters": {
				"key": "value"
			}
		}
	]
}

This is for manually configuring the applications that will appear inside Smile Portal.

• label: Text used for displaying the app on the menu
• group: Used to group menu items together
• url: URL to be used to embed the app in Smile Portal
• appType: Built-in app to be used in Smile Portal
• additionalParameters: Used for custom configuration for the apps
• fhirRepo: The fhir repo that stores the resources

54.0.2Client Creation and Configuration

An OIDC client is also required as part of Smile Portal configuration. Client creation and configuration can be done as follows:

• Under “Users & Authorization” from the Smile CDR's navigation menu, select “OpenID Connect Clients”;
• Select “Add Client” to create a new OIDC Client
• Provide a value for ClientID. Use this same ClientID in the Smile Portal module configuration.
• In the Authorized Grant Types field, select "Authorization Code" and "Refresh Token".
• In the Authorized Redirect URLs field, include the link to the Smile Portal. NOTE: Ensure that the name entered for the Context Path field while configuring the Smile Portal module is correctly reflected. Including the / the end of the URL is important. e.g. https://try.smilecdr.com/smile-portal/
• In the Scopes field, enter the scopes (whitespace separated) that can be requested (e.g. online_access openid profile).