Skip to content

microsoft/Health-AI-Blueprints-TA4HVisualizer

Repository files navigation

Health-AI-Blueprints-TA4HVisualizer

Goal

Utilize the Visualizer tool to extract insights from unstructured medical text. Healthcare providers can use it to answer the following questions:

  • Patients diagnosed with X are typically treated with Y
  • The top 5 symptoms our doctors treat with medication X
  • What percentage of women are diagnosed with X, Y and have symptoms Z or W?
  • The three most common pathways for patients diagnosed with X 3 months before being treated by Y
  • What are the most common examinations and what are their medical codes?

Dashboard

Sample Dashboard

High Level Architecture

Architecture

Deployment

Steps at high level:

1. Deploy "Green path" pipeline (step 1):
Deploy to Azure
(Deploys required Azure Resources: Web App, Storage Account, Function App, Text Analytics for Health and Health Data Services)

2. Complete "Green path" pipeline (step 2):

Before running Armed Template:
a. Go to "Azure Active Directory"
b. Click App registrations
c. Create new registration
d. Create new secret and copy its value
e. Add "Fhir Contributor" Role for created "App regestration" in "ta4h Fhir Service" resource

Run Armed Template:
Deploy to Azure
That will open https://raw.githubusercontent.com/microsoft/healthcare-apis-samples/main/src/templates/importer.json taken from open source https://github.com/microsoft/healthcare-apis-samples/tree/main/src/FhirImporter

After running Armed Template:
a. Go to new created function.
b. Open configuration
c. Change value of AzureWebJobsStorage to a connection string taken from storage "fhirstorageXXX"
d. Press Save and wait for approval

3. "Yellow path" pipeline (optional):
a. https://github.com/microsoft/FHIR-Analytics-Pipelines/blob/main/FhirToDataLake/docs/Deployment.md
(Moves FHIR server data to Azure Data-Lake to perform analytics and ML)
b. Create report using this tutorial: https://docs.microsoft.com/en-us/azure/synapse-analytics/get-started-visualize-power-bi

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.