Clinical Bridge/Cloverleaf questions

Hello all!

I was wondering if I could get some feedback about experiences using Clinical Bridge and/or Cloverleaf? We are considering this installation and I would like to see how others feel about how it works, if it is easy to manage, and if it provides good data for clinicians and Finance both ways. Also, I could you a little bit of information about the advantages of having both (Clinical Bridge and Cloverleaf) or if it is actually necessary. We are needing to replace our current interface with Epic, we just have a custom program that transfers our item master and RRB to OpTime. It was built in 2009 and it needs to go! We are also in need of an inventory management system for our ORs. We are V10 and hosted.

Any information is great!

Thanks

Angela

Find more posts tagged with

Infor Lawson Supply Chain Management - Discussion

Comments

unknown

If you have purchased it, too bad. If you haven't, I am not sure its worth. We only use that to send IC524 to Ensemble. We did not/do not need that overhead for one file. We could easily take the IC524 file, give it to Ensemble for processing instead of Cloverleaf converting the file to HL7 and passing to Ensemble. If it has other functionality that I am not aware, I am subscribing to this thread.

downloadexport2010_1.zip

dechevar

My understanding is that these are 2 distinct products. Cloverleaf is an interface engine that can be used for any product not just Infor. It would be considered an enterprise application for your IT department. We use Rhapsody and previously eGate. If you already have an interface solution, there is no need for Cloverleaf.

Clinical bridge is a black box version of Cloverleaf specifically designed to run the interface between Point of Use, Lawson S3, and specifically Epic. It pulls in your ADT information in order to assign items to patients/procedures in Point of Use. I believe it also does patient refund interface as well. If you do not have POU, there is no need to have it. The benefit of having it if you utilize POU is that as Infor makes changes to POU, they update Clinical Bridge as well. That means you do not have to engage with IT to recode and test the interface every time there is an update.

unknown

This is a best explanation that I have received so far. Thank you! So do you think that we can keep our current interface engine (OpenLink) and then I can use IC524/IC525 to push our item master out to Epic? Our custom program currently pulls item master information based on fields that we fill in IC11; ITE-USER_FIELD4, ITE-USER_FIELD5, ITE-USER_FIELD-N2, and if the item is stocked in specific Par locations. How do I use IC524/IC525 and not send everything? Just items stocked in certain Pars and surgical items (ones with the fields listed above?)

Thanks!

dechevar

We created a custom job to extract the data required for Epic and Optime and then ftp to a server for the interface engine to pick up.

unknown

Did you create it in LID? That is what we are doing also, but it is so difficult to update, if needed.

0712131256598360.doc

Copyright © 2025 Infor. All rights reserved.