Share via

Patient Outreach Design Best Practices and Considerations

  • Article

These design best practices and considerations for configuring and extending Patient Outreach to support the pillars of Well-Architected for Microsoft Cloud for Healthcare.

Note

Dynamics 365 Marketing and Dynamics 365 Customer Insights are now Customer Insights - Journeys and Customer Insights - Data. For more information, see Dynamics 365 Customer Insights FAQs

New Customer Insights - Journeys customers receive real-time journeys features only. For more information, see Default real-time journeys installation.

Configuration

  • Ensure user/group mapping for the requisite licenses are done before deploying the solutions to Microsoft Power Platform.
  • The user who deploys and configures the Dynamics 365 Customer Insights - Journeys solution must be Global Admin, Power Platform Admin, Dynamics 365 Admin or have sufficient permissions directly on the target Power Platform environment.
  • The user deploying the Dynamics 365 Customer Insights - Journeys application, must have permissions to register applications in Microsoft Entra ID.
  • Due to technical constraints, the user deploying the Dynamics 365 Customer Insights - Journeys solution must be associated with a Dynamics 365 Customer Insights - Journeys license.
  • For Customers using still outbound marketing, use 'dynamic segments' as it reflects to the latest new, removed or updated contact information. Dynamic segments are not applicable for real-time marketing users.
  • 'Behavioral block' queries are not synced with Dynamics 365 organization database
  • Segments from Customer Insights - Journey are synced with marketing-insights service so your contact and marketing lists are continuously in-sync when the two systems are work together.
  • Marketing-insights service processess changes to segment membership asynchronously, which means you can't predict the order in which changes are processed.
  • Segments must be live before you utilize them within customer journeys.
  • Use Get estimated segment size to get an estimate for the number of contacts that will be included in the segment, so you are aware of the segment size.
  • Use Customer Insights - Journeys segments, based on data residing in Data Lake without having to bring them into Dataverse.
  • Use content setting to setup repositories of standard and required values for email messages.
  • Use peronalization to place dynamic field values. Personalization dialog only shows entities and relations that are synced with marketing-insights service. If you want to see more information or use relations for one or more entities then an Admin has to choose entities to sync with the marketing-insights service.
  • Use personalization to place a dynamic expression.
  • It is highly recommended to use at most two hops (periods) in your field expression.
  • Dynamics 365 Customer Insights - Journeys email sending functionality does not support calculated fields.
  • Use dynamic values to choose an image source or link. Images must be hosted to your own store location. This is because Dynamics 365 Customer Insights - Journeys generates a unique GUID-based file path, so the stored image URL is unpredictable.
  • Make sure to follow guidelines for conditional statements and comparisons.
  • Make sure to check follow latest known issues for Customer-Insights - Journeys.

Customizing and extending Patient outreach

Reliability

  • Test features in a non-prod environment.
  • Design an on-premises data gateway for reliability by including high-available data gateway for on-premise data.
  • Maintain a development, test environment and a production environment.
  • For your Azure components consider the reliability design checklist from Azure Well-Architected Framework.

Security and compliance

  • Privacy features and consent management.
  • Set up security boundaries and provide environments with flexibility for change management.
  • Set up Microsoft Sentinel cloud-based security operations for your solution as is natively integrated with Power Apps logging, Power Automate activity logging Dynamics 365 auditing, Microsoft Entra ID, Microsoft Dataverse and model-driven apps activity logging, Microsoft Teams and other sources.

Cost optimization

  • Use another data store such as Azure Data Lakes and move only needed data to Dataverse. That can decrease the cost in case of high volumes of data. It is recommended to store data in Dataverse for small organizations or those that have significant amounts of data in Dataverse for other applications already.
  • Customer Insights - Journeys quota limits
  • Follow latest Customer Insights - Journeys licensing model

Performance efficiency

  • Marketing-insights service when processing very large databases, it can take up to six hours for a given segment to update so you cannot rely on any one segment being processed before or after a specific other segment, so be careful when orchestrating related campaigns or using.
  • Use Get estimated segment size to get an estimate for the number of contacts that will be included in the segment, so you are aware of the segment size.
  • Service limits and fair use policy for Dynamics 365:
  • Throughput guidance for Dynamics 365 Customer Insights - Journeys.

See also

Next steps