Medical Practice Cloud Migration | Intelligent Networx

CloudManaged ITHealthcare

The Situation

Two GPs running a regional practice on the NSW Central Coast had been running their clinical software on a Windows Server 2012 box in the storeroom. The server was five years old, backed up to a USB drive that the practice nurse took home each evening. The practice manager rang us after the server blue-screened on a Tuesday morning and they lost four hours of bookings while it was rebuilt.

The Problem We Found

Clinical software, the booking system and patient email all ran on the same physical server.
The USB backup had not been tested; when we attempted a restore we found two of the last four nightly backups had failed silently.
Staff desktops were not domain-joined; each machine had its own local credentials.
The internet connection was a single NBN business-grade circuit with no failover.
The practice had no documented incident response plan; when the server failed, no one knew who to call.

What We Did

We migrated the clinical software to an Azure virtual machine in the Australia East region. Patient data remained in Australia. Each GP and receptionist connected via a thin-client session, which meant the application ran in the cloud but the user experience on their existing desktops did not change.

We moved the practice's email to Microsoft 365 Business Premium, enabled multi-factor authentication for every user, and set up Intune so each device was enrolled and could be remotely wiped if a laptop was lost. The NBN circuit was retained as primary, with a 4G backup router that kicked in automatically when the wired connection dropped.

Backup was re-architected: Azure Backup took daily snapshots of the clinical VM, and a separate cloud-to-cloud backup product protected Microsoft 365 mailboxes and Sharepoint document libraries. We ran a full restore test before go-live and a second one thirty days later.

Outcome

The storeroom server was retired. The practice now has no on-premise hardware to maintain.
Clinics stayed open through a three-hour NBN outage because the 4G backup carried them.
Backup restores are tested quarterly and the practice manager receives a written report.
Every user has MFA; no clinical credentials have been compromised in the twelve months since go-live.
The practice can add a new clinician in under a day, which previously required a hardware purchase.

The practice has since approached us about adding a telehealth room with a dedicated connection, which we designed and deployed in a second phase.

Technical detail

The practice had three GPs, four reception staff and a storeroom server running MedicalDirector on Windows Server 2012 R2. The server was ten years old, had no tested backup, and was connected to a single NBN circuit with no failover. The practice manager had been told for two years that "it will be fine".

We migrated the MedicalDirector database to an Azure virtual machine in Australia East, configured Azure Backup with a recovery services vault, and set up a 4G backup circuit at the clinic. The clinical software runs on the Azure VM, with local workstations connecting over the internet. We configured quality of service on the 4G circuit so telehealth video calls take priority over general web traffic.

Patient data remains in Australia. We did not select a region outside Australia. We documented the recovery time objective at four hours and tested it: we restored the database from a backup and confirmed the clinic could see patients within that window. The practice manager signed off on the test.

What the practice manager noticed first

The first thing the practice manager noticed was that the server fan noise in the storeroom stopped. The second was that internet outages no longer closed the clinic. The third was that, when a receptionist's laptop died, we restored their profile in twenty minutes rather than rebuilding it from scratch. The monthly cost is a fixed fee that covers the Azure hosting, the backup, the 4G circuit and the helpdesk.