A signal with no named recipient is not a care program.
Caretech designs and integrates wearable programs for elderly care, home care and clinical settings — vital, sleep, activity and mobility data brought into a care workflow. The work is mostly routing: who receives what, how quickly, and what they are accountable for doing.
Everyone asks what it can detect. Nobody asks who answers.
A wearable program fails in the same place every time, and it is never the wrist.
The band works. The data arrives. And then it reaches a dashboard that is open during office hours, or a family member who is at work, or a shared inbox belonging to a shift that ended, or a care manager holding two hundred residents and no way to tell which of the day's signals is the one that mattered. The program is measured on what the device can sense and evaluated by families on what somebody did.
So Caretech designs backwards from the recipient. Who is the named person. What are they expected to do. What is their window. What happens when they do not respond, and who is next. What is written down at each step. Sensing is the easy half; that list is the program.
Seven steps, and a person's name at the fifth.
The grammar is unchanged: data is captured with its context, validated against the record, tested against the program's own rule, and routed to a named human being who acknowledges it and acts. The software does not decide, and it does not stand in for staffing.
From a wearable signal to a recorded action
01 · Wearable data
- From the person's own device, chosen by them or by the program. Caretech AI makes none of them.
02 · Capture
- With the time it was recorded and the device it came from.
03 · Validation
- Checked against the record, so a slipped strap is not read as a clinical change.
04 · Threshold or rule
- Written by the care program, visible to it, and changeable by it.
05 · Named recipient
- A specific person, on shift, with an escalation path behind them. Never a shared inbox.
06 · Acknowledged
- Within an agreed window, with an onward path when it is not.
07 · Action & audit
- What was done, by whom, and when — the part a family and a regulator both ask for.
What wearable data honestly is.
Caretech's wearable programs carry the data types below. Each is described as what the device reports, not as what it proves — and each is read by a qualified person in the context of everything else known about that person.
Vital data
Heart rate, oxygen saturation and similar values as reported by a consumer or clinical device. Useful as a trend, weak as a single reading, and never a substitute for a measurement taken properly.
Sleep and rest
Duration and regularity, inferred by the device from movement and heart rate. It is an estimate produced by a manufacturer's model, and it is presented as one.
Activity
Steps, minutes and intensity. The clearest and most reliable thing a wearable produces, and the one most directly useful to a care plan.
Mobility
How much someone moves around their own home or facility, and how that changes week to week. Change is the useful part; the absolute number rarely is.
Reminders
Prompts a person or their carer has asked for — medication times, appointments, a scheduled check. A reminder is a prompt to a human being, and the program does not treat one as evidence that anything was taken or done.
Trends over time
The same measure, from the same device, over months. Longitudinal trend analysis is where wearable data earns its place, and it needs no inference about the future to do so.
How alerting is engineered.
Alerting is the most requested feature in this capability. Every alerting capability here is a coordination tool and not an emergency response service.
Routing a signal to a carer
Where a program defines a threshold — a value outside an expected range, a device that has gone quiet, an activity pattern that has changed — the workflow can route that signal to the named person responsible for the resident or patient, and record when they acknowledged it. This is not an emergency response service. It does not summon anyone, it does not guarantee that a recipient is awake, available or in range, and in an emergency a person must contact local emergency services.
Notifying a family member
Where a person has consented to it, a family member or caregiver can be included as a recipient, with the same acknowledgment recorded against their name. It is a way of keeping a family informed inside a care program — it is not supervision, and it does not replace a call system or a clinical assessment.
The same engineering governs any device feature that reports a fall or other event: Caretech routes what the device reports to a named person and records the response. The detection belongs to the device; the routing, the acknowledgment and the record belong to the platform.
Seven settings. One accountable name in each.
Caretech's wearable programs are built for settings where somebody is already accountable for a person's care, because that accountability is what a signal routes into.
- Devices belong to the person, the program or their supplier. Caretech routes what they report, and each integration is scoped and built for the program.
- Coverage is a property of your staffing, not of the software. Caretech names the recipient, the window and the escalation behind them, and records all three.
- Wearable data is not a clinical measurement and produces no diagnosis, no score of a person's clinical risk, and no prediction. Longitudinal trend analysis is where it earns its place.
Tell us who answers at two in the morning.
Name them, name their window, and name who is behind them. A wearable program designed from that sentence outwards works; one designed from the device inwards produces signals nobody owns.