patientOutreach

Patient outreach

Patient outreach is a patient campaign management application that helps organize and automate marketing and outreach to patients. Healthcare providers can communicate with their communities and patients in a targeted, efficient way. Providers can use email, text, regular mail, or a combination, to provide healthcare information to specific groups of patients and community members.

Key capabilities of Patient outreach include:

• Patient segmentation: Prebuilt patient segments to provide baseline patient cohorts.
• Patient engagement campaigns: Create healthcare-specific email campaigns that use prebuilt patient segments.
• Event management: Use provider/payor event management templates for event administration and registration.

Reference implementation	Description	Deploy
Patent Outreach	Patent Outreach for patient campaign management to help organize and automate marketing and outreach to patients.

Prerequisites

Before you deploy and configure, verify you have implemented the prerequisites.

Specifically for patient outreach, you need:

• Power Platform environments
  • Must be created upfront, in United States with Dataverse and D365 Apps enabled
  • D365 application dependencies, such as D365 Marketing

Note: The implementation of the Patient Outreach solution can currently not be automated, and requires manual implementation and configuration across Solution Center, Power Platform Admin Center. See Configure the Dynamics 365 Marketing app for Patient outreach for detailed instructions.

Planning guidelines for Patient Outreach

This section provide prescriptive guidance with design considerations and recommendations across the critical design areas for Patient Outreach for the teams that will deploy and manage the Patient Outreach capabilities within the Microsoft Cloud for Healthcare.

Note: The design areas for Patient Outreach are lightweight as the critical design areas, considerations and recommendations should be addressed in the Power Platform architecture itself. This is primarily because the Patient Outreach scenario and its dependencies are D365 applications that must only be sequenced and deployed into existing environments.

• Identity and access
• Deployment

Identity and access

Design considerations

• The user who deploys and configures the D365 Marketing solution must either be Global Admin, Power Platform Admin, D365 Admin, or have sufficient permissions directly on the dedicated Power Platform environment.
• If you are deploying to an Environment in Power Platform that previously had the Marketing solution deployed, then the Service support admin user must use the same user ID as was used for the initial install. If not, a user with Global Admin, Power Platform Admin, or D365 Admin must deploy it.
• The user deploying the D365 Marketing app must also have permissions to register applications in Azure AD.
• Due to technical constraints, the user deploying the D365 Marketing solution must be associated with a D365 Marketing license.
• To deploy the Patient Outreach solution, the user must have an assigned license for the Healthcare add-on.

Design recommendations

• Ensure user/group mapping for the requisite licenses are done before deploying the solutions to Power Platform.
• Ensure appropriate RBAC is assigned to the Security group for the dedicated Environment for Healthcare in Power Platform, ideally as part of the Environment creation process.
• If privileged access to application registration in Azure AD cannot be granted for the group/users who will deploy and operate the D365 Marketing solution and Patient Outreach scenario, a Global Administrator must assist with the deployment.

Deployment

Design considerations

• Deployment of D365 Marketing solution starts from within the Admin Center of Power Platform, which then will take you to the Dynamics 365 apps admin page to complete the setup.
• Deployment of D365 Marketing solution can take several hours, and puts a write lock on the environment to prevent parallel deployments of solutions.
• There's limited logs and telemetry available during the deployment in case anything fails, hence you should ensure you have reserved enough time to get D365 Marketing app installed successfully as a dependency to the Patient Outreach solution deployment.

Design recommendations

• If Global Administrator permissions are needed to complete the deployment, ensure this is a joint activity in order to troubleshoot and follow-up with support in case D365 Marketing deployment is having issues.
• Deploy D365 Marketing to test, development, and production environment to align with the overall Environment strategy recommendations for Industry solutions in Power Platform.
• Similarly, deploy Patient Outreach (and all other Healthcare solutions) to test, development, and production environments per the above.

---

Back to documentation root