A motion sensor notices that an older adult has not entered the kitchen by their usual breakfast time. A wearable device detects a possible fall. A home-based monitoring system identifies a change in nighttime activity that might indicate deteriorating health. Each technology offers a potential opportunity to respond earlier, reduce unnecessary intervention, and support people to remain in their own homes.
Yet the same information can reveal when someone sleeps, eats, receives visitors, leaves home, or chooses not to follow an established routine. In Home- and Community-Based Services (HCBS), the boundary between helpful observation and intrusive surveillance is therefore not simply a technical question. It is a question about rights, authority, relationships, and who ultimately controls everyday life.
This tension sits at the center of the wider Innovation, Pilots & Emerging Models Knowledge Hub, where new approaches to community support need to be evaluated against the outcomes they deliver rather than the sophistication of the technology involved.
The strongest opportunity for technology-enabled care is not continuous observation for its own sake. It is the selective use of reliable information to support decisions that people understand, influence, and benefit from. Equally, the principles of rights, consent, and decision-making cannot be treated as secondary safeguards added after a monitoring system has already been purchased.
For Medicaid agencies, managed care organizations, providers, families, and people receiving support, the central challenge is to establish when monitoring expands independence, when it genuinely improves safety, and when it begins to substitute institutional control for community living.
1. Remote Monitoring Is Becoming Part of the Infrastructure of Community-Based Care
Remote monitoring in HCBS encompasses a range of technologies with different purposes, levels of intrusion, and operational consequences. Some devices provide a straightforward alert when a person requests assistance. Others collect environmental or physiological information, identify changes in routine, or transmit information to caregivers and provider teams. Emerging systems may combine multiple data sources to generate predictions about future risks.
These technologies are not interchangeable. A personal emergency response button depends on the person activating it. A fall-detection device attempts to identify an event automatically. A passive sensor may infer activity from movement or appliance use. Video monitoring can capture substantially more intimate information, while audio-enabled systems may expose conversations involving other household members or visitors.
The distinction matters because a system's technical capabilities determine the kinds of information collected, but its operating model determines how that information affects a person's life.
A device that alerts a trusted contact when someone requests help may strengthen autonomy. A system that automatically informs multiple professionals whenever the person leaves home could create pressure to restrict ordinary activity, even where no immediate danger exists.
In practice, monitoring can serve several legitimate functions:
- Emergency response: identifying or communicating events requiring prompt assistance.
- Health-related observation: supporting appropriate clinical review of changes in symptoms or physiological indicators.
- Daily living support: identifying agreed changes in activity that may warrant a supportive check-in.
- Environmental safety: detecting hazards such as smoke, extreme temperatures, or certain equipment failures.
- Service continuity: providing information relevant to the timely delivery of authorized support.
These purposes should not be merged into a single broad authorization to monitor a person's home. Each requires a separate assessment of necessity, consent, proportionality, information access, and response arrangements.
The operational starting point is therefore not which device offers the most features. It is what problem needs to be addressed, whether monitoring is an acceptable response for the individual, and what less intrusive alternatives have been considered.
2. The Federal-State Framework Sets Important Boundaries Without Creating One National Monitoring Model
Medicaid-funded HCBS operates through multiple authorities, including state plan services, Section 1915(c) waivers, and other approved arrangements. States determine many aspects of covered services, provider qualifications, payment methodologies, and implementation within the applicable federal framework. Some states use managed long-term services and supports arrangements, while others rely on fee-for-service administration or combinations of delivery models.
Remote monitoring may be addressed through state-specific assistive technology, personal emergency response, electronic support, telehealth-related, or other benefit provisions. Coverage, service definitions, prior authorization, documentation, and provider qualifications vary. A technology funded under one state's waiver cannot be assumed to be reimbursable under another state's program.
The federal HCBS settings requirements are especially relevant where monitoring affects privacy, autonomy, choice, or freedom of movement. The settings framework emphasizes community integration, individual rights, and person-centered service planning. Additional requirements apply to provider-owned or controlled residential settings, including protections relating to privacy and autonomy. Modifications to certain residential-setting conditions must follow applicable individualized, assessed-need and documentation requirements.
However, the settings rule does not establish a single national consent form or authorize every proposed monitoring practice. State law, applicable Medicaid requirements, residential licensing, contractual provisions, and other legal protections must also be considered.
Nor should monitoring be confused with electronic visit verification (EVV). Federal EVV requirements apply to specified Medicaid-funded personal care and home health services and concern verification of service visits. They do not create general permission to track beneficiaries continuously or observe their private activities.
Privacy law adds further complexity. HIPAA may apply when protected health information is handled by covered entities or business associates, but not every technology vendor or family-operated monitoring arrangement falls within the same legal relationship. State privacy, consumer protection, disability rights, recording, and surveillance laws may impose additional obligations.
Providers therefore need a jurisdiction-specific analysis rather than an assumption that purchasing a healthcare-oriented product establishes compliance. The Regulatory Readiness Gap Analyzer can help organize a review of applicable requirements, evidence gaps, and oversight responsibilities, while formal legal and regulatory interpretation remains with appropriately qualified advisers and authorities.
3. Independence Must Be Defined by the Person, Not by the Technology
The strongest case for remote monitoring is that it may enable someone to live with less unwanted intervention. A person who previously received repeated overnight checks might prefer an agreed environmental alert that allows uninterrupted sleep. Someone with a physical disability may value a reliable way to summon assistance without waiting for a scheduled visit. An older adult may feel more confident living alone when they know help can be requested promptly.
Yet independence is not synonymous with reduced staff presence. Some people experience regular human contact as an essential part of wellbeing, community connection, and reassurance. Others may value privacy more highly than the additional protection offered by monitoring. A person may accept one type of device while rejecting another.
Meaningful person-centered planning establishes the individual's own priorities before identifying technology options. This includes exploring what information the person is comfortable sharing, which events justify an alert, who should receive it, and what should happen afterward.
For people with intellectual and developmental disabilities, communication differences must not be mistaken for an absence of preference or decision-making ability. Accessible explanations, practical demonstrations, supported decision-making, and opportunities to reconsider a choice are important safeguards. The principles underlying supported decision-making in IDD services are particularly relevant when a monitoring proposal originates with a family member, guardian, or provider rather than the person receiving support.
Where a legally authorized representative is involved, the scope of that person's authority and the individual's retained rights require careful consideration under applicable law. Family concern, professional preference, or organizational convenience does not automatically justify intrusive monitoring.
The Positive Risk Enablement Planner offers a practical structure for exploring how autonomy, foreseeable risk, safeguards, and individual preferences can be considered together. Its value lies in supporting transparent reasoning, not in replacing the person's decision or determining legal authority.
4. Scenario: Replacing Overnight Checks Without Replacing Personal Choice
Consider an illustrative HCBS arrangement involving an adult with a physical disability who lives in an apartment and receives Medicaid-funded personal assistance. The person has become frustrated by repeated overnight checks that interrupt sleep, but their support team remains concerned about their ability to obtain assistance following a fall.
A provider proposes a combination of a personal emergency response device and a limited movement alert. The initial proposal would notify staff whenever the person leaves the bedroom after midnight. During planning discussions, the individual explains that they frequently get up to read or prepare a drink and do not want those activities reported.
The team revises the proposal. The individual agrees to a wearable emergency response function and a narrowly configured alert for a specific circumstance that they identify as concerning. Routine nighttime movement is not monitored for staff review. The person chooses which contacts receive alerts and agrees on how a responder should communicate before entering the apartment.
The service coordinator checks whether the proposed equipment and related services are covered under the applicable state program and whether any authorization or plan amendment is needed. The provider documents the individual's preferences, alternative options, device limitations, response arrangements, and review date.
During the first month, the device generates two false alerts. Staff review the incidents with the person rather than automatically expanding monitoring. A technical adjustment reduces unnecessary notifications, although the team continues to assess reliability.
The meaningful outcome is not simply that fewer overnight visits occurred. It is that the person reports better sleep, retains control over ordinary nighttime activities, and has an agreed route to assistance. The example illustrates how positive risk-taking and least restrictive practice can guide technology decisions without ignoring genuine safety needs.
5. The Operational Difference Between Detection and Effective Response
A remote monitoring system may identify an event without ensuring that anyone responds appropriately. This is one of the most important distinctions for provider executives and Medicaid purchasers.
An alert can be technically successful while the service response fails. A fall-detection system might transmit information immediately, but the designated responder may be unavailable. A monitoring center might contact the wrong number. An alert may be classified as low priority despite a significant change in the person's condition. A family caregiver may be expected to respond without having agreed to provide continuous availability.
Consequently, monitoring arrangements require a clearly defined operational pathway. Providers need to understand which alerts are informational, which require timely follow-up, which demand immediate emergency action, and which fall outside the provider's responsibility.
Response arrangements should distinguish routine observation from clinical assessment and emergency intervention. A DSP or monitoring-center employee may be able to contact a person and follow an established escalation protocol, but that does not necessarily authorize independent clinical interpretation or changes to treatment.
Alert thresholds also require attention. Excessive notifications create alarm fatigue, while overly restrictive thresholds may fail to identify meaningful changes. Both problems become more serious when staffing levels are stretched or responsibilities are divided between providers, technology vendors, health plans, and family members.
Effective crisis prevention and escalation therefore depends on the connection between information, human judgment, and available response capacity.
The provider's evidence should demonstrate more than device activation. It should show that response responsibilities are understood, contact details are current, staff are competent, exceptions are reviewed, and failures lead to operational improvement.
6. Medicaid Funding, Service Authorization and the Economics of Monitoring
Remote monitoring is frequently presented as a way to reduce avoidable costs. It may help prevent certain emergencies, support earlier intervention, or reduce the need for some routine checks. However, the economic case depends on the population, service model, state coverage arrangements, and quality of implementation.
Medicaid reimbursement is not automatic simply because a device is clinically useful or commercially available. States may define covered equipment, installation, ongoing monitoring, maintenance, and associated support differently. Some arrangements require assessment, prior authorization, specified provider qualifications, or inclusion in an approved person-centered service plan.
In managed care systems, the MCO may have additional responsibilities relating to benefit administration, network arrangements, care coordination, and contracted monitoring services. The precise division of responsibility depends on state contracts and approved benefit structures. In fee-for-service arrangements, providers may instead work directly with state authorization and billing processes.
Medicare may cover certain remote physiological monitoring services when applicable coverage and billing conditions are met, but those arrangements should not be conflated with Medicaid HCBS environmental monitoring or personal emergency response benefits. Dual eligibility does not make the funding streams interchangeable.
There are also costs beyond the device itself: connectivity, installation, accessible training, monitoring-center capacity, software subscriptions, cybersecurity, equipment replacement, staff time, false alerts, and emergency response coordination.
A credible return-on-investment assessment considers both financial and human outcomes. Reduced staffing expenditure cannot be treated as a benefit if it results in loneliness, delayed assistance, or deterioration in quality of life.
Payment incentives deserve particular scrutiny. A provider paid primarily to reduce service utilization could face pressure to substitute monitoring for authorized personal assistance. Conversely, a reimbursement structure that funds equipment but not the necessary response infrastructure may encourage adoption without dependable service delivery.
Strong purchasing arrangements specify what the technology is expected to achieve, how individual choice is protected, who funds the response, and how unintended consequences will be identified. Where savings are claimed, the analysis should distinguish genuine avoided need from unmet need that has become less visible.
7. Scenario: A Managed Care Pilot Produces Savings but Raises Questions About Unmet Need
Imagine a state-authorized managed long-term services and supports pilot in which an MCO offers passive home monitoring to a group of older adults who receive HCBS. The pilot is designed to identify emerging problems earlier and reduce avoidable emergency department use.
After six months, the plan reports fewer emergency visits among participants and lower expenditure on certain scheduled support activities. The technology supplier presents the results as evidence that the model should be expanded.
However, the MCO's quality team identifies important limitations. Participants were not randomly assigned, some individuals had greater family support than others, and the analysis did not adequately account for differences in health status. Several people also reported that they had become less confident about requesting in-person assistance because they believed monitoring was intended to replace visits.
The plan reviews authorization records, service changes, grievances, emergency response logs, and participant interviews. It discovers that one provider had reduced routine contact without documenting individualized reassessment or confirming that the reduction was consistent with the person's authorized services and preferences.
The MCO pauses expansion and requires the provider to review affected service plans. The pilot evaluation is revised to include unmet need, participant-reported autonomy, caregiver workload, false alerts, and response reliability alongside utilization and expenditure.
Some participants still report meaningful benefits, particularly where monitoring supports earlier contact without reducing desired services. The pilot is not abandoned, but its claims become more precise.
The lesson is that pilot evaluation and learning must test the consequences of the operating model, not merely whether the technology generates alerts or appears to reduce expenditure.
8. Privacy, Consent and the Architecture of Digital Surveillance
Remote monitoring can create an unusually detailed record of private life. Even systems that do not capture images or conversations may reveal patterns of sleep, movement, visitors, household activity, and absence from home. When combined with other information, apparently limited data can become highly revealing.
Privacy protection therefore begins with system design. Providers and purchasers should examine what information is collected, whether each data element is necessary, how long it is retained, who can access it, and whether the technology permits secondary uses unrelated to the agreed support purpose.
Consent is particularly complicated when monitoring operates continuously. A person may understand the initial purpose but not appreciate the implications of long-term data accumulation, software updates, or changes in access permissions. A decision made during a hospital discharge or service crisis may also be influenced by pressure to accept whatever arrangement appears to make community living possible.
Meaningful consent processes should be accessible, specific, and revisited when circumstances change. They should explain the limits of the technology as well as its potential benefits. Where consent is not the applicable legal basis, organizations still need to establish the relevant authority, rights protections, and requirements under the governing framework.
The principles of privacy-by-design and risk mitigation require decisions about data minimization and access before deployment rather than after a complaint or breach.
For example, a provider supervisor may need confirmation that an emergency alert was acknowledged without requiring unrestricted access to the individual's full movement history. A service coordinator may need information about an agreed change in support needs rather than continuous access to sensor activity. A vendor may need technical diagnostic information without requiring identifiable records beyond what is necessary.
Information-sharing agreements, role-based access, audit logs, retention schedules, and incident response procedures should reflect these distinctions. Where HIPAA applies, relevant business associate arrangements and security obligations must be addressed. Other legal and contractual requirements may apply where HIPAA does not govern the entire relationship.
Additional care is needed in shared housing. One person's monitoring arrangements may capture information about roommates, staff, visitors, or family members. Their interests cannot be disregarded simply because the device was installed for another resident's benefit.
Remote monitoring becomes surveillance when observation expands beyond a justified purpose, when people cannot meaningfully challenge its use, or when information is used to control behavior rather than support agreed outcomes.
9. Scenario: Monitoring in a Shared Home Creates a Rights Conflict
Consider an illustrative supported living arrangement for three adults with intellectual and developmental disabilities. One resident has experienced several nighttime falls. Their family asks the provider to install a camera in a shared hallway so staff can identify when the resident leaves their bedroom.
The provider initially views the proposal as a straightforward safety intervention. During consultation, however, another resident explains that the hallway connects their bedroom to the bathroom and that they do not want their movements recorded. A third resident is concerned that visitors could be observed.
The service coordinator and provider review the individual's assessed needs, the proposed camera's field of view, applicable residential requirements, and alternative arrangements. The team explores a personal emergency response option, environmental adjustments, targeted staff support, and a device that does not record identifiable images of other residents.
The family remains concerned that a less intrusive solution may provide weaker protection. The provider acknowledges that concern but explains that one resident's support needs do not automatically override the privacy rights of others.
A narrower monitoring arrangement is eventually agreed for a trial period, with clear limitations on data access and an identified response protocol. The person's service plan records the reasoning and review arrangements. The provider also checks whether the proposed intervention triggers any applicable state-specific requirements concerning restrictive practices or residential-setting modifications.
At review, the team considers fall incidents, response reliability, the person's experience, and feedback from housemates. The arrangement is retained only to the extent that its benefits and proportionality remain demonstrable.
This scenario shows why IDD risk and restrictive-practice governance cannot be separated from technology procurement. The least intrusive technically feasible option may also be the more defensible operational choice.
10. Workforce Roles Change When Information Arrives Between Scheduled Visits
Monitoring does not eliminate workforce responsibilities. It changes when information becomes available and may create new expectations about responsiveness.
A traditional home care model often organizes activity around scheduled visits, documented tasks, and agreed escalation procedures. Remote monitoring introduces events that may occur at any time. Someone must determine whether an alert requires action, whether a change in routine is meaningful, and whether information should be shared with a clinician, family member, or emergency service.
These responsibilities can fall between established roles. DSPs may be asked to interpret dashboards without appropriate training. Supervisors may assume that a vendor's monitoring center is managing risk. Families may receive notifications that they cannot realistically respond to while working or sleeping.
Workforce redesign should therefore clarify the distinction between technical observation, routine support, clinical judgment, and emergency response. Staff competence needs to be demonstrated through realistic scenarios and observed practice, not simply completion of an online device tutorial.
The workforce innovation and role redesign implications extend to staffing models, supervision, out-of-hours coverage, and the relationship between remote and in-person support.
Technology can reduce unnecessary travel or repetitive checks, but the resulting capacity should not be assumed to translate directly into staffing reductions. Providers may need additional coordination time, technical support, and specialist oversight, particularly during implementation.
Staff also need permission to question the system. A DSP who notices that alerts are inconsistent with the person's observed wellbeing should be able to raise concerns without being told that the technology is inherently more reliable than professional experience.
The mature operating model treats monitoring information as one source of evidence within a relationship-based service, not as an automated substitute for understanding the person.
11. Reliability, Cybersecurity and Continuity Are Direct Care Risks
Remote monitoring creates dependencies that may not exist in traditional support arrangements. Devices require power, connectivity, maintenance, correct configuration, and reliable communication channels. Software platforms may depend on external hosting, third-party integrations, or subscription services.
Failure can be subtle. A device may appear active while transmitting incomplete information. A battery warning may be overlooked. A software update may change alert behavior. A provider may discover that a vendor has discontinued support for equipment still used by vulnerable individuals.
Cybersecurity incidents can also become service incidents. Unauthorized access may expose intimate personal information, while ransomware or platform outages may interrupt monitoring or prevent staff from retrieving necessary information.
Provider and payer due diligence should examine vendor security controls, service availability, incident notification arrangements, data portability, subcontractors, maintenance obligations, and exit planning. Contractual assurances are important, but organizations also need to test how failures affect actual service delivery.
The Digital Transformation, AI and Cybersecurity Readiness Assessment can support a structured examination of technical capability, workforce readiness, supplier dependencies, information governance, and continuity planning.
A strong business continuity and operational resilience approach establishes what happens when monitoring becomes unavailable. This may include temporary increases in in-person contact, alternative communication methods, manual checks, or emergency escalation arrangements appropriate to the individual's needs.
Importantly, contingency arrangements must be practical within the provider's staffing and geographic footprint. A rural service cannot assume that an employee can reach every monitored household immediately, and a family caregiver should not be treated as an unlimited backup resource.
12. From Alerts to Predictive Monitoring: A New Accountability Threshold
Established monitoring technologies generally identify an event, transmit a signal, or display information for review. Emerging systems may attempt to recognize patterns associated with deterioration, falls, behavioral distress, or changes in daily functioning.
Predictive capability could offer significant benefits where it supports earlier, proportionate intervention. A change in mobility patterns might prompt a conversation about pain, medication effects, or environmental barriers before a serious fall occurs. A sustained change in activity might lead a care coordinator to check whether the person's existing support remains appropriate.
However, predictions introduce uncertainty. An algorithm may identify correlations without explaining the cause. A change in routine may reflect a new hobby, a visitor, a religious observance, or a personal choice rather than deterioration. Systems trained on one population or living environment may perform differently elsewhere.
These limitations become especially important when predictive outputs influence service authorization, staff allocation, or judgments about a person's ability to live independently.
In the foreseeable future, providers may encounter systems that automatically prioritize alerts or recommend follow-up actions. Such capabilities should be distinguished from autonomous clinical decision-making or automatic restrictions on services. Human review remains essential when a recommendation could materially affect rights, care, safety, or access.
Organizations considering AI and automation in care should require evidence about validation, false positives, missed events, subgroup performance, model updates, and the circumstances in which human judgment overrides the system.
The key governance question is not whether an algorithm can predict a problem. It is whether the prediction is sufficiently reliable, actionable, and proportionate to justify the intervention that follows.
13. Scenario: A Predictive Alert Misinterprets a Change in Daily Routine
Imagine an older adult receiving HCBS who has agreed to passive monitoring following a period of recurrent falls. The system establishes a baseline of household activity and later generates an alert because the person has been leaving home earlier and returning later than usual.
The monitoring platform classifies the change as potentially concerning. A supervisor initially suggests that additional checks may be necessary, while a family member asks whether the person is becoming confused.
Before changing support arrangements, the assigned care coordinator contacts the individual. The person explains that they recently joined a community gardening group and now leave home several mornings each week. They are pleased with the activity and do not want staff or relatives questioning every trip.
The coordinator confirms that the individual understands the monitoring arrangement and asks whether the alert settings should be adjusted. The person agrees to retain emergency-related functions but requests that routine departures no longer generate notifications to family members.
The provider records the discussion and reviews whether the monitoring system can distinguish meaningful safety events from ordinary changes in lifestyle. The quality team examines whether similar false alerts disproportionately affect people who are socially active or whose routines differ from the population used to configure the system.
The case becomes part of a wider review of trust, transparency, and ethical data use. Staff are reminded that deviations from a statistical baseline are not, by themselves, evidence of incapacity or unsafe behavior.
The strongest outcome is that the person's increased community participation is recognized as a positive development rather than treated as a monitoring problem.
14. Governance and Assurance Must Examine Consequences, Not Just Device Performance
Provider boards, executive teams, state agencies, and MCOs need assurance that remote monitoring is producing the intended benefits without creating unacceptable risks. Device uptime, installation numbers, and alert volumes provide useful operational information, but they do not establish whether people are safer or more independent.
A mature assurance framework connects technical performance with service response, participant experience, rights protection, and outcomes.
Relevant evidence may include:
- Choice and consent: whether people understand the arrangement, influence its configuration, and can request review.
- Response reliability: alert acknowledgment, appropriate escalation, missed events, and unresolved notifications.
- Rights and privacy: access exceptions, complaints, unauthorized disclosure, and concerns about restrictive use.
- Service continuity: whether monitoring supports or displaces necessary in-person assistance.
- Outcomes and equity: participant-reported independence, safety, community participation, and variation between groups.
- Technical resilience: outages, device failures, cybersecurity events, and successful contingency responses.
These indicators need interpretation. A high alert volume may indicate effective detection, poor configuration, increased need, or unnecessary intrusion. A low complaint rate may reflect satisfaction, but it may also reflect inaccessible complaints processes or uncertainty about whether monitoring can be challenged.
The Quality Dashboard Builder can help leadership teams organize a balanced set of operational, experience, quality, and outcome indicators. Its usefulness depends on the validity of the underlying data and the decisions taken in response.
Boards should also understand how monitoring risks are owned across the organization. Clinical leaders may oversee health-related escalation, operational managers may own response capacity, privacy officers may oversee information protection, and executives may be accountable for supplier performance and strategic investment.
Where responsibilities cross organizational boundaries, risk ownership and assurance lines should identify who investigates a failure, who approves corrective action, and who confirms that improvement has been sustained.
People receiving services should have a meaningful role in governance. Their accounts of feeling safer, more independent, watched, or pressured provide evidence that technical dashboards cannot capture.
15. Complaints, Incidents and Corrective Action Reveal Whether Safeguards Work
Monitoring-related concerns may first emerge through routine conversations rather than formal incidents. Someone may report that staff know too much about their daily activities. A family caregiver may complain about constant notifications. A DSP may notice that a device is generating misleading information. A person may feel unable to refuse monitoring because they fear losing support.
These concerns should be taken seriously even where no technical fault has occurred. A system can function exactly as designed while still being inappropriate for the person or setting.
When a serious incident occurs, the provider should distinguish immediate protective action from longer-term improvement. A missed emergency alert may require urgent support, notification under applicable state or contractual requirements, preservation of relevant records, and review of the response pathway. Suspected abuse, neglect, exploitation, or other reportable concerns may require external notification to the appropriate authorities; internal investigation alone may be insufficient.
Corrective action should examine the interaction between technology and service design. Was the alert threshold appropriate? Was the person informed? Were responders available? Did the vendor meet its obligations? Did staffing arrangements make timely action realistic?
Where repeated failures occur, the Quality Improvement Action Plan Builder can support the translation of findings into accountable actions, implementation checks, and sustained monitoring.
Strong incident reporting and learning also requires organizations to examine whether problems recur across devices, service locations, populations, or vendor arrangements. Replacing one faulty device may resolve an immediate problem without addressing weaknesses in training, procurement, escalation, or oversight.
The assurance test is whether changes in policy and equipment produce demonstrable changes in practice and outcomes.
16. Equity, Digital Inclusion and the Risk of Creating Two Standards of Community Support
Remote monitoring may expand access in communities where specialist services are difficult to reach. It may support people living in rural areas, reduce unnecessary travel, and enable more flexible contact between scheduled visits.
Yet these benefits depend on infrastructure and individual circumstances. Reliable broadband, cellular coverage, electricity, suitable housing, accessible devices, and technical assistance are not evenly distributed. People with limited income may face costs that are not fully covered by the applicable benefit. Individuals with sensory, cognitive, or communication disabilities may encounter products that were not designed around their needs.
Language access also matters. Consent materials, device instructions, alerts, and customer support may be inaccessible to people who do not use English as their primary language.
The danger is that technology becomes an assumed substitute for in-person care in communities where workforce capacity is already constrained. People who have the resources to purchase additional support may retain meaningful choice, while others may be offered monitoring as the only practical option.
Addressing digital exclusion and access requires more than distributing devices. Providers and purchasers need to assess whether people can use, understand, maintain, and challenge the technology throughout its operating life.
Equity analysis should also examine who is most frequently monitored, whose activities generate the greatest number of alerts, and whether some populations experience more restrictive responses than others. Differences may reflect genuine need, but they may also reveal bias in service design or technology configuration.
For state Medicaid agencies and MCOs, equitable implementation means evaluating whether monitoring expands options across the population rather than concentrating intrusive alternatives among people with fewer resources or less influence over service decisions.
17. The Next Phase: From Monitoring People to Supporting Better Decisions
The future of remote monitoring in HCBS is likely to involve more integrated information, improved sensor capabilities, and increasingly sophisticated decision support. Some systems may connect environmental information with care coordination records, while others may help identify patterns that warrant preventive outreach.
These developments are plausible directions rather than a uniform national operating model. Their adoption will depend on state Medicaid policy, reimbursement, privacy protections, technology validation, provider capacity, and participant acceptance.
The more promising direction is selective monitoring designed around specific decisions. Rather than collecting every available data point, systems could focus on information that enables an agreed response, provides clear value, and can be explained to the person concerned.
Future procurement may place greater emphasis on configurable privacy settings, interoperable records, independent performance evaluation, accessible interfaces, and the ability to discontinue a vendor without losing essential service information.
State agencies and MCOs may also develop more sophisticated purchasing arrangements that evaluate participant experience and outcomes alongside utilization. However, payment innovation will require reliable measures and safeguards against reducing authorized support simply because monitoring creates an appearance of coverage.
For providers, the strategic opportunity is to integrate technology with skilled relationships, responsive workforce models, and accountable governance. Systems that generate more information than organizations can interpret or act upon are unlikely to deliver sustainable value.
The strongest emerging models will make it easier for people to obtain assistance when they want it, retain privacy when they do not, and challenge decisions that affect their lives.
Conclusion
Remote monitoring has genuine potential to strengthen Home- and Community-Based Services across the United States. Properly designed, it can support timely assistance, reduce unnecessary interruptions, improve confidence, and help people remain in homes and communities of their choosing. For some individuals, a limited monitoring arrangement may provide greater freedom than repeated in-person observation.
But these benefits cannot be assumed from the presence of technology. A device that improves detection without ensuring response offers incomplete protection. A system that reduces service expenditure while increasing unmet need cannot be described as successful. Monitoring that captures intimate information without meaningful choice, proportionality, or accountability risks undermining the very independence that HCBS is intended to support.
The federal Medicaid framework establishes important rights and program boundaries, while state implementation, payer arrangements, provider operations, and individual service planning determine how those principles work in practice. Strong governance connects these layers through clear responsibilities, dependable escalation, privacy safeguards, workforce competence, and evidence of real outcomes.
The next generation of remote monitoring should therefore be judged less by how continuously it observes people and more by how effectively it supports informed choice, appropriate assistance, and community participation.
The defining question is not whether technology can see more of a person's life. It is whether the person gains greater control over that life as a result.
0 comments