Lawson to Epic - Supply/Implant Type Maintenance

Hi,

We are interested in finding out how other facilities using Lawson and interfacing to Epic using the IC524 or IC527 files maintain their supply types in Epic.

We currently (under direction from Epic) use the noun type to designate whether or not it's a supply or an implant. Does anyone else use a different management process for maintaining that information within Epic? Or is there anyone that maintains the usage identifier flag in Lawson IC11?

Thanks

Find more posts tagged with

Comments

kheeter

John,

We use the IC11 User Field "Item Alpha 3" position to define Supply or Implant. The IT/Lawson side of the house set up a "bridge" for Epic to pick the data up.

We also used the Add-Ins/Lawson Upload Wizard to enter the initial data to save time.

Legacy Contributor

We use the IC12 User Field Item Location Alpha 1 field to define supply, implant, dressing, or instrument. We use a customized version of the IC528 to send the data to Epic once each day.

Legacy Contributor

We assign all Lawson items which we interface to Epic (via IC525) an inventory minor class (IC11).

When the item goes thru the interface, we've created a table with our IS integration team (inventory minor class vs. implant/supply) which reads each item's inventory minor class, then converts it to an implant or supply category.

Legacy Contributor

We use the Use Identifier flag on the IC11 main tab. Blank = Supply, L = Implant. We pulled it from GL code to begin with but have since moved it to the initial file request. (Interceed is something where it's reimbursed as supply but charted as implant so the flag and GL code do not match)

The generic/noun then populates as

Blank - Supply, Generic is the Supply Type

L (Implant) - Supply Type is Implant, Generic is the Implant Type.

This is going to Epic Optime, Cupid and Radiant through Cloverleaf with no issues.

Copyright © 2025 Infor. All rights reserved.