Products & tools

Connected Devices & Integrations

Bring useful information into context, with a clear purpose and permission to use it. Device information and system connections need to fit the people, equipment, and responsibilities involved.

Who it is for

For families and teams considering another source of context

A family might want to understand which devices are associated with a home. An organization might need a connection between genusConnect and software it already uses. These needs start with a question: what information would help, who should see it, and what would they do with it?

The Care App includes device-management views for personal and community contexts. Real-device connections are a separate matter: the device, service, data flow, and operating arrangements must be confirmed for the intended setup.

The components

The pieces to work through

Device inventory

Device records can include a name, category, room, type, and state. Personal and community scopes help organize the information around the relevant person or group.

Information and readings

The views can present device state and sensor information supplied to them. Temperature or movement may be useful examples to discuss, but a displayed value needs a known source, timestamp, and meaning before someone relies on it.

People and permissions

A device has an owner or creator and, in a community context, designated editors. The person receiving support should be part of decisions about what information is collected and who can use it.

System connections

An organization-specific integration needs an agreed information flow, identity and access rules, ownership, and error handling. Existing software does not become connected simply because it serves the same person.

Demonstration and connected modes

Device views include simulated examples that help explain an experience. A simulated reading is not a live sensor reading. A connected-mode label or a device brand shown in an example is not, on its own, confirmation of a working integration.

In practice

Start with one question about home support

An illustrative planning example, not a claim that a particular device or automated alert is already connected.

  1. Agree what would be useful

    A participant, family member, and support team discuss whether information such as home temperature would help. They agree who could see it and keep ordinary calls and visits part of the plan.

  2. Confirm the connection

    The technical team checks the specific device and service, permissions, data freshness, and what happens when information is missing. Any demonstration remains clearly separate from live use.

  3. Decide how people will respond

    The team agrees how to interpret the information and who is responsible for follow-up. An unexpected or missing reading prompts appropriate human attention; it is not treated as a diagnosis or a guaranteed emergency alert.

How it connects

Add context without opening every record

Device information may sit alongside the Care App experience where supported. An organizational connection may support a portal workflow. In either case, sharing needs a specific purpose and appropriate access; connecting tools does not mean every participant, partner, or AI service can see the underlying information.

Where AI helps

No automatic conclusions about a person

Connecting a device does not automatically give AI access to its information or permission to act on it. Any proposed AI-assisted review needs its own defined scope, appropriate permissions, and a check that the information is suitable for that use.

Do not assume that a motion pattern proves how someone feels, that a missing reading means they are in difficulty, or that an AI suggestion has confirmed a health issue. People need the source, limitations, and context to make sense of a signal.

What to confirm

Confirm before relying on a connection

Device compatibility, available readings, update frequency, connection reliability, and supported actions must be checked for each setup. Examples of device categories or brands are not a compatibility list. We should also agree support responsibilities and what people see when a connection stops working.

These tools do not replace personal check-ins, clinical judgment, emergency services, or a dedicated safety system. You can begin with the coordination and communication tools while evaluating whether a device or system connection would add something useful.