SAGE ConnectCare connected clearly

The doctor’s book, digitised and auditable

Retire the doctor’s book.

SAGE Connect helps residential aged-care organisations close the loop on clinical concerns. Nurses and invited clinicians can see what was raised, who responded and what needs follow-up.

RACF organisation as customer · Invited clinicians · Synthetic-only release

A worn paper ledger open on a nurses’ station counter in a residential aged care home — The communication workflow SAGE aims to support. Existing RACF and clinician systems remain the primary clinical records.

Release status: synthetic-only. The approved RACF-centred model is being implemented in a remediation candidate. Migration, isolation testing and deployed verification remain open. Read the Trust page before assessing readiness for real resident data.

01 / The round

One review, start to finish.

A shared workflow from concern to response, acknowledgement and follow-up.

01

A nurse raises a review

Reviews, messages, attachments and status sit in one workflow. Enter only what the care team needs.

Illustration of the candidate workflow · synthetic data

Concern raised

Resident: Synthetic resident · Room 20B
Concern: Limited detail needed for this review
Assigned to: Permitted clinician at this site
GP AoB: Separate evidence; does not block review

02

The system timestamps it

The moment it is raised it is on the record — who asked, when, and why.

Illustration of the candidate workflow · synthetic data

Workflow history

09:10 · Nurse: Concern raised
09:15 · Clinician: Request acknowledged
Status: Awaiting clinical response

03

GP assignment evidence stays separate

GP enduring assignment of benefit (AoB) is a separate evidence function. Missing AoB never blocks a clinical review. Specialist AoB and claim-readiness are outside scope.

Illustration of the candidate workflow · synthetic data

Separate GP assignment evidence

Decision scope: GP enduring assignment of benefit
Representative: Authority for this decision must be verified
Clinical review: Continues if evidence is absent
Specialists: Communication only; no AoB or claim-readiness

04

The doctor has the list before arriving

One entry per resident, with the requester and the reason attached.

Illustration of the candidate workflow · synthetic data

Clinical concerns for review

Resident A · West wing: Response awaited
Resident B · East wing: Follow-up requested
Access: Only authorised site and assigned records

05

The response returns to the care team

The care team acknowledges the response and records follow-up in its primary clinical system. An entry marked reviewed alone does not prove the loop has closed.

Illustration of the candidate workflow · synthetic data

Close the communication loop

Clinician: Response recorded
Care team: Acknowledgement recorded
Follow-up: Recorded in the primary clinical system
Closure: Requires the workflow steps to be completed

02 / The trail

Who asked for Stanley R. to be seen, and when?

Illustration of the candidate workflow · synthetic data

An illustrative communication history

09:10 · Nurse: Clinical concern raised
09:15 · Clinician: Request acknowledged
10:30 · Clinician: Response recorded
10:40 · Nurse: Response acknowledged
11:00 · Care team: Follow-up entered in the primary record
Separate function: GP assignment evidence does not determine claim validity

Illustrative candidate history · example timestamps and roles · synthetic resident, synthetic facility

Follow the request and the response.

Use the workflow history to understand what was requested and recorded. Application audit entries are append-only for the runtime role; this is not an immutable record or evidence of regulatory compliance.

03 / The people doing the work

A doctor’s book that your nurses and doctors will use.

For the nurse

One place to follow a clinical concern.

See existing requests and their status before raising another. Keep emergency escalation and downtime procedures available.

For the GP

Be prepared for the list before the round.

One entry per request, with the requester and the reason attached. Keep the existing clinical record and escalation procedures.

See who raised the concern and what was recorded. Clinical decisions and the primary clinical record remain with the care team and clinician.

A female doctor in a white coat and a female nurse in navy scrubs seen from behind, standing together in a doorway looking ahead into a resident’s room.

Built by a geriatrician and a GP who do this work every week.

04 / Families

Families hear from you.

A family relationship or next-of-kin entry does not establish authority. A person may sign GP enduring assignment evidence only after authority for that specific decision is verified. Optional family status updates are a separate communication preference.

An older woman's hands resting in a younger woman's hands on a wooden table beside a cup of tea.

