Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Microsoft is evolving the delivery model for healthcare data solutions in Microsoft Fabric. Beginning August 3, 2026, a downloadable source code and documentation package is available for customers to create customer-managed implementations. Support for the current managed healthcare data solutions in Microsoft Fabric ends on December 31, 2027. Starting October 1, 2026, only existing customers can deploy the current managed solution by using the instructions in this documentation. New customers should use the downloadable package instead. Existing customers can continue using the current managed solution while planning their transition. The complete source code, documentation, and deployment guides for the healthcare data solutions in Microsoft Fabric are now available in the Microsoft Download Center.
Healthcare data solutions in Microsoft Fabric let you analyze Dragon Ambient eXperience (DAX) Copilot raw data using data insights from DAX Copilot. You can ingest and store DAX Copilot artifacts such as transcript data, audio files, and AI summaries in Fabric lakehouses with the DAX Copilot integration with Microsoft Fabric feature. With the DAX Copilot data transformation capability, you can now ingest and transform raw transcript data across different lakehouse levels and structure it for analytics, AI/machine learning modeling, and Power BI visualization. This capability helps healthcare professionals, researchers, and analysts use ambient clinical intelligence for advanced analytics, supporting collaboration, research and development, and AI innovation in healthcare.
DAX Copilot data transformation is an optional capability under healthcare data solutions in Microsoft Fabric. You have the flexibility to decide whether to use it, depending on your specific needs or scenarios.
To learn how to deploy, set up, and use this capability, see:
Conceptual architecture
The DAX Copilot data transformation capability uses the medallion lakehouse architecture explained in Data architecture and management in healthcare data solutions. Here's how this framework organizes and processes DAX Copilot data across the different lakehouse layers:
Landing zone: DAX Copilot data files land in the bronze landing zone. You must first Integrate DAX Copilot with Microsoft Fabric and set up the required configuration as a prerequisite. The files in the landing zone are stored in a complex folder structure that includes a date-based hierarchy and a type-based hierarchy.
Bronze: Also called the raw zone, this layer stores the source conversational data from DAX Copilot. The healthcare#_msft_dax_bronze_ingestion notebook ingests this data into a bronze table called DaxCopilotData. This table stores the DAX file content and metadata.
Silver: In this layer, the healthcare#_msft_dax_silver_ingestion notebook builds the silver model based on the bronze data. DAX Copilot transcripts are stored here in the DAXTranscripts table. This table stores the transformed transcript content for further AI-based enrichments.