Shown at assignment signing
To a resident or representative following a secure link
Enduring assignment of Medicare benefits
This is the GP enduring assignment-of-benefit evidence function. The signing page identifies the resident, GP/provider scope and wording. It is separate from treatment, general information sharing and the clinical communication workflow. Specialist AoB and claim-readiness are outside scope.
We collect necessary resident and Medicare details, provider and service scope, signer identity, decision-specific authority evidence, signature, wording version, decision and timestamps. Relationship or next-of-kin status alone does not establish authority.
Signing is optional. Missing or declined AoB must not prevent, hide, delay or deprioritise care. SAGE does not determine eligibility or claim validity; the GP and practice retain those responsibilities.
Authorised users may access evidence only for its permitted purpose. RACF workflow access does not imply unrestricted access to signed GP artefacts. The v1.1 review records encrypted artefacts in RDS in AWS Sydney; external SMS and identity suppliers have separate processing boundaries.
Kudosity is selected for SMS. It receives the number and full message, including any link. Production enablement and supplier evidence remain open. Provider acceptance does not prove delivery. Optional family updates are a separate preference.
Contact the practice or privacy@sageconnect.au for access, correction, questions or withdrawal. Remote links normally expire after seven days, in-person links after one hour, and failed identity checks can lock the link. Do not provide bank details, online-account passwords or payment through a signing link.
Shown at nurse intake
To facility staff raising a request
What is recorded when you raise a request.
When you raise a concern, SAGE records your identity and role, the resident and site, the necessary concern details and time. Enter only what authorised care staff and clinicians need.
The workflow supports response, acknowledgement and follow-up; record required clinical information in the existing RACF system. Use established emergency channels for urgent care.
Authorised participants see only the records permitted by their organisation, site, role and assignment. Corrections may retain an audit history. Application audit is append-only for the runtime role, not immutable.
Current environments are synthetic-only. The currently deployed synthetic-only environment still uses practice-level RLS with facility/object checks. The RACF-root tenancy remediation is the next release candidate and remains subject to migration, negative isolation testing and deployment verification. Contact your organisation administrator or privacy@sageconnect.au for access or correction.
Given at resident admission
To a resident, or the person who assists them — supplied for
the facility's admission pack
How requests for a doctor are recorded here.
The RACF organisation uses SAGE Connect to communicate clinical concerns with invited GPs and permitted specialists. Existing RACF and clinician systems remain the primary clinical records.
Limited identifiers, review reasons, messages, necessary attachments, responses, acknowledgement and follow-up may be held. The RACF, clinicians and, where relevant, you or a verified representative supply information for that workflow.
GP enduring AoB evidence is a separate purpose. Its absence does not prevent clinical review. Family or next-of-kin status does not by itself establish authority to sign or make decisions.
Access is limited to authorised participants and necessary service suppliers. Information is not sold, used for advertising or used to train AI models. Core AWS services are in Sydney in the v1.1 evidence; supporting suppliers can process information overseas. Real-data use remains subject to the release gates.
Ask the RACF organisation or privacy@sageconnect.au about access, correction or a complaint. See the privacy policy for supplier, retention and complaint details.
Shown on account creation
To clinicians, practice administrators and facility staff
Your workforce account information
We collect your name, work email, role, RACF organisation, site and clinician associations, relevant credentials, authentication metadata and access events to administer and secure your access.
Clerk provides authentication and may process workforce metadata overseas. Resident profiles are not intentionally included in identity claims. Invited participation does not confer access to every resident in a practice or organisation.
Contact your organisation administrator or privacy@sageconnect.au for access or correction. MFA, account lifecycle and deprovisioning controls must be verified before real-data launch.
Shown at website enquiry
To a business contact submitting the interest form
How we handle your enquiry
We collect facility name, your role, current workflow and work email, plus submission time and correspondence, to respond to your enquiry. Do not include resident, patient or clinical information.
Google Apps Script and Sheets process and store the enquiry, and nominated SAGE personnel receive email copies. Google may process this outside Australia. Website delivery suppliers may also handle connection and security metadata; their actual configuration must be confirmed in the website supplier register.
Submission is optional. You can opt out of follow-up or ask about access, correction and retention at privacy@sageconnect.au. The approved business-record retention schedule must cover the form store and email copies.