My Health Records Act 2012 — section 77

This is a genuine localisation rule, but it is narrower than all healthcare data and all healthcare email. Applicability turns on the system, participant, record, and processing role.

Country
Australia
Rule type
Healthcare system
Regional pressure
Explicit Australian boundary

Who this reaches

The System Operator and specified registered repository, portal, and contracted service providers that hold records for the My Health Record system or access information relating to those records.

What the rule requires

Section 77 restricts covered participants from holding or taking relevant records outside Australia and from processing or handling related information outside Australia, subject to the Act's terms and limited exceptions.

What changes when the email path is regional

Boundry offers a Sydney regional email plane that can be assessed when a notification workflow must avoid adding an offshore messaging path. Sensitive record content should still be minimised and kept behind an authenticated application boundary.

What your team still owns

Boundry does not claim registration as a My Health Record operator or automatic compliance with the Act. Do not place My Health Record information into email without a specific legal and architecture assessment.

Read the primary sources

This is an engineering and vendor-evaluation guide, not legal advice. Confirm the current rule for your entity, contract, and workload from the primary source.

Turn this rule into an email path you can defend.

Start with one workflow. Classify the data, keep the message minimal, and trace it through the Sydney regional plane.