Illustrative SMS · synthetic example

Example Home: A clinical response has been recorded. Please contact the home using its usual telephone number if you need to discuss the update.

Optional status updates require a separate recipient preference. They do not confirm that care is complete.

05 / Why now

Make each handover easier to follow.

For the RACF organisation

See requests, responses and follow-up across participating homes, with access limited to each person’s authorised role and site.

For invited clinicians

Review clinical concerns and return a response. GP assignment evidence is separate and does not determine Medicare eligibility or claim validity.

For the care team

Keep the primary care record in the existing RACF and clinician systems, and record acknowledgement and follow-up through the communication workflow.

Current environments remain synthetic-only. RACF tenancy migration, isolation testing and the remaining privacy, security and operational gates must close before real resident data is enabled.

The nurse station where the round starts.

Everything after that nurse station is a question of the record: who asked, when, on whose authority, and what came back.

See the trail →

An empty sitting room in a residential aged-care home in late afternoon light, two armchairs facing each other.

06 / Talk to us

We are looking to CONNECT.

You have digitised at least one workflow, now digitise your doctor's book.

What Connect means

01

A direct line to the founders.

02

A virtual meeting to understand your needs.

03

Agreed in conversation and onboarding.

Express interest

Facility nameYour roleWhat does your round run on today?Work email

Do not include resident or clinical information. Google Apps Script and Google Sheets process and store this enquiry, and nominated SAGE team members receive email copies. Google may process it outside Australia. We use it to answer and manage your enquiry; you can opt out of follow-up at any time. See our website enquiry notice.

SAGE ConnectCare connected clearly

← Back to the argument

The trust

The Trust

Everything a provider's risk, privacy or governance team needs before signing — and the things we have not proven yet, stated plainly.

What SAGE Connect is, and is not

SAGE Connect is an RACF-centred clinical communication and assurance platform. The RACF organisation is the customer and payer; homes are sites. GPs, practices and permitted specialists participate as invited clinicians. Clinical concerns move through a closed-loop communication workflow. The existing RACF and clinician systems remain the primary clinical records. SAGE may hold limited identifiable health information required for that workflow. GP enduring AoB is a separate billing-evidence function; its absence does not prevent clinical review, and SAGE does not determine Medicare eligibility or claim validity. Specialist communication may occur, but specialist AoB and specialist claim-readiness are outside scope. Representative authority is decision-specific and is not inferred from family/NOK status.

Clinical decisions and emergency escalation remain with the treating clinicians and RACF care team. SAGE does not diagnose, determine urgency or make care conditional on billing evidence.

Your residents' information

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.

Verified Data Flow v1.1, reviewed 20 September 2026 against application commit 9fe9ce3, reports core AWS application, private RDS PostgreSQL, KMS, secrets, workload logs and backups in Sydney (ap-southeast-2). Global edge and external suppliers are separate; this is not an assurance that all information stays in Australia.

Resident profiles, GP assignment artefacts, attachments and retained referral material use AES-256-GCM envelope encryption, with wrapped data keys protected by KMS. Encrypted blobs are held in RDS. Other operational fields rely on encrypted storage and access controls. Authorised downloads create copies outside the service boundary.

Application audit records are append-only for the runtime role. Operational records can be corrected; neither the whole database nor application audit is WORM or cryptographically chained. AWS CloudTrail is a separate control-plane log.

When something goes wrong

The v1.1 evidence records RDS point-in-time recovery of 35 days for production and 7 days for staging, plus weekly encrypted logical backups to S3. Production is Single-AZ. Successful restoration and recovery timings have not been evidenced.

Production application DNS remained unresolved in the review. WAF rules were counting, not enforcing blocking. These are open release gates, not completed protections.

The RACF and clinicians must keep emergency and downtime procedures. Incident contacts, notification duties, restore tests and operational ownership must be agreed and exercised before real-data use.

Who else is involved

AWS provides core hosting, RDS, KMS, secrets, workload logging and backups. Cloudflare DNS and AWS CloudFront provide the reviewed application edge path; edge processing is global.

