Using STS and ELSO Data to Govern Perfusion Quality

Most health systems already sit on the data they would need to govern perfusion quality. It is in the STS Adult Cardiac Surgery Database, in ELSO registry submissions, in the perfusion record, and in the blood bank. The problem is not a shortage of data. It is that the data is fragmented, vendor-held, and never assembled into a view leadership can actually act on.

From registry submission to governance tool

For many programs, the STS database is treated as a reporting obligation — data goes in, a benchmark report comes back, and little changes. Used well, it is a governance instrument: risk-adjusted outcomes, transfusion rates, and process measures, comparable across sites and against national benchmarks. The same is true of ELSO data for ECMO. The registries are only as valuable as the questions leadership learns to ask of them.

What an executive perfusion dashboard shows

Data integrity is the quiet prerequisite

A dashboard is only as trustworthy as the data beneath it. In fragmented programs, submission completeness varies by site and by vendor, definitions drift, and gaps go unnoticed. Independent oversight of the data pipeline — verifying that what is submitted is complete and consistent — is unglamorous and absolutely foundational. Predictive analytics on top of unreliable data is just faster guessing.

Analytics is how oversight scales

No one can personally watch every case in a multi-site system. Analytics is what makes governance possible at scale — surfacing the site that is drifting, the metric that is slipping, the program that needs attention before an event forces it. A Perfusion Program Management Organization builds STS- and ELSO-aligned analytics not as a report, but as the early-warning system that lets leadership govern by signal instead of by surprise.