Elderly care · Funds + carbon

Elderly care

Do not assume elders use smartphones: card, watch, face and family proxy in parallel

Assisted-meal subsidy by age bandFamily proxy top-up and lookupAge-friendly and delegated operation
Back to the zero-carbon smart card solution
Scene position

First principle: do not require elders to learn a system

Other scenes may assume a phone. Elderly care cannot. The product centre of gravity moves from self-service to proxy and physical carriers.

Principals
Care homes, day-care centres, happiness canteens
Account shape
Funds + carbon account
Delivery layer
Tier 1 full delivery
Primary carrier
Physical card and watch, not a mini-app
Elderly care
People and roles

The person who actually operates the system is often not the elder

Design around who is clicking, not only around who receives the service.

EldersTap or face to dine; no need to understand balances and rules; large type, few steps
FamilyTop up remotely, view meals and spend, receive anomaly alerts
CarersAct for the elder, batch-check meals, record service; operations leave a trail
Institution adminsRoster, subsidy, meal stats and subsidy-settlement reports
Civil-affairs authorityAggregated issuance and use of assisted-meal subsidy, for settlement and supervision
Core capabilities

What elderly-care delivery must include

Assisted-meal subsidy by age band and split books is the most core — and most error-prone — capability in this scene.

Assisted-meal subsidy by age band

Different subsidy amounts for bands such as 60–69, 70–79, 80+

Subsidy and self-pay split

Government subsidy and personal self-pay booked separately, with separate settlement reports

Family proxy

After binding, family can top up, look up and set limits; binding needs institution or self confirm

Delegated-operation trail

Carer actions record operator and time; auditable

Multi-carrier

Physical card, watch or face — any one can complete meal write-off

Cross-site use

Several meal sites in one sub-district share one roster and subsidy rule

Scene hard parts

How elderly-care projects differ at the root

Moving a campus or government product here usually fails.

Elders have no smartphone, or will not use one

Asking elders to install a mini-app, remember a password or scan is unrealistic

Physical card and face as primary carriers; the phone end faces family, not elders

Subsidy is fiscal money

Assisted-meal subsidy is fiscal; it must be real-name, anti-impersonation and settleable

Real-name verify + split books + monthly filing reports

Do not replace the institution’s existing system

Care homes often already have nursing or health systems

Connect and fill; card-side and assisted-meal capabilities only

Carbon value

Record carbon in passing — do not add burden on elders

Any design that needs extra elder action to earn points is unworkable here.

Assisted-meal clean-plate

Weigh stations

Done by carer or canteen side; elders do not operate

Walking and wellness activities

Activity check-in

Paired with the institution’s daily activity programme

Institution energy saving

Submetering

Institution-side stats; not into personal accounts

Delivery boundary

What we do, and what we do not

Elderly care needs the most restraint: more features make elders less able to use it.

Delivered in this solution

  • Assisted-meal spend and subsidy split
  • Family end and carer proxy
  • Multi-carrier write-off
  • Sub-district multi-site roll-up

Out of scope

  • No health monitoring or medication management
  • No nursing roster or care plans
  • No clinical steps of medical-care integration
  • No requirement that elders self-serve

Want to see how this scene is actually delivered?

A demo walks the account, spend or entitlement write-off and the carbon board for this scene. You can also return to the solution overview to see platform capabilities.