Latest EHR Healthcare Case Study (2024) - Google Cloud (GCP) Architect

Company overview

EHR Healthcare is a leading provider of medical electronic health record software. Multinational medical offices, hospitals, and insurance carriers use EHR Healthcare's software as a service. Key focus of this case study is Cloud Architecture for on-premises to cloud migration and scalability issues.

This case study has been around for a while and was recently modified on May 1, 2021 to coincide with the latest version of the Architect certificate exam. Let's discuss understand and analyze this case study

you can refer the case study document at : https://services.google.com/fh/files/blogs/master_case_study_ehr_healthcare.pdf

• Provides software as a service to multi-national medical offices, hospitals, and insurance companies
• Provides electronic health record software to the medical business
• Year after year, EHR Healthcare's revenue has increased dramatically.
• Environments must be scaled, disaster recovery plans must be modified, and new CD capabilities must be implemented.
• They've decided to replace their current colocation facilities with Google Cloud.

Current State

• Multiple colocation facilities are available. One of the data centers leases is ready to expire
• Web-based applications, many of which run on a cluster of Kubernetes nodes.
• MySQL, MS SQL Server, Redis, and MongoDB are used to store data.
• On-premises, EHR hosts many old file and API-based insurance provider connections. (to be replaced over the next few years)
• Monitoring is done with open source software, and email alerts are frequently disregarded.

Business requirements

Their requirements are:

• As rapidly as feasible, onboard additional insurance providers.
• Ensure that all customer-facing systems are available at least 99.9% of the time.
• Provide consolidated visibility into system performance and utilisation, as well as preventive action.
• Enhance your ability to provide healthcare trend analysis.
• All clients latency will be reduced.
• Comply with all regulations.
• Lower the cost of infrastructure administration.
• Use provider data to make predictions and publish reports about industry trends.

Technical requirements

• Maintain historical insurance provider interfaces with connectivity to both on-premises and cloud-based systems.
• Provide an uniform way to manage container-based customer-facing apps.
• Establish a reliable and secure link between on-premises systems and Google Cloud.
• Provide logging, log retention, monitoring, and alerting features that are consistent.
• Managing and maintaining various container-based environments is a must.
• Scale and provision new environments in real time.
• Develop user interfaces for ingesting and processing data from new sources.

Possible Architecture Solution

For building a hybrid cloud Platform solution we can consider below major components here :

• Anthos : Anthos will help to manage both cloud and On-prem
• Database : Cloud SQL, Memorystore(instead of Redis) and Datastore (instead of Mango DB)
• Cloud Storage Log Retention
• Batch : Cloud Storage > Dataflow > BigQuery - Make predictions and generate reports on industry trends
• Streaming : Pub/Sub > Dataflow > BigQuery
• Cloud CDN : Reduced latency
• CI/CD : Container Registry, Cloud Build, Kubernetes Engine

Reference Architecture Solution diagram

There will be multiple possible solutions for this use case, to understand the implementation better we have give reference architecture which is one of possible solution
Below reference architecture depicts different aspect of Gaming Analytics cloud Platform solution like gaming server on GKE, Batch and stream pipeline and common cross cutting infrastructure components :