Smile CDR v2024.05.PRE
On this page:

17.4.1Other Configurations
Trial

 

Some additional configurations need to be made to ensure that the appSphere module will function correctly.

17.4.2Configuring NGINX for the Module
Trial

 

A reference for the appSphere module needs to be made in NGINX. The instructions to do this setup is here.

17.4.3Configuring Different Users
Trial

 

Appropriate roles and permissions must be assigned for different users to enable proper functioning of the appSphere.

To begin with, add users by selecting “Users & Authorization” from the header's navigation menu on the landing page of the Smile CDR Web Admin Console. Under “Users & Authorization”, select “User Management” from the dropdown list, select “Add User” to be directed to the page where new user records can be created.

User Manager

17.4.3.0.1Admins

Ensure the following information is added in the respective sections to create a new user record:

Demographics

  • Username
  • Family Name
  • Given Name
  • Email Address

Add User

Roles and Permissions

Toggle to “Yes” to ensure the following permissions are appropriately assigned:

  • Permission. "ACCESS_ADMIN_JSON"
  • Permission. "AG_ADMIN_CONSOLE_READ"
  • Permission. "AG_ADMIN_CONSOLE_WRITE"
  • Permission. "OPENID_CONNECT_ADD_CLIENT"
  • Permission. "OPENID_CONNECT_EDIT_CLIENT"
  • Permission. "OPENID_CONNECT_VIEW_CLIENT_LIST"
  • Permission. ""FHIR_EXTENDED_OPERATION_ON_SERVER"", argument. "$partition-management-list-partitions"
  • Permission. "OIDC_CLIENT_PRESET_PERMISSION", argument. "FHIR_OP_INITIATE_BULK_DATA_EXPORT"
  • Permission. "OIDC_CLIENT_PRESET_PERMISSION", argument. "FHIR_OP_INITIATE_BULK_DATA_EXPORT_GROUP"
  • Permission. "OIDC_CLIENT_PRESET_PERMISSION", argument. "FHIR_OP_INITIATE_BULK_DATA_EXPORT_SYSTEM"
  • Permission. "OIDC_CLIENT_PRESET_PERMISSION", argument. "FHIR_OP_INITIATE_BULK_DATA_EXPORT_PATIENT"

User Permissions

17.4.3.0.2Developers

Ensure the following information is added in the respective sections to create a new user record:

Demographics

  • Username
  • Family Name
  • Given Name
  • Email

Roles and Permissions

Toggle to “Yes” to ensure the following permissions are appropriately assigned:

  • Permission. "ACCESS_ADMIN_JSON"
  • Permission. "AG_DEV_PORTAL_READ"
  • Permission. "AG_DEV_PORTAL_WRITE"
  • Permission. "OPENID_CONNECT_ADD_CLIENT"
  • Permission. "OPENID_CONNECT_EDIT_CLIENT"

After entering the aforementioned information and ensuring that the roles and permissions are appropriately assigned, click "Save". The user records added can be seen in the users table on the “User Manager” page. Select “Modify” from the first column of the users table to make changes to the existing configurations for each user type.

For EHR launch - The practitioner field in the 'Default Launch Contexts' section of user management should have a value. Default launch PRAC ID value

** IMPORTANT NOTE **

If the correct permissions for the developer or admin role are not assigned, then the following error message will be displayed when logging in to the Developer Portal or Admin Console.

Error 403