Hi,
We are stuck because the production server where the final testing is being done can’t pull a token from the Quest Hub. It is that server issue. The user can get a token from the command line using curl but the application can’t pull in a token. I have no idea what to instruct them to do. I asked Ron at Quest if we could get another company to do the production testing to finish the certification. I am waiting for an answer.
Which application. Your app Sherwin can’t pull what token?
@sjpadgett it is not the fault of the app. I have the same Quest Lab app running on two different servers and both of them pull a token from Quest. There is a feature in the app to test if the server is getting a token from Quest. The system in question does not. But can from the command line. I don’t have access to the server in question (nor do I want access). =^)
I have the code on a private repo. https://github.com/juggernautseinc/oe-quest-lab-hub but without a Quest account it is useless.
I get it but it just was interesting to me what the issue could be. Perhaps a PHP setting!
Anyway to satisfy my curiosity would you report back if you solve?
Yes, because that is what I am thinking it is a settings issue but the really weird thing is that the same system could pull a token from the Quest sandbox but not from the production system. The same code with no changes other than the URL. It should have been easy peasy. But then Murphy got involved and you know what that means.
If it is url, are you sure Quest has set up their prod server to issue the token to you? Are you saying you can get token from that url using plain browser but not thru your code? Can you post code snippet and error log? Quest does not include any diagnostic tool to validate the setup on their side?
PS
In EDI world, one of the most common issues during server switch is clients forgetting to switch ‘T’ to ‘P’ causing production server on other end to reject/ignore the messages as it is incapable of supporting T(est) mode. If Quest has similar approach, they would have documented this somewhere.
@mdsupport I asked the client if he had checked the box in the Globals. He assured me that he did.
I sent him traps set throughout the code. He sent me back the log entries. The cURL call is posting the correct URL. His credentials work from the command line so Quest has his account set up on the production server. I have used his credentials on my server and I am able to get a token from the Quest production server. On his server, the cURL call is not receiving the credentials. 
I’d grab a phpinfo dump of the server. IE send a phpinfo.php file for the customer to put on the server and compare the extension info. Could be the php-curl extension is a different version or something is going on with the SSL handshake at the php level. I’ve seen that go wrong if you are getting things on the command line but nothing on the server.
I just got word back from the provider today that he reinstalled the original code and the test brought back a token. He was able to send an order in. Now, Ron needs to find the order in the queue. Then we will be in release.
@adunsulag the doctor on the other side would never give me that information. Whenever I ask for the log file. He only sends me the lines of the log file he thinks I need to see and nothing more.
But all seems well now and we may be live before December 1!
1 Like
Clap your hands. We are nearing a release of this module (again).
2 Likes
Hand clapping literally
Has this been released officially?
Yes, but it is unsupported until patch one is released.
https://www.open-emr.org/wiki/index.php/OpenEMR_Modules#Quest_Quantum_Hub_Module
Here are the code base changes that are needed to support the module.
It has been in action in the field since February 2024.
Best!
Awesome work Sherwin!
1 Like
Help,
After reading through this post, I located the Quest module in my OEM 7.0.2, install it, enable it and now I can’t access to log into my OEM. It is just a blank page. My OEM sits on Ubuntu 22.04, PHP-FPM 8.2, serving on NginX . Error log shows :
2024/03/27 15:36:21 [error] 1391#1391: *2118 FastCGI sent in stderr: "PHP message: PHP Warning: Private methods cannot be final as they are never overridden by other classes in /var/www/html/emr/src/Common/Logging/EventAuditLogger.php on line 21; PHP message: PHP Fatal error: Uncaught Error: Class “OpenEMR\Events\Encounter\EncounterButtonEvent” not found in /var/www/html/emr/interface/modules/custom_modules/oe-quest-lab-hub/src/Bootstrap.php:97
Any idea on how I can fix this?
I also see this error in my log but can’t find out how to fix this
src/Events/Encounter/EncounterButtonEvent.php
Since patch one has not been released. It will not work and possibly break your system. Unless you install all of the core parts that need to be in the system.
Uninstall the module until the patch is release or install the core parts that are needed to operate the module.
How can I uninstalled it? I can’t log in. What are the command line instructions to do a complete module uninstall
I got it back. All I had to do was to remove the directory in the …/interface/modules/custom_modules/oe-quest-lab-hub. Then I went to module management and uninstall it.
Is there anything else I need to do to be certain I won’t be haunted my this module until it is later release in future patches?
1 Like
Not that I know of at this time. Thanks for your patience and posting here on the forum.