Prev
Next
Forums Lawson S3 Supply Chain

Optime Charge Codes - From Lawson or Epic?

Sort:
You are not authorized to post a reply.
Author
Messages
Kat V
Veteran Member
Posts: 1020
Veteran Member
6/18/2015 6:29 PM

    We have Epic HB (Billing) and have Optime (OR), Cupid (Cath Lab) and Radiant (Radiology) installed.

     

    We have charge codes built in PC10 as this was the setup in legacy systems.  However, it was recently pointed out to us that this means - we build a code in Epic, send it to Lawson to send it back to Epic (Optime, Cupid and Radiant).

     

    Is anyone else doing this or do the Epic modules see one another?

    JonathanF
    Posts: 3
    7/6/2015 3:13 PM
      Since you are using PC10, then you are using that with an Item Master interface, which exchanges data between the Lawson Item Master and the Epic SUP and BAL INI's (tables).

      Building these charge codes means creating EAP values that then allow the interfaced Item Master details to include these two details of Charge Status (Y/N) and Charge Code from your Lawson "System of Record", so to speak. There are a number of Hospitals that interface their Lawson Item Master with Epic.

      A carefully mapped out workflow needs to be created so that the coding is available within Epic prior to the interface message containing that referenced value - otherwise you will have an error on the Epic side where the "square peg" (non-existant EAP) assigned to a given SUP record...just shows up as a blank charge code - either within the Epic general "Item Master" (SUP) record, or the Epic Location-level (BAL) record for that item.

      I'd suggest the workflow include turn-around times and monitoring of this Bridging/interface error queue - so when human error catches you, it's addressed as soon as possible - so your OpTime/Cupid/Radiant (and as of 2012 - even listed charge-able floor items) billing does out in a timely fashion.
      Kat V
      Veteran Member
      Posts: 1020
      Veteran Member
      7/8/2015 1:38 PM
        We are using a custom sql to move the item master across. When we add an item we load to PC10 with 0000000 as a "placeholder" EAP. Yes, it creates errors in the workqueue if they need to bill it prior to a "real" EAP being built.

        So we load to PC10, Epic builds an EAP, we load back to PC10 to delete the old EAP and then back to load the correct EAP to Lawson to then send in the interface to Optime/Radiant/Cupid.

        We would rather take Lawson out of the middle. We have issues maintaining EAPs in both Epic HB and Lawson PC10.

        Given what you've just told me - Optime won't build the item at all. So perhaps a cloverleaf solution? We send the file without PC10 - Cloverleaf takes the item and looks up in HB, if found attach EAP, if null attach 0000000.

        I believe they have a workflow like you are describing. This is how we find out that HB and PC10 do not match currently.
        You are not authorized to post a reply.