Eldercare Robot Procurement: Questions About Device Data and Support Access

A service robot offered for an older-adult setting may collect information through an app, a support service or optional sensors. Before purchasing, the organisation should understand what information is involved, why it is used and who can access it. A supplier’s promise that a product is “private” is a starting point for questions, not a complete description of the data flow.

Inventory information by task

List the tasks the organisation intends to use and ask the supplier what information each task requires. Separate information entered by a user, device-generated logs, optional recordings and data shared with a support provider where these apply. If a feature is not part of the proposed configuration, do not assume that its data collection is either present or absent without confirmation.

Record the product model, software version, enabled features and the date of the supplier’s response. Ask for the relevant documentation and identify any items that remain unknown. The inventory is an organisational tool, not a statement that all service robots collect the same information.

Ask why each item is needed

The UK Information Commissioner’s Office discusses data protection by design and by default, including the relationship between data minimisation and the purposes of processing. The guidance is framed in UK data-protection law; an organisation elsewhere needs to assess the rules and advice relevant to its own jurisdiction.

For each proposed data item, ask the supplier to identify its purpose and whether the feature can operate with a different setting or with less information. Record the supplier’s answer rather than assuming that an option exists. A procurement checklist does not decide a lawful basis or replace an organisation’s privacy assessment.

Understand storage, access and support

Ask where information is stored, whether it leaves the local device, who can view it, and what access a manufacturer or support provider may request. Record any stated retention or deletion arrangements, together with the source and date of the answer. If a supplier says that information is deleted automatically, ask what the statement covers and how the organisation can verify its own responsibilities.

Ask whether the support arrangement involves subcontractors, whether administrators can review access activity, and how the supplier communicates changes to its service. Record the answers for the configuration actually being purchased. A response about one optional module should not be treated as a complete description of every other module or external integration.

Do not ask staff or residents to place passwords, identity documents or sensitive care information in a demonstration ticket. Access credentials should be handled by authorised administrators through the organisation’s approved process. Where a question concerns medical, care or other sensitive information, involve the appropriate professional and privacy teams.

Explain the proposed experience to participants

The W3C guidance on involving users in web accessibility projects discusses informed participation and the value of learning from people with different needs. Its scope is web accessibility work; it does not by itself establish how a physical robot should be used in a care setting.

For a voluntary product evaluation, explain the purpose, what will be observed or recorded and whom participants can contact with questions. The organisation should use its own approved consent and ethics procedures where applicable. One person’s experience should not be presented as the experience of all older adults.

Use a hypothetical feature review

Imagine a facility evaluates an optional support feature that sends device logs to a supplier. Before enabling it, the procurement team asks what the logs contain, who receives them, why they are needed and whether the feature has a documented alternative. The team records the response and any unresolved point. This is a hypothetical example, not a claim about a real product or vendor.

If the response says a feature can be disabled, ask who controls the setting and how the organisation can confirm its state on the delivered version. Do not promise that disabling one feature prevents all data collection unless the relevant product documentation and assessment support that conclusion.

Maintain an open-issues record

Assign unanswered questions to an owner and record the supplier’s supporting documents, the date reviewed and the next action. Revisit the inventory when a software update, new integration or change of purpose alters the proposed configuration. A completed procurement form alone does not demonstrate ongoing security or legal compliance.

The site’s article on web accessibility and robot usability addresses a different but related procurement question. The industry information section provides background. This article provides questions for an organisation’s review, not medical or legal advice.