Clerk provides workforce sign-in and invitations. Staff identity and organisation/site metadata may leave Australia; resident profiles are not intentionally sent in identity claims. MFA enforcement, webhook verification and deprovisioning evidence remain open.

Kudosity is the selected SMS provider. It receives mobile numbers, message bodies and link metadata. Staging is configured; production secret seeding, SenderID registration and rollout remain pending in v1.1. Provider acceptance is not proof of handset delivery; no receipt callback was verified. Supplier countries, retention and contractual evidence remain required.

The separate website enquiry form sends facility name, role, current workflow and work email to Google Apps Script and Sheets, with email copies to nominated SAGE personnel. Google may process this outside Australia. Do not submit resident or clinical information. This website flow is additional to the app marketing pages reviewed in v1.1.

Stripe code is present in the application but its secrets were not injected into the reviewed AWS deployment. Self-onboarding and payments are disabled. No live practice-management-system integration was verified.

A completed supplier register, subprocessors, contracts and processing locations remain real-data launch requirements.

What we have proven, and what we have not

Current: synthetic-only environments and the dated v1.1 deployed evidence. Target: the RACF-root remediation candidate implementing the approved product scope. A source-code change is not proof that a control is deployed.

Evidence required: RACF migration and negative isolation tests; exact-commit staging verification; production DNS and rollback; WAF enforcement; restore drills and availability decisions; Clerk and MFA controls; supplier due diligence; production SMS and alarm tests; retention approval; PIA and independent penetration testing; operational sign-off.

Verified Data Flow v1.2 must be generated against the release commit actually deployed and tested. Until then, the new architecture is a candidate and the real-data hold remains in place.

Documents & requests

Request the product-scope decision, PIA v0.2 working assessment, Procurement v1.0 controlled review copy and the verified v1.1 baseline at security@sageconnect.au. Each has a different evidence status; none is a certification or a completed procurement approval.

Contract terms, insurance and service commitments require the signed agreement and current supporting evidence. Accessibility has not been independently audited. Contact hello@sageconnect.au for an accessible copy or to report an issue.

Report vulnerabilities to security@sageconnect.au without including resident information. Avoid disruptive testing. The machine-readable security contact is at /.well-known/security.txt.

SAGE ConnectCare connected clearly

← Back to the argument

The team

Built by people who do the rounds.

Two of the three of us are in residential aged care every week. The third has spent a decade building records that have to hold up.

Dr Vincent Siaw

Geriatrician · founder

Dr Vincent Siaw

Consultant geriatrician working across metropolitan residential aged care. Brings the clinical reality of the round and the need for clear communication between the care team and invited clinicians.

Dr David Ta

General practitioner · co-founder

Dr David Ta

GP attending residential aged-care facilities weekly. Owns the practice-side view: what a doctor needs before walking in, and what a practice must be able to show afterwards.

Ziggy Hao

Product engineer · co-founder

Ziggy Hao

Shapes the product from discovery through to architecture, including audit history, encrypted artefact handling and access controls. RACF-root tenancy is a remediation candidate awaiting deployment verification.

Mission

The administrative gap, and the record that closes it.

Between a nurse noticing something and a GP recording a visit there is a paper book on a counter. Nothing about that seam is written down in a way anyone can produce later.

Our focus is a closed-loop communication workflow: raise a concern, obtain a clinical response, acknowledge it and record follow-up. The RACF organisation is the customer and payer; clinicians participate by invitation.

We make no claim about care outcomes, and we do not intend to. The record is the product.

SAGE ConnectCare connected clearly

← Back to the argument

Contact

Real people, named.

No support queue. Founding facilities reach the founders directly.

Founding facilities

Dr Vincent Siaw · founder
Dr David Ta · co-founder

hello@sageconnect.au

Privacy and data

Dr Vincent Siaw · privacy officer
Ms Ziggy Hao · privacy officer

privacy@sageconnect.au

Security reports

Ms Ziggy Hao · engineer

security@sageconnect.au

Registered office

SAGE Connect Pty Ltd
112/78 Doncaster Road
Balwyn North, Victoria 3104
ABN 78 699 224 176 · ACN 699 224 176

How to reach us

