Build custom healthcare solutions using healthcare data solutions in Power Platform

Healthcare data solutions in Power Platform include foundational components designed for reuse and customization to address organizational needs. Built on Power Platform, developers can use the platform tools to extend or modify these components for diverse industry scenarios. These building blocks, combined with other Microsoft applications, provide an enterprise-ready platform that supports a wide range of healthcare scenarios.

Explore components

The following sections outline the major components provided with healthcare data solutions in Power Platform.

Healthcare data model for Dataverse

Healthcare applications often focus on managing healthcare data. The healthcare data model, based on the HL7 FHIR (Fast Healthcare Interoperability Resources) standard, provides a FHIR-aligned relational data model in Dataverse. It ensures compatibility across data-centric solutions and aligns with familiar standards.

The relational model includes a subset of FHIR resources required for Microsoft and partner healthcare applications. Built on Dataverse, you can customize it using the available maker portal tools. To learn how to extend this data model, see Extend the healthcare data model in Dataverse.

Healthcare template applications

Healthcare template applications address common use cases and help you build healthcare apps in Power Platform. They use the healthcare data model for Dataverse. Examples include the care management and unified patient view applications.

You can use these templates as starting points to create targeted solutions. Customize the data model, application definitions, forms, and views without coding, or extend these solutions using plugins, APIs, and Power Apps component framework (PCF) controls.

Dataverse healthcare APIs

Enterprise healthcare systems require interoperability, and aligning with the FHIR standard supports enterprise interoperability needs. Dataverse healthcare APIs enable FHIR bundle processing and ingestion to create or update Dataverse records. They also include a writeback service to create or update data on FHIR services such as Azure Health Data Services.

System administrators can configure the entity and attribute mapping rules for ingestion and writeback. So, you can fully customize these rules if you update the FHIR data model.

Virtual health data tables

If you need interoperability without synchronizing data between systems, you can use virtual health data tables. This custom virtual table provider uses the same custom maps as the Dataverse healthcare APIs to transform FHIR data into Dataverse records.

Unlike the Dataverse healthcare APIs, the custom provider retrieves FHIR data from Azure Health Data Services without persisting it in Dataverse. This approach helps reduce storage costs and simplifies data synchronization.

The FHIRlink connector is a first-party Power Platform FHIR connector that enables direct connectivity with Azure Health Data Services FHIR services, Google™ Cloud Healthcare API, and Epic® on FHIR®. It supports interoperability across different systems.

You can use the FHIRlink connector to build Power Platform canvas apps, Power Automate flows, and Azure Logic Apps. It eliminates the need for manual data synchronization between systems.

Explore industry scenarios

The healthcare industry demands a wide range of solutions for different personas. The building blocks and reusable components included with healthcare data solutions in Power Platform, along with other Microsoft applications, create a robust platform to address various healthcare scenarios.

Personalized care and secure patient access

With the healthcare data model for Dataverse, you can build applications that offer personalized experiences. These applications engage patients in care decisions through secure, individualized encounters that help them stay involved in their health and wellness journey.

You can design a model-driven app to capture Patient and Appointment records, which are part of the healthcare data model for Dataverse tables. Healthcare administrators can manage these records internally. You can also capture and manage extra data elements such as medications, encounters, and observations, all available in the existing data model. Use the Power Pages platform to design and deploy a public portal that provides patients direct access to their health information and appointment scheduling.

To extend this scenario further, you can consider including the following capabilities in the application:

  • Enable provider and location search
  • Allow patients to self-schedule appointments
  • Provide patient access to extended clinical data

For more information on the Power Platform portal capabilities, see Microsoft Power Pages.

Patient engagement and communication

You can use the existing data model, components, and application templates to engage directly with patients within your custom model-driven apps. Solutions such as Microsoft Omnichannel for Customer Service allows you to monitor and manage patient interactions and communications. Engagements can include topics like upcoming appointments or questions about prescribed medications. You can capture all the relevant data within the solution and link it to the central patient record.

For more information on the connectivity and messaging capabilities integrated with Dynamics 365, see Introduction to Omnichannel for Customer Service.

Patient outreach via outbound marketing and journeys

Healthcare teams often need the ability to perform outreach with patients and members. Outreach can include marketing messages and trigger-based journeys that engage patients across multiple touchpoints. Using the healthcare data model for Dataverse, you can integrate with Microsoft Dynamics 365 Customer Insights to implement patient segmentation and campaign management. This approach allows for more targeted engagement with patients based on specific conditions.

By combining healthcare data solutions in Power Platform and Dynamics 365 solutions, you can achieve the following key goals:

  • Engage patients and their family members in patient care decisions with personalized engagement solutions.
  • Provide a personalized healthcare experience to help patients stay informed and involved in their treatment.
  • Enable healthcare providers to communicate efficiently with their patients and communities.
  • Enable providers to use emails, text messages, or both to share healthcare information with specific patient and community member groups.

Key capabilities that you can implement include:

  • Patient segmentation: Provide standard and customizable patient segments to define patient cohorts.
  • Patient engagement campaigns: Create healthcare-specific email campaigns based on patient segments.
  • Event management: Use provider and payor specific event management templates for event administration and registration.

For more information, see:

Schedule and coordinate home visits

Home visits are a critical requirement for many healthcare solutions. Patients unable to attend in-person appointments often rely on caregivers to schedule and deliver in-home care. To coordinate home care effectively, providers need to communicate the right information, at the right time, to the right people.

The healthcare data model for Dataverse includes standard data tables such as Patient (with demographics) and Organizations (with locations). These tables can help manage home visit schedules, notify patients, and give providers access to medical information on the go.

You can deploy the Dynamics 365 Field Service application with the healthcare data model to offer a powerful solution for delivering onsite services to customer locations. The application combines workflow automation, algorithm scheduling, and mobility tools to support remote workers. Providers can schedule appointments for patients based on various factors and access patient information in context. You can also define a guided business process flow to ensure all necessary steps are followed before and after booking an appointment.

Here are some of the key capabilities that you can include in the custom application:

  • Home visit scheduling: Allow care coordinators to schedule home visit appointments and view patient information in context.
  • Provider scheduling: View schedules of care team members and optimize visiting routes.
  • Home visit coordination: Coordinate care and support distinct processes and tasks for home visits.
  • Patient notifications: Notify patients about arrival times and send follow-up patient satisfaction surveys.

You can also integrate Power Pages to provide patients direct access to their appointments, messages, medications, and extended medical record details. For more information, see Overview of Dynamics 365 Field Service.