Singular items that have multiple uses

I'm not well versed in creating interfaces but is there a way a calculation can be introduced that would divide the unit cost by 10 for these few items and enter that result in Meditech? Otherwise, if you have to manipulate Lawson to get the cost per use you could create a lower uom called a "use", USE perhaps so you would have for instance

1 USE = 1 USE
1 EA = 10 USE
1 CA = 100 USE

Make USE a secondary transactional uom only and issue or purchase by the EA or CA. I can't think of any reason this wouldn't work. Might cause some headaches for inventory though if any of theses items are stock. There are many user fields that could be used to store that conversion value but I don't think the standard interface files grab any of those fields.

We use DaVinci too, Bev. We added them into our Sterile Processing Inventory (under protest). The instrument coordinators in the OR keep track of how many uses they've gone through and switch out the items for new ones once 10 uses has been reached. In order to have the purchasing information unsullied by the repetitive use, we have it loaded as an each (after all, that's how we have to buy them).

On IC11, we've cannibalized User Field 1 and User Field 2 for our interface needs. User Field 1 has the word DaVinci in it for items that are DaVinci items and User Field 2 has the number 10. This tells the custom interface program that my IT department wrote to divide the average cost by 10 when sending the cost information to EPIC Optime. So, basically, we divide the cost of the item so that our purchasing information is correct. We use the same fields for other interfaces that requires multiplication or division for interfaces as well (nonstocks being sent to Optime will send the each cost when they divide by field 2).

Hope this helps!

We took Jon's route. We have the "Stock" UOM as PU (Patient Use - designed not to duplicate any standard UOM codes) and then build up from there. It is SOLELY for the robotic supplies.

If you win the battle and use an alternate field, I'd suggest attributes that would let you create several flags for one item