Care Coordination Module issue importing documents

Support
1

Situation
Care Coordination Module displays the following error message after attempting to import a ccd document for a new patient, not added yet:

An error occurred

An error occurred during execution; please try again later.

This is a persistent error and also occurs in the CCDA import page.
The CCR page itself displays the following;
ERROR :
Exception: Statement could not be executed (HY093 - - )
Exception: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens
SQL statement : SELECT am.id as amid, cat.name, u.fname, u.lname, d.imported, d.size, d.date, d.couch_docid, d.couch_revid, d.url AS file_url, d.id AS document_id, ad.field_value, ad1.field_value, ad2.field_value, pd.pid, CONCAT(ad.field_value,’ ‘,ad1.field_value) as pat_name, DATE(ad2.field_value) as dob, CONCAT_WS(’ ',pd.lname, pd.fname) as matched_patient
FROM documents AS d
JOIN categories AS cat ON cat.name = ‘CCR’
JOIN categories_to_documents AS cd ON cd.document_id = d.id AND cd.category_id = cat.id
LEFT JOIN audit_master AS am ON am.type = ‘11’ AND am.approval_status = ‘1’ AND d.audit_master_id = am.id
LEFT JOIN audit_details ad ON ad.audit_master_id = am.id AND ad.table_name = ‘patient_data’ AND ad.field_name = ‘lname’
LEFT JOIN audit_details ad1 ON ad1.audit_master_id = am.id AND ad1.table_name = ‘patient_data’ AND ad1.field_name = ‘fname’
LEFT JOIN audit_details ad2 ON ad2.audit_master_id = am.id AND ad2.table_name = ‘patient_data’ AND ad2.field_name = ‘DOB’
LEFT JOIN patient_data pd ON pd.lname = ad.field_value AND pd.fname = ad1.field_value AND pd.DOB = DATE(ad2.field_value)
LEFT JOIN users AS u ON u.id = d.owner
WHERE d.audit_master_approval_status = 1
ORDER BY date DESC(‘CCR’)

#0 /var/www/html/openemr/interface/modules/zend_modules/module/Application/src/Application/Model/ApplicationTable.php(62): Laminas\Db\Adapter\Driver\Pdo\Statement->execute()
#1 /var/www/html/openemr/interface/modules/zend_modules/module/Ccr/src/Ccr/Model/CcrTable.php(95): Application\Model\ApplicationTable->zQuery()
#2 /var/www/html/openemr/interface/modules/zend_modules/module/Ccr/src/Ccr/Controller/CcrController.php(72): Ccr\Model\CcrTable->document_fetch()
#3 /var/www/html/openemr/vendor/laminas/laminas-mvc/src/Controller/AbstractActionController.php(77): Ccr\Controller\CcrController->indexAction()
#4 /var/www/html/openemr/vendor/laminas/laminas-eventmanager/src/EventManager.php(331): Laminas\Mvc\Controller\AbstractActionController->onDispatch()
#5 /var/www/html/openemr/vendor/laminas/laminas-eventmanager/src/EventManager.php(188): Laminas\EventManager\EventManager->triggerListeners()
#6 /var/www/html/openemr/vendor/laminas/laminas-mvc/src/Controller/AbstractController.php(103): Laminas\EventManager\EventManager->triggerEventUntil()
#7 /var/www/html/openemr/vendor/laminas/laminas-mvc/src/DispatchListener.php(139): Laminas\Mvc\Controller\AbstractController->dispatch()
#8 /var/www/html/openemr/vendor/laminas/laminas-eventmanager/src/EventManager.php(331): Laminas\Mvc\DispatchListener->onDispatch()
#9 /var/www/html/openemr/vendor/laminas/laminas-eventmanager/src/EventManager.php(188): Laminas\EventManager\EventManager->triggerListeners()
#10 /var/www/html/openemr/vendor/laminas/laminas-mvc/src/Application.php(331): Laminas\EventManager\EventManager->triggerEventUntil()
#11 /var/www/html/openemr/src/Core/ModulesApplication.php(116): Laminas\Mvc\Application->run()
#12 /var/www/html/openemr/interface/modules/zend_modules/public/index.php(66): OpenEMR\Core\ModulesApplication->run()

OpenEMR Version
I’m using OpenEMR version 6.0.0 with the 6-0-0-Patch-3 applied.
PHP 8.0.12 (cli) (built: Oct 19 2021 10:34:32) ( NTS gcc x86_64 )
Copyright (c) The PHP Group
Zend Engine v4.0.12, Copyright (c) Zend Technologies
with Zend OPcache v8.0.12, Copyright (c), by Zend Technologies

Browser:
I’m using: Firefox 94.0 (64-bit)

Operating System
I’m using: Fedora 35

Logs
I just turned onn User Debugging under Administration->Globals->Logging User Debugging Options=>All.

Simple-xml is enabled;
php -i | grep -i simplexml
/etc/php.d/20-simplexml.ini,
SimpleXML
SimpleXML support => enabled

Let me know what else that you may need.
In a search, I could not find a previous situation that described my issue.

Thanks!

2

That’s a really bizarre error because that query doesn’t have any bound parameters as far as I can tell at all. Can you copy the query and run it in phpmyadmin? Does the query execute?

Only thing I can think of is that maybe your missing a column and need to run the sql_upgrade.php and the query error message is being triggered due to a missing column and not a bound parameter problem.

3

OK, I’m not a phpmyadmin regular user, but this is what I get;

SQL query:
SELECT am.id as amid, cat.name, u.fname, u.lname, d.imported, d.size, d.date, d.couch_docid, d.couch_revid, d.url AS file_url, d.id AS document_id, ad.field_value, ad1.field_value, ad2.field_value, pd.pid, CONCAT(ad.field_value,’ ‘,ad1.field_value) as pat_name, DATE(ad2.field_value) as dob, CONCAT_WS(’ ',pd.lname, pd.fname) as matched_patient FROM documents AS d JOIN categories AS cat ON cat.name = ‘CCR’ JOIN categories_to_documents AS cd ON cd.document_id = d.id AND cd.category_id = cat.id LEFT JOIN audit_master AS am ON am.type = ‘11’ AND am.approval_status = ‘1’ AND d.audit_master_id = am.id LEFT JOIN audit_details ad ON ad.audit_master_id = am.id AND ad.table_name = ‘patient_data’ AND ad.field_name = ‘lname’ LEFT JOIN audit_details ad1 ON ad1.audit_master_id = am.id AND ad1.table_name = ‘patient_data’ AND ad1.field_name = ‘fname’ LEFT JOIN audit_details ad2 ON ad2.audit_master_id = am.id AND ad2.table_name = ‘patient_data’ AND ad2.field_name = ‘DOB’ LEFT JOIN patient_data pd ON pd.lname = ad.field_value AND pd.fname = ad1.field_value AND pd.DOB = DATE(ad2.field_value) LEFT JOIN users AS u ON u.id = d.owner WHERE d.audit_master_approval_status = 1 ORDER BY date DESC(‘CCR’);

MySQL said: Documentation
#1583 - Incorrect parameters in the call to native function ‘CONCAT’

4

Double check that wherever you are copying that query from doesn’t have special quote characters. From what you are posting here it looks like different quotes are being used but that may just be a rendering problem here in the forum. I’d double check that.

5

Thanks, I will try and do this. Interestingly, i installed another instance of OpenEMR in a virtual machine on Windows 11 with XAMPP. Same errors on the import pages.

6

I get the same error. xampp 8 on mac, openemr 6 patch 3. I did not have errors with care coordination until I applied the patch. Did not see any issues when I ran sql_patch.php

7

The only error in php_error_log is:
Invalid parameter number: number of bound variables does not match number of tokens
SQL statement : SELECT option_id, title FROM list_options WHERE list_id = ‘abook_type’(’’)
#0 /Applications/XAMPP/xamppfiles/htdocs/openemr/interface/modules/zend_modules/module/Application/src/Application/Model/ApplicationTable.php(62): Laminas\Db\Adapter\Driver\Pdo\Statement->execute(Array)

8

Yes, that error shows on my installation as well under the export tab in the CareCoordination module.

So, the net result right now is that no imported xml files show under imports, therefore, cannot be linked to existing patients.

i also did a complete reinstall on the Fedora machine…same problem.

I’m going to play around with some other things and see what happens.

9

Screenshot 2021-11-24 at 14-12-53 OpenEMR
Screenshot 2021-11-24 at 14-12-53 OpenEMR1920×746 13.9 KB

Screenshot 2021-11-24 at 14-13-14 OpenEMR
Screenshot 2021-11-24 at 14-13-14 OpenEMR1920×746 211 KB

This shows what is being displayed in the import tabs.

10

Any more suggestions on this error that occurs in Fedora, now version 37? It persists on this installation.

11

We don’t really support the CCR import as CCR is not commonly used as far as I know. Can you explain your need.
My major focus has been on CCDA as it has the most widespread use.

Also if you need CCDA import I’d upgrade to v7 with patch 2 applied.

Try importing your document with CCDA import.

12

Thank you for the quick response. I apologize for any confusion, but I probably need to post a new thread, as I now have a new install with OpernEMR V7 with the newest patch applied. The message is now “Connection failed” when I try to access the Care Coordination Module.

Fedora 37
Nodejs installed V 16.8
Checked off Care Coordination only in Admin/Connectors.

I looked around the posts in search and found nothing that matches this issue.

13

Go to the ccdaservice directory and run npm install then npm ci

14

Thank you for the reply. Still a no go. I did previously do npm install,and now added ci. Not sure if it matters, but I needed to run these as the root user, using sudo.

image

It looks like the Fedora development page for nodejs may help with this, I’ll try that and see what happens. Here is the error page when i try to bring up Care Coordination;

image
image1814×626 58.9 KB

15

No luck with this. Any other suggestions?
node -v = v16.18.1
npm -v = 8.19.2
sudo node serveccda.js
node:events:491
throw er; // Unhandled ‘error’ event
^

Error: listen EADDRINUSE: address already in use 127.0.0.1:6661
at Server.setupListenHandle [as _listen2] (node:net:1463:16)
at listenInCluster (node:net:1511:12)
at GetAddrInfoReqWrap.doListen [as callback] (node:net:1660:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:111:8)
Emitted ‘error’ event on Server instance at:
at emitErrorNT (node:net:1490:8)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
code: ‘EADDRINUSE’,
errno: -98,
syscall: ‘listen’,
address: ‘127.0.0.1’,
port: 6661

16

You need to figure out what is already using the 6661 port. You may already have the service running.

This command will tell you if the process is already running

ps aux | grep serveccda

and this command should tell you what is using port 6661

netstat -a | grep 6661
17

Thanks for the quick reply.
ps aux | grep serveccda

10772 0.0 0.1 712440 56560 pts/0 Tl 07:35 0:00 node serveccda
12433 0.0 0.0 222152 2168 pts/0 S+ 07:48 0:00 grep --color=auto serveccda

netstat -a | grep 6661
tcp 0 0 localhost:6661 0.0.0.0:* LISTEN

18

you can try killing the process and then check if the module starts the service
kill 10772