In writing at hello@sageconnect.au — answered by a founder, not a queue.

Hours

Mon–Fri 08:00–18:00 AEST · urgent product issues prioritised

Privacy officer & complaints

If you are unhappy with how we handled your information.

01
Write to our privacy officers at privacy@sageconnect.au, or by post to the registered office below.
02
We acknowledge in 5 business days and give you a written answer within 30 days.
03
If you are not satisfied, you may escalate to the Office of the Australian Information Commissioner at oaic.gov.au or 1300 363 992.

SAGE ConnectPrepared for print · A4 · single page

Head-office summary

SAGE Connect: clinical communication centred on the RACF.

Written for the person who was never in the demo. Every name, room and timestamp below is synthetic.

What it is

SAGE Connect is an RACF-centred clinical communication and assurance platform. The RACF organisation is the customer and payer; homes are sites. GPs, practices and permitted specialists participate as invited clinicians. Clinical concerns move through a closed-loop communication workflow. The existing RACF and clinician systems remain the primary clinical records. SAGE may hold limited identifiable health information required for that workflow. GP enduring AoB is a separate billing-evidence function; its absence does not prevent clinical review, and SAGE does not determine Medicare eligibility or claim validity. Specialist communication may occur, but specialist AoB and specialist claim-readiness are outside scope. Representative authority is decision-specific and is not inferred from family/NOK status.

What it is not

SAGE is not an emergency channel, primary clinical record or claims service. GP enduring AoB evidence is separate from clinical review. Specialist billing is outside scope. Payments and self-onboarding are disabled in the reviewed AWS deployment.

Why it matters to head office

A shared workflow can help authorised staff follow clinical concerns, responses and acknowledgement. Workflow history supports review; it does not certify clinical completion, compliance or claim validity.

Risk position

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.

The founding arrangement

One facility, sixty to a hundred and fifty residents, metro, already digitised in at least one workflow. A direct line to the founders, a hand in what gets built next, and founding terms agreed in conversation. Expression of interest asks four fields: facility name, role, what the round runs on today, and a work email.

Specimen trail · Stanley R. · Rm 20B · Tue 04 Aug 2026 (synthetic)

Illustrative candidate workflow · synthetic resident and site · not a verified clinical record

20:48	Review requested — reason recorded: “caught flu”	Nurse · Riverside Nurse Test
20:48	GP AoB evidence managed separately	System
20:48	Visit scheduled	Nurse · Riverside Nurse Test
20:52	Message from the clinician	Dr Aisha Reyes
20:53	Care-team acknowledgement recorded	Dr Aisha Reyes
20:53	Follow-up recorded in the primary clinical system	Dr Aisha Reyes

SAGE ConnectCare connected clearly

← Back to the argument

Legal

Privacy policy

Australian Privacy Principles · Privacy Act 1988 (Cth) · Health Privacy Principles · Health Records Act 2001 (Vic)

In short

SAGE Connect is an RACF-centred clinical communication and assurance platform. The RACF organisation is the customer and payer; homes are sites. GPs, practices and permitted specialists participate as invited clinicians. Clinical concerns move through a closed-loop communication workflow. The existing RACF and clinician systems remain the primary clinical records. SAGE may hold limited identifiable health information required for that workflow. GP enduring AoB is a separate billing-evidence function; its absence does not prevent clinical review, and SAGE does not determine Medicare eligibility or claim validity. Specialist communication may occur, but specialist AoB and specialist claim-readiness are outside scope. Representative authority is decision-specific and is not inferred from family/NOK status.

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.

The v1.1 review records core AWS services in Sydney. Identity, SMS, edge and website-enquiry suppliers are separate processing boundaries; their locations and contracts remain subject to verification.

Residents and their families do not have accounts with us and are not our users. Section 09 explains who to ask to see or correct information. Section 11 explains how to complain.

01Who we are

