Jill SweeneyGuest
Daniel LitwinHost
Jennifer BingamanGuest
All right, transitioning now to another common complaint, another common source of data disasters.

And this would be just general reporting problems, right? When you hear the common complaint, hey, this report is wrong, right? Often though, The report is showing something important.

Or maybe they're seeing a report that is feeding off of data that they don't feel in their day to day.

It might just be that the report is mismatched with reality or with the data they're expecting.

So, Jennifer, tossing it your way now, when someone says, hey, sorry, guys, this report is wrong, what's usually happening? Like, is it really wrong? Is it just a mismatch of expectations? Kind of unpack what's really going on here.

So the data on those reports can only reflect the process or what's being recorded in Sensitrack.

And then too, as we just talked about, if there are pieces of data missing, you know, from the overall SenseTrack database, then that can play a factor, you know, in as well, but it's mostly because workflows.

Could you expand on that a little bit? And, you know, Jill, feel free to chime in here too, but what are some examples of reporting frustrations that you see often from facilities in their day to day?

Well, I'm going to take it back to printing a label from inventory rather than assembling a tray.

Your turnaround time for that tray from the minute it hits decontam all the way through sterilization is going to be way off because there's no way.

It's missing how long it took somebody to inspect every single instrument on that tray and make sure it's ready for sterilization.

If they're not scanning, you know, they'll see some folks have processed 10 trays through assembly in the same eight hour period and somebody processed 100 trays.

But it looks a little off because those 100 trays were cameras or batteries.

And so it makes it seem like the information is not correct, but it's really uncovering what's going on in the department.

Jill would love your thoughts on this one too, right? What do you see from the trenches on some common examples of reporting frustrations that facilities run into quite a bit?

All right, transitioning now to another common complaint, another common source of data disasters.

And this would be just general reporting problems, right? When you hear the common complaint, hey, this report is wrong, right? Often though, The report is showing something important.

Or maybe they're seeing a report that is feeding off of data that they don't feel in their day to day.

It might just be that the report is mismatched with reality or with the data they're expecting.

So, Jennifer, tossing it your way now, when someone says, hey, sorry, guys, this report is wrong, what's usually happening? Like, is it really wrong? Is it just a mismatch of expectations? Kind of unpack what's really going on here.

So the data on those reports can only reflect the process or what's being recorded in Sensitrack.

And then too, as we just talked about, if there are pieces of data missing, you know, from the overall SenseTrack database, then that can play a factor, you know, in as well, but it's mostly because workflows.

Could you expand on that a little bit? And, you know, Jill, feel free to chime in here too, but what are some examples of reporting frustrations that you see often from facilities in their day to day?

Well, I'm going to take it back to printing a label from inventory rather than assembling a tray.

Your turnaround time for that tray from the minute it hits decontam all the way through sterilization is going to be way off because there's no way.

It's missing how long it took somebody to inspect every single instrument on that tray and make sure it's ready for sterilization.

If they're not scanning, you know, they'll see some folks have processed 10 trays through assembly in the same eight hour period and somebody processed 100 trays.

But it looks a little off because those 100 trays were cameras or batteries.

And so it makes it seem like the information is not correct, but it's really uncovering what's going on in the department.

Jill would love your thoughts on this one too, right? What do you see from the trenches on some common examples of reporting frustrations that facilities run into quite a bit?
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.