Cooma AI is developing Australian AI estates for health and life-sciences workloads where sensitive data, accelerated compute, human accountability and regulatory boundaries must be designed together.
Infrastructure can protect a boundary. It cannot replace clinical evidence.
A useful health AI briefing separates research, administrative and clinical intended uses before discussing models or GPUs. That determines the relevant privacy, evidence, safety and procurement work.
Sensitive information
Personal information stays subject to privacy law inside AI.
OAIC guidance says the Privacy Act applies where AI handles personal information and warns against placing sensitive information into publicly available generative-AI tools.
The TGA regulates software and AI when their intended purpose meets the medical-device definition, including certain diagnostic, prediction, monitoring and treatment functions.
Select a health or research workload to inspect the likely compute pattern, data sensitivity and operating controls.
01 / Imaging
Imaging and pathology model development.
Create a controlled environment for approved image data, annotation, GPU training and reproducible evaluation before any clinical deployment decision.
Readiness-sprint outcomeAn intended-use, data, evidence, compute and deployment brief owned by clinical, privacy and technology leaders.
Compute pattern
Multi-GPU training + batch evaluation
Data profile
Sensitive image data, labels and clinical context
Likely deployment
Isolated research/evaluation estate before validated production
The health AI ledger
Privacy, evidence and operations in one view.
The ledger is a discovery tool. It does not determine legal status or substitute for privacy, clinical, ethics or regulatory review.
01
Data
Document legal basis, consent/waiver where relevant, de-identification, cohort provenance, access, retention and deletion.
02
Models
Track intended use, training data, model version, performance by cohort and known limitations.
03
People
Assign clinical/research, privacy, data-custodian and technical accountability with least-privilege access.
04
Operations
Separate research from production; capture runs, outputs, reviewers and release decisions.
05
Continuity
Do not make care dependent on an unvalidated service; define recovery and safe clinical fallback.
Proposed deployment pattern
Separate experimentation from clinical production.
A controlled research and evaluation estate can make data, model and evidence handling more explicit before an organisation decides whether and how a workload should enter production.
Approved sources
Clinical, research & laboratory data
Purpose-limited datasets, controlled access and authoritative source systems.
Research, training and evaluation capacity subject to customer and supply agreements.
→Decision gate
Research result or validated pathway
Keep the workload in research, stop it, or progress through the required assurance and production process.
Australian hosting does not make an AI system clinically safe, legally permitted or TGA compliant. Those conclusions depend on intended use, evidence, organisational controls and the applicable law.
Commercial path
Begin with a bounded use. Earn the production decision.
The fastest credible path often starts with research, evaluation, administrative work or another clearly bounded use—not an uncontrolled clinical deployment.
01 / Triage
Intended-use session
Name the user, decision, data and whether the output could influence diagnosis, treatment or care.
Workload classification02 / Qualify
Privacy & evidence scope
Bring clinical/research, privacy, data, regulatory and technology owners into one scope.
Approved discovery basis03 / First revenue
Readiness sprint
Produce the data boundary, evidence plan, architecture, GPU envelope and decision gates.
Binding paid SOW · 4–6 weeks04 / Evaluate
Governed design partnership
Build and test in a separated environment with pre-agreed measures and oversight.
Paid evaluation milestones05 / Decide
Production or research path
Progress only when legal, clinical, privacy, security and procurement owners approve the path.
Capacity agreement if justified
Health & life-sciences briefing
Bring the intended use. Leave patient data behind.
Do not submit health, genetic, personal, clinical-trial or otherwise sensitive information. The first discussion needs only the intended outcome, user and workload type.