Chartis Says Healthcare Is Moving to an Always-On Care Model. Revenue Cycle Will Have to Move With It.

Chartis’ HealthCare360 framework describes a future of continuous, AI-enabled, site-agnostic care. The RCM implication is just as important: financial workflows built around episodic encounters will have to become more distributed, automated and continuous too.

Chartis is arguing that healthcare delivery is approaching a structural redesign, not just another wave of digital tools.

Its new HealthCare360 framework describes a future in which care becomes continuous, personalized and increasingly independent of a traditional physical encounter. Agentic AI helps coordinate patients, clinicians and care settings while the health system remains the central architect of the experience.

The clinical implications are obvious. The revenue-cycle implications may be just as consequential.

Chartis sees three forces converging

Chartis points to demographic pressure, rapid technology-driven clinical innovation and a large influx of capital as forces pushing healthcare toward a new operating model.

The demographic argument is particularly stark. Chartis says one in five Americans will be 65 or older by 2035 and projects that, without action, the median health system could lose 11.1 percentage points of operating margin. That creates pressure to expand capacity without simply adding more physical infrastructure and labor.

At the same time, Chartis says AI is already moving beyond documentation assistance into care management, coordination, scheduling, symptom support and navigation. Capital from growth investors, hyperscalers and incumbent health-tech companies is accelerating that transition.

The HealthCare360 model is really an orchestration model

Chartis defines five characteristics of the emerging system: always-on personalized engagement, intelligent orchestration and navigation, care delivered anywhere, human-agentic care teams and evolving financing models that reward health management and outcomes rather than volume.

The common thread is orchestration.

Patients may move among home, virtual, asynchronous and physical settings. AI agents may coordinate pieces of that journey. Clinicians increasingly work with software agents. Financing may become less tightly linked to a discrete visit or procedure.

That is a much more fluid delivery model than the one most revenue-cycle infrastructure was designed to support.

Revenue cycle has been built around the encounter

Traditional RCM assumes something fairly linear: a patient schedules an encounter, eligibility is checked, care is delivered, charges are captured, a claim is created, the payer adjudicates it and a balance is resolved.

HealthCare360 starts to break that sequence apart.

A patient may receive asynchronous clinical support before any visit exists. An AI care manager may initiate navigation or monitoring. Services may shift among sites. A human clinician may enter only when escalation is required. Payment may increasingly depend on outcomes, attribution, episodes or longitudinal management rather than a single transaction.

Once care becomes continuous, the financial event is no longer synonymous with the clinical encounter.

That creates a new RCM infrastructure problem

The emerging stack will need to continuously answer questions that historically occurred at discrete points in the revenue cycle: Who is the patient? What coverage is active? Which network applies? What authorization is required? What entity performed the service? What should be billed? Who owns the financial risk? What evidence proves the activity occurred?

This is why RCAI has been tracking the growing importance of healthcare infrastructure layers such as provider network intelligence, programmable clearinghouse infrastructure and AI-enabled RCM orchestration platforms.

Those categories can look separate today. In an always-on care model, they begin to converge around the same requirement: machine-readable infrastructure capable of understanding the patient, provider, payer, workflow and financial context in real time.

The site-of-care shift becomes a revenue-cycle shift

Chartis explicitly argues that physical locations should no longer be the default. Care should move to the most appropriate modality and site, including home, remote and asynchronous settings.

Every shift in site of care creates downstream financial complexity. Networks differ. Contracts differ. reimbursement methodologies differ. Authorization and benefit rules can differ. Provider identity and billing entities matter. Attribution and risk arrangements become more complicated.

That means the future of distributed care is partly a data-normalization and payment-orchestration problem.

The organizations that solve that layer may become as strategically important as the applications delivering the clinical experience.

Agentic care will create agentic administration

Chartis calls out human-agentic care teams as one of the five defining features of HealthCare360. If that model scales clinically, the administrative layer is unlikely to remain primarily human.

An AI care agent scheduling a patient should be able to understand network status and benefit design. An agent recommending a site of care should understand its financial implications. An autonomous workflow initiating a service should be able to determine whether authorization is required and assemble the evidence needed to obtain it.

Clinical and administrative agents will increasingly have to share context.

That is why the distinction between “clinical AI” and “RCM AI” may eventually become less clean. The same workflow that determines what should happen next for a patient may also need to determine how that action gets authorized, documented, priced and paid.

Health systems may become the control plane

One of Chartis’ most important assertions is that established health systems will remain pivotal architects of the future model even as health-tech companies help build it.

That mirrors the RCM operating-model shift RCAI has been watching.

Rather than handing an entire function to one external platform, large health systems increasingly appear interested in owning the control layer and connecting specialized infrastructure underneath it. CommonSpirit’s planned post-Conifer model is one visible example on the administrative side.

HealthCare360 suggests the same architecture could emerge across the broader patient journey.

RCAI Take

Chartis’ HealthCare360 framework is useful because it connects several trends that are often analyzed separately: aging demographics, workforce constraints, site-of-care migration, agentic AI, consumer navigation and new financing models.

For revenue cycle leaders, the key insight is that these are not downstream clinical trends to watch from a distance.

They change the object that RCM is built to monetize.

The old revenue cycle followed an encounter.

The next revenue cycle may have to follow the patient continuously across agents, clinicians, sites, networks, contracts and financing arrangements.

That requires infrastructure that is far more programmable, interoperable and autonomous than today’s transaction-oriented stack.

If Chartis is directionally right about the future of care delivery, the next era of RCM will not simply automate the existing revenue cycle.

It will have to be redesigned around a healthcare system in which the encounter is no longer the center of everything.