SystemView 2 – Infrastructure Summary

Overview

SystemView 2 is an enterprise-grade analytics platform designed to operate across hospital environments. The platform is deployed on your infrastructure, giving you complete control over your data whilst delivering powerful operational intelligence.

Platform performance, stability, and upgrade resilience are directly dependent on compliant infrastructure. This article provides a high-level summary of the infrastructure standards required to support SystemView 2.

For full technical specifications, see: SystemView 2 – Technical Infrastructure Requirements

Architecture Overview

SystemView 2 deploys on Azure infrastructure, integrating with your existing hospital data sources whilst maintaining complete data sovereignty. The following diagram illustrates a typical deployment architecture.

Figure 1: SystemView 2 reference architecture on Microsoft Azure showing key components, network segmentation, and data flow. Your deployment will be tailored during technical planning based on your specific requirements.

Mandatory Deployment Requirements

All SystemView 2 deployments require:

• Four environments: Development, Test, UAT, Production

• Multi-node Kubernetes cluster (minimum 7 nodes per environment)

• CSI-compliant storage with Premium SSD for user-facing and analytics workloads

• Workload isolation for medium and large hospital deployments (≥1000 beds)

Environment Provisioning

For new installations, the Development environment is required first to support initial configuration and integration development. Test, UAT, and Production environments may be provisioned later based on agreed timelines. This phased approach must be discussed during project initiation phase.

Infrastructure Sizing Bands

Infrastructure requirements are based on a typical deployment supporting approximately 1,750 hospital beds across 8 facilities. Your specific requirements will be right-sized during technical planning.

Sizing Methodology

The bed count classifications above provide an initial framework for infrastructure planning. However, bed count is an indicative guide, not a definitive calculator.

Your actual infrastructure requirements depend on factors including facility distribution, concurrent users, data volumes, historical retention periods, reporting complexity, and integration requirements. During technical planning, HealthCare Logic will assess these factors holistically to recommend the appropriate configuration for your environment.

For organisations near classification boundaries (e.g., 950 beds or 5,200 beds), we may recommend the higher tier to ensure performance headroom and accommodate future growth.

Optional AI Insights Module

Progressive Availability: The AI Insights feature is being progressively developed and implemented. Timing and final specifications will be confirmed between all parties once available.

When enabled, AI Insights requires additional GPU resources per environment:

• GPU-enabled node (NVIDIA Tesla T4 with 16GB VRAM)

• Always-on system node for AI services (2 vCPU, 4GB RAM)

• Storage account for large language model hosting

• Linux App Service Plan for API communication (P0v3 or equivalent)

Why This Standard Exists

SystemView 2 processes:

• Near real-time operational data ingestion and refresh

• High-frequency dashboard queries from concurrent users

• Data warehouse aggregation and historical analysis

• Analytical cube processing for multidimensional analysis

• Optional AI-powered insights and predictions

 

Under-sized or non-compliant infrastructure may result in:

• Slower dashboard performance and query timeouts

• Increased data refresh times affecting real-time visibility

• Platform upgrade instability and extended maintenance windows

• Concurrency bottlenecks during peak operational periods

 

Infrastructure alignment, consistent deployments and repeatable playbooks ensure predictable platform performance and a positive user experience.

Deployments that materially deviate from the supported infrastructure standard may require formal technical review prior to go-live.

Infrastructure alignment is assessed during the project initiation phase. Material deviations are flagged for joint resolution between the customer and HealthCare Logic technical teams to ensure platform performance and stability.

Next Steps

1. Review Technical Requirements

See SystemView 2 – Technical Infrastructure Requirements for detailed specifications, node configurations, storage requirements, and operating system options.

2. Schedule Technical Planning Session

The HealthCare Logic team will coordinate a technical planning session with your IT and infrastructure teams to confirm sizing, deployment configuration, and timeline.

3. Provision Development Environment

For new installations, provision the Development environment first. Additional environments (Test, UAT, Production) can be provisioned according to agreed timelines established during mobilisation planning.

4. Initiate Phase

HealthCare Logic will configure your environment, establish connectivity, validate infrastructure compliance, and prepare for deployment. This phase includes data mapping, integration development, and business requirements capture.