The Operating Intelligence Shift: Why Senior Living Must Own Its Enterprise Memory

WEBVTT
00:00:00.160 --> 00:00:05.679
Imagine for a second, right, that you're running a business, but uh this isn't just any regular business.
00:00:06.000 --> 00:00:06.080
Right.
00:00:06.160 --> 00:00:07.280
It's way more complicated than that.
00:00:07.519 --> 00:00:08.160
Oh, exactly.
00:00:08.320 --> 00:00:18.480
It is like simultaneously a life or death healthcare facility, a massive real estate portfolio, and um a really high turnover hospitality service.
00:00:18.800 --> 00:00:19.679
All at the exact same time.
00:00:19.920 --> 00:00:20.480
All at once.
00:00:20.640 --> 00:00:30.559
And you're trying to manage all these incredibly complex operations, but to make it genuinely impossible, imagine trying to steer this ship while your own brain is deliberately fractured.
00:00:30.960 --> 00:00:32.719
Like broken into a dozen different pieces.
00:00:32.799 --> 00:00:33.840
Aaron Powell Yes, exactly.
00:00:34.079 --> 00:00:38.240
Locked in separate boxes that just completely refuse to communicate with one another.
00:00:38.320 --> 00:00:44.159
Aaron Powell Which sounds insane, but that is the actual reality for thousands of operators out there right now.
00:00:44.240 --> 00:00:45.119
Aaron Powell It really is.
00:00:45.359 --> 00:00:50.799
In the senior living and uh post-acute care industry, this is the daily reality.
00:00:50.880 --> 00:00:55.200
So today we're uncovering a hidden data war that's just raging across this sector.
00:00:55.280 --> 00:00:58.240
Aaron Powell Yeah, it's the battle for what's being called operating intelligence.
00:00:58.320 --> 00:00:58.880
Aaron Powell Right.
00:00:59.039 --> 00:01:02.880
And it might just define the entire future of healthcare technology.
00:01:03.200 --> 00:01:13.519
So our guide for this deep dive is a June 2026 white paper, along with its press release titled Beyond the Silo: The Rise of Operating Intelligence.
00:01:14.000 --> 00:01:18.959
Published by a senior CRE, which is an AI data platform based down in Dallas, Texas.
00:01:19.359 --> 00:01:19.680
Right.
00:01:19.920 --> 00:01:35.200
So we are going to explore the grand illusion of digital transformation, why a massive tech rivalry and life sciences actually predicted this exact moment, and you know, why just slapping artificial intelligence onto a broken system doesn't fix it.
00:01:35.280 --> 00:01:36.959
Aaron Powell It actually makes it exponentially worse.
00:01:37.359 --> 00:01:38.719
Kind of terrifying, honestly.
00:01:38.959 --> 00:01:40.640
But um okay, let's unpack this.
00:01:40.879 --> 00:01:45.200
To understand the cure they're proposing, we really have to correctly diagnose the disease here.
00:01:45.280 --> 00:01:46.239
Aaron Powell Yeah, totally.
00:01:46.400 --> 00:01:52.400
And the core issue is that for 20 years, operators in senior care have been sold a very specific version of modernization.
00:01:52.480 --> 00:01:54.480
Aaron Powell, which was basically just buy more software.
00:01:54.560 --> 00:01:55.040
Trevor Burrus Exactly.
00:01:55.200 --> 00:01:56.239
Just buy an app for everything.
00:01:56.319 --> 00:01:56.480
Trevor Burrus, Jr.
00:01:56.560 --> 00:01:56.719
Right.
00:01:56.879 --> 00:01:59.920
Because early on, you know, the goal was just to get off paper.
00:02:00.000 --> 00:02:01.519
The push was to digitize everything.
00:02:01.599 --> 00:02:02.319
Aaron Powell Sure.
00:02:02.560 --> 00:02:07.439
So a facility would buy an EHR, an electronic health record system, right?
00:02:07.680 --> 00:02:09.199
Just to handle their clinical docs.
00:02:09.599 --> 00:02:09.759
Yeah.
00:02:09.840 --> 00:02:18.080
And then they realized, oh, we need an EA mayor, an electronic medication administration record to tie prescriptions directly to a patient's chart.
00:02:18.159 --> 00:02:21.280
Aaron Powell So nurses wouldn't make errors, which is a good thing.
00:02:21.360 --> 00:02:22.319
Aaron Powell Of course.
00:02:22.560 --> 00:02:28.719
But then they bought a CRM to track sales and uh a totally separate scheduling system for labor.
00:02:28.800 --> 00:02:30.159
Aaron Ross Powell And a different one for payroll.
00:02:30.400 --> 00:02:31.680
And another one for the general ledger.
00:02:31.759 --> 00:02:32.400
It just kept going.
00:02:32.479 --> 00:02:35.599
Aaron Powell And look, we have to give credit where it's due, right?
00:02:35.919 --> 00:02:42.000
Every single one of those software vendors solved a very real specific workflow problem at the time.
00:02:42.080 --> 00:02:44.240
Aaron Powell Getting off paper was a necessary step.
00:02:44.639 --> 00:02:45.280
It was.
00:02:45.520 --> 00:02:48.960
But the white paper points out this massive unintended consequence.
00:02:49.199 --> 00:02:55.599
This whole era of buying a new app for every problem, it didn't result in true digital transformation.
00:02:55.680 --> 00:02:58.479
Aaron Powell No, it resulted in what they call application sprawl.
00:02:58.879 --> 00:02:59.280
Exactly.
00:02:59.439 --> 00:03:00.159
Application sprawl.
00:03:00.960 --> 00:03:04.400
Think of it like hiring an absolute all-star executive team for your company.
00:03:04.479 --> 00:03:05.599
Aaron Powell I love this analogy.
00:03:05.680 --> 00:03:05.759
Yeah.
00:03:06.000 --> 00:03:06.080
Yeah.
00:03:06.319 --> 00:03:06.560
Right.
00:03:06.800 --> 00:03:16.560
You've got the best clinical director, a brilliant finance lead, the top-tier HR manager, but you put each of them in their own individual soundproof room.
00:03:16.639 --> 00:03:18.240
Aaron Powell Then they can't talk to each other at all.
00:03:18.319 --> 00:03:18.879
Aaron Powell Right.
00:03:19.039 --> 00:03:24.000
The clinical team only sees the care info, the finance team only sees revenue.
00:03:24.240 --> 00:03:26.159
Nobody anywhere sees the whole picture.
00:03:26.240 --> 00:03:30.560
Aaron Powell And that structural isolation creates a really dangerous gap.
00:03:30.800 --> 00:03:34.800
It's a gap between where data is created and where business decisions are actually made.
00:03:34.879 --> 00:03:41.759
Aaron Powell Because if you're a regional operator overseeing, say, a dozen communities, you're managing a living ecosystem.
00:03:41.840 --> 00:03:49.919
Aaron Powell But because of these vendor-controlled application silos, you are effectively trying to steer a massive cargo ship by only looking at the wake it leaves behind.
00:03:50.319 --> 00:03:50.479
Wow.
00:03:50.639 --> 00:03:52.400
You just you don't see the warning signs in front of you.
00:03:52.479 --> 00:04:01.039
Aaron Powell No, you just see the financial or clinical aftermath, whether that's massive staff turnover or you know terrible compliance results from state regulators.
00:04:01.199 --> 00:04:01.360
Trevor Burrus, Jr.
00:04:01.439 --> 00:04:02.879
Or a sudden drop in profitability.
00:04:03.039 --> 00:04:03.759
But wait, hold on.
00:04:03.919 --> 00:04:05.439
I've seen pitches for these software platforms.
00:04:05.759 --> 00:04:06.000
Oh, sure.
00:04:06.080 --> 00:04:07.120
The sales pitches are great.
00:04:07.439 --> 00:04:07.680
Right.
00:04:07.919 --> 00:04:12.000
Every single sauce product out there sells you on their fancy analytics.
00:04:12.240 --> 00:04:13.280
They all have reporting tabs.
00:04:13.599 --> 00:04:14.000
They do.
00:04:14.319 --> 00:04:24.240
So why can't the regional operator just log into their clinical system, pull up the dashboard, and you know, look at the charts to see what's happening.
00:04:24.639 --> 00:04:30.720
Well, what's fascinating here is how the authors of the white paper actively dismantle what they call the dashboard myth.
00:04:30.800 --> 00:04:31.920
Aaron Powell The dashboard myth.
00:04:32.240 --> 00:04:32.399
Yeah.
00:04:32.560 --> 00:04:38.720
I mean, yes, you get a dashboard, but an application dashboard only answers narrow, siloed questions.
00:04:38.800 --> 00:04:41.199
Aaron Powell Bound by its own field of vision, basically.
00:04:41.279 --> 00:04:42.079
Aaron Powell Exactly.
00:04:42.319 --> 00:04:45.759
A CRM dashboard can tell you how many leads you have in the pipeline.
00:04:45.920 --> 00:04:48.480
An EHR dashboard can tell you today's bed census.
00:04:48.560 --> 00:04:50.160
Aaron Powell But those are workflow questions, right?
00:04:50.240 --> 00:04:50.639
Trevor Burrus Right.
00:04:50.879 --> 00:04:53.839
Operating intelligence, on the other hand, answers business model questions.
00:04:53.920 --> 00:04:54.240
Aaron Powell Okay.
00:04:54.399 --> 00:05:02.240
So workflow tells you what is happening in one department, but business model questions tell you how those departments are like colliding with each other.
00:05:02.319 --> 00:05:03.360
Aaron Powell Spot on.
00:05:03.519 --> 00:05:16.959
A business model question is what is the mathematical relationship between rising patient acuity on the clinical side, staffing variants on the HR side, and margin erosion on the finance side.
00:05:17.040 --> 00:05:18.879
Aaron Powell A single dashboard can't tell you that.
00:05:18.959 --> 00:05:23.600
Aaron Powell No, because the data required to answer that question lives in three different soundproof rooms.
00:05:23.680 --> 00:05:26.720
Aaron Powell Which brings up a term from the paper that really stood out to me.
00:05:26.879 --> 00:05:28.319
They call it enterprise memory.
00:05:28.399 --> 00:05:29.839
Aaron Powell Yes, enterprise memory.
00:05:29.920 --> 00:05:30.959
It's a crucial concept.
00:05:31.040 --> 00:05:35.120
Aaron Powell But wait, isn't that just a fancy buzzword for a data warehouse?
00:05:35.360 --> 00:05:38.800
Like operators have had data warehouses for a decade, right?
00:05:38.959 --> 00:05:41.040
Just dumping spreadsheets into a server.
00:05:41.120 --> 00:05:41.920
Aaron Powell Well, that's the thing.
00:05:42.000 --> 00:05:44.480
A data warehouse is often just a passive graveyard for numbers.
00:05:44.560 --> 00:05:45.759
Aaron Powell A passive graveyard.
00:05:45.839 --> 00:05:46.079
I like that.
00:05:46.160 --> 00:05:46.480
Aaron Powell Yeah.
00:05:46.639 --> 00:05:47.920
You dump historical data in there.
00:05:48.000 --> 00:05:51.600
And maybe, you know, a data scientist runs a report on it two weeks later.
00:05:51.839 --> 00:05:57.600
But enterprise memory, in the context of operating intelligence, it's active.
00:05:57.759 --> 00:05:58.399
It's continuous.
00:05:58.480 --> 00:05:59.839
Aaron Powell So it's real-time knowledge.
00:06:00.160 --> 00:06:00.319
Right.
00:06:00.560 --> 00:06:08.240
Currently, a senior living organization's actual memory, the collective knowledge of what care was delivered, what was billed, it's incredibly fragile.
00:06:08.399 --> 00:06:08.560
Trevor Burrus, Jr.
00:06:08.720 --> 00:06:11.279
Because it's scattered across PDFs and emails.
00:06:11.360 --> 00:06:12.319
Aaron Powell Exactly.
00:06:12.480 --> 00:06:16.720
And most dangerously, it's trapped in the brains of a few key regional leaders.
00:06:16.800 --> 00:06:17.839
Aaron Powell Oh, right.
00:06:18.079 --> 00:06:21.839
So when a brilliant VP of operations leaves the company.
00:06:22.319 --> 00:06:24.319
That memory just vanishes with them.
00:06:24.879 --> 00:06:25.519
Wow.
00:06:25.920 --> 00:06:27.199
That's a huge liability.
00:06:27.680 --> 00:06:27.920
It is.
00:06:28.160 --> 00:06:38.800
So the argument here is that the operator must own the canonical operating record of the entire enterprise, not just passively store data or, you know, rent access to a chart from a vendor.
00:06:38.879 --> 00:06:39.839
Aaron Powell Okay, that makes sense.
00:06:40.160 --> 00:06:46.079
And the paper actually mentioned a massive lawsuit in the life sciences space as a historical precedent for this.
00:06:46.160 --> 00:06:48.480
Aaron Powell The IQVIA and Viva systems case.
00:06:48.560 --> 00:06:49.759
Aaron Powell Yeah, that's the one.
00:06:50.160 --> 00:06:57.360
But how does a fight over pharmaceutical software predict what's going to happen to senior living operators in 2026?
00:06:57.439 --> 00:07:01.920
Aaron Powell It's actually a perfect parallel because it illustrates what happens when vendors fight over data sovereignty.
00:07:02.000 --> 00:07:03.040
Trevor Burrus Okay, break that down for me.
00:07:03.120 --> 00:07:08.560
Aaron Powell So for years, IQVIA and Viva were two absolute titans in the life sciences market.
00:07:08.800 --> 00:07:13.360
IQVIA had incredible deep data assets regarding physician prescribing habits.
00:07:13.519 --> 00:07:14.319
Trevor Burrus Right, and Viva.
00:07:14.720 --> 00:07:21.360
Viva had built the dominant CRM software platform that pharmaceutical reps actually used every single day.
00:07:21.439 --> 00:07:24.160
Aaron Powell Okay, so one had the data, one had the workflow.
00:07:24.480 --> 00:07:24.959
Exactly.
00:07:25.199 --> 00:07:30.879
And starting back in 2017, they engaged in this high-stakes, bitter litigation battle.
00:07:31.279 --> 00:07:32.160
Over who controlled what?
00:07:32.480 --> 00:07:32.639
Yeah.
00:07:32.800 --> 00:07:39.040
They were essentially restricting access to their respective systems, fighting over who got to control the rep's workflow and data.
00:07:39.120 --> 00:07:39.199
Trevor Burrus,
00:07:39.279 --> 00:07:39.279
Jr.
00:07:39.279 --> 00:07:46.639
So if the pharmaceutical companies, the actual enterprise customers who were paying millions of dollars for these tools, they were basically caught in the clos fire.
00:07:47.040 --> 00:07:48.800
Totally held hostage by their own vendors.
00:07:49.120 --> 00:07:49.680
That's crazy.
00:07:49.920 --> 00:07:50.399
It is.
00:07:50.639 --> 00:07:53.040
And that conflict dragged on for years.
00:07:53.279 --> 00:07:58.639
Until 2025, when the two companies finally announced a resolution and formed long-term partnerships.
00:07:59.040 --> 00:08:03.680
But the white paper makes a point that it wasn't just about two tech giants making nice, right?
00:08:04.000 --> 00:08:04.240
No.
00:08:04.399 --> 00:08:08.399
The significance was the market proving a fundamental economic principle.
00:08:08.639 --> 00:08:12.480
Eventually, enterprise customers will reject closed system conflict.
00:08:12.800 --> 00:08:19.040
Because large operators simply cannot run mission-critical businesses around the turf wars of their software vendors.
00:08:19.360 --> 00:08:19.839
Exactly.
00:08:20.000 --> 00:08:26.399
The customers will eventually force the market to compromise, demanding that data and workflow become mutually usable.
00:08:26.639 --> 00:08:30.879
So if you're listening to this, think about the software tools you use every day.
00:08:31.120 --> 00:08:38.240
If your vendors are actively building walled gardens to protect their market share, your business is the one paying the invisible tax.
00:08:38.559 --> 00:08:40.559
You're losing efficiency every single day.
00:08:40.879 --> 00:08:41.200
Right.
00:08:41.360 --> 00:08:46.159
And the sources are arguing that senior care is hitting this exact inflection point right now.
00:08:46.480 --> 00:08:47.200
It absolutely is.
00:08:47.440 --> 00:08:50.399
But practically speaking, how does an operator fix this?
00:08:50.559 --> 00:08:56.080
Do you just rip out massive incumbent systems like point click care or matrix care or YARDI?
00:08:56.320 --> 00:08:56.960
Oh, definitely not.
00:08:57.279 --> 00:09:01.840
Because honestly, that sounds like trying to change the engines on an airplane while it's in flight.
00:09:02.000 --> 00:09:04.159
The clinical risk just seems way too high.
00:09:04.559 --> 00:09:05.679
It is dangerously high.
00:09:05.919 --> 00:09:08.399
And the white paper is emphatic about this.
00:09:08.639 --> 00:09:11.279
Rip and replace is a massive strategic disaster.
00:09:11.600 --> 00:09:12.639
Okay, so don't rip it out.
00:09:12.879 --> 00:09:13.200
Right.
00:09:13.360 --> 00:09:19.600
Ripping out a clinical EHR faces huge resistance from nurses and creates unacceptable clinical risk.
00:09:19.840 --> 00:09:22.399
The incumbents are deeply embedded for a reason.
00:09:22.480 --> 00:09:24.080
Aaron Powell They're vital to the operation.
00:09:24.159 --> 00:09:25.039
Aaron Powell They are.
00:09:25.360 --> 00:09:30.960
But the key distinction the authors make is that the EHR is necessary, but not sufficient.
00:09:32.000 --> 00:09:35.200
A system like Point Quick Care is a critical layer one system.
00:09:35.600 --> 00:09:37.360
Layer one being the system of record.
00:09:37.759 --> 00:09:37.919
Right.
00:09:38.159 --> 00:09:42.480
The white paper outlines a future market structure defined by four distinct layers.
00:09:42.559 --> 00:09:43.759
Aaron Powell Okay, walk me through the layers.
00:09:44.080 --> 00:09:50.000
So layer one is your systems of record where transactions are captured, the EHR, payroll, accounting.
00:09:50.240 --> 00:09:50.480
Got it.
00:09:50.639 --> 00:09:55.120
Layer two is the integration and data access layer, the pipelines that let the data move.
00:09:55.360 --> 00:09:55.519
Okay.
00:09:55.840 --> 00:10:01.759
But the real strategic battleground, the open question for the entire sector is layer three, operator controlled intelligence.
00:10:02.080 --> 00:10:02.240
Okay.
00:10:02.320 --> 00:10:05.279
So layer three doesn't replace the EHR, it sits on top of it.
00:10:05.600 --> 00:10:07.519
It sits above the entire stack of applications.
00:10:07.679 --> 00:10:09.759
It extracts data via APIs in real time.
00:10:09.919 --> 00:10:15.039
Aaron Powell So while a system of record just captures an isolated transaction like a resident was admitted.
00:10:15.120 --> 00:10:15.600
Trevor Burrus Right.
00:10:15.759 --> 00:10:19.360
A system of intelligence connects those isolated transactions across domains.
00:10:19.440 --> 00:10:22.559
It cross-references clinical changes with payroll hours dynamically.
00:10:22.639 --> 00:10:22.799
Trevor Burrus, Jr.
00:10:22.879 --> 00:10:25.840
Which then feeds layer four, the decision and action layer.
00:10:25.919 --> 00:10:26.559
Aaron Powell Exactly.
00:10:26.720 --> 00:10:26.879
Yeah.
00:10:27.120 --> 00:10:31.600
Which is what actually helps operational leaders intervene before crisis happens.
00:10:31.679 --> 00:10:34.000
Aaron Powell But wait, here's where it gets really interesting to me.
00:10:34.159 --> 00:10:41.840
If I need an intelligence layer, why wouldn't I just buy whatever new AI add-on my EHR vendor is pushing right now?
00:10:41.919 --> 00:10:44.480
Aaron Powell Everyone is definitely pushing AI right now.
00:10:44.559 --> 00:10:45.519
Aaron Powell They really are.
00:10:45.679 --> 00:10:51.200
But the senior CRE paper makes this deeply counterintuitive argument.
00:10:51.440 --> 00:10:56.240
It claims that AI does not eliminate fragmentation, it actually magnifies it.
00:10:56.320 --> 00:10:57.120
Aaron Powell It really does.
00:10:57.279 --> 00:11:00.720
And it comes down to the mechanics of how AI models actually function.
00:11:00.799 --> 00:11:08.000
Aaron Powell How so Well, an AI agent is only as smart and only as reliable as the data environment it can reason across.
00:11:08.080 --> 00:11:08.399
Aaron Powell Right.
00:11:08.720 --> 00:11:16.720
So if you put an incredibly powerful AI assistant inside a siloed billing system, it doesn't suddenly understand your clinical ops or your HR challenges.
00:11:17.039 --> 00:11:20.639
It just becomes a highly polished, very fast way to get partial answers.
00:11:20.720 --> 00:11:21.519
Aaron Powell Exactly.
00:11:21.679 --> 00:11:25.679
True agentic execution requires governed access across all data domains.
00:11:25.840 --> 00:11:28.720
Trevor Burrus And the paper calls this master entity resolution, right?
00:11:28.960 --> 00:11:31.679
Which is basically solving the identity crisis of your data.
00:11:31.759 --> 00:11:33.279
Aaron Powell Yeah, that's a great way to put it.
00:11:33.360 --> 00:11:40.559
Aaron Powell Because if your CRM thinks Jane Doe is a sales prospect, but your clinical software thinks patient J Doe is an active resident.
00:11:41.039 --> 00:11:44.080
And your billing software has her listed under a slightly different name.
00:11:44.159 --> 00:11:46.639
Aaron Powell The AI doesn't know they are the exact same human being.
00:11:47.039 --> 00:11:48.080
It can't connect the dots.
00:11:48.320 --> 00:11:52.080
So it's going to hallucinate or give you structurally unreliable reporting.
00:11:52.159 --> 00:11:53.120
Aaron Powell That's a huge problem.
00:11:53.200 --> 00:11:53.919
Aaron Powell It is.
00:11:54.159 --> 00:11:59.600
That identity resolution is the absolute bedrock of operating intelligence.
00:12:00.000 --> 00:12:02.559
Without it, your AI is essentially guessing.
00:12:02.639 --> 00:12:09.200
Aaron Powell The white paper highlights eight necessary components to build this safely, and master entity resolution is right at the top.
00:12:09.519 --> 00:12:09.919
It has to be.
00:12:10.159 --> 00:12:16.480
Okay, so identity is one piece, but in healthcare, you also have regulators breathing down your neck at all times.
00:12:16.960 --> 00:12:17.360
Constantly.
00:12:17.679 --> 00:12:17.919
Right.
00:12:18.080 --> 00:12:25.919
So if an AI agent recommends a massive shift in how you staff your nursing floors, how do you prove to a state surveyor why it made that choice?
00:12:26.080 --> 00:12:30.960
Aaron Powell And that brings up the second critical component data lineage and auditability.
00:12:31.039 --> 00:12:32.240
Aaron Powell Data lineage, okay.
00:12:32.720 --> 00:12:36.879
In healthcare, you need to know exactly where a piece of data came from, who changed it, and when.
00:12:37.200 --> 00:12:41.200
So if a predictive model flags a building for a compliance risk.
00:12:41.279 --> 00:12:46.799
Aaron Powell You must be able to trace the exact lineage of the data that fed that prediction.
00:12:47.200 --> 00:12:50.159
AI does not reduce the need for auditability.
00:12:50.639 --> 00:12:52.320
It vastly increases it, I'd imagine.
00:12:52.559 --> 00:12:52.960
It does.
00:12:53.120 --> 00:12:55.360
You have to be able to show your work to the regulators.
00:12:55.440 --> 00:13:05.519
Aaron Powell Which makes me think if I don't build that auditability myself and I just rely on my vendors' AI, aren't I just handing them the keys to my entire business strategy?
00:13:05.840 --> 00:13:06.879
You absolutely are.
00:13:07.120 --> 00:13:09.039
The Techs calls this cognitive lock-in.
00:13:09.440 --> 00:13:10.320
Cognitive lock-in.
00:13:10.559 --> 00:13:11.360
That sounds terrifying.
00:13:11.759 --> 00:13:12.399
Which should be.
00:13:12.559 --> 00:13:18.559
If you let one of your software vendors own your AI intelligence layer, their product model essentially becomes your business model.
00:13:18.879 --> 00:13:24.399
You're outsourcing your enterprise brain to a company whose ultimate goal is just to sell you more software.
00:13:24.720 --> 00:13:24.879
Right.
00:13:24.960 --> 00:13:31.039
And every strategic move you want to make down the road, whether it's acquiring new buildings or restructuring capital, becomes exponentially harder.
00:13:31.120 --> 00:13:31.279
Trevor Burrus, Jr.
00:13:31.360 --> 00:13:34.399
Because your vendor essentially holds your operational memory hostage.
00:13:34.799 --> 00:13:35.440
Exactly.
00:13:35.600 --> 00:13:38.080
And we have to look at why this is so critical right now.
00:13:38.240 --> 00:13:41.759
The on-the-ground stakes for getting this right are existential.
00:13:42.080 --> 00:13:43.279
Let's talk about those stakes.
00:13:43.600 --> 00:13:48.480
According to the NIC data cited in the sources, occupancy is actually rebounding.
00:13:48.639 --> 00:13:51.759
It hit 89.1% at the end of 2025.
00:13:52.159 --> 00:13:53.919
Which sounds like great news, right?
00:13:54.080 --> 00:13:55.120
Demand is strengthening.
00:13:55.440 --> 00:14:00.879
It sounds great, but that rising occupancy masks a very fragile operational environment.
00:14:01.279 --> 00:14:02.480
Fragile because of the margins.
00:14:02.879 --> 00:14:04.799
Margins, labor, and compliance.
00:14:05.039 --> 00:14:11.519
Operators are dealing with severe caregiver shortages, rising resident acuity, and intense regulatory pressure.
00:14:12.000 --> 00:14:15.279
Like the CMS 2024 long-term care staffing rule.
00:14:15.600 --> 00:14:15.840
Yes.
00:14:16.000 --> 00:14:21.919
That federal mandate that essentially forces facilities to maintain strict minimum staffing hours for nurses.
00:14:22.320 --> 00:14:25.919
Regardless of how incredibly difficult it is to actually hire them right now.
00:14:26.240 --> 00:14:26.559
Exactly.
00:14:27.120 --> 00:14:32.960
When occupancy rises in that kind of high pressure environment, you have to manage everything with razor-sharp precision.
00:14:33.039 --> 00:14:35.519
Aaron Powell Or else you'll just bleed money while appearing to grow.
00:14:35.840 --> 00:14:36.159
Exactly.
00:14:36.480 --> 00:14:38.720
Let's make that financial impact real for a second.
00:14:38.879 --> 00:14:44.720
The white paper lists seven practical use cases where this layer three tech physically saves an operator from going under.
00:14:45.039 --> 00:14:46.000
Yeah, let's look at one of them.
00:14:46.320 --> 00:14:46.559
Okay.
00:14:46.720 --> 00:14:50.559
Let's walk through the mechanics of acuity to labor to margin intelligence.
00:14:51.200 --> 00:14:52.720
Here is the domino effect.
00:14:53.440 --> 00:14:54.080
Say Mrs.
00:14:54.159 --> 00:14:55.679
Smith moves into a community.
00:14:55.919 --> 00:14:56.240
Okay.
00:14:56.559 --> 00:14:59.279
Initially, she just needs a little help with meals.
00:14:59.440 --> 00:15:03.279
But over six months, her health needs her acuity naturally rise.
00:15:03.679 --> 00:15:06.799
Now she requires a two-person transfer just to get out of bed.
00:15:07.200 --> 00:15:07.360
Right.
00:15:07.440 --> 00:15:12.480
And the nurses are logging those new intensive care tasks in the clinical EHR system.
00:15:12.879 --> 00:15:13.200
Yes.
00:15:13.600 --> 00:15:18.399
And because those tasks increase, the labor scheduler has to add more hours for the floor staff.
00:15:18.559 --> 00:15:18.720
Trevor Burrus, Jr.
00:15:18.799 --> 00:15:21.279
Which means the payroll system is cutting bigger checks.
00:15:21.600 --> 00:15:21.759
Right.
00:15:21.919 --> 00:15:23.519
Labor costs are spiking.
00:15:23.759 --> 00:15:28.720
But if the billing system is sitting in its own soundproof room and doesn't talk to the clinical system.
00:15:29.120 --> 00:15:29.360
Mrs.
00:15:29.440 --> 00:15:32.080
Smith's service level isn't updated on the financial side.
00:15:32.399 --> 00:15:36.799
The operator is paying for the extra labor, but they aren't billing for the extra care.
00:15:37.120 --> 00:15:41.279
And the regional manager will just see a massive drop in net operating income at the end of the month.
00:15:41.519 --> 00:15:43.759
And they'll have absolutely no idea why it happened.
00:15:43.919 --> 00:15:45.600
That is managing via the ship's wake.
00:15:45.840 --> 00:15:51.840
But with an operating intelligence layer sitting above those systems, the organization sees that full chain instantly.
00:15:52.159 --> 00:15:59.919
So the clinical data changes, the system calculates the new labor requirements, and the billing module is automatically flagged for an update.
00:16:00.240 --> 00:16:04.799
It shifts the entire organization from a reactive scramble to proactive control.
00:16:05.200 --> 00:16:06.159
That's huge.
00:16:06.399 --> 00:16:10.159
The paper also outlines early survey risk detection.
00:16:10.399 --> 00:16:14.559
How do you actually predict a state citation before it happens?
00:16:14.960 --> 00:16:19.279
Well, compliance citations from state surveyors don't just materialize out of thin air.
00:16:19.519 --> 00:16:19.840
They don't.
00:16:20.240 --> 00:16:24.080
No, they form through detectable behavioral patterns within the facility.
00:16:24.240 --> 00:16:28.320
For example, you might have a cluster of late clinical assessments logged in the EHR.
00:16:28.559 --> 00:16:28.799
Okay.
00:16:29.039 --> 00:16:35.200
And at the exact same time, your payroll system is showing high staffing instability, lots of overtime or agency use.
00:16:35.519 --> 00:16:38.879
And maybe your CRM is logging a sudden spike in family complaints.
00:16:39.200 --> 00:16:39.600
Exactly.
00:16:39.759 --> 00:16:43.600
In a siloed world, those three red flags are sitting on three different desks.
00:16:43.840 --> 00:16:50.000
The clinical director sees the assessments, HR sees the overtime, and sales sees the complaints, but nobody puts it together.
00:16:50.399 --> 00:16:50.720
Right.
00:16:50.960 --> 00:16:53.840
But an intelligence layer cross-references them.
00:16:54.000 --> 00:17:02.159
It recognizes the pattern and flags the building as high risk 60 days before a state surveyor ever walks through the front door.
00:17:02.480 --> 00:17:02.799
Wow.
00:17:02.960 --> 00:17:09.200
So you can deploy a clinical strike team to fix the underlying issues before a citation ever occurs.
00:17:09.680 --> 00:17:15.759
It's the difference between reading a history book of what went wrong and having an active radar system showing you what's about to hit you.
00:17:16.079 --> 00:17:18.240
That is such a perfect way to put it.
00:17:18.400 --> 00:17:20.319
So let's synthesize this whole journey.
00:17:20.640 --> 00:17:21.440
Yeah, let's do it.
00:17:21.759 --> 00:17:30.240
We started by looking at the tangled mess of application sprawl that operators bought into over the last 20 years, assuming they were achieving digital transformation.
00:17:30.319 --> 00:17:32.079
Aaron Powell When really they were just building silos.
00:17:32.400 --> 00:17:32.559
Right.
00:17:32.799 --> 00:17:42.720
Then we looked at the life sciences industry, which proved that when software vendors fight over data sovereignty, enterprise customers eventually force them to open up their walled gardens.
00:17:42.799 --> 00:17:46.559
Aaron Powell Because the business just cannot survive without interoperability.
00:17:46.880 --> 00:17:47.279
Exactly.
00:17:47.440 --> 00:17:52.880
And finally, we discovered that in the age of artificial intelligence, simply buying an AI tool isn't enough.
00:17:53.039 --> 00:17:56.880
An AI locked in a silo just gives you faster partial answers.
00:17:57.359 --> 00:18:02.480
Which leads directly to the ultimate thesis delivered by senior CRE in this white paper.
00:18:02.799 --> 00:18:03.920
What's the main takeaway?
00:18:04.319 --> 00:18:12.079
As we look at the future market structure of senior living and post-acute care, the software vendors will continue to own the applications.
00:18:12.400 --> 00:18:12.640
Right.
00:18:12.720 --> 00:18:14.319
They'll own the day-to-day workflows.
00:18:14.640 --> 00:18:15.039
Yes.
00:18:15.279 --> 00:18:18.000
But the operators must own the operating intelligence.
00:18:18.400 --> 00:18:20.400
They have to own their enterprise memory.
00:18:20.720 --> 00:18:21.119
Exactly.
00:18:21.440 --> 00:18:30.240
So think about your own organization, whatever industry you happen to be in, as AI agents rapidly evolve to become a core part of your new workforce.
00:18:30.559 --> 00:18:31.519
Which is happening everywhere.
00:18:31.759 --> 00:18:32.079
Right.
00:18:32.319 --> 00:18:39.920
What happens if your company's enterprise memory is entirely owned by five different software vendors who flat out refuse to speak to each other?
00:18:40.319 --> 00:18:41.680
It's a recipe for disaster.
00:18:41.920 --> 00:18:49.039
If your corporate brain is deliberately fractured into a dozen different pieces, who is actually steering the ship?
00:18:49.359 --> 00:18:51.759
It's a question every leader needs to be asking right now.
00:18:52.000 --> 00:18:52.559
Absolutely.
00:18:52.799 --> 00:18:55.119
Well, thank you so much for joining us on this deep dive.
00:18:55.279 --> 00:18:58.319
Keep questioning the systems around you, and we'll see you next time.