voipbound wrote on Thursday, December 04, 2008:
Arghhh
I formatted and reinstalled everything. It is a fresh install with ubu 8.1, openemr 2.9.0, mysql 5.0, etc… I followed instructions from here, http://www.oemr.org/modules/wiwimod/index.php?page=UbuntuInstall&back=OpenEmrInstallHowtos. If I am missing a PERL module, which do you think it is?
voipbound wrote on Thursday, December 04, 2008:
Looking thru the error, can you guys tell me what you have for /usr/share/sql-ledger/ws_server.pl on line 130? I have &CT::save_customer(’ ', %$myconfig, %$form);
TIA
drbowen wrote on Thursday, December 04, 2008:
Install MySQL like usual.
Set the root password, etc.
Make sure the MySQL server starts like normal.
Then Stop the MySQL server.
move the new /var/lib/mysql to a new directory (for paranoid metal state thinking).
such as:
mv /var/lib/mysql /home/voipbound/mysql.new
Copy the old mysql to /var/lib/mysql
cp /home/voipbound/mysql.original /var/lib/mysql -R
"mv" works also but does not protect your backup copy.
Restart the mysql server.
Everything should be there and working.
I think the module that you are missing is CT::save_customer. This seems to be due to a miss match between the ws_server.pl and the version of SQL-Ledger.
I found a reference to this problem on openemr dot net while on searching the web:
**********
When trying to save patient data after adding demographic data, I received an error indicating that ‘save_customer’ could not be found in CT. After looking in ws_server.pl, I found the sub ‘rpc_add_customer’ that calls: CT::save_customer(’’, %$myconfig, %$form). I then looked in CT.pm and found that there was no sub in CT.pm named ‘save_customer’ I did find a sub named ‘save’ that looked like it performed the correct tasks. Just to find out if it would work, I copied ‘save’ into ‘save_customer’ and it worked. Since this is a major part of the system, and I have not seen other posts about it, I figured that I had done something wrong on install to cause this. Any thoughts?
Update: 4/8/08 - I found that sql-ledger 2.8.x has changed the CT.pm package to contain a save() sub, but not a save_customer() sub any more. I am not sure if I chose the version of sql-ledger, or if it is included in the openemr package. I will check that next, but it looks like if anyone intends to use a newer sql-leger version, the calls to it will need to be changed.
My setup:
Ubuntu server 6.06 LTS, Apache 2, MySql 5.0
OpenEMR v3.3.8-rc1 (from the current download page)
Sql-ledger 2.8.13
***********
A couple of issues come up.
1) I don’t think that we use “ezybiz”
2) SQL-Ledger development is not under our control and it is possibly that it is really the newer version of the SQL-Ledger that is causing this problem
3) There is another project that insists on using the name openEMR but "they are not us".
4) If you could consider upgrading to OpenEMR 2.9.1-dev from CVS. You won’t need ws_server.pl or PERL or SQL-Ledger since the AR management is now inthe the OpenEMR code. (Unless you still want to use SQL-Ledger for your accounting).
Which versions of OpenEMR and SQL-Ledger are you using?
Sam Bowen, MD
voipbound wrote on Friday, December 05, 2008:
First, thank you so much for finding the answer to my problem. I could not find it by googling. Looking thru sql-ledger and its development, I was about to install a few missing packages until I checked back here. Now i can move on. As to my current versions, I am using OpenEMR 2.9.0, Ubu 8.1, Sql-Ledger 2.8.13, Mysql 5.0, Apache 2. I see that you are using OpenEMR 3.3.8? I thought 2.9.1 dev is the latest.
i am looking forward to the using OpenEMR with its own ledger and have installed it to test it out. I am following its development closely and hope that I can transfer the data to it smoothly.
And thank you so much in helping me restore my data with your instructions above. I am sure it will go thru smoothly.
finally, while reinstalling everything in ubu 8.1, I had to add (apt-get install) libwww-mechanize-perl before I could load the CPT codes into the new OS. I hope this is helpful to someone later. If it is, it will be the first helpful thing in these forums.
voipbound wrote on Tuesday, December 09, 2008:
Ok, I moved the old mysql back into /var/lib and renamed the new one. I had to chown the old mysql again like this chown -R mysql;mysql /var/lib/mysql. now I can access the database. when I restart it, there is a password problem but openemr can access the database.
I am testing and wanted to resend a x12 form. This is the error I got
Entry has not been previously sent to external system or no entry was found for them in the integration mapping, could not send claim. Patient: ‘6’
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/classes/WSClaim.class.php:224) in /var/www/openemr/interface/billing/billing_process.php on line 111
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/classes/WSClaim.class.php:224) in /var/www/openemr/interface/billing/billing_process.php on line 112
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/classes/WSClaim.class.php:224) in /var/www/openemr/interface/billing/billing_process.php on line 113
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/classes/WSClaim.class.php:224) in /var/www/openemr/interface/billing/billing_process.php on line 114
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/classes/WSClaim.class.php:224) in /var/www/openemr/interface/billing/billing_process.php on line 115
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/classes/WSClaim.class.php:224) in /var/www/openemr/interface/billing/billing_process.php on line 116
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/classes/WSClaim.class.php:224) in /var/www/openemr/interface/billing/billing_process.php on line 117
Then underneath this last line is an output of the pt and his x12 info. Can you help? In the meantime, I will look at the WSClaim and billing_process and see if there is anything obvious that I can troubleshoot.
TIA
voipbound wrote on Tuesday, December 09, 2008:
Please ignore all of the above. The problem was solved once I uninstall sql-ledger 1.86 and reinstall 1.6.
something
voipbound wrote on Friday, December 19, 2008:
Now that I brought back the old files in openemr and downgraded the sql-ledger, I have another problem. All my claim submissions do not have the ICD-9 and so Office Ally has rejected all the claims. Do I have to re-import all of the ICD’s, CPT, etc… for it to show up in EDI? As of right now, when I enter encounters, they are all there already.
TIA
ripoff wrote on Monday, January 26, 2009:
I have installed the new version 2.9.1 ver and I am getting the following error when I try to save a new encounter:
ERROR: query failed: select id, date, form_id, form_name,formdir,user from forms where encounter = ‘18’ and pid=‘1’ ORDER BY FIND_IN_SET(formdir,‘vitals’) DESC, date DESC
Error: Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation ‘find_in_set’
I appreciated if you can help!
Mark
ripoff wrote on Monday, January 26, 2009:
I just made a posting for the encounter error and I found the solution as posted By: Joe Holzer (ideaman911) on - 2008-11-29 22:46
Thank you Joe!
Mark
the problem was:
ERROR: query failed: select id, date, form_id, form_name,formdir,user from forms where encounter = ‘18’ and pid=‘1’ ORDER BY FIND_IN_SET(formdir,‘vitals’) DESC, date DESC
Error: Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation ‘find_in_set’