Interfacing into a Surgical Information System

Bill:

You have this in Financials, is this better suited to Supply Chain? Also, it looks like you need to develop an HL7 interface based on a modified schema, but the immediate problem is your base UOM, do I have that right?

It may be that this could have gone in Supply Chain but you are right in that what I really need to know is how folks have accounted for the mismatch in UOM.

Bill -

Here is a thread I started 2 years ago:

https://www.lawsonguru.co...v/topic/Default.aspx

Reach out to JonA, he might be able to help you. His simple answer regarding Par and Perpetual Inventory controls encouraged my client to stick with Lawson because both are supported.

Research ICI1.1 - Unit Of Measure Routines. You can load the form into portal and select Form Help. If that does not work you will find the form documented using Lawson standard 4GL docs -
dbdoc -w productline IC

The APIs might be able to derive a more granular UOM, but this does mean a 4GL approach. Based on my experience, a custom 4GL program would be your most reliable alternative.

That thread is close but I guess what I'm really wondering is if anyone has found a way to account for low unit of measure to be used with a custom interface. Another thing is isolating subsets for surgical specific items. If there is anyone out there that has gone through an interface with a Surgical System I'd like to get some insights on what to look out for and maybe compare notes on outcomes.

I'm posting in here because we are working on an interface issue now.
We took into account the lowest UOM already and setup our items so that the lowest UOM is what would be used.

My question is this; are you putting all items into the item master? We don't want our item master growing too large and full of items that are only used maybe once a year. But, these items need to get into SIS. Is there a way to maybe put the items into the item master, but not have them displayed during a search of items in RQC? Or, maybe do some sort of purge of the IC11??

I should have added some sort of way to have them not appear in RQC searches OTHER than just setting them to an inactive state in the IC11.
:doze:

Apart from customizing the search function in RQC you could use the Purchasing Class field to prevent certain items from showing up in the search. You would have to identify the items you don't want to show with one class and all the rest with another class. Then assign the "all the rest" class to every Requester in the Purchasing Classes tab in RQ04.

We ran a successful interface to SIS for a number of years until we moved to Cerner. We originally customized the IC522 to do the extract for us.
The UOM issue will require a change in the way purchasing does business. We came up with a new "rule" in regard to UOM.
For every item in the item master the first UOM must ALWAYS be EA. Even if EA is not valid for the item, we have EA as the first UOM. Then the next UOM can be PR or whatever with 1 EA to a PR.
In this way we know that someone has actually looked at the item, and made the decision that EA is not valid for the item.
However in the extract we always pull EA (in Cerner it's madatory) and send EA as the UOM.

It has worked for us. I would be happy to share our experiences off line if you want to give me a call at 716 859 8114

We are running a modified IC527 into Cerner's Surginet app.