Orchestrate multimodal AI insights within your healthcare data estate (Public Preview)
In today’s healthcare landscape, there is an increasing emphasis on leveraging artificial intelligence (AI) to extract meaningful insights from diverse datasets to improve patient care and drive clinical research. However, incorporating AI into your healthcare data estate often brings significant costs and challenges, especially when dealing with siloed and unstructured data. Healthcare organizations produce and consume data that is not only vast but also varied in format—ranging from structured EHR entries to unstructured clinical notes and imaging data. Traditional methods require manual effort to prepare and harmonize this data for AI, specify the AI output format, set up API calls, store the AI outputs, integrate the AI outputs, and analyze the AI outputs for each AI model or service you decide to use. Orchestrate multimodal AI insights is designed to streamline and scale healthcare AI within your data estate by building off of the data transformations in healthcare data solutions in Microsoft Fabric. This capability provides a framework to generate AI insights by connecting your multimodal healthcare data to an ecosystem of AI services and models and integrating structured AI-generated insights back into your data estate. When you combine these AI-generated insights with the existing healthcare data in your data estate, you can power advanced analytics scenarios for your organization and patient population. Key features: Metadata store lakehouse acts as a central repository for the metadata for AI orchestration to effectively capture and manage enrichment definitions, view definitions, and contextual information for traceability purposes. Execution notebooks define the enrichment view and enrichment definition based on the model configuration and input mappings. They also specify the model processor and transformer. The model processor calls the model API, and the transformer produces the standardized output while saving the output in the bronze lakehouse in the Ingest folder. Transformation pipeline to ingest AI-generated insights through the healthcare data solutions medallion lakehouse layers and persist the insights in an enrichment store within the silver layer. Conceptual architecture: The data transformations in healthcare data solutions in Microsoft Fabric allow you ingest, store, and analyze multimodal data. With the orchestrate multimodal AI insights capability, this standardized data serves as the input for healthcare AI models. The model results are stored in a standardized format and provide new insights from your data. The diagram below shows the flow of integrating AI generated insights into the data estate, starting as raw data in the bronze lakehouse and being transformed to delta tables in the silver lakehouse. This capability simplifies AI integration across modalities for data-driven research and care, currently supporting: Text Analytics for health in Azure AI Language to extract medical entities such as conditions and medications from unstructured clinical notes. This utilizes the data in the DocumentReference FHIR resource. MedImageInsight healthcare AI model in Azure AI Foundry to generate medical image embeddings from imaging data. This model leverages the data in the ImagingStudy FHIR resource. MedImageParse healthcare AI model in Azure AI Foundry to enable segmentation, detection, and recognition from imaging data across numerous object types and imaging modalities. This model uses the data in the ImagingStudy FHIR resource. By using orchestrate multimodal AI insights to leverage the data in healthcare data solutions for these models and integrate the results into the data estate, you can analyze your existing data alongside AI enrichments. This allows you to explore use cases such as creating image segmentations and combining with your existing imaging metadata and clinical data to enable quick insights and disease progression trends for clinical research at the patient level. Get started today! This capability is now available in public preview, and you can use the in-product sample data to test this feature with any of the three models listed above. For more information and to learn how to deploy the capability, please refer to the product documentation. We will dive deeper into more detailed aspects of the capability, such as the enrichment store and custom AI use cases, in upcoming blogs. Medical device disclaimer: Microsoft products and services (1) are not designed, intended or made available as a medical device, and (2) are not designed or intended to be a substitute for professional medical advice, diagnosis, treatment, or judgment and should not be used to replace or as a substitute for professional medical advice, diagnosis, treatment, or judgment. Customers/partners are responsible for ensuring solutions comply with applicable laws and regulations. FHIR® is the registered trademark of HL7 and is used with permission of HL7.
How to Getting Started with Intune: SOE Deployment, CIS Compliance, and Device Upgrades
We are planning to use Intune as our endpoint management tool and need guidance to get started. Our environment consists of: Windows 10/Windows 11 Professional devices Some Windows 10 Home Edition devices macOS devices Questions: Where should we begin? My initial plan is to upgrade the Windows 10 Home devices to Windows 11 Professional. How can we deploy a Standard Operating Environment (SOE) using Intune? We need to comply with CIS benchmarks. Considering the numerous configurations required, configuring everything manually via device profiles seems time-consuming. Is it possible to use a pre-configured image and deploy it through Intune? Your guidance and suggestions will be greatly appreciated!Using FFU Imaging; after Optimize-FFU it no longer works
Hi, I installed a fresh copy of Windows Home v21H1. In audit mode, I ran installed all the Windows Updates and then ran System Prep with "System Cleanup Action > Enter System Audit mode" and shutdown the system. I then booted to WinPE and was able to successfully capture an FFU image to a network share. I was also able to successfully deploy this image to another machine with a larger SSD. However, anything with a small drive won't work so I ran the 'Optimize-FFU' command from the Deployment and Imaging Tools command prompt on my sever which hosts the network share and that process went through successfully. My understanding is that this modifies the image so that it will work on small drive sizes. My issue is that AFTER running this 'Optimize-FFU' the image will not deploy on ANY machines. When I try to deploy the 'optimized' image to the same machines the original image worked or any other machine on I get an error: 0x8000ffff ANY IDEAS? 2021-09-05 13:56:54, Info DISM PID=1488 TID=1464 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir 2021-09-05 13:56:54, Info DISM PID=1488 TID=1464 DismCore.dll version: 10.0.22000.1 - CDISMManager::FinalConstruct 2021-09-05 13:56:54, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log 2021-09-05 13:56:54, Info DISM PID=1488 TID=1464 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession 2021-09-05 13:56:54, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log 2021-09-05 13:56:54, Info DISM DISM Provider Store: PID=1488 TID=1464 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2021-09-05 13:56:54, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log 2021-09-05 13:56:54, Info DISM DISM Manager: PID=1488 TID=1464 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2021-09-05 13:56:54, Info DISM DISM.EXE: 2021-09-05 13:56:54, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2021-09-05 13:56:54, Info DISM DISM.EXE: 2021-09-05 13:56:54, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22000, Running architecture=amd64, Number of processors=4 2021-09-05 13:56:54, Info DISM DISM.EXE: Dism.exe version: 10.0.22000.1 2021-09-05 13:56:54, Info DISM DISM.EXE: Executing command line: dism /apply-ffu /ImageFile=W:\Win10-9-5-21.ffu /ApplyDrive:\\.\PhysicalDrive0 2021-09-05 13:56:54, Error DISM DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008. 2021-09-05 13:56:54, Info DISM DISM FFU Provider: -------- Security Header ---------------------------------- 2021-09-05 13:56:54, Info DISM DISM FFU Provider: Size = 32 2021-09-05 13:56:54, Info DISM DISM FFU Provider: Signature = SignedImage 2021-09-05 13:56:54, Info DISM DISM FFU Provider: ChunkSizeInKB = 128 2021-09-05 13:56:54, Info DISM DISM FFU Provider: AlgorithmId = 32780 2021-09-05 13:56:54, Info DISM DISM FFU Provider: CatalogSize = 328 2021-09-05 13:56:54, Info DISM DISM FFU Provider: HashTableSize = 5505024 2021-09-05 13:56:54, Info DISM DISM FFU Provider: ----------- Image Header ---------------------------------- 2021-09-05 13:56:54, Info DISM DISM FFU Provider: Size = 24 2021-09-05 13:56:54, Info DISM DISM FFU Provider: Signature = ImageFlash 2021-09-05 13:56:54, Info DISM DISM FFU Provider: ManifestLength = 1723 2021-09-05 13:56:54, Info DISM DISM FFU Provider: ChunkSize = 128 2021-09-05 13:56:54, Info DISM DISM FFU Provider: ----------- Store Header ---------------------------------- 2021-09-05 13:56:54, Info DISM DISM FFU Provider: UpdateType = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: MajorVersion = 1 2021-09-05 13:56:54, Info DISM DISM FFU Provider: MinorVersion = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: FullFlashMajorVersion = 3 2021-09-05 13:56:54, Info DISM DISM FFU Provider: FullFlashMinorVersion = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: PlatformId = 2021-09-05 13:56:54, Info DISM DISM FFU Provider: BlockSize = 131072 2021-09-05 13:56:54, Info DISM DISM FFU Provider: WriteDescriptorCount = 172004 2021-09-05 13:56:54, Info DISM DISM FFU Provider: WriteDescriptorLength = 3440080 2021-09-05 13:56:54, Info DISM DISM FFU Provider: ValidateDescriptorCount = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: ValidateDescriptorLength = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: InitialTableIndex = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: InitialTableCount = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: FlashOnlyTableIndex = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: FlashOnlyTableCount = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: FinalTableIndex = 0 2021-09-05 13:56:54, Info DISM DISM FFU Provider: FinalTableCount = 172004 2021-09-05 13:56:54, Info DISM DISM FFU Provider: CompressionAlgorithm = 3 2021-09-05 13:56:55, Info DISM DISM FFU Provider: Anti-theft feature is not supported on this machine. 2021-09-05 13:56:55, Error DISM DISM FFU Provider: (Partition) Name is not present in manifest. 2021-09-05 13:56:55, Error DISM DISM FFU Provider: CManifest::GetDriveLayoutInfoEx#788 failed with 0x8000ffff. 2021-09-05 13:56:55, Error DISM DISM FFU Provider: CFfuReader::ProcessWriteDescriptors#1260 failed with 0x8000ffff. 2021-09-05 13:56:55, Error DISM DISM FFU Provider: CFfuReader::PreApply#303 failed with 0x8000ffff. 2021-09-05 13:56:55, Error DISM DISM FFU Provider: FfuApplyInternal#477 failed with 0x8000ffff. 2021-09-05 13:56:55, Error DISM DISM FFU Provider: FfuApplyImage#85 failed with 0x8000ffff. 2021-09-05 13:56:55, Error DISM DISM FFU Provider: PID=1488 TID=1464 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:515 - CFfuManager::Apply(hr:0x8000ffff) 2021-09-05 13:56:55, Error DISM DISM FFU Provider: PID=1488 TID=1464 Failed to apply an FFU image to '\\.\PhysicalDrive0'. - CFfuManager::InternalCmdApply(hr:0x8000ffff) 2021-09-05 13:56:55, Error DISM DISM FFU Provider: PID=1488 TID=1464 "Error executing command" - CFfuManager::InternalExecuteCmd(hr:0x8000ffff) 2021-09-05 13:56:55, Error DISM DISM FFU Provider: PID=1488 TID=1464 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:224 - CFfuManager::ExecuteCmdLine(hr:0x8000ffff) 2021-09-05 13:56:55, Error DISM DISM.EXE: FfuManager processed the command line but failed. HRESULT=8000FFFF 2021-09-05 13:56:55, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2021-09-05 13:56:55, Info DISM DISM.EXE: 2021-09-05 13:56:55, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2021-09-05 13:56:55, Info DISM DISM.EXE:
