Healthcare IT
Infrastructure

Architected an isolated 4TB on-premise Docker server for medical imaging, and engineered a separate public WordPress platform featuring Google Calendar API real-time scheduling.

Infrastructure Reliability

Architecture Evolution

Modernizing legacy infrastructure into an automated, high-availability ecosystem.

Legacy Operations

Booking: Manual appointment scheduling via phone calls and WhatsApp.
Hosting: Public website hosted on unreliable legacy shared hosting.
Imaging: Massive medical imaging datasets scattered across individual clinic PCs.
Operations: Fragmented corporate email and poor SEO presence.

Modern Ecosystem

Booking: Automated patient slot booking integrated directly with the Google Calendar API.
Hosting: Full redeployment to Hostinger with Cloudflare Edge Caching.
Imaging: 4TB on-premise Docker cluster hosting 1.5TB of centralized active imaging data.
Operations: Managed enterprise email configurations and executed technical SEO audits.

Production Implementation

Features explicitly implemented and managed as the Sole IT Engineer.

SchedulingCalendar APIReal-time Google API integration.

Public WebWordPressRedeployed CMS platform.

InfrastructureLinuxOn-premise bare-metal servers.

ContainerizationDockerIsolated imaging environments.

Reverse ProxyNginxSecure internal routing.

DNS & EdgeCloudflareCaching and DDoS protection.

HostingHostingerScalable web deployment.

DiscoveryTech SEOSearch engine optimization.

Architecture Data Flow

A hybrid infrastructure topology handling both public web traffic and secure internal clinical data.

Public WordPress

Hostinger / Cloudflare

Local Intranet

Clinic Workstations

Google Calendar API

Real-Time Syncing

On-Premise Docker

1.5TB Medical Imaging

Nginx Reverse Proxy

Technology Decisions (ADRs)

Architectural decisions made balancing cloud scalability with on-premise security.

Google Calendar API for Scheduling

Problem: Patients needed to book appointments without calling, but the system had to perfectly reflect real-time clinic availability.

Why Chosen: Integrating the Google Calendar API directly into the public website allowed the web booking system to read/write slots based on the exact calendar the doctors already used on their phones.

Trade-offs: Requires maintaining OAuth consent screens and API rate limits.

Benefits: Zero additional training required for clinical staff, as they simply checked their Google Calendar as usual.

On-Premise Docker vs Cloud Storage

Problem: The clinic possessed over 1.5TB of active, high-resolution medical imaging data that needed to be accessed instantly during consultations.

Why Chosen: Architecting a 4TB on-premise Linux server running Docker containers (like Immich) ensured that accessing massive image files was restricted to the gigabit local network (LAN) speeds, rather than relying on fluctuating internet bandwidth.

Trade-offs: Requires manual hardware maintenance and local backup strategies.

Benefits: Saved thousands of dollars in recurring AWS S3 storage/egress fees and eliminated loading latency during critical patient consultations.

My Responsibilities

Architected

The 4TB on-premise Linux server cluster, configuring Docker, Nginx reverse proxies, and local network accessibility.

Engineered

The real-time Google Calendar API appointment scheduling system to automate patient slot bookings.

Managed

End-to-end digital operations, including WordPress CMS redeployment to Hostinger, SEO optimization, and corporate email configuration.

Engineering Challenges

Hybrid Infrastructure: Balancing a public-facing cloud web presence (WordPress/Hostinger) with a secure, on-premise local intranet (Docker/Linux) requires strict separation of concerns and tight network firewall rules.
API Sync Conflicts: Handling edge cases in the Google Calendar API where two patients might attempt to book the same slot simultaneously. Solved by implementing strict server-side validation and immediate calendar polling.

Lessons Learned

The "Sole IT" Reality: Managing an entire corporate digital ecosystem means you cannot just be a software engineer. You must seamlessly shift contexts between SysAdmin (Linux/Docker), Web Developer (WordPress/APIs), and IT Support (Email configuration).
Pragmatic Tooling: While custom building a bespoke scheduling backend is fun, leveraging the Google Calendar API was the pragmatic business choice that required zero staff retraining.

Project Outcomes

Measurable operational improvements for the clinical staff.

Infrastructure4TBOn-Premise Cluster Architected

Patient BookingAutomatedReal-Time Google API

Storage1.5TBActive Imaging Data Hosted

Production Tech Stack

Docker

Cloudflare

WordPress

Linux

Nginx

G. Calendar

Healthcare IT Infrastructure