what we learned from this, the variation that we're seeing across sites, and plug that back into the research arm,
both for additional observational analyses as well as maybe some pragmatic clinical trials here, to then be able
to figure out what the actual recommendation is — or what we're seeing that we can share with quality
champions and providers across MPOG that could potentially change their practice. Because what we're really
talking about is not how you are going to change your practice, but really just, like, enlightening us about what
our practices are, and I think that's the hat that we should think about this with.
You know, Morgan, your statement in the chat, which is thoughts about adding in time to OME — like, OME per
hour of case — what you've actually uncovered is the fact that this current informational measure, the way it's
displayed in the QI Reporting Tool, is actually not working as intended. When we moved the QI Reporting Tool to
the new platform, the way that this measure works kind of broke, which is why what you're seeing now is not
completely accurate, and you're not actually able to dive into the measure summary screens to look at the
opioid administration per hour equivalents that we developed. What you're supposed to be seeing currently is
essentially, for an average person and an average duration case, what the average opioid equivalence was in
morphine equivalents — and you're not quite seeing that.
I think part of what we would like this Quality Committee to comment on via the poll is, first, do we actually
want to continue sharing opioid equivalents in the way that Dr. Fisher described for what you have right now,
which is these procedure groups — spine, cardiac, abdomen, hip, knees? And then, number two, should we
think about this pilot where we look at opioid concentration? And from number two, I absolutely think we
should do this. We can make the pilot somewhat restricted by a very limited amount of maybe even, like, one or
two procedure types. And we can use maybe just, like, fentanyl and morphine — limit the number of
medications. We also have to see what's available. And maybe we could just look at that and see if this is
computationally feasible for MPOG, and if the answer is yes, and if it's something that we can then share on the
dashboard, then we can come back —we don't have to wait three years; we can even come back sooner than
that, before the next measure review, and just share some details on that and decide if folks want to further
explore that. And not to mention, if there's a great research use case for it, then that's another pathway as well.
Anyway, so I'll stop there. Other comments from folks?
01:07 – Sarah Zhao (MPOG) (via chat):
Is “stanpumpR.io” package specifically designed for OME study?
01:08 – Sarah Zhao (MPOG):
I'm asking this question because I tried this package before in my study, and I found that in this package
there's only — it only includes about seven medications which are OME medications. And it also
includes other medications which are not OME. I found that in this package it only included fentanyl,
hydromorphone, morphine, oxycodone, and another two — methadone, alfentanil, sufentanil —
included in this package. But in my study, I included some other medications also. Let me give you some
examples. So, [unclear], opium, hydrocodone, and naloxone. So some of that is not covered in this
package, which means that if I want to do some study including all these opioid medications, this
package might not work, or it will give me inaccurate results. So do you have the same issue, or...?
01:07 – Michael Mathis (MPOG):