Skip to main content
StaffCore
The care world

The technology that lets an older person feel safe, independent and connected.

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

Language: English

Press and speak

Detected intent

Visit started

Confirm?

08:12

Visit started
  • “The caregiver has arrived”
  • “The caregiver has finished”
  • “The caregiver went on a break”
  • “The caregiver is back”
  • “I need help”
  • “I am not feeling well”
What is inside

Four layers around one person

The elder speaks, the system understands, the family sees and the company manages. Each layer stands alone and none of them needs a camera.

Bracelet and voice button

Capability status: Coming soon

The elder presses and speaks freely. No menu, no numbers to press, no app to learn.

  • “The caregiver has arrived” / “the caregiver has finished”
  • “Gone on a break” / “back again”
  • “I need help” / “I am not feeling well”
  • Speech-to-text, language detection and intent understanding
  • An attendance event with a timestamp, linked to the right caregiver
  • A spoken confirmation request when the system is unsure

Voice report

Language: English

Press and speak

Detected intent

Visit started

Confirm?

08:12

Visit started
  • “The caregiver has arrived”
  • “The caregiver has finished”
  • “The caregiver went on a break”
  • “The caregiver is back”
  • “I need help”
  • “I am not feeling well”

Non-invasive sensing

Capability status: Planned

Wi-Fi / RF sensors detect movement in a space without filming and without recording. Privacy First as architecture, not as a slogan.

  • Presence in a room and movement between rooms
  • No movement for an unusual period
  • Possible fall or prolonged lying on the floor
  • A change in movement pattern, or leaving the house
  • No video and no continuous audio recording

Non-invasive sensing

No video · no continuous recording

Living room

Movement

Kitchen

Quiet

Bedroom

Quiet

Hallway

Passing

Last movement
4 minutes ago
Daily pattern
Normal
Fall suspected
None detected

Family portal

Capability status: In pilot

A family member sees what is happening without calling three times a day and without intruding.

  • The elder’s status and the caregiver’s visits
  • Attendance reports and alerts
  • Medications and exceptional events
  • Viewing permissions and privacy settings
  • Contacts and ways to get in touch

Family portal

Status

Calm

Last visit

Today 08:12

Medication

Morning — given

Alerts

1 open

  1. 08:12Caregiver arrived — voice report
  2. 09:30Morning medication given
  3. 12:05Break — 30 minutes
  4. 16:00Visit ended

Caregiver app

Capability status: In pilot

The caregiver sees what needs doing today, reports check-in and check-out, and raises exceptions.

  • Tasks, visits and care plan
  • Check-in and check-out with a timestamp
  • Medications, notes and exception reporting
  • Documents, chat with the family and with the company
  • A multi-language interface

Caregiver app

Current visit · 08:12

  • Morning medication
  • Meal
  • Short walk
  • Exception report

End visit

Safety and emergency

From the press of a button to a closed event

One chain, documented end to end, with automatic escalation when nobody answers.

  1. 01

    Distress

    A press on the bracelet, or a suspected fall.

    Event opened

    • Source: bracelet
    • Time recorded
    • Location: living room
  2. 02

    Verification

    A verification call to the elder before escalating.

    Verification call

    • Attempt 1 — no answer
    • Attempt 2 — answered
    • Response recorded
  3. 03

    Alert

    The family and the centre are alerted.

    Alerts

    • Family — sent
    • Centre — sent
    • Caregiver — sent
  4. 04

    Escalation

    No answer — move to the next contact.

    Escalation

    • Contact 1
    • Contact 2
    • Service centre
  5. 05

    Closure

    Treatment status, summary and event history.

    Event closure

    • Status: handled
    • Summary recorded
    • Written to audit log
The real status

What is live, what is in development and what is vision

An explicit separation between capabilities running today, capabilities in active development, and capabilities that depend on hardware or approvals we do not yet hold.

In pilot

Patient and caregiver files, care plan, attendance verification, family portal, alerts and reports — running with pilot customers.

In development

Free-speech voice reporting, the home edge hub and bracelet connectivity — in active development, not yet generally available.

Product vision

Wi-Fi / RF sensing, GPS location and a full monitoring centre — dependent on hardware, sensors and the relevant approvals.

Privacy

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.

Frequently asked — care

No. The architecture is based on wireless movement sensing and on deliberate voice reporting. There is no video and no continuous audio recording.

StaffCore Care

Care happens at home. Oversight has to happen in the system.

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.

Coming soon

CareLink Duo — distress and care verification in two buttons

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.

Architecture

Five layers that make up Care

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.

01

The information layer

