Patient Summary in Notes:
Fault: Code: 2 Reason ‘Invalid return payload: enabling debugging to examine incoming payload’
On Magnifying Glass Icon under patient documents:
Warning: Missing argument 3 for find_action() in /srv/www/htdocs/openemr/controllers/C_PatientFinder.class.php on line 34
Generate Report with jpg Documents:
Document ‘wristjpeg.JPG’
NOTE: Document ‘wristjpeg.JPG’ cannot be displayed inline becuase its type is not supported by the browser.
Yet it is viewable under documents option.
Remember, under the openemr version of sql-ledger there was a symbolic link from sql-ledger/ws_server.pl to sql-ledger/bin/ws_server.pl so it just needs to point to where ever ws_server.pl is stored.
I updated the includes/config.php to
$GLOBALS[‘oer_config’][‘ws_accounting’][‘url’] =
“/sql-ledger/bin/ws_server.pl”;
and I placed a sym link to it as well. Further more I created a new patient as well.
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: ‘35’
Warning: Cannot modify header information - headers already sent by (output started at /srv/www/htdocs/openemr/library/classes/WSClaim.class.php:159) in /srv/www/htdocs/openemr/interface/billing/billing_process.php on line 77
I’m hoping to find a work around before blowing the DB away. For my demo site I dont have a problem with this. But I’m sure that a clients sqeal will not be one of joy.
So you got rid of the "invalid return payload" message? Good!
You can check the integration_mapping table and others from the Administration/Database Reporting page, which is really phpMyAdmin. See if you have an entry for that patient, or for any patients. If you do, you can check the local_id in the patient_data table, and the foreign_id in the sql-ledger customer table (use psql or phpPgAdmin).
I don’t think blowing away the database will solve anything. This is a debugging problem.
No, the payload error sounds serious to me. It may be related to the integration_mapping table not getting updated. Start by reproducing the problem and then checking your log files. If you like, you could email your configuration files to me and I’ll check them over.
Probably /var/log/apache or /var/log/apache2 depending on your installation of apache. I’m assuming that you’re using apache here. If not, then it will probably be in /var/log somewhere
This will be system-dependent. On my Ubuntu (Debian-like) setup PHP errors go to /var/log/user.log and Apache errors to /var/log/apache2/error.log. There can also be meaningful messages in places like /var/log/messages or /var/log/syslog.
Im using SuSE 9. I did notice that /sql-ledger/bin/ws_server.pl points to srv/www/sql-ledger. I’ve changed it to /srv/www/htdocs/sql-ledger. What entries should be in the pg_hba.conf file?