# Fighting with the Fee Sheet

**URL:** <https://community.open-emr.org/t/fighting-with-the-fee-sheet/9345>\
**Category:** OpenEMR Development\
**Created:** [November 25, 2017, 3:45am UTC](https://community.open-emr.org/t/fighting-with-the-fee-sheet/9345 "2017-11-25T03:45:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![roland](https://community.open-emr.org/user_avatar/community.open-emr.org/roland/32/13141_2.png) [@roland](https://community.open-emr.org/u/roland)\
**Post date:** [November 25, 2017, 3:45am UTC](https://community.open-emr.org/t/fighting-with-the-fee-sheet/9345/1 "2017-11-25T03:45:58Z")

</div>

Hi,  
As we were not happy with the way we had to enter non-drug products, I created an extra set of forms and a “products” table plus “product inventory” table, to separate ND from drugs (with an addition to the Inventory menu). It works and we have now two separate drug and ND views with more columns appropriate to ND products (variation, weight color etc) and no dosage and routes…  
They also show up in the fee sheet with a checkbox (when clicking the products button), but that’s about it. The ND products have their own prod\_id, but the Fee Sheet, and corresponding Class and ClassHTML files don’t look for that, they just include the drug\_id. So I cannot get them into the billing lines and eventually the sales and billing tables, without considerable changes to the Fee Sheet + Class code.  
Does anyone have a bright idea how to accomplish that task without changing all the arrays and control mechanisms to include the new prod\_id?  
Or is there someone who has done that already?

thanks  
Roland 🐾

---

<div class="post-metadata">

**Author:** ![juggernautsei](https://community.open-emr.org/user_avatar/community.open-emr.org/juggernautsei/32/10764_2.png) [@juggernautsei](https://community.open-emr.org/u/juggernautsei)\
**Post date:** [November 30, 2017, 10:22pm UTC](https://community.open-emr.org/t/fighting-with-the-fee-sheet/9345/2 "2017-11-30T22:22:23Z")

</div>

@Roland It seems like you took the long way around what should have already been functioning within the program.

Can you shed a lot more light on what was displeasing about the inventory setup that is currently built into the system?

How long has your office been using OEMR?