Patient file and caregiver file: details, contacts, preferences, skills, training and documents. This is the foundation everything else reads from.

Capability status: In pilot
02

The matching layer

An 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 pilot
03

The care layer

A 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 pilot
04

The verification layer

Arrival 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 pilot
05

The transparency layer

A 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 pilot
Capabilities

What is in the system — and the status of every capability

Every 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.

Patient and care management

  • Complete patient fileCapability status: In pilot

    Personal details, contacts, functional status, preferences and flagged sensitivities.

  • Care planCapability status: In pilot

    Daily and weekly tasks, frequency, special instructions and completion tracking.

  • Visit recordsCapability status: In pilot

    Marking completed tasks, notes from the field and photos where needed.

  • Incident managementCapability status: In pilot

    Reporting an unusual incident with classification, escalation and tracking through to closure.

Caregivers and scheduling

  • Caregiver fileCapability status: In pilot

    Training, languages, skills, service areas and valid documents.

  • Matching engineCapability status: In pilot

    Suggested candidates with a match score and a rationale.

  • Scheduling and visitsCapability status: In pilot

    A visit schedule, swaps and cover — while preserving continuity of care.

  • Caregiver payrollCapability status: In pilot

    Verified hours that flow into the same payroll accounting engine as the rest of the system.

Transparency, consent and privacy

  • Family portalCapability status: In pilot

    Viewing visits and updates at a predefined level of information.

  • Consent managementCapability status: In pilot

    A record of consents to share information, per patient and per family member.

  • Privacy modesCapability status: In pilot

    Setting different exposure levels for sensitive information by role.

  • Defined alertsCapability status: In pilot

    Alert rules for the coordinator, the manager and the family — without continuous monitoring.

Hardware and future capabilities

  • CareLink DuoCapability status: Coming soon

    A two-button component for visit verification and for a distress call. In development.

  • In-home edge hubCapability status: Coming soon

    A local communications component for connecting devices and working even on weak connectivity. In development.

  • Voice updateCapability status: Coming soon

    A spoken report from the caregiver that is converted into a structured record. In development.

  • Environmental sensorsCapability status: Planned

    Connecting to sensors in the patient’s home. In planning only.

  • Location trackingCapability status: Planned

    An advanced location layer for caregivers in the field. In planning only.

  • Monitoring centreCapability status: Planned

    A control-centre layer for managing alerts. In planning only, and it is not an emergency response centre.

Hardware

CareLink Duo — two buttons, two purposes

A simple physical component designed for two situations only. The simplicity is the point: no screen, no menu and no training required.

Care verification button

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.

Distress call button

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.

  • The component is in development and is not available as an off-the-shelf product. An availability date will be set later.
  • CareLink Duo is not a medical device and is not intended for diagnosis, medical monitoring or treatment.
  • The component does not prevent falls, does not detect a medical event and does not operate automatically without a press.
  • Alerts are sent to the parties defined in your organisation. Responsibility for the availability of a response and for the response itself is yours.
  • Operation of the component depends on electricity and network connectivity at the installation site.
Family

Controlled transparency for family members

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.

Visits and timesWhen a visit took place, who carried it out and how long it lasted.
Task completionWhich tasks from the care plan were carried out, and what was deferred and why.
Updates from the fieldGeneral notes that the caregiver or the coordinator chose to share.
Defined alertsA notification about a change in scheduling or about an incident, according to what was configured.
By consent onlyAccess is opened only after the relevant consents have been recorded.
No detailed medical informationThe default is operational information, not a medical record.
Privacy

Information about people in their own homes calls for particular care

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 minimum requiredEvery role sees only the information it needs in order to do the work.
Recorded consentsSharing information with family members is conditional on a consent recorded in the system.
Access logEvery view of sensitive information is logged with the user and the time.
Privacy modesSensitive fields can be hidden from routine operational views.
No continuous monitoringThe system does not track patients or caregivers on an ongoing basis.
Retention policyThe retention period for information is set by you, including archiving and controlled deletion.

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.

What StaffCore Care is not

  • It is not a medical device and is not registered as one.
  • It does not provide diagnosis, medical advice or a medical recommendation of any kind.
  • It is not an emergency response centre, is not an emergency call centre and is not a substitute for emergency services.
  • It does not monitor patients continuously and does not detect events automatically.
  • It does not prevent falls, injuries or deterioration in health.
  • It does not replace the professional judgement of the nursing or medical team.
  • System alerts are sent to the parties defined in your organisation, and responsibility for the response is yours.
Frequently asked questions

StaffCore Care — frequently asked questions

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.

Let us walk through your process

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.

1-800-100-350jerry@alinclean.co.il