Management of Par Location in Epic

Anthony Risteff

We are currently transitioning to Epic and incorporating par locations into the Epic interface. We are seeking guidance on how others are managing the removal of items from a par location to ensure that Clinical Bridge properly communicates this removal to Epic so that it can inactivate that item from the BAL record.

It appears that we need to inactivate the item in the par location first. After the interface processes this change, we could then delete the item from the par location. However, this poses challenges for our Operations departments because the standard practice today is to delete the item. Additionally, it seems that using the mass par update to swap products does not work effectively in this context.

Any insights or advice on this issue would be greatly appreciated. Thank you!

lcleary

Epic recognizes Active Yes or No. It does not recognize DELETE. We send a file to Epic every hour. Items are inactivated at the Par Location first. After an hour, or more, they can be deleted. This action changes the Active status in Epic from Active Yes to Active N. I'm sure if we did an audit we would find errors. How do you enforce the "1 hour wait time" with multiple users across multiple hospitals?

I agree. This is ineffective for Operations. I experienced the same issue at a previous Hospital. They sent the file only once per day, at midnight. So, for example, Operations could inactivate items at the Par Locations on Monday and then delete them on Tuesday.

I also agree that using Mass Par Update will not work for "swaps". Along with DELETE, Epic does not recognize REPLACE.

Following to see if anyone else has found a solution . . .