CCDA or QRDA Cat I: Gateway Timeout

kkappiah · June 4, 2025, 1:01pm

Situation
@sjpadgett , @adunsulag Trying to import CCDA using the tab CCDA or QRDA Cat I, the page takes a while to load and responds with the error “504: Gateway Timeout”. In the apache logs i get the following error

[proxy_fcgi:error] [pid 11374:tid 133869147772608] (70007)The timeout specified has expired: [client 129.224.201.130:26530] AH01075: Error dispatching request to : (polling), referer: http://localhost/openemr/interface/modules/zend_modules/public/encountermanager

In the Network tab in the browser, i see the reference to the failing url as

http://localhost/openemr/interface/modules/zend_modules/public/carecoordination/upload?id=1

I have has set indefinite settings for my php.ini
max_execution_time = 0
memory_limit = -1

Thanks in advance

OpenEMR Version
7.0.2

Browser:
I’m using: Chrome

Operating System
I’m using: Ubuntu

sjpadgett · June 6, 2025, 8:40pm

Ensure RewriteEngine is installed and enabled. Also try setting up directories for zend modules are included in your vhost.
openemr install doc shows what these directories are I believe.

Good luck. BTW tested okay for me on ubuntu.

kkappiah · June 9, 2025, 3:36pm

Thanks Jerry,

I am not sure if this information will help.

After a fresh installation of OpenEMR, the Carecoordination interface shows up for importing CCDA files. I have had a couple of files imported. Then suddenly, i start getting gateway timeout errors.

Thats a little confusing.

Modrewrite has been installed and enabled else the CCDA would not show up.

juggernautsei · June 9, 2025, 5:55pm

@kkappiah, have you followed these instructions?

github.com/openemr/openemr

ccdaservice/README.md

master

# 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

sjpadgett · June 9, 2025, 6:26pm

Look into your environment(could have shared that at top of issue) and check or mod configs
#php.ini
request_terminate_timeout = 300
max_execution_time = 300
memory_limit = 512M
post_max_size = 32M
upload_max_filesize = 128M

#In vhost or apache2.conf
ProxyTimeout 300

How large are the files and does same ccda fail while others succeed? Are you dealing with more of those mass imports from some ehr?

kkappiah · June 9, 2025, 9:00pm

I actually use this as a guide in installing the module.

kkappiah · June 9, 2025, 9:02pm

The only thing i haven’t tried here is the “request_terminate_timeout” and the “proxyTimeout”.

The files are a few KB. i havent seen any file above 1MB.

Yes, dealing with mass import from another EHR

sjpadgett · June 9, 2025, 9:08pm

Certainly could use some more information my friend! Does it fail consistently on any one ccda import? If so send to my email. For sure, some work and others don’t, correct?

Proxy concerns me some. You still haven’t given us a run down of the environment running in!

Re: could have a bug causing an endless loop

kkappiah · June 9, 2025, 9:13pm

I haven’t been able to confirm if there is a specific file causing the issue.

Oh sorry, i missed the part of the environment setup
I am running OpenEMR 7.0.2 on Ubuntu

16GB RAM
4vCPU
Thus AWS m8g.xlarge