PrecisionCare Case Study

Overview

PrecisionCare is a cutting-edge medical research company specializing in personalized treatment plans. They have their main office in Boston.

Existing Environment: Technical Environment

PrecisionCare's on-premises network contains a single Active Directory domain named precisioncare.com. PrecisionCare has a single Azure subscription.

Existing Environment: Business Partnerships

PrecisionCare has a business partnership with GenomeTech, Inc. GenomeTech users access some PrecisionCare applications over the internet using Azure Active Directory (Azure AD) guest accounts.

Requirements: Planned Changes

PrecisionCare plans to deploy two applications named PatientTrack and GenomeAnalyzer to Azure.

Requirements: PatientTrack

• PatientTrack will be a Python web app hosted in Azure App Service that requires a Linux runtime. Users from PrecisionCare and GenomeTech will access PatientTrack.
• PatientTrack will access several services that require third-party credentials and access strings. The credentials and access strings are stored in Azure Key Vault.
• PatientTrack will have six instances: three in the East US Azure region and three in the West Europe Azure region.
• PatientTrack has the following data requirements:
  • Each instance will write patient data to a data store in the same availability zone as the instance.
  • Patient data written by any PatientTrack instance must be visible to all PatientTrack instances.
• PatientTrack will only be accessible from the internet. PatientTrack has the following connection requirements:
  • Connections to PatientTrack must pass through a web application firewall (WAF).
  • Connections to PatientTrack must be active-active load balanced between instances.
  • All connections to PatientTrack from North America must be directed to the East US region. All other connections must be directed to the West Europe region.
• Every hour, you will run a maintenance task by invoking a PowerShell script that copies patient files from all the PatientTrack instances. The PowerShell script will run from a central location.