Item Master interface with Epic

Good morning!

I am needing some assistance on understanding and executing an item master interface with Epic. We currently have a custom batch job (ZZ531) that runs every evening that is supposed to pick up surgery items, but I am being told that it is no longer working. The individuals that built the job are no longer around and I need to get this fixed. I put in an incident with Infor, but the response I was received was we can help but it will be billable. I just need to know how it works and if anyone out here has a similar set-up. Any assistance would be greatly appreciated.

Thanks!

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

The out of the box interface to Epic is IC524. It sounds like you have customized that at your organization. We have Cloverleaf that picks up the IC524 and sends over to Epic as HL7 message. What will need to happen at your location is, you will need to review the IC524 spec and map accordingly. Do you folks use Cloverleaf? If yes, then you can do some mapping and manipulation there as well.

unknown

we also use IC524 to pull item info for OR and Cath Lab. Clinical bridge/Cloverleaf on the Infor Lawson side picks up the file and sends an HL7 message to our Cloverleaf engine which sends the HL7 messages to Epic.

unknown

I am told that ZZ531 is a customized batch job that creates a file of any changes done to items lagged as surgical items in IC11. The file is picked up by OpenLink and then sent to Epic OpTime. The unfortunate situation is that our IT department no longer administers Lawson because we are in the cloud. Also the individuals that built this job or had knowledge of it are no longer around. I believe that I need to start over, but I don't have a clue about next steps.

unknown

We just went live in the cloud and also had customized COBOL programs. Part of the process involved Infor looking at our custom code and approving it to stay custom in the cloud. They accepted all of our custom programs, and then they compiled them all in the cloud. We had an SLA waiver and a work order for their billable hours to do this. We don't yet have our DEV environment set up, but once we do, Infor tells me that we can make changes to these programs as needed and compile/test them in DEV. Once tested, we'll put an incident in for them to compile them to PROD.

unknown

It sounds like you are in a Windows or Unix environment. To start with (this isn't the entire answer) you need to log in via LID and go into 'pgmdef', then look at the source code. This will give you a lot of information. If the source shows that much of this is in COBOL then it's not difficult to figure out. Much more likely, I'm guessing based on past experience, the program is making a call back out to the operating system and running things outside. The COBOL may show you what's being invoked, but you will then have to go and look at the outside scripts to see what broke. Because, custom programs like that, which consultants loved building back in the 80's, 90's, 2000's, and up, will break when migrated to new systems. Just a simple directory name change can hose the entire script. Just some suggestions...

Copyright © 2025 Infor. All rights reserved.