SAGE Connect is operated by SAGE Connect Pty Ltd, ABN 78 699 224 176 · ACN 699 224 176, of 112/78 Doncaster Road, Balwyn North, Victoria 3104. Contact privacy@sageconnect.au about personal information.
SAGE Connect is an RACF-centred clinical communication and assurance platform. The RACF organisation is the customer and payer; homes are sites. GPs, practices and permitted specialists participate as invited clinicians. Clinical concerns move through a closed-loop communication workflow. The existing RACF and clinician systems remain the primary clinical records. SAGE may hold limited identifiable health information required for that workflow. GP enduring AoB is a separate billing-evidence function; its absence does not prevent clinical review, and SAGE does not determine Medicare eligibility or claim validity. Specialist communication may occur, but specialist AoB and specialist claim-readiness are outside scope. Representative authority is decision-specific and is not inferred from family/NOK status.
The RACF organisation directs its authorised workflow use. Participating clinicians remain responsible for their own clinical records and professional duties. SAGE processes information to provide and secure the service and has its own privacy obligations. Contractual allocations do not remove any party’s statutory duties.
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.
02What information we collect

The clinical workflow may hold limited resident identifiers, date of birth, site and room, review reason, urgency entered by staff, messages, response, acknowledgement, follow-up and necessary attachments. These can be identifiable health information. Existing historical referral material must also be covered by access and retention controls.
The separate GP enduring AoB function may hold relevant Medicare identifiers, GP/service scope, signer identity, relationship, decision-specific authority evidence, wording version, signature and timestamps. Family or next-of-kin status alone is not authority. Specialist AoB and claim-readiness are outside scope.
Workforce information includes name, work email, role, RACF organisation, site and clinician associations, credentials, authentication metadata and access events. Operational information includes audit, security, support and provider-acceptance metadata. Website enquiries collect facility, role, current workflow and work email.
Only information needed for the stated purpose should be entered. Internal identifiers do not make linked personal information anonymous. Current environments are restricted to synthetic information.
03How we collect it

Information comes from authorised RACF staff and invited clinicians, and from residents or appropriately verified representatives for the separate GP assignment workflow. Workforce users and website enquirers provide their own details; suppliers return necessary service metadata.
The relevant party must establish a lawful basis for collection and sharing and provide the applicable collection notice. Authority to make one decision must not be assumed to cover treatment, information sharing or Medicare assignment generally.
04Why we collect it, and how we use it

The primary purpose is to communicate a clinical concern, route it to an authorised clinician, record a response and support care-team acknowledgement and follow-up. Relevant clinical content must be recorded in the existing RACF and clinician systems.
GP enduring AoB is a separate evidence function. It does not determine Medicare eligibility, entitlement or claim validity, and its absence does not block, hide or delay clinical review. Specialist communication is permitted; specialist AoB and billing readiness are outside scope.
Other purposes are account administration, access control, security, support, responding to business enquiries and meeting legal obligations. Resident health information is not used for advertising, sale or training AI models.
05Who we disclose it to

Access is limited to authorised RACF and clinical participants according to organisation, site, role and assignment. A person’s membership of a practice or family does not create unrestricted resident access. RACF administration must not expose detailed GP assignment artefacts without a specific authorised purpose.
Operational suppliers receive information required for their service. Optional family updates require a separately recorded recipient and communication preference; they are not bundled with GP AoB signing.
Information may also be disclosed where required or authorised by law, or to professional advisers under appropriate confidentiality controls. See the Trust page for the reviewed supplier status and open evidence requirements.
06Whether information goes overseas

The v1.1 review records core application, RDS, KMS, secrets, workload logs and backups in AWS Sydney. Global edge services and external suppliers are separate processing boundaries.
Clerk receives workforce identity and account metadata. Kudosity receives destination numbers, SMS bodies and link metadata; production enablement and supplier due diligence remain pending. Google processes the separate website enquiry and email copies, potentially outside Australia.
Supplier and subprocessor countries, retention, access and contractual safeguards must be confirmed before real resident data is enabled. This page does not claim that all processing stays in Australia. Stripe code is present but payments are disabled in the reviewed deployment.
07How we hold and protect it

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.
The v1.1 review reports KMS-backed AES-256-GCM envelope encryption for selected profiles and artefacts, held as encrypted blobs in RDS, with infrastructure encryption for other operational fields. Authorised downloads leave the controlled service boundary.
Clerk provides workforce identity. Enforcement of MFA, invitation lifecycle and deprovisioning remains an evidence requirement. Application audit entries are append-only for the runtime role; they are not an immutable or WORM record.
The review records encrypted backups and point-in-time recovery, but a successful restore drill has not been evidenced. WAF was count-only and production app DNS unresolved. See the Trust page for the full open-gate position.
08How long we keep it, and deletion

