What Health System Leaders Are Really Saying About Data Lifecycle Management

MediQuant recently partnered with Becker's Healthcare to convene an executive advisory session on data governance, modernization, storage strategy, and AI readiness, bringing together CIOs, CTOs, and data leaders from health systems of very different shapes and sizes.

The topline: the conversation is shifting from how long do we have to keep this to what should remain, where should it live, what does it cost, and when can we let it go. That shift wasn't a tidy consensus. It was a room of smart people working the same hard problem from different angles.

Here's what stood out.

Proactive in theory, reactive in practice

Most leaders agreed data now enters planning conversations earlier, though several admitted the shift is only partial: teams still have to push business units to loop in data considerations before a system change, not after.

A recurring culprit is SaaS sprawl: a business unit signs up for a new platform without IT in the room, and data questions get discovered rather than planned for. One system's fix has been a governance committee with real teeth, where IT, security, finance, and clinical leaders all have to sign off before anything new gets deployed.

Modernization forces the hard questions

Every major transition, a new ERP, a new EHR, a merger, leaves an organization holding years of data that doesn't cleanly belong anywhere. Leaders handled it differently: one rural hospital built an AI-searchable data lake wired directly into the EHR; another caches only the data needed for scheduled visits to keep cloud costs down; an academic research environment needs longer retention horizons than day-to-day operations require. The common thread is that "the retention policy" is usually several policies wearing one name.

Storage economics are now a governance question

Cost and governance used to be separate conversations, one for finance, one for compliance. That line is blurring. Leaders pointed to consumption costs, disaster recovery overhead, and duplicate copies of the same data scattered across systems, lakes, and warehouses. Several noted that aligning how information is stored with how it is used, rather than defaulting to one tier for everything, is one of the more practical levers available.

The question nobody had fully solved

The sharpest moment came when Mike McGuire, MediQuant's SVP of Product Strategy, posed this scenario: if data meets its retention requirement and gets purged from the archive, but a copy still sits in a data lake built for analytics, has it actually been purged? Could the organization prove that if a legal request came in later?

The answer that emerged wasn't a tool. It was a discipline. Leaders agreed this starts as governance before it's technical: you have to know where your data lives, and who has access to it, before you can responsibly delete anything. One leader described treating the lake as a hub connected to the EHR and other systems, so a deletion in one place cascades everywhere else. Another was more blunt about the current state: without a connected inventory, it's still "best effort."

AI raises the stakes, it doesn't solve the problem

AI came up in nearly every answer, but rarely as the headline. More often, it was the reason the underlying data problem now matters more. Leaders pointed to the need for a real governance and semantic layer beneath any AI initiative, since a data lake is not the same thing as a knowledge layer AI can actually reason over.

So, whose data is it, anyway?

The closing question drew the most personal answers. Several leaders argued the data ultimately belongs to the patient, who should eventually be able to see who accessed their information and why. Others preferred a different frame altogether, arguing that asking who's responsible at each stage is more useful than arguing over who owns it. A third view placed accountability with the health system's board and leadership.

These views don't fully contradict each other; they reflect the same theme the session kept circling back to: data lifecycle management isn't a decision made once. It's an ongoing, cross-functional discipline, with legal, clinical, financial, and technical stakeholders continuously weighing different priorities.

That's the thinking built into MediQuant's DataArk platform and data lifecycle management approach: tagging data with its retention and disposition rules the moment it arrives, keeping frequently needed information readily accessible while aligning rarely touched information with the storage tier that fits how it's actually used, and giving organizations a defensible, auditable answer to the question this session kept returning to: not just what should we keep, but what should happen to it next.

Read the full press release: Healthcare CIOs Are Shifting from Data Retention to Data Lifecycle Management

More Thought-Leadership