Patient charges for synthetic grafts

Jon,
I am not stating this as "best practice", simply as our way around the issue...
In the Item Master, we use the User Field 5 (the lower one) to house the calculated cost of the item at the Stock UoM and the date of the calculation. For skin substitutes, and myriad other items, this calculates to the EA. If the Unit of Use (UoU) is lower than the Stock UoM, we populate User Field 4 with the designated UoM (completely non-ANSI standard) and the conversion of the UoU to the Stock UoM. So, as an example for a 6x16cm skin substitute...

User Field 4: SQCM-96
User Field 5: 1250.0000-20170120

Of course, this means you will need to incorporate these fields (or something similar) into your interface processes.
Hope that helps,
Red

Jon,

We do something similar to what Red. We use user field 1 and 2 from the lower set of 5. In user field 1 we put the UOM on the contract for anything going through the interface. In user field 2 we put the conversion.

Example 1: something actually coming as each
User Field 1: EA
User Field 2: 1

Example 2: something like the mesh
User Field 1: EA
User Field 2: 96

This tells the interface to pull the price from the vendor agreement line and divide it by user field 2 for the each price that is sent.

So basically...you have to jury rig something.

Michelle

Jon - we're in the same boat. With robotics for example, that can be charged 10 times, this is what the user fields would look like:
Last Epic Calculated Cost Update 11/21/2016
Epic Calculated Cost Flag R (Y = reprocessed, not using at this time)
Epic Calculated Cost Percentage .1
Epic Calculated Cost 270.00 (This field auto populates after the interface runs)

Good Luck,
Beth

Thank you everyone. Very helpful.