Retention must be approved by record class, purpose, applicable law and signed agreement. GP enduring evidence, clinical communication, authority records, audit, security logs, enquiries and backups require separate decisions. A blanket two-year disposal rule is not appropriate.
Automated disposal coverage, legal holds and backup expiry must be tested. Candidate safeguards and source configuration do not establish a completed disposal programme.
When information is no longer needed and no lawful retention requirement applies, destruction or de-identification must follow the approved schedule. Backup disposal follows its verified lifecycle. Access and deletion requests can be made to privacy@sageconnect.au.
09Access and correction

Residents and appropriately authorised representatives can ask to access or correct information. Contact the RACF organisation first for its clinical-communication records, or the treating practice for its primary clinical and GP assignment evidence. SAGE will assist the responsible party and can be contacted at privacy@sageconnect.au.
For account, enquiry, support or security records managed by SAGE, contact SAGE directly. Identity and authority for the specific request will be checked. We aim to respond within 30 days and explain any refusal and complaint route. Corrections may preserve a restricted audit history.
10Data breach notification

We have a documented plan for responding to a data breach. If one occurs we contain it, assess what happened and who is affected, and act on that assessment.

We take all reasonable steps to complete an eligible-data- breach assessment expeditiously and within the statutory assessment period. Where notification is required, the responsible entity notifies the OAIC and affected individuals as the Notifiable Data Breaches scheme requires.

We coordinate with affected customers. Contractual customer-notification periods and responsibility are set by the signed agreement and applicable law.
11Complaints

If you are unhappy with how we have handled personal information, tell us first.

Email privacy@sageconnect.au, or write to our Privacy Officers at the address in section 01. We acknowledge complaints promptly and aim to provide a substantive response within 30 days.

If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner — oaic.gov.au, 1300 363 992, GPO Box 5218, Sydney NSW 2001.

For Victorian health information, the Health Complaints Commissioner may also have jurisdiction. Another state or territory health privacy regulator may apply depending on where the information was handled.
12Changes to this policy

This is version 1.2, updated 20 September 2026 for the approved RACF-centred model. It is a controlled review copy pending legal approval and publication. It does not alter signed agreements or represent approval for real-data use.
Material changes to information handling must be assessed and communicated to affected organisations and individuals as appropriate. Earlier versions are retained as historical records.

SAGE ConnectCare connected clearly

← Back to the argument

Legal

Terms of service

Public review terms for RACF organisation customers · signed agreements prevail

What we commit to

Care is never conditional on billing. The system will never withhold, delay or deprioritise a request for a doctor's visit because an assignment is missing or a billing requirement is unmet — and you agree not to use it as though it did.

Rights in customer content and permitted clinician use are governed by the signed agreements. Available exports are limited to tested reports and artefact downloads; complete export and transition commitments require a tested service schedule.

SAGE does not lodge Medicare or DVA claims or receive assigned benefits. Payments and self-onboarding are disabled in the reviewed AWS environment.

These website terms are a lawyer-review draft. The order form, master agreement, data processing and sharing arrangement and service schedule form the customer agreement. Signed documents prevail over website summaries.

01Parties and definitions

These review terms describe SAGE Connect Pty Ltd and the RACF organisation named as Customer in the signed order form. A person entering an agreement must have authority to bind that organisation.
Customer means the RACF organisation and payer. A home is a site. Authorised users include approved RACF staff and invited GPs, practices and permitted specialists. Participation does not make a clinician or practice the platform customer. Customer content means information submitted or generated for the authorised service purposes.
02What the service is

