I am trying to generate X12 using ‘standard’ and I am gettin the following error. Where should I look, so far I spent half-day ?
XML error: Invalid document end at line 10Fault: Code: 2 Reason ‘Invalid return payload: enabling debugging to examine incoming payload’
XML error: Invalid document end at line 10Fault: Code: 2 Reason ‘Invalid return payload: enabling debugging to examine incoming payload’
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/freeb/xmlrpc.inc:996) in /var/www/openemr/interface/billing/billing_process.php on line 102
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/freeb/xmlrpc.inc:996) in /var/www/openemr/interface/billing/billing_process.php on line 103
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/freeb/xmlrpc.inc:996) in /var/www/openemr/interface/billing/billing_process.php on line 104
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/freeb/xmlrpc.inc:996) in /var/www/openemr/interface/billing/billing_process.php on line 105
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/freeb/xmlrpc.inc:996) in /var/www/openemr/interface/billing/billing_process.php on line 106
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/freeb/xmlrpc.inc:996) in /var/www/openemr/interface/billing/billing_process.php on line 107
Warning: Cannot modify header information - headers already sent by (output started at /var/www/openemr/library/freeb/xmlrpc.inc:996) in /var/www/openemr/interface/billing/billing_process.php on line 108
ISA*00* *00* *ZZ*701100204…
I think this happens when OpenEMR and SQL-Ledger are out of sync. Apparently, when patient demographics and provider information are entered into OpenEMR, the information is also sent over to SQL-Ledger. If you put information into OpenEMR before you were connected to SQL-Ledger, you may get an error like the one you describe.
Try this:
"Edit" demographics for all your patients, even if you make no actual changes and save patient demographics.
Do the same thing for all providers, including "admin."
I think this happens when OpenEMR and SQL-Ledger are out of sync. Apparently, when patient demographics and provider information are entered into OpenEMR, the information is also sent over to SQL-Ledger. If you put information into OpenEMR before you were connected to SQL-Ledger, you may get an error like the one you describe.
Try this:
"Edit" demographics for all your patients, even if you make no actual changes and save patient demographics.
Do the same thing for all providers, including "admin."
I am moving from 2.7.3 to 2.8.3.
I have applied the sql updates to the openemr database.
On the postgres side I just moved the database. Are there any updates
I should be doing on the database on the postgres side , probably sql-ledger has some
updates ?
Otherwise, the two sides should be in sync.
Do I have to update the demographics one by one ? I have close to 5000 patients
Thanks,
braman
Naturally, you can continue with the older version until you get this debugged.
Maybe try the edit/save thing with providers – should be a small number and ONE patient. Then try creating a new transaction with that ONE patient to see if the error goes away for that ONE patient’s single electronic claim/batch.
The output looks the same as what I get when this is the problem.
This would not be an out-of-sync problem, but rather a problem with the XML/RPC/HTTP communication between OpenEMR and SQL-Ledger. It’s tough to debug that without a programmer being involved, but make sure that your pointer to ws_server.pl in includes/config.php is valid, and that ws_server.pl was installed correctly into the sql-ledger directory and is not missing any dependencies (try running it from a command prompt).
The PostgreSQL database does not need updating unless you have also upgraded SQL-Ledger or PostgreSQL.
Thanks Rod. I am relieved that it’s not a sync’ing problem.
Running ws_server.pl from command line doesn’t report any problem. I’ll thoroughly check the installation.
I am sure I’ve screwed up somewhere.
Funny thing is that billing to paper generates a beautiful hcfa1500.pdf, only the x12 has problems.
Thanks,
braman
If I recall correctly, paper billing does not write to SQL-Ledger until you "Mark as Cleared". See if it fails when you do that.
By the way, make sure you are using ws_server.pl or ws_server_26.pl (renamed to ws_server.pl), as appropriate, from 2.8.3, as well as the current freeb.
Yes, I did get the error when I tried to clear it.
Eventually, to close this thread - I went back to sql_ledger v.2.4.7 and now everything seems to be working. There’s some mismatch with sql_ledger v.2.6 and the old data in v.2.4.7, inspite of applying the sql updates mentioned in sql_ledger.
