CCDA NPM@16 not available nor 18 both deprecated

Day-to-Day Users
1

@sjpadgett

To my knowledge, the CCDA service was built around NPM 16. I looked it up, and it was deprecated in 2023. What npm version are we supposed to install to get the CCDA service running?

 npm error notarget No matching version found for npm@16.
2 Likes
2

Hi Sherwin,
Do you mean node version? I believe we recommend v24.
I haven’t paid attention to npm version. I run v11.3.

Still the good news is that @Firehed Eric has been developing a new engine using pure PHP which is turning out very well. I would expect at his current rate of work we could have it by time we attest for 2027 certification.

So here soon I hope to be seeing a forum topic asking me what PHP version is required for CCDA. :slight_smile:
Seriously, the migration is a big deal to the project.

1 Like
3

@sjpadgett

I always follow the instructions in the read me file. I have a version 8.2.0 of the program on Ubuntu 24.04 with npm 11.x.

Ccda service will not start up.

I have a migration to do now. I did hear about the PHP version coming. That’s nice but not helpful today.

4

NPM builds the project node runs it so what version node are you running.node -v

5

My npm version is 11.18.0.

sherwin@ip-172-31-11-16:/var/www/html/emr/ccdaservice$ sudo npm install --omit=dev
changed 1 package, and audited 329 packages in 1s

47 packages are looking for funding
run npm fund for details

5 moderate severity vulnerabilities

To address issues that do not require attention, run:
npm audit fix

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.
npm warn allow-scripts 1 package has install scripts not yet covered by allowScripts:
npm warn allow-scripts libxmljs2@0.37.0 (install: node-gyp rebuild)
npm warn allow-scripts
npm warn allow-scripts Run npm approve-scripts --allow-scripts-pending to review, or npm approve-scripts <pkg> to allow.

RuntimeException

File:

/var/www/html/emr/src/Services/Qrda/QrdaReportService.php:47

Message:

Can not complete report request. Node Service is not running.

There are no errors in the error log.

6

OpenEMR has to auto start two or three node servers, CQM, Schematron if turned on in Config and serveccda service.
We’ve never had issues with spawning on linux but windows it occasionally comes up.
I fixed widows a few versions ago and recently have been having issue using master.

I’d bet this is your issue but to test the build and specific failure designation service not starting you can test going to:

  • Failing to start from app: node ccdaservice/packages/oe-cqm-service/server.js
  • CCDA service: node ccdaservice/serveccda.js

CRTL-C to exit or leave running.

If

node ccdaservice/packages/oe-cqm-service/server.js
node:events:485
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use 127.0.0.1:6660
    at Server.setupListenHandle [as _listen2] (node:net:1939:16)
    at listenInCluster (node:net:1996:12)
    at node:net:2205:7
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1975:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  code: 'EADDRINUSE',
  errno: -4091,
  syscall: 'listen',
  address: '127.0.0.1',
  port: 6660
}

Node.js v24.0.1

Already running in which case app will ignore and start carecoordination.

Sherwin, if ya need some help give me a call. Easier for me and I’ll return here with outcome.
Also, it’d be nice to let us know OpenEMR and node -v versions

7

Thanks for burning some energy on this post.

Part of my issue was that npm was installed root:root and a slew of other cascading issues that were all server install related. Thanks again. It is working now. Oz fixed it.