To setup the Healthcare capabilities that spans the Microsoft Clouds, the following pre-requisites are required.
The table below summarizes the licenses you may require depending on the Healthcare scenarios you want to deploy. See specific requirements in the respective documentation and implementation guide for each scenario.
| Product name |
|---|
| Microsoft Cloud for Healthcare |
| Digital Messaging add-in for Dynamics 365 Customer service |
| Dynamics 365 Customer Service Enterprise |
| Dynamics 365 Marketing |
| Power BI Pro |
| Power Apps for Dynamics 365 |
| Dynamics 365 Field Service |
| Sales Insights Add-in for Dynamics 365 Sales |
| Dynamics 365 Sales Enterprise |
| Microsoft Teams |
Healthcare APIs require a subscription (landing zone) in Azure that will host the Healthcare APIs to enable FHIR to integrate with the Healthcare applications.
Prescriptive guidance for Azure landing zone and reference implementation
Use this reference implementation to deploy Healthcare APIs into your landing zone, which follows best practices and alignes with the proven recommendations. Additional configuration and enhancement can be made per your requirements.
Healthcare requires Power Platform environments (recommendation is dedicated environments for test, development, and production) that are created into the target region with Dataverse and D365 applications enabled.
Prescriptive guidance and design recommendations for Power Platform for Healthcare
Teams is used for many of the healthcare capabilities, such as care management and collaboration.
Prescriptive guidance and design recommendations for Microsoft Teams for Healthcare