Distress
A press on the bracelet, or a suspected fall.
Event opened
- Source: bracelet
- Time recorded
- Location: living room
A smart bracelet, reporting by voice, non-invasive sensing and a system that connects the elder, the caregiver, the family and the service centre — with no cameras and no rebuilding the home.
Some capabilities on this page are in pilot, in development, or at product-vision stage. The status is marked next to each one.
5
reporting languages planned
0
cameras in the home
4
parties on the same picture
Voice report
Press and speak
Detected intent
Visit started
Confirm?
08:12
The elder speaks, the system understands, the family sees and the company manages. Each layer stands alone and none of them needs a camera.
The elder presses and speaks freely. No menu, no numbers to press, no app to learn.
Voice report
Press and speak
Detected intent
Visit started
Confirm?
08:12
Wi-Fi / RF sensors detect movement in a space without filming and without recording. Privacy First as architecture, not as a slogan.
Non-invasive sensing
Living room
Movement
Kitchen
Quiet
Bedroom
Quiet
Hallway
Passing
A family member sees what is happening without calling three times a day and without intruding.
Family portal
Status
Calm
Last visit
Today 08:12
Medication
Morning — given
Alerts
1 open
The caregiver sees what needs doing today, reports check-in and check-out, and raises exceptions.
Caregiver app
Current visit · 08:12
End visit
One chain, documented end to end, with automatic escalation when nobody answers.
A press on the bracelet, or a suspected fall.
Event opened
A verification call to the elder before escalating.
Verification call
The family and the centre are alerted.
Alerts
No answer — move to the next contact.
Escalation
Treatment status, summary and event history.
Event closure
An explicit separation between capabilities running today, capabilities in active development, and capabilities that depend on hardware or approvals we do not yet hold.
Patient and caregiver files, care plan, attendance verification, family portal, alerts and reports — running with pilot customers.
Free-speech voice reporting, the home edge hub and bracelet connectivity — in active development, not yet generally available.
Wi-Fi / RF sensing, GPS location and a full monitoring centre — dependent on hardware, sensors and the relevant approvals.
No cameras. Audio recorded only around a deliberate report. Viewing permissions are set in advance and logged.
Non-invasive sensing capabilities depend on hardware, sensors, the required approvals and actual product capability. Nothing here claims that the hardware is live with customers today, and there is no existing connection to emergency services. Any future connection will be made only through an authorised body.
No. The architecture is based on wireless movement sensing and on deliberate voice reporting. There is no video and no continuous audio recording.
Nursing care has two people in every equation: the person giving care and the person receiving it. StaffCore Care manages both on the same infrastructure that manages attendance, documents and payroll — so the caregiver is a full-fledged employee, and the patient gets a file, a plan and a record.
A hardware component under development: one button to verify that a visit took place, a second button for a distress call. The component is not available as an off-the-shelf product, is not a medical device and does not prevent falls or medical events.
Each layer stands on its own, but the value comes when they are connected — from information about the patient all the way to the hour that lands on the caregiver’s payslip.
Patient file and caregiver file: details, contacts, preferences, skills, training and documents. This is the foundation everything else reads from.
Capability status: In pilotAn engine that suggests suitable caregivers by language, gender, skill, area, availability and matching history — instead of relying on a coordinator’s memory.
Capability status: In pilotA care plan with tasks, frequency and instructions. The caregiver sees it during the visit and marks what was done, what was deferred and why.
Capability status: In pilotArrival and departure confirmation according to the policy you define — a code, a location or a dedicated component. The verified hours are the basis for payroll and for billing.
Capability status: In pilotA family portal, alerts to the coordinator and incident records. Each party sees exactly what they have been defined as entitled to see.
Capability status: In pilotEvery capability is shown with its real status. Some capabilities are live, some are in pilot and some are still in development or in planning. We will not present anything as available if it is not.
Personal details, contacts, functional status, preferences and flagged sensitivities.
Daily and weekly tasks, frequency, special instructions and completion tracking.
Marking completed tasks, notes from the field and photos where needed.
Reporting an unusual incident with classification, escalation and tracking through to closure.
Training, languages, skills, service areas and valid documents.
Suggested candidates with a match score and a rationale.
A visit schedule, swaps and cover — while preserving continuity of care.
Verified hours that flow into the same payroll accounting engine as the rest of the system.
Viewing visits and updates at a predefined level of information.
A record of consents to share information, per patient and per family member.
Setting different exposure levels for sensitive information by role.
Alert rules for the coordinator, the manager and the family — without continuous monitoring.
A two-button component for visit verification and for a distress call. In development.
A local communications component for connecting devices and working even on weak connectivity. In development.
A spoken report from the caregiver that is converted into a structured record. In development.
Connecting to sensors in the patient’s home. In planning only.
An advanced location layer for caregivers in the field. In planning only.
A control-centre layer for managing alerts. In planning only, and it is not an emergency response centre.
A simple physical component designed for two situations only. The simplicity is the point: no screen, no menu and no training required.
The caregiver presses it at the start of the visit and at the end. The press confirms that the visit took place at the patient’s home, and feeds the hours into the system with no form and no app.
A press sends an immediate alert to the parties defined in your organisation. This is an internal call to your team — not a dial-out to an emergency call centre and not a rescue service.
Most enquiry calls from families come from a simple lack of information: did the caregiver arrive, what was done and what has changed. The family portal answers that without exposing information that is not required.
Nursing care touches the most sensitive information an organisation holds. That is why the defaults in Care are narrow, and every widening of access is an explicit decision.
The system was designed with permission layers, logging and controls suited to working with sensitive information. This is not a declaration of compliance with any standard or certification, and the system’s fit with the regulatory requirements that apply to you is examined together with you during implementation.
The core of the module — patient file, caregiver file, care plan, scheduling and visit records — is in pilot with early users. The hardware and sensor capabilities are still in development or in planning. Every capability on the site is marked with its status, and in a demo we will show you what actually works.
In the demo we look at a single day — from the elder’s report to the attendance report that comes out at the end of the month.