Care coordination in U.S. community-based services is partly an information problem, partly an operational problem and fundamentally a human one. A coordinator may need to understand a person's goals, authorized services, changing health needs, housing situation, transportation barriers, behavioral health support, family circumstances, provider capacity and multiple organizations' responsibilities. Much of that information may sit in different systems, arrive at different times and use different terminology.
That makes care coordination an important frontier for the Innovation, Pilots & Emerging Models Knowledge Hub. Artificial intelligence could increasingly organize records, summarize changes, identify unresolved referrals, prompt follow-up, support navigation and help coordinators see patterns that fragmented systems make difficult to detect. The emerging field of AI and automation in care therefore raises a more consequential question than whether software can reduce administration: could some of the coordinating function itself become digitally augmented?
The answer depends on what is meant by coordination. Information retrieval and routine follow-up are different from negotiating competing preferences, recognizing coercion, understanding why a person no longer trusts a service, balancing autonomy with safety or challenging an authorization decision. In complex community support, effective coordination also depends on care coordination and information governance. AI may become increasingly capable of supporting the coordinator. That does not mean the coordinator's accountability, judgment or relationship with the person can simply be automated away.
Care Coordination Is Not One Function
The term “care coordinator” can describe very different roles across the United States. Depending on the state, program and payer, coordination may be undertaken by a Medicaid case manager, MCO care manager, service coordinator, supports coordinator, health-plan employee, provider-based coordinator, community health worker, behavioral health professional or another designated role. Some people receiving self-directed services may exercise much greater control over how supports are organized, while families, guardians and advocates may also participate.
Federal Medicaid frameworks establish important parameters around covered services, person-centered planning and program administration, but states determine substantial elements of benefit design, waiver structures, delivery systems and operational processes. Some populations receive LTSS through managed care; others remain within fee-for-service arrangements. Responsibilities may be divided between state agencies, MCOs, county systems, providers and other entities. An AI system cannot safely “become the coordinator” without first understanding which coordinating function it is actually performing and under whose authority.
That distinction creates a useful way to think about automation. Care coordination contains at least four layers:
- administrative coordination, including scheduling, reminders, document retrieval and routine status checks;
- information coordination, including assembling records, identifying changes and maintaining a coherent view across services;
- decision support, including highlighting risks, options, gaps and issues requiring professional review; and
- relational and accountable coordination, where judgment, advocacy, negotiation, rights, consent, trust and responsibility become central.
AI is likely to advance furthest and fastest across the first three layers. The fourth creates a much higher threshold because the issue is no longer whether technology can generate a plausible recommendation. It is whether the system can legitimately hold responsibility for decisions affecting a person's life.
From Administrative Assistant to Coordination Intelligence
Many immediate opportunities do not require autonomous decision-making. A digitally augmented coordination platform could summarize a long case history before a review, identify that an authorized service has not started, detect that a specialist referral remains open, remind a coordinator that a reassessment is approaching or bring together information from several records for human review.
Generative AI could reduce the time spent searching lengthy notes and converting fragmented information into summaries. Predictive analytics could identify patterns suggesting that a person's support arrangement is becoming unstable. Workflow automation could route routine tasks. Conversational systems could help people understand services, prepare questions or navigate common processes outside office hours.
These capabilities become more valuable when they reduce work that currently competes with meaningful contact. The strongest case for automation is not necessarily fewer coordinators. It may be giving coordinators more time for the activities that require a person: listening, visiting, observing, resolving disagreement, advocating, challenging assumptions and understanding what matters beyond the record.
Organizations considering that transition can use the Digital Transformation, AI and Cybersecurity Readiness Assessment to examine whether their data, governance, workforce capability, security arrangements and operational infrastructure are mature enough to support technology-enabled care. An organization with fragmented records and weak information controls does not become digitally mature simply by adding an AI interface.
The Data Problem Comes Before the AI Problem
An AI coordinator can only reason from the information available to it. Community-based support frequently crosses Medicaid, physical health, behavioral health, pharmacy, housing, transportation, social services and community organizations. Even where information can lawfully be exchanged, technical interoperability does not guarantee that it is complete, timely or meaningful.
A record may show that personal care was authorized without showing that the provider cannot staff the hours. Claims may eventually confirm service delivery but arrive too late for immediate coordination. Encounter data may describe an activity without capturing whether it achieved the person's goal. A hospital record may document discharge while the community provider knows that the home environment has changed. A case-management note may contain the crucial information, but only as unstructured text.
This is why data quality, integrity and audit readiness become safety issues rather than technical housekeeping. An AI system may summarize inaccurate information with exceptional fluency. It may connect incomplete data more quickly than a human without making the resulting conclusion more reliable.
Strong implementation therefore requires provenance: users need to understand where important information came from, how current it is, what may be missing and whether a generated conclusion is an inference rather than an established fact. Where the underlying record is contested, the technology should not convert uncertainty into apparent certainty.
Scenario: An Older Adult Returning Home
Consider an older adult with multiple chronic conditions returning home after hospitalization. She receives Medicaid-funded personal assistance, has a daughter who helps with groceries and appointments, and has recently become less steady when walking. The discharge record changes several medications, a home health referral is made, and transportation is needed for follow-up. Her personal care agency does not automatically receive all hospital information.
An AI-enabled coordination layer could assemble available discharge information, compare medications with the existing record, identify the outstanding home health referral, flag that no transportation arrangement is recorded and prompt the coordinator to verify whether authorized personal assistance remains sufficient. It could create a concise briefing rather than requiring the coordinator to reconstruct the transition manually.
But the system cannot safely infer from the daughter’s involvement that she is willing or able to provide additional unpaid care. Nor should a prediction of elevated fall risk automatically reduce independence or trigger a more restrictive support arrangement. The coordinator still needs to speak with the woman, understand what she wants, confirm what has actually happened since discharge and determine which issues require clinical or payer escalation.
The value of AI in this scenario is not that it “managed” the person. It reduced the probability that fragmented information became fragmented action. That is a potentially powerful contribution to hospital discharge and transitional care, but responsibility remains with the humans and organizations authorized to act.
Person-Centered Planning Cannot Become Algorithm-Centered Planning
Community-based support exists to help people live lives, not to optimize records. That distinction becomes especially important when AI is introduced into person-centered planning. Systems may become very good at identifying statistically common goals, recommending familiar service combinations or predicting risks from historical patterns. None of those capabilities establishes what a particular person values.
A person with IDD may choose a community activity that creates some manageable risk because friendship and independence matter more to them than eliminating every possibility of harm. Someone receiving behavioral health support may reject a service because of a previous experience that a structured dataset does not capture. A person may communicate preferences through behavior, assistive communication or trusted relationships rather than through the conventional language an AI model handles most easily.
The stronger design principle is therefore augmentation of rights, consent and decision-making, not substitution for them. AI can help organize options and surface relevant information, but significant decisions still require appropriate human authority, accessible communication, supported decision-making and routes for challenge.
For organizations working through complex choices involving autonomy and safety, the Positive Risk Enablement Planner provides a structured way to examine goals, risks, safeguards and review arrangements without treating risk elimination as the objective. That distinction becomes even more important when automated systems can make conservative recommendations appear objective.
Authorization, Eligibility and the Boundary of Automated Decision Support
One of the most important boundaries concerns decisions that determine access to publicly funded support. AI may help coordinators identify missing documentation, summarize assessment information, recognize an approaching authorization expiry or model the consequences of different service arrangements. That is different from allowing a general-purpose coordination system to determine Medicaid eligibility, establish medical necessity or autonomously approve or deny services.
The precise authorization architecture varies by state, program and payer. State Medicaid agencies may retain functions directly, delegate functions to MCOs or operate different arrangements for different populations and benefits. Clinical criteria, functional assessments, waiver rules, utilization management processes and appeal rights can all affect the pathway. AI therefore enters an existing structure of utilization management and service authorization; it does not erase that structure.
The governance test is particularly important when an algorithm influences a recommendation that a human subsequently approves. A nominal human review offers little protection if staff are expected to accept automated recommendations rapidly, cannot understand the reasoning, lack access to contrary evidence or are measured against agreement with the system. Meaningful human oversight requires both authority and practical capacity to disagree.
People also need routes to correct inaccurate information and challenge decisions through the applicable grievance, appeal or due-process framework. An automated system should not create a new layer of opacity between the person and the organization accountable for the decision.
AI Could Strengthen Closed-Loop Coordination
A persistent weakness in community systems is not necessarily failure to make referrals; it is failure to know whether anything happened afterward. A person may be referred to behavioral health treatment, primary care, housing support, transportation or another community service, yet the referring organization may not know whether the referral was received, accepted, scheduled, completed or unsuccessful.
AI and automation could make closed-loop care coordination and data exchange more manageable at scale. A system could identify referrals without a recorded response, prioritize follow-up according to urgency, reconcile messages arriving through different channels and alert a coordinator when repeated attempts have failed.
The operational benefit is significant because coordination capacity can then be directed toward exceptions rather than routine status checking. Yet the reason for an unsuccessful referral still matters. A service may have no capacity. The person may not want it. Transportation may have failed. Language access may be inadequate. An authorization may be missing. The provider may not accept the payer. A telephone number may simply be wrong.
Automation can identify the open loop; effective coordination still requires understanding why it remains open and what should happen next.
Scenario: IDD Support Across Multiple Providers
A Medicaid beneficiary with IDD lives in a supported apartment, receives employment support from another agency and uses behavioral health services. Over several weeks, support staff record disrupted sleep and increasing anxiety. The employment provider records several missed shifts. A behavioral health appointment is rescheduled twice, while the residential provider experiences turnover among familiar DSPs.
No single event appears exceptional. An AI-supported coordination system able to access appropriately governed information could bring the pattern together: workforce instability, reduced community participation, disrupted clinical follow-up and changing daily presentation. Rather than diagnosing the cause, it could identify that several domains have changed simultaneously and ask the service coordinator to review the situation.
The human response remains decisive. The person may explain that a trusted DSP left and that unfamiliar staff have changed morning routines, making work increasingly stressful. The preferred intervention might therefore involve restoring predictable support and improving communication between providers rather than escalating immediately to a more restrictive behavioral response.
This illustrates why person-centered planning in IDD services cannot be separated from predictive technology. Pattern recognition may reveal something that fragmented organizations have missed. Only engagement with the person can establish what that pattern means in their life.
Privacy, Consent and Information Governance Become Design Requirements
A highly capable digital coordinator would create little value if people could not trust how their information was being used. Community-based coordination can involve particularly sensitive information about disability, mental health, substance use, family relationships, housing, finances, daily routines and risk. Different legal and contractual requirements may apply depending on the information, organization and service involved, including HIPAA and, where applicable, 42 CFR Part 2.
AI therefore increases the importance of privacy-by-design and risk mitigation. Organizations need to understand what information enters a model, whether information is retained or used for other purposes, which users can access outputs, how vendors handle data, how consent and authorization requirements operate and what happens if information is exposed or the system is compromised.
Minimum-necessary principles also matter. A coordinator does not automatically require unrestricted access to every piece of information simply because technology makes aggregation possible. Technical capability should not silently expand organizational authority.
For people receiving support, transparency needs to be practical rather than buried in technology documentation. They should be able to understand when AI materially contributes to their support, what role it plays, what remains a human decision and how to raise concerns. Accessibility, language and digital inclusion are part of that transparency.
The Workforce Question Is More Complex Than Job Replacement
Discussion of AI frequently moves quickly to whether roles will disappear. In community-based care, a more immediate question is how roles will change. Coordinators often spend substantial time on documentation, record searching, scheduling, routine communication, authorization follow-up and repeated data entry. Reducing some of that burden could allow scarce professional capacity to move toward complex coordination and direct engagement.
That does not happen automatically. Poorly designed technology can increase workload through duplicate systems, excessive alerts, unreliable summaries and additional verification requirements. Staff may spend as much time checking AI-generated material as they previously spent producing it. Organizations may also underestimate the capability required to recognize when a fluent output is wrong.
Workforce development therefore needs to include critical use of technology: understanding system limitations, verifying important information, recognizing bias, protecting confidentiality and knowing when an automated pathway should be overridden or escalated. This is part of broader workforce innovation and role redesign, not simply software training.
The future coordinator may spend less time assembling information and more time interpreting it. Supervisors may need to review not only case decisions but how teams use automated recommendations. Provider leaders may need new roles combining service expertise, data governance and technology assurance. The organizations that gain most from AI may therefore be those that redesign work rather than merely inserting technology into existing processes.
Scenario: Behavioral Health Follow-Up Without Digital Overreach
A Medicaid MCO supports members with serious mental illness through a care-management program. One member has recently used crisis services and has missed a scheduled outpatient follow-up. Claims and encounter information, care-management records and permitted provider information indicate several recent changes. An AI system classifies the case for expedited coordinator review.
The appropriate response is not an automated message declaring the member “high risk” and prescribing a standardized pathway. A human coordinator reviews the information, contacts the member using the agreed communication method and learns that the outpatient appointment conflicted with a new work schedule. The member does not want intensive outreach; they want an evening appointment and help resolving transportation.
Technology has performed a useful triage function without defining the person's needs. The coordinator can work with the provider network to identify an accessible alternative, document the member's preference and determine whether further clinical follow-up is needed. If the system repeatedly flags missed appointments caused by unavailable evening capacity, the pattern should also reach network-management governance rather than being treated as repeated individual nonadherence.
This is where AI could strengthen integrated behavioral health and community care: not by replacing therapeutic or relational work, but by connecting individual coordination with wider intelligence about barriers in the delivery system.
Governance Has to Follow the Decision, Not the Technology
As AI becomes embedded in coordination, organizations need to know who remains accountable when it contributes to a decision. Responsibility cannot disappear into the software supply chain. A provider may purchase the technology, an MCO may specify a workflow, a state may establish program requirements and a vendor may operate the model, but each organization still needs defined accountability for the functions it controls.
Boards and executives should be able to distinguish low-risk automation from systems that materially influence access, prioritization, risk classification or care planning. Governance should examine not only whether a tool functions technically, but whether its use changes outcomes, creates disparities, generates inappropriate recommendations or alters staff behavior.
The Governance Maturity Assessment can support leadership teams in testing whether decision rights, assurance lines, escalation and accountability are sufficiently developed for more technology-enabled operating models. AI governance is strongest when it sits within established organizational governance rather than becoming an isolated technology committee.
For significant AI-enabled coordination, assurance should normally enable leaders to understand:
- which decisions the technology informs and which it cannot make;
- how frequently humans override or correct its outputs and why;
- whether accuracy and outcomes differ between populations;
- how complaints, incidents and adverse outcomes involving the system are investigated;
- what happens when the technology or data feeds fail; and
- whether people receiving services understand and trust its role.
This moves governance beyond asking whether the organization has an AI policy. The relevant question is whether it can demonstrate that AI-enabled coordination remains safe, effective, equitable and accountable in practice.
Measuring Whether AI Actually Improves Coordination
Efficiency metrics alone will not establish that an AI coordinator is successful. Faster documentation, shorter call handling or more automated contacts may reduce administrative cost without improving continuity. An organization could become highly efficient at generating reminders while people still wait for services or repeat their story to multiple agencies.
Evaluation should connect operational measures with meaningful outcomes. Relevant evidence may include referral closure, time from authorization to service commencement, avoidable coordination delays, continuity after hospital discharge, successful connection with primary or behavioral health care, unresolved service gaps, participant experience, caregiver burden, grievance patterns and disparities between populations.
The Quality Dashboard Builder can help organizations structure a balanced evidence set rather than relying on technology-use statistics alone. The critical analytical question is whether the intervention improved coordination, not whether staff used the system.
Evaluation also needs counterfactual discipline. If outcomes improve after AI deployment, leaders should examine whether the improvement came from the technology, redesigned workflows, additional staffing, better data exchange or some combination. That matters when deciding whether to scale an emerging model across populations or regions.
Payment Will Shape What Kind of AI Coordination Emerges
Technology adoption does not occur separately from reimbursement. A provider paid narrowly for face-to-face units may have little financial capacity to invest in sophisticated coordination infrastructure even when better coordination could reduce wider system costs. A health plan operating under capitation may have stronger incentives to invest where improved coordination reduces avoidable utilization, but those incentives do not automatically ensure that savings translate into better member experience or stronger community-provider capacity.
Medicaid funding structures vary significantly between states and programs. Care-management functions may be embedded in managed care contracts, waiver services, health-home arrangements, provider payments or other delivery structures. Medicare may also fund relevant coordination activities for eligible beneficiaries, particularly where people are dually eligible, but Medicare and Medicaid responsibilities should not be treated as interchangeable.
Emerging technology-enabled payment models may create additional opportunities, particularly where reimbursement increasingly recognizes ongoing digital support and measurable outcomes. The important principle within value-based care innovation is that payment should reward meaningful benefit rather than simply subsidize technology adoption.
States and plans considering AI-enabled coordination should therefore ask whether the payment model supports the human capacity needed around the technology. If automation produces more risk flags but coordinators lack time to respond, the system has created detection without intervention. If digital navigation identifies unmet needs but provider networks lack capacity, better intelligence exposes rather than resolves the underlying access problem.
Scenario: Rural Coordination Where Technology Cannot Create Capacity
A rural Medicaid program covers people across a large geographic area with limited specialist and home-based provider capacity. An AI-enabled navigation service can identify participating providers, match service requirements with available information and help coordinators prioritize unresolved needs. For one beneficiary, it identifies that several technically eligible providers exist within the network.
Human follow-up reveals a different reality. One provider is not accepting referrals, another cannot cover the travel distance and a third has a six-week workforce delay. The algorithm's directory-based answer is technically coherent but operationally false.
The coordinator records the actual access barriers and arranges an interim response within the available state and payer framework. More importantly, aggregated information from similar cases becomes evidence of a regional capacity problem. What began as an individual navigation issue can then inform network management, state oversight and decisions about rural and underserved communities.
This scenario demonstrates an important limit. AI can improve visibility of capacity, but it cannot manufacture a DSP workforce, transportation network or specialist provider. Mature systems should use coordination intelligence to expose structural problems rather than repeatedly routing individuals around them.
AI Could Connect Individual Coordination With System Learning
One of the more transformative possibilities is that future coordination systems may learn across thousands of individual pathways without reducing people to averages. Repeated authorization delays, unsuccessful referrals, provider shortages, transportation failures or discharge problems could be aggregated to reveal where system design is creating predictable friction.
That would connect frontline coordination with data-led purchasing and oversight. State Medicaid agencies and MCOs could identify where nominal network capacity differs from real access. Providers could see where internal processes repeatedly interrupt continuity. Quality teams could examine whether certain populations experience longer delays or poorer referral completion.
The danger is that learning can move in the opposite direction: historical inequities can become encoded into future recommendations. If a population has historically received less intensive support, an algorithm trained on historical utilization may interpret that lower utilization as normal need rather than constrained access. If rural referrals frequently fail, a model might learn that referral is unlikely to succeed rather than identifying the need for investment.
Human governance therefore has to ask not only whether predictions are accurate against historical data, but whether history is an appropriate standard for the future. Accuracy and fairness are related, but they are not synonymous.
Testing Future Models Before They Become Operational
The shift from administrative AI to more consequential coordination intelligence should not occur through uncontrolled experimentation on people receiving services. Organizations can test proposed workflows, decision thresholds and capacity assumptions before allowing them to influence live pathways.
The Digital Twin Scenario Modeler offers one way to structure future-state analysis around workforce capacity, service stability, demand and quality risk. Scenario modeling cannot establish how every person will respond, but it can help leaders examine the operational consequences of assumptions before scaling a new model.
For example, an organization could test what happens if automation reduces routine coordinator administration by 20 percent but increases identified follow-up work by 30 percent. It could examine whether existing teams have enough capacity to respond, whether escalation pathways become congested and whether expected efficiencies disappear once human review is included.
This is particularly important when moving from pilots to scale. A successful pilot may have unusually motivated staff, additional project support, carefully selected participants and intensive vendor involvement. Pilot evaluation and learning loops should therefore examine whether the operating model remains credible under normal workload, funding and workforce conditions.
What a Mature Human-AI Coordination Model Could Look Like
The plausible future is less likely to involve one autonomous “AI care coordinator” and more likely to involve a layered coordination environment. Routine administrative work could increasingly be automated. Conversational tools may provide navigation and education. AI may summarize records, identify unresolved actions and detect emerging patterns. Predictive systems may help prioritize human attention. Interoperability may allow information to follow people more effectively between settings.
Human coordinators would remain responsible for the parts of coordination where context, legitimacy and relationship matter most. Their role could become more specialized around complex decisions, advocacy, conflict resolution, supported decision-making, transitions, safeguarding, escalation and cross-organizational problem solving.
For that model to be credible, several conditions need to develop together: interoperable and reliable information; explicit decision rights; accessible human review; privacy and security controls; workforce competence; monitoring for differential impact; continuity arrangements when systems fail; and meaningful participation by people who receive services.
Technology suppliers also become part of the assurance environment. Providers, states and plans need sufficient understanding of model limitations, data use, update processes and incident response to govern the service they are purchasing. Contracting cannot outsource accountability for consequences.
The Future Is Likely to Be Augmented Coordination, Not Coordinator Replacement
Over the coming years, the dividing line between a case-management system and an intelligent coordination environment is likely to become less distinct. AI may increasingly interpret rather than merely store information. Systems may proactively identify tasks, summarize changes, detect coordination gaps and offer possible responses. Conversational interfaces may make navigation more accessible to some people and provide support beyond conventional office hours.
That trajectory is consistent with a wider movement toward technology-enabled care, but community-based support presents challenges that cannot be solved by technological capability alone. Medicaid programs operate through different state architectures. People move between organizations whose incentives and information systems do not always align. Community capacity is uneven. Many of the most consequential decisions involve rights, relationships and uncertainty rather than predictable transactions.
The strongest future model therefore places AI around the coordinator rather than automatically in place of the coordinator. Technology can maintain continuity of information while humans maintain continuity of accountability. It can identify patterns while people interpret meaning. It can surface options while authorized professionals and the person receiving support determine what should happen.
Some functions will undoubtedly become highly automated. Some coordination roles may be redesigned substantially. New digital navigation roles and hybrid operating models are likely to emerge. But organizations should judge progress by whether people experience more coherent support, greater control and fewer avoidable gaps—not by how closely software resembles a human coordinator.
Conclusion
AI could become a powerful part of care coordination across U.S. community-based support, but the most useful question is not whether technology can imitate a care coordinator. It is which elements of coordination can be performed more reliably by technology, which decisions require accountable human authority and how the two can be combined without weakening rights, trust or continuity.
For Medicaid agencies, MCOs and provider organizations, implementation will depend on more than acquiring an AI product. State program architecture, authorization processes, payment arrangements, interoperability, privacy, provider capacity and workforce capability will determine what is operationally possible. Governance must remain visible wherever technology influences prioritization, planning, risk or access, and people receiving services need meaningful ways to understand, challenge and shape how those systems affect them.
The strongest opportunity is an augmented model in which AI removes avoidable administrative friction, connects fragmented information and identifies coordination gaps early enough for people to act. Human coordinators can then concentrate more of their capacity on judgment, advocacy, relationships, complex decisions and system problem solving. If that balance is achieved, AI may not replace the care coordinator. It may help community-based systems finally give coordinators the intelligence, time and connectivity needed to coordinate care well.