Deployment best practices and considerations for Patient Service Center
- You must have a Microsoft account.
- You must be a Microsoft Power Platform admin, Dynamics 365 admin, or a tenant admin.
- You must have licenses for Dynamics 365 Customer Service and Digital Messaging add-on for Dynamics 365 Customer Service.
- You must have an assigned license for the Healthcare add-on.
- If you're missing any licenses, you'll be notified during the deployment process.
- If new licenses are needed for deployment, please wait about 8 hours after purchase for the system to be ready for set-up.
- When setting up your Dataverse environment, you must select Yes for Enable Dynamics 365 apps, and select Dynamics 365 Customer Service solution to deploy into the environment.
- You must provision Omnichannel for Customer Service in the environment before you can deploy Patient Service Center.
- You will deploy the Patient Service Center solution from Microsoft Cloud Solution Center.
- Deployment of D365 solution can take several hours, and puts a write lock on the environment to prevent parallel deployments of solutions.
- Microsoft Cloud Solution Center has limited logs and telemetry available during the deployment in case anything fails. Be sure to reserve enough time to install the applications successfully. To view the deployment status of your solutions, go to your environment in the Microsoft Power Platform admin center. For more information, visit Manage Dynamics 365 apps.
- Sample data can be added when deploying the solution in the solution center, however you cannot remove the sample data from solution center once it's been added.
- If you're deploying the solution for the first time, select the "Configuration Data" option to enjoy an automated configuration process otherwise you will need to do the post deployment configurations as a post-deployment step.
- If you have already deployed the solution with customizations and are performing an update, don't select the "Configuration Data" option as it will overwrite your customizations.
- The solutions in Microsoft Cloud for Healthcare are not multi-geo by design. If data processing laws require that data be preserved in the country/region, a deployment tenant must be created in the geography to ensure that data stored in the services stay within the region. - Check out the regions and languages supported.
- You'll need to assign additional security roles to your users so they can access the individual apps.
- If you enable the Teams collaboration and chat features for any app, it's enabled for all the supported apps.