Getting rid of SQL-Ledger

sunsetsystems wrote on Monday, September 29, 2008:

Just wanted to let folks know that I’m finally working on building A/R support into OpenEMR to eliminate the need for SQL-Ledger.  Current ETA is around the end of October.

Rod
www.sunsetsystems.com

mike-h30 wrote on Monday, September 29, 2008:

This is good news Rod!   Aside from my 2.8.3 to 2.9.0 upgrade issues I was getting ready to install SQL Ledger and transition our billing to OpenEMR  by the end of the year so we could start 2009 accounting with OpenEMR.  Looks like I  might hold off  on that.   I can help test this if you need some extra testers.

-Mike

drbowen wrote on Tuesday, September 30, 2008:

Yea!  Rod!

Sam Bowen, MD

fred0 wrote on Tuesday, October 14, 2008:

Rod,

Will the new features support physical product sales and sales tax?

sunsetsystems wrote on Tuesday, October 14, 2008:

Fred: Drug/product sales and sales tax are already supported; that will not change.

Mike: Testers will definitely be appreciated!

Rod
www.sunsetsystems.com

mike-h30 wrote on Tuesday, October 14, 2008:

Let me know when Rod.

I have a ton of patient encounters that have not been billed ( from within OpenEMR ).

-Mike

omo66 wrote on Friday, October 17, 2008:

I attempted to install SQL Ledger last and got some problems.
Now I have a clean install of 2.9 ready for production this week (Neurology practice).

I hope this new version will easily upgrade openemr 2.9 to do the biling.
I am willing to test it as well.

thanks,

gutiersa wrote on Wednesday, October 22, 2008:

count me in for testing!

voipbound wrote on Wednesday, October 22, 2008:

I think it is safer to ask who doesn’t want in

sunsetsystems wrote on Wednesday, October 29, 2008:

Finally!  I have committed these changes to CVS.  The modified files are:

includes/config.php
interface/billing/billing_process.php
interface/billing/billing_report.php
interface/billing/indigent_patients_report.php
interface/billing/sl_eob_invoice.php
interface/billing/sl_eob_search.php
interface/billing/sl_receipts_report.php
interface/forms/fee_sheet/new.php
interface/forms/fee_sheet/view.php
interface/patient_file/deleter.php
interface/patient_file/front_payment.php
interface/patient_file/pos_checkout.php
interface/patient_file/summary/demographics.php
interface/patient_file/summary/pnotes.php
interface/reports/collections_report.php
interface/reports/receipts_by_method_report.php
interface/reports/sales_by_item.php
library/Claim.class.php
library/billing.inc
library/invoice_summary.inc.php
library/patient.inc
library/sl_eob.inc.php
library/classes/WSClaim.class.php
library/classes/WSProvider.class.php
sql/2_9_0-to-2_9_1_upgrade.sql
sql/database.sql

The legacy SQL-Ledger support is still there as an option.  See the comments in includes/config.php regarding the correct setting for $GLOBALS[‘oer_config’][‘ws_accounting’][‘enabled’].

There will be a script to convert from SQL-Ledger, but that is not done yet.

Testing feedback is appreciated.  There are surely some bugs, so don’t use it for production yet!

Rod
www.sunsetsystems.com

penguin8r wrote on Wednesday, October 29, 2008:

Nice!  Well done, Rod!  somebody buy that man a drink.

rpl121 wrote on Thursday, October 30, 2008:

Rod, I’m encouraged by your efforts to put patient accounting into the realm of OpenEMR rather than SQL-Ledger.  I’ve used cvs to install your new files, and on two separate installations (after running the 2.9.0 to 2.9.1 database conversion), I get this error message:

Parse error: syntax error, unexpected T_SL in /var/www/openemr/includes/config.php on line 109

I tried eliminating white space before and after this line, and that didn’t correct the error.

Maybe it’s just me, but this is holding me back on testing your new code.

Ronald Leemhuis MD

voipbound wrote on Thursday, October 30, 2008:

Can someone post instructions on how to get this CVS update into the system, I think that would help everyone.

sunsetsystems wrote on Thursday, October 30, 2008:

A quick google turns up this:

http://www.faqts.com/knowledge_base/view.phtml/aid/18379/fid/51

Try doing a clean checkout into a new working directory.

Rod
www.sunsetsystems.com

sunsetsystems wrote on Thursday, October 30, 2008:

Info about accessing CVS is here:

https://sourceforge.net/cvs/?group_id=60081

Rod
www.sunsetsystems.com

bradymiller wrote on Thursday, October 30, 2008:

Rod,
  This is great
  What happens if the $GLOBALS[‘oer_config’][‘ws_accounting’][‘enabled’]  is set to true or false?
  I ask this because if you have “true” do the same thing as “2”, then people can test your changes on the online OpenEMR tester (it resets to the newest cvs version of openemr every day at 7:02 AM) at:
http://www.oemr.org/modules/wiwimod/index.php?page=DemoCVS

-Brady

Also, can you change version to 2.9.1-dev so everybody knows its a dev version with these changes in progress (I’d do it, but having lots of technical problems)

sunsetsystems wrote on Thursday, October 30, 2008:

true will behave the same as 1, and false like 0.  This is for compatibility with existing sites when an old config.php is preserved during an upgrade.  I think Sam would need to intervene re the demo site, however proper testing really needs local/private installations going through the whole billing cycle.

I changed the version number in CVS as you requested.

Cheers,

Rod
www.sunsetsystems.com

bradymiller wrote on Thursday, October 30, 2008:

Rod,
  That makes sense.  This is gonna break the script on my Developer Appliance and my online CVS demo (they both auto-configure by changing the line from false to true), but your changes are well worth it. I wanted to  release new version of the Developer Appliance anyways, which also functions as the online CVS demo, and this is the bit of motivation that I needed to finish it.
-Brady

BTW, both the developer appliance and CVS demo are on the oemr.org wiki

bradymiller wrote on Thursday, October 30, 2008:

Rod,
  Actually, I just realized your changes don’t affect the function the of my Developer Appliance or my CVS demo. My auto-config script requires “false”, but since you have it set as “2”, it just leaves your default value. False alarm. I ran a quick a quick bill thru the above online CVS demo and seems to work.
-Brady

sunsetsystems wrote on Thursday, October 30, 2008:

Cool!

Are you dealing with the database update in 2_9_0-to-2_9_1-upgrade.sql?

Rod
www.sunsetsystems.com