Lawson and Epic-creating new items in the IC11 when product changes

Does anyone on Lawson and Epic or Lawson and anything create new IC11 records when a product changes? I was informed in an Epic meeting that anytime a product changed (i.e. a switch from Bard to Kendall on a syringe) or was subbed, I would have to create a new IC11, IC12, etc etc.

Currently our practice was to just update the manufacturer info and PO13.3 data and contract.

Not crazy about it but I see pros and cons. For Epic the data stays until supplies exhausted for the old product and then they pull the new. Certainly nicer when UOMs are different but we like usage under one IC11 record.
My thought was if I have to build a new item each time to just create with a alpha character every time a product changed and the crystal report would pull the number with a wildcard for the IC11 and pull all usage.

I would appreciate any feedback on your practices.

Find more posts tagged with

Comments

Legacy Contributor

We create new item number for 95% of product changes, do not for custom packs. Due to the fact we have several sites around the country using the same items we need to keep the old until all sites have used the product, with some sites using new before others. We also like to do this for recall processing.

Legacy Contributor

We're using Lawson with an custom medical record and are creating a new item number each time the NDC changes. We had hoped to use the IC11.6 NDC codes to manage them all under a single item number, but it doesn't allow us to easily identify which NDC was used when issuing stock to departments. We use the issue information when NDC information is missing for claims, and if there are drug recalls.

If anyone is using the IC11.6 and can track the NDC detail on issues - we would really like to hear from you!

Legacy Contributor

We create a new IC11 if there is a manufacturer or number change. I feel anything with a different barcode number is a new item. We used to change the information, but ran into issues during surgery inventory time. It was painful to track down the old item/price once the information was changed. We interface with Cerner Surginet. We've also started loading the GTIN information in Lawson as we are transacting with Cook. It's a way of transitioning to GTIN and UDI's.

For subbed items, we use the same item number but add to the PO25.6. On the PO13.3 we make the subbed item the default. That may eventually change with the implementation of the contract module, GTIN's and UDI's.

We do have one exception...Cardinal custom kits. Only the last digit on the custom kit changes with a new release. Since the kit itself does not change, we update the IC11/IC12/PO13.3.

Hope that helps.

jon-athey

We build a new item when there's a manufacturer number change for ANY item in the system except custom packs, not just items in Cerner. We don't attempt to tie the new number to the old in any way. This has not been an issue for us in our usage reporting according to our contracts and value analysis staff.

Copyright © 2025 Infor. All rights reserved.