SAGE Connect is an RACF-centred clinical communication and assurance platform. The RACF organisation is the customer and payer; homes are sites. GPs, practices and permitted specialists participate as invited clinicians. Clinical concerns move through a closed-loop communication workflow. The existing RACF and clinician systems remain the primary clinical records. SAGE may hold limited identifiable health information required for that workflow. GP enduring AoB is a separate billing-evidence function; its absence does not prevent clinical review, and SAGE does not determine Medicare eligibility or claim validity. Specialist communication may occur, but specialist AoB and specialist claim-readiness are outside scope. Representative authority is decision-specific and is not inferred from family/NOK status.
Feature availability is governed by the tested release and signed service schedule. The current environments remain 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.
03What the service is not

SAGE is not an emergency channel, primary clinical record, clinical decision-support system, medical service or claiming agent. Clinical urgency and care decisions remain with the RACF and treating clinicians.
GP enduring assignment evidence is separate. SAGE does not determine Medicare eligibility or claim validity, lodge claims or receive clinical-service benefits. Specialist AoB and specialist billing readiness are outside scope. Missing assignment evidence must not withhold, hide, delay or deprioritise clinical review.
Residents and representatives do not receive workforce accounts. A secure signing link does not establish the recipient’s authority; that authority must be verified for the particular decision. Optional status messages require a separate preference.
04Your obligations

Enter only necessary, accurate and lawfully collected information. Provide relevant notices and verify decision-specific authority. Do not infer authority from family or next-of-kin status.
The RACF organisation and participating clinicians must maintain correct role, site, credential and assignment permissions, promptly revoke access when no longer needed, and retain their own primary clinical records.
Maintain emergency, downtime and escalation procedures. A software status alone does not establish that a clinical concern has been resolved.
Do not access another organisation’s records, disrupt the service, upload malicious material or use it for unlawful monitoring or unsolicited communications. Report security issues without resident information or destructive testing.
05Accounts, access and multi-factor authentication

Each user has a named individual account. Shared, generic and role-based logins are not permitted, because the value of the record depends on every entry being attributable to a person.

Authentication is delivered through the configured identity provider. Any MFA commitment applies only as stated in the order form or security schedule and after production enforcement has been verified.

You are responsible for what is done under your users' accounts. Tell us immediately if you believe an account has been compromised. We may suspend an individual account without notice where we reasonably believe it has been compromised or misused, and will tell you as soon as we can.
06Data ownership, export and return

Your record is yours. We claim no ownership of it. We hold it for you and, where section 11 applies, on your instructions.

The current service provides specified CSV and PDF reports and artefact downloads. Any obligation to provide a complete tenant export, its format, timing, cost and post-termination availability must be stated in the order form or data schedule and tested before use.

What we do not do with your record

We do not sell it, license it, or share it with anyone for their own purposes. We do not use it to train or develop any model. We do not use it to build products or insights for other customers. We may use aggregated statistics that identify no resident, no clinician and no customer, solely to operate and improve the service.

Access and report scope

Reports and downloads follow the Customer's tenant, role, facility, clinician and assignment permissions. Facility users have only the access needed for their authorised workflow. Available exports must not be treated as a complete clinical or statutory record.

Retention and deletion vary by record class, law, contract, dispute and security need. The applicable schedule and transition arrangements form part of the signed agreement; the website does not promise an unimplemented full-export or disposal capability.
07Availability and support

We aim to make the service available at all times other than planned maintenance, which we schedule to minimise disruption. Support response times and advance-notification commitments are agreed with you in the order form.

Because care must never depend on the service being available, you must keep a workable manual fallback for requesting a doctor's visit. We will tell you what to do if the service is unavailable during a round.
08Fees

The RACF organisation is the customer and payer. Fees, covered sites, term, GST and renewal are established in the signed order form. No practice-seat price or automatic clinician charge is created by these pages.
SaaS fees are separate from Medicare, DVA and private clinical-service payments. Payments and self-onboarding are disabled in the reviewed AWS environment. Any future payment activation requires review and an agreed service schedule.
09Liability and indemnity

The lawyer-approved master agreement and order form must state the liability cap, excluded-loss categories, privacy and security treatment, indemnities and insurance position. Nothing excludes rights or remedies that cannot lawfully be excluded, including applicable Australian Consumer Law protections. These website terms do not create an unstated liability cap.
10Clinical responsibility

