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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, Rod, for that advice. I created another directory called /var/www/openemr_dev and did a fresh CVS installation. I made the changes in globals.php so that it recognized that as the proper working directory. I am able to use the same working openemr database with either version of OpenEMR.
I'va had a chance to try the pdf and X12 insurance claim generation, the billing reports, invoices, payment application, receivables ageing etc. Now that I've found my way through the menus, it's time to do some serious playing around with it.
Ronald Leemhuis MD
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hey,
Nope, the online CVS demo and Developer Appliance install from scratch every time. They take advantage of the Virtual Machine function of being able to revert to a previous "snapshot". So, the CVS demo basically resets to a blank slate every morning, and then installs the most recent version of OpenEMR from CVS. So, it's doesn't test any of the upgrade scripts(phpGACL, sql, etc.).
-Brady
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Front Office Receipts report doesn't seem to do anything. I've tested with a co-pay and a checkout function and neither transaction seems to appear.
This may be the way it's always been, but the tax rate entry in lists requires the tax expressed as a decimal multiplier instead of a whole number percentage (.0825 instead of 8.25). This is fine, just confusing. Only realized it when I went to checkout and my tax was higher than the charge itself.
The pop-ups for checkout, pre-pay, import/export, etc stop working after 1 use in Apple's Safari.
Also, I know just from some recent hassles with our practice and sql-ledger that we will require more reporting tools than currently provided. I'll need to poke at it some more and think about it, but I will try to compile a list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tested it. it is working great so far.
Here what I did. I did not want to mess with the production server, so I created a back up copy as follow:
1-I upgraded 2.9 to include the backup restore link (added all files from CVS)
2- create back up tar (emr_backup.tar) ~ 18 MB
3- used the script inside contribute to restore into an experimental server with Fedora 9 installed.
All database installed automatically (openemr, pgpgacl) with real data.
Then I download from CVS all updated files for Accounting (see above) and replaced all files.
It worked right away no issues so far...
Great job Rod.........Perfect.........I will keep testing then consider upgrading my production sever.
Is this a complete replacement for SQL-Ledger?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
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
Yea! Rod!
Sam Bowen, MD
Rod,
Will the new features support physical product sales and sales tax?
Fred: Drug/product sales and sales tax are already supported; that will not change.
Mike: Testers will definitely be appreciated!
Rod
www.sunsetsystems.com
Let me know when Rod.
I have a ton of patient encounters that have not been billed ( from within OpenEMR ).
-Mike
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,
count me in for testing!
I think it is safer to ask who doesn't want in
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
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
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
Thanks, Rod, for that advice. I created another directory called /var/www/openemr_dev and did a fresh CVS installation. I made the changes in globals.php so that it recognized that as the proper working directory. I am able to use the same working openemr database with either version of OpenEMR.
I'va had a chance to try the pdf and X12 insurance claim generation, the billing reports, invoices, payment application, receivables ageing etc. Now that I've found my way through the menus, it's time to do some serious playing around with it.
Ronald Leemhuis MD
Nice! Well done, Rod! somebody buy that man a drink.
Can someone post instructions on how to get this CVS update into the system, I think that would help everyone.
Info about accessing CVS is here:
https://sourceforge.net/cvs/?group_id=60081
Rod
www.sunsetsystems.com
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)
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
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
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
Cool!
Are you dealing with the database update in 2_9_0-to-2_9_1-upgrade.sql?
Rod
www.sunsetsystems.com
hey,
Nope, the online CVS demo and Developer Appliance install from scratch every time. They take advantage of the Virtual Machine function of being able to revert to a previous "snapshot". So, the CVS demo basically resets to a blank slate every morning, and then installs the most recent version of OpenEMR from CVS. So, it's doesn't test any of the upgrade scripts(phpGACL, sql, etc.).
-Brady
Rod,
Things I've seen so far in just a few minutes:
The Front Office Receipts report doesn't seem to do anything. I've tested with a co-pay and a checkout function and neither transaction seems to appear.
This may be the way it's always been, but the tax rate entry in lists requires the tax expressed as a decimal multiplier instead of a whole number percentage (.0825 instead of 8.25). This is fine, just confusing. Only realized it when I went to checkout and my tax was higher than the charge itself.
The pop-ups for checkout, pre-pay, import/export, etc stop working after 1 use in Apple's Safari.
Also, I know just from some recent hassles with our practice and sql-ledger that we will require more reporting tools than currently provided. I'll need to poke at it some more and think about it, but I will try to compile a list.
Oh! And great work so far!
I tested it. it is working great so far.
Here what I did. I did not want to mess with the production server, so I created a back up copy as follow:
1-I upgraded 2.9 to include the backup restore link (added all files from CVS)
2- create back up tar (emr_backup.tar) ~ 18 MB
3- used the script inside contribute to restore into an experimental server with Fedora 9 installed.
All database installed automatically (openemr, pgpgacl) with real data.
Then I download from CVS all updated files for Accounting (see above) and replaced all files.
It worked right away no issues so far...
Great job Rod.........Perfect.........I will keep testing then consider upgrading my production sever.
Is this a complete replacement for SQL-Ledger?