Deploy Microsoft Cloud for Healthcare solutions powered by Dynamics 365

Organization administrators can use this article to deploy Microsoft Cloud for Healthcare solutions powered by Dynamics 365. At the end of this deployment process, you'll have one or more of the following healthcare solutions or apps installed in your environment:

During the deployment process, you can configure more capabilities.

Prerequisites

  • You must be a Microsoft Power Platform admin or a tenant admin to deploy the Microsoft Cloud for Healthcare solutions powered by Dynamics 365.

  • You must have licenses for Microsoft Cloud for Healthcare and various Dynamics 365 apps, which depends on the solution to be deployed. If you're missing any licenses, you'll be notified during the deployment process. More information: Licensing

  • Learn more in Compliance in Microsoft Cloud for Healthcare and ensure you use services that match your requirements.

Step 1: Prepare environment

The Dynamics 365 healthcare solutions are deployed to a Microsoft Dataverse environment with a database.

Important

The Dynamics 365 healthcare solutions in Microsoft Cloud for Healthcare can only be deployed to a Microsoft Dataverse environment that is created in one of the following Dataverse regions: Asia, Australia, Canada, Europe, France, Germany, Great Britain, United States. The solutions are only available in the following languages: Dutch, English, French, and German.

We recommend that you select all languages that you want to make available during your first installation. If you want to enable another language after you've already installed, you'll need to contact Support.

If you enable multiple languages and you're using Patient access, you'll need to follow the instructions in Enable multiple-language portal support.

In addition to a Dataverse environment with a database, these are the Dynamics 365 apps and Power Apps features required for deploying the healthcare solutions and capabilities:

Solution Dependencies
Care management No additional dependencies
Home health Dynamics 365 Field Service
Patient service center Dynamics 365 Customer Service
Digital Messaging add-on for Dynamics 365 Customer Service
Patient outreach Dynamics 365 Marketing
Patient access Power Apps portal (Customer self-service)
Dynamics 365 Customer Service
Health assistant License only (Sales Insights Add-in for Dynamics 365 Sales)

Note

The healthcare data model is included in Microsoft Cloud for Healthcare. You can also deploy it as a standalone solution to build your own application.

A Dataverse environment is a prerequisite to using the healthcare data model.

Note

Before installing the Patient access solution, ensure that the target environment has only one portal of Customer self-service type. Otherwise, installing the Patient access solution can lead to unintended behavior and overwrite other portals in the environment. You must also ensure that you don't create additional portals in the target environment after deploying the Patient access solution.

If you don't have a Dataverse environment with a database, you'll need to create one. Though you can choose to create a Dataverse environment while deploying a healthcare solution, we recommend you create it ahead of installing a solution to install the prerequisite Dynamics 365 apps and solutions.

  1. Sign in to Power Platform admin center.

  2. Create a Dataverse environment with a database. More information: Create an environment with a database

    If you're planning to deploy Home health or Patient service center, you must select Yes in the Enable Dynamics 365 apps option and choose appropriately. Dynamics 365 Field Service is required for Home health and Dynamics 365 Customer Service is required for Patient service center.

  3. You can access your environment by using the following URL, https://[myenv].crm.dynamics.com, where [myenv] is the name of your environment.

  4. You can now install other dependencies as mentioned earlier.

Step 2: Deploy healthcare solutions

