Healthcare · Scale & integration

Scaling technology with a
growing care network.

A secure, standardized technology foundation that grew from one office to nearly 20 locations while supporting acquisitions, mobile clinical work, and uninterrupted patient care.

Selected prior experienceTechnology leadership + infrastructure architecture
Experience note: This case study reflects work led by bluealpha founder Randall Johnson in a previous healthcare technology leadership role. The organization is generalized and the work is not represented as a bluealpha client engagement.
20locations supported at scale
700+clinicians enabled
1,000+managed clinical devices
99.9%service availability
01 · Context

Healthcare growth made technology mission-critical.

A homecare startup expanded rapidly across Indiana through organic growth and the acquisition of more than ten agencies. What began as technology for a single office needed to become a dependable shared platform for nearly 20 locations, more than 700 clinicians, and a workforce delivering care in the field.

Availability and security were directly connected to clinical operations. The technology foundation had to scale quickly without creating fragmented identity, communications, support, or protected-health-information practices at every new location.

02 · Challenge

Standardize a changing organization without disrupting care.

  • New offices and acquired agencies arrived with different systems, devices, networks, and processes.
  • Clinicians needed secure access and dependable mobile technology outside traditional office boundaries.
  • HIPAA-aligned controls had to remain consistent during rapid expansion.
  • Small infrastructure failures could interrupt scheduling, communications, and care delivery.
  • Capital investment needed to scale more efficiently than the physical footprint.
03 · Decisions

Create one foundation that could absorb change.

01

Centralize core services

Consolidate identity, infrastructure, communications, storage, and support around standardized enterprise services.

02

Design for distributed care

Use secure Cisco LAN/WAN and VPN patterns to connect offices and mobile clinical operations consistently.

03

Manage the endpoint lifecycle

Introduce enterprise mobility management to enforce policy and support more than 1,000 clinical devices.

04

Integrate acquisitions deliberately

Use repeatable identity, data, endpoint, communications, and support patterns for every acquired agency.

04 · Delivery

The platform grew in step with the organization.

Private-cloud and network foundation

A VMware-based private cloud, centralized Windows and identity services, and a resilient Cisco network created the shared infrastructure required for distributed operations.

Secure mobility

AirWatch enterprise mobility management standardized configuration, security, and support across more than 1,000 clinical devices—extending governance to work performed in homes and community settings.

Acquisition integration

More than ten acquired agencies were brought onto common identity, data, endpoint, communications, and infrastructure services. Repeatable integration reduced variation while local teams continued serving patients.

Operational discipline

Monitoring, backup, support, and lifecycle practices improved reliability and gave the growing organization a consistent way to manage technology risk.

The architecture succeeded because it treated every new location and acquisition as an extension of one operating model—not another isolated technology stack.
05 · Outcomes

A stable platform supported statewide growth.

  • Scaled technology operations from one office to nearly 20 locations and more than 700 clinicians.
  • Maintained 99.9% availability while the organization expanded rapidly.
  • Managed 1,000+ clinical mobile devices with consistent security and support controls.
  • Integrated systems and operations across more than ten acquired agencies.
  • Reduced data-center-related capital expense by approximately 50% through consolidation and virtualization.
  • Maintained HIPAA-aligned operations throughout growth and integration.
06 · Lessons

Scale depends on repeatability.

  1. Standard patterns make growth faster only when they include operations and support—not architecture alone.
  2. Endpoint and identity strategy matter as much as infrastructure in a distributed workforce.
  3. Acquisition integration works best with a defined playbook, clear ownership, and an explicit continuity plan.

Scaling a distributed or regulated organization?

We can help create the architecture and operating model that lets growth happen without multiplying risk and complexity.

Talk through the challenge