Prev
Next
Forums Supply Chain Management Lawson S3 Supply Chain

Singular items that have multiple uses

 3 Replies
 0 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
Bev Edwards
Veteran Member
Posts: 366
Veteran Member
10/22/2013 2:05 PM
    We have several Davinci items that are a single UOM, however each item has 10 uses, 1 per patient case.

    We have a daily interface that picks up new Lawson items and pricing and uploads them to our Meditech system. Our IT department is saying that we can apply the UOM as 10 and then the cost will be calculated correctly when it's uploaded to Meditech so that when a patient is billed, only 1/10 of the cost will be charged, which is correct.

    What I'm not sure about, is if this is the appropriate way to house the item in Lawson and have the UOM showing as 10, when in actuality, its really 1.

    Another suggestion was to use an alternate field in Lawson for the number of uses. Is there an alternate field in Lawson that could be used for this value?

    Bev

    JonA
    Veteran Member
    Posts: 1163
    Veteran Member
    10/22/2013 4:06 PM

      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.

      Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
      Michelle Wetzel
      Veteran Member
      Posts: 183
      Veteran Member
      10/22/2013 5:40 PM
        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!
        Kat V
        Veteran Member
        Posts: 1020
        Veteran Member
        10/23/2013 5:16 PM
          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