Home/Industries/Healthcare
Industries — HealthcareSensitive data, decades of retention, finite budget.
Healthcare has the hardest combination in Australian cloud: the most sensitive category of personal information, the longest retention obligations, and typically the tightest funding envelope.
Where healthcare estates come under strain
Health information is a special category
Under the Privacy Act, health information attracts stricter handling than ordinary personal information, and a breach involving it is very likely to be notifiable. That raises the bar on access control, logging and segregation well above a typical corporate estate.
- Classification and tagging at ingestion
- Row and column-level access, provable in audit
- Masked or synthetic data for non-production
- Access logs held outside the audited accounts
Retention is measured in decades
Clinical records and imaging carry retention obligations that outlast most technology decisions — in some jurisdictions well beyond a patient's lifetime for paediatric records. Storage architecture chosen for convenience becomes a permanent cost.
- Tiering to Glacier classes with retrieval SLAs matched to clinical need
- Object Lock where immutability is required
- Format and readability planning, not just bytes retained
- Legal-hold exceptions that do not disable the whole policy
Funding does not flex with usage
Most healthcare organisations cannot pass cloud cost growth through to anyone. That makes FinOps a clinical-capability issue rather than a finance hygiene issue — money spent on idle infrastructure is money not spent on care.
- Attribution by service line and facility
- Commitment strategy sized to a stable baseline
- Imaging storage cost modelled over the full retention period
- Non-production shutdown schedules that actually hold
Where healthcare cloud spend usually leaks
These four findings recur across the healthcare estates we assess. They are patterns, not any one customer's numbers — and we would rather show you which of them applies to your estate than quote you an average.
- Non-production copies of real patient data created for a migration test and never torn down — a cost problem and a privacy problem at once
- Imaging and clinical document archives in S3 Standard with no lifecycle policy, growing indefinitely against a decades-long retention obligation
- Spend that cannot be attributed to a service line or facility, so nobody can reasonably be asked to reduce it
- Commitments bought against a pre-rightsizing baseline, locking in the waste for one to three years
The 72 hours you cannot improvise
Under the Notifiable Data Breach scheme you must assess a suspected eligible breach expeditiously — generally within 30 days — and notify affected individuals and the OAIC where serious harm is likely. In practice the useful window for containment and evidence is the first 72 hours, and it is not a window you can spend working out who to call.
- Assessment procedure written and rehearsed before you need it
- Forensic logging retained and separately controlled, so it survives the incident
- Containment playbooks for credential compromise and exposed storage
- Clinical, legal and communications contacts identified in the plan itself
- Post-incident report written for both engineers and your board
The finding we make most often
Non-production environments containing a copy of real patient data, usually created for a migration test years earlier, with broader access than production and no lifecycle policy. It is the single most common serious finding in healthcare assessments.
Data residency
Workloads and backups stay in ap-southeast-2 (Sydney) or ap-southeast-4 (Melbourne) unless you direct otherwise. Support tooling that touches customer data is hosted in Australia, and our sub-processor register lists every location.
Start with the estate you already have
The free Well-Architected review covers security, cost and resilience together — which in healthcare is usually where the interesting findings are.