Error On Modules > Carecoordination

reymondko · March 2, 2023, 10:09am

Situation
There seems to be an error when trying to access the CareCoordination tab under the modules, i have already added the settings on manage modules and etc, also ran the ccdaservice but i still get the error (connection failed). please help.

OpenEMR Version
I’m using OpenEMR version 7.0.1-dev

Browser:
I’m using: Brave, Chrome

Operating System
I’m using: AWS Linux 2 server

please help.
here is the screenshot of the error:

bearzillasquatch · March 2, 2023, 12:25pm

@reymondko I had errors similar to this. In my situation it was caused by node.js not running and I also didn’t have node package manager installed on the server. Maybe this will help point you in the right direction or at least rule out a couple of things.

luisuriarte · March 2, 2023, 3:38pm

github.com

openemr/openemr/blob/master/ccdaservice/README.md

# About
This module/service will provide the necessary template engine to create a Patient Summary CCD.
CCD's can be generated from the Onsite Patient Portal or the Carecoordination Module.

Beside installing the C-CDA service, also included in this installation are two new services.
- oe-schematron-service for validating QRDA and CDA type documents. Runs on port 6662.
- oe-cqm-service is our CQM calculator service. Runs on port 6660
## Prepare
* If not already completed, you must install/initialize the CCM features by going to the `Modules->Manage Modules` top menu then click Unregistered tab and install the necessary components.
* Add any appropriate settings like granting Access Control for the appropriate users. Menu item: `Modules->Manage Modules->Access Control->General->Care Coordination`.
* Ensure all appropriate fields are populated in `Modules->Manage Modules Settings` tab such as Author, Primary Care Provider and so forth.
## Updating
#### It's important to note when updating or re-installing to stop any existing node processes before implementing any changes to the service.
Whenever there are new versions or updates, be sure to navigate into the ccdaservice directory and run:
- `npm i --omit=dev`
- `npm ci --omit=dev`

To ensure the lastest libraries are installed, node version changes or the package lock file is for a different build version then it is necessary to run `node install` to update dependencies to locked versions. Next, ensure the installation is renewed by running `node ci` (clean install) will ensure package dependencies are in sync and the node_modules directory is deleted and rebuilt.

This file has been truncated. show original

reymondko · March 3, 2023, 12:49am

yes but i have it on my server

luisuriarte · March 3, 2023, 1:58am

In the readme use node.js version 18.13

reymondko · March 3, 2023, 7:45am

thanks for the reply, but I am actually Using AWS Linux 2 and i dont think its allowing me to install node.js version 18.13. hmmmm