To deploy the healthcare solution, use the Microsoft Cloud Solution Center.

  1. Sign in to Microsoft Cloud Solution Center. You can also access it by doing one of the following:

    • Select the link in the email you received from Microsoft after buying the Microsoft Cloud for Healthcare license.
    • From the Microsoft 365 admin center, select the Healthcare collection under setup and the action called Enable healthcare solutions powered by Dynamics 365.
  2. In the Microsoft Cloud Solution Center, you can select Support in the left pane to open the Help + Support experience in the Power Platform admin center, where your organization admin can get self-help solutions in real time for their issue.

    On the Home page, select the Microsoft Cloud for Healthcare tile to get started with the deployment, or you can select Solutions > Healthcare in the left pane.

    Deploy the healthcare solution from Microsoft Cloud Solution Center.

  3. On the Microsoft Cloud for Healthcare page, you'll see a list of capabilities.

    Select capability.

    For each capability, you can:

    • Select Quick view to learn more about the component and its dependencies.
    • Select the card to view and deploy solutions.
  4. On the Healthcare solutions page, you'll see a list of available solutions to deploy.

    Select solutions to deploy.

    On this page, you can:

    • Select All in the Filter by capability dropdown to view all available solutions.
    • Select Add all Healthcare solutions to deploy all solutions.
    • Select Quick view to learn more about the component and its dependencies.
    • Select Add to select one or more solutions for deployment.

    For Virtual visits and Azure Healthcare APIs (preview), select Go to setup to visit the Microsoft 365 admin center to continue with the setup. More information: Use the Microsoft 365 admin center for setup

  5. After selecting the required solutions to deploy, select Deploy in the upper-right corner to deploy them.

  6. The Select destination page allows you to select the destination environment for deployment or create an environment.

    • If you already created an environment, select it from the list.
    • Otherwise, select Create new to create an environment using the Power Platform admin center, and then come back to the Solution Center to select it. More information: Create an environment in the Power Platform admin center

    Select destination environment.

  7. Agree to the terms of service, and then select Next.

  8. The Configure dependencies page guides you to install and configure dependencies.

    Note

    The dependencies list will vary for you depending on the solutions you selected to deploy in the earlier step.

    Configure dependencies for your solutions.

    Select Install or Configure for a dependency to view the documentation on how to set it up. Make sure you install the dependency in the same environment where you're running the deployment.

    See Step 1 to check dependencies for each solution.

  9. After you complete the dependency setup, return to the Microsoft Cloud Solution Center and select Recheck dependencies to refresh the Configure dependencies page.

  10. You now have the options to include sample content (in English only) and sample value sets for codeable concepts (in English only).

    Note

    Codeable concepts is a data type in HL7 FHIR to help with tracking information based on a predefined ontology. The sample includes codes for devices and conditions to be used when interacting with a patient, based on the HL7 FHIR standard. Learn more on the HL7 FHIR standard, the values used for [device types] (https://www.hl7.org/fhir/valueset-device-type.html) and conditions

  11. After all the dependent apps have been installed and configured, and you selected any additional components, select Deploy to continue.

    Note

    The solution deployment starts and will continue to run in the background. Depending on the solutions you have selected to install, it might take a while for them to be deployed in your environment. You will receive a notification through email when the deployment has been completed successfully.

  12. After the deployment is complete, links will be available in the Microsoft Cloud Solution Center to launch your solution. There might be some extra steps to finish configuring your solution. Select the View documentation link to learn more about post-deployment configuration or explore our ecosystem for other health applications.

    Solution deployment success.

    For information about post-deployment configuration for each solution, go to Post-deployment configuration for healthcare solutions.

Step 3: Add users and assign security role

To access the healthcare apps you deployed, users in your organization must be assigned the Healthcare User role and other appropriate security roles.

  1. Sign in to the Power Platform admin center.

  2. Select your environment by clicking the environment name, and then select See all under Users.

    Environment details to access users.

  3. On the Users page, add users to your environment and assign them the Healthcare User security role. More information: Add users to an environment

    Also, depending on the solution you deployed, you'll have to assign additional security roles to your user to access the individual apps:

    Solution Security role
    Care management Basic User
    Healthcare User
    Healthcare care plan template administrator (when using care plans)
    FHIR Sync Agent Healthcare User (when using FHIR Sync agent)
    Care Team Member Field Service – Resource
    Healthcare User
    FHIR Sync Agent Healthcare User (when using FHIR Sync agent)
    Home health Field Service - Dispatcher
    Healthcare User
    FHIR Sync Agent Healthcare User (when using FHIR Sync agent)
    Patient service center Basic User
    Customer Service Representative
    Omnichannel Agent/Supervisor
    Healthcare User
    FHIR Sync Agent Healthcare User (when using FHIR Sync agent)
    Patient outreach Marketing Professional – Business
    Event Planner
    Healthcare User
    FHIR Sync Agent Healthcare User (when using FHIR Sync agent)
    Patient access No additional security roles required

Next step

See also