genus perspective
Who responds when a device sends a signal?
A connected device can send information without settling what happens next. A 2023 study of remote patient monitoring invites a practical conversation about people’s expectations, agreed contact arrangements, and the human work behind a connection.
What we found in the news
A qualitative study published in JMIR Human Factors on July 27, 2023 (opens in a new tab) explored remote patient monitoring at one US academic health system. It combined clinician interviews with workshops in which patients and patient representatives imagined possible futures for care.
The authors noted that:
“priorities of different stakeholders regarding these technologies may not overlap”
— Lawrence and colleagues, JMIR Human Factors
This was a small, context-specific study using convenience sampling, not a trial proving clinical benefit. For us, it opens a practical conversation about what each person expects a connection to do. The questions below are our application of that idea to planning a service.
Why this matters to us
Imagine a home-support arrangement with a connected device. A person sees confirmation that information has been sent. They understand that to mean someone has looked at it. The service means only that it has arrived in a system.
Both interpretations can seem reasonable until they are put side by side. A device can perform its technical task while leaving the person unsure about the human response.
At genus, we want that conversation to happen while the service is being designed. What is being shared? Who receives it? What has the team actually agreed to do? Those answers belong beside the device, where the person can find and question them.
Describe the arrangement in everyday language
Start with the purpose of collecting the information. Explain what the device is intended to contribute and what remains outside that purpose. Avoid asking a reassuring symbol or a product name to carry the explanation.
Walk through one ordinary example together. Information is collected, sent, received, and reviewed at different points. Say which of those steps the person can see and what any confirmation actually means.
Be specific about the agreed contact route and hours. If the arrangement includes routine review at defined times, describe it that way. A person should not have to infer continuous attention from the fact that a device stays connected.
Ask the person to describe how they understand the arrangement, with the communication support they choose. This is a chance to improve the explanation and identify a mismatch before it becomes an expectation.
Give the response work a place in the day
In our example, a team member needs an agreed role in reviewing the incoming information. That responsibility has to fit into the service’s actual staffing and relevant professional procedures. Adding a screen does not make time available to look at it.
Identify who covers the role when that colleague is away and where questions about the arrangement go. Test the handover with a fictional example. Can the covering person find the agreed contact plan and understand what work is theirs?
Keep technical support and care responsibilities clear. A colleague who helps reconnect a device may not be the person authorized to interpret its information. The participant should be able to reach the appropriate help without having to work out the organization’s internal structure.
Include the day when information is missing
Plan a nonclinical test in which a device is disconnected or an expected transmission does not arrive. What would the service show, and who would notice? The team should know the difference between no new information and a record that someone has reviewed.
Explain any agreed follow-up in a way the person can find later. Avoid turning an equipment problem into an assumption about their willingness to participate. They may need help with charging, connectivity, or deciding whether this arrangement still suits them.
Revisit the agreement when circumstances change. A new contact person, different hours, or a replacement device can alter what someone needs to understand. Updating the equipment record and checking the person’s understanding are both useful parts of that work.
What this means for the people you serve
People should have a say in what is collected and shared, with whom, and for what purpose. Make room for questions about the arrangement and for a person to discuss changing it. A device connection should leave them better informed about the support around it.
The genus connection
Today, genus device-management tools can organize device details and supplied sensor information in supported configurations. A device entry alone does not establish a live connection, an alert service, or a monitoring commitment.
The device, data flow, permissions, reliability, and response arrangements need separate confirmation with the organization. We would use those decisions to shape the configuration and explain its limits. Technology should make agreed responsibilities easier to understand; it cannot supply an unstaffed human response.
One question for your next team meeting
When a person sees that their device has sent information, does their expectation of what happens next match the service we have actually arranged?
Supporting references
- Operational Implementation of Remote Patient Monitoring Within a Large Ambulatory Health System: Multimethod Qualitative Case Study (opens reference preview; direct link opens in a new tab)
JMIR Human Factors · 2023-07-27
Published July 27, 2023. Qualitative evidence from one health system; interviews and speculative workshops explored perspectives rather than proving clinical outcomes. Service-planning examples here are genus interpretation.