Clinical judgement, urgency, handback and primary recordkeeping remain with the treating clinicians and RACF care team. SAGE supports communication and assurance without assuming their professional or statutory duties.
The rendering GP and practice remain responsible for any assignment requirements, eligibility and claim validity. Specialist communication is supported within permitted access; specialist AoB and claim-readiness are excluded.
11Privacy and data handling

The RACF organisation directs its authorised clinical-communication use. Homes are sites, and clinicians and practices participate by invitation. The signed data arrangement must allocate collection notices, access, correction, retention and incident responsibilities without removing statutory obligations.
GP assignment evidence is limited to its verified purpose and permissions. Representative authority is decision-specific and must not be inferred from relationship labels.
The current synthetic deployment and the RACF-root target architecture have different evidence status, as set out on the Trust page. No unrelated organisation receives automatic access. SAGE separately manages its own workforce, support, security and website-enquiry records.
12Confidentiality

Each party must keep the other's confidential information confidential and use it only for the purposes of these terms. This does not apply to information that is public through no fault of the recipient, was already known, or must be disclosed by law.

Your record is your confidential information. The service, its design and its documentation are ours.
13Suppliers

Services and their current enablement are described on the Trust page, including AWS, Clerk, Kudosity and the separate Google website enquiry flow. Stripe is not enabled in the reviewed deployment.
Supplier processing locations, subprocessors, retention and contracts remain evidence requirements before real-data use. Notification and objection rights for material supplier changes are governed by the signed agreement.
14Intellectual property

We own the service, its software, design and documentation. You get a non-exclusive, non-transferable right to use it during the agreement.

You own your record and grant us only the rights needed to provide the service to you. If you give us feedback or suggestions we may use them without obligation, and that gives us no right to your record.
15Term, suspension and termination

The agreement runs for the term in the order form and continues until either party ends it on written notice. Either party may terminate immediately if the other commits a material breach not remedied within 30 days of written notice, or becomes insolvent.

Suspension

We may suspend affected access where reasonably necessary for a serious security threat, unlawful use, legal requirement or material unpaid fee, subject to the signed agreement. We will not make care conditional on subscription status. The Customer's clinical and manual-fallback duties continue during an outage or suspension.

On termination

Cure periods, data return, available export formats, transition assistance, retention and deletion are governed by the order form and data schedule. These terms do not promise an unimplemented 90-day self-service export window. Accrued and expressly surviving obligations continue after termination.
16Changes to the service and to these terms

We may change the service, provided we do not materially reduce its core function, and we give notice of any change that materially affects how you use it.

Notice and customer rights for material changes to health-information handling, pricing or key suppliers are those in the signed agreement. A revised website page does not retrospectively amend a signed agreement.
17Insurance

Insurance types and limits apply only as stated in the signed agreement and supported by current certificates of currency. Penetration tests, certifications and other assurances are described as complete only while current evidence supports them.
18General and governing law

Governing law.

Victoria, Australia. Both parties submit to the non-exclusive jurisdiction of its courts.

Disputes.

Before starting proceedings, each party must give written notice of the dispute and meet, in person or by video, within 15 business days to try to resolve it. This does not prevent either party seeking urgent relief.

Assignment.

Neither party may assign without the other's written consent, not to be unreasonably withheld. We may assign to a related body corporate or on a sale of our business, on notice.

Notices.

In writing, to the addresses in the order form; email is sufficient if acknowledged.

Force majeure.

Neither party is liable for failure caused by events beyond its reasonable control, provided it tells the other promptly and mitigates.

Entire agreement.

The signed master agreement, order form, service schedule and data processing and sharing arrangement form the agreement in their stated order of precedence. They replace prior proposals about the same subject. The privacy policy is a public notice, not a substitute for those signed terms.

SAGE ConnectCare connected clearly

← Back to the argument

Legal

How we collect information

Point-of-collection notices for signers, staff, residents and website enquirers. The relevant notice must be shown when the information is collected; this page is the public copy.

Version 1.2 · legal review copy · updated 20 September 2026

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.