Skip to content
ORVIXLABSMain site
// SYSTEM SECTION

Argos Care · Privacy

What information the system needs and how it can remain under local control.

THESISEVIDENCELIMITSTESTDECISION ARGOS CARE PRIVACIDADORVIXLABS

Care does not authorise unlimited access

A person's habits do not automatically belong to everyone around them. Deployment agrees who can inspect events, the detail shown and retention periods. Information is processed locally in the private mode; authorised notifications to relatives outside the home have limited content and an explicitly defined channel.

What the system contributes

The architecture can keep sensors, images, routines and state inside owner-controlled infrastructure. Only what an authorized integration or protocol needs is shared.

The person retains a role in the decision

Support is not permission to impose surveillance for somebody else's convenience. Scope must be explained understandably and reviewed with responsible people and the recipient as appropriate. Records are not used to assign diagnoses or abilities. Care and professional decisions do not transfer to an engine merely because sensors exist.

A notification also needs a response

Sending a family notification does not prove it was read or that the person is well. The workflow shows its state and follows available escalation rules. A silent sensor is reported as a limitation rather than interpreted as normality. Testing includes those cases and the manual procedure for continuing.

Test against the actual routine

Review normal situations, expected changes, alerts to disregard and circumstances needing a check. Evaluation involves users and carers, including sensor or communication loss. Argos Care does not replace medical care, carers or emergency services. Success means useful, understandable assistance, not a promise to detect every incident.

// ORVIXLABS

Tell us about the real operation. We will show you how Argos Care could fit it without forcing a generic product on top.

Discuss this system