Elder Care pilot privacy notice

Pre-operational pilot draft v1.0 · Last updated 13 July 2026
In short
Elder Care is not yet a live public service. This draft explains the proposed minimum-data approach for a supervised hospital pilot; enrollment and consent controls must be tested and approved before real care information is collected.

1. Who this draft covers

The proposed notice covers a senior receiving pilot care and a family member or authorised representative coordinating that care. A representative must not claim consent for a competent senior without the senior's knowledge and agreement.

2. Proposed information

A pilot may need identity and contact details, home address, emergency contacts, relevant conditions, allergies, medicines, mobility needs, schedules, vital readings, consultation notes, delivery details, caregiver assignments and consent records. The final form must collect only fields approved for the pilot.

3. Proposed purposes

Information would be used for eligibility assessment, agreed care coordination, safety escalation, service fulfilment and approved family updates. It must not be sold, used for unrelated advertising or reused for a materially different purpose without a new lawful basis and notice.

4. Senior choice and family access

The senior's capacity, preferences and private clinical communication must be respected. A nominated family member should receive only the updates agreed for their role. Changing access will require identity and authority checks; the working controls are not yet publicly available.

5. Pilot partners

Before launch, each participating hospital, clinician, caregiver, pharmacy, laboratory, meal or technology partner must be identified, appropriately qualified and covered by confidentiality, data-processing and role-access terms. No partner is implied by this draft.

6. Retention and deletion

An approved schedule must define how long each pilot record is kept under applicable legal, clinical, contractual and dispute requirements. Requests cannot override a lawful retention duty. The deletion and anonymisation workflow must be tested before pilot enrollment opens.

7. Consent and requests

The pilot must provide understandable consent, withdrawal, correction and grievance routes, with identity checks and records of decisions. Dashboard withdrawal and self-service data requests are proposed features, not currently available public capabilities.

8. Safety and emergencies

The proposed Elder Care pilot is a coordinated, non-emergency service. It is not continuous monitoring and cannot guarantee detection of an abnormal event. For chest pain, severe breathing difficulty, unconsciousness, stroke signs or another emergency, call 108 immediately.

9. Security and incidents

Before real information is collected, the pilot requires approved authentication, role restrictions, encryption, audit evidence, incident handling and partner-access procedures. The public preview does not claim that every proposed control is operational.

10. Contact and approval gate

A verified privacy contact, named grievance officer, postal address, response timelines, participating hospital and final notice approval must be published before pilot enrollment begins. Until then, do not submit sensitive care information through general website channels.