Quovadx Secure Messenger (HTTPS) and the Engine

[Bob Richardson]

Greetings,

We are looking to evaluate the Quovadx Secure Messenger product from Quovadx (a 30 day pilot) for possible direct connections to/from payers.  Does anyone have experience in working with this product?  Any documentation?  Caveats for the Engine?

Thanks in advance for any response.

Topic

[Rick Martin]

Hi Bob,

It doesn’t look like you got a reply to your inquiry.  Did you evaluate this product?  If so, what did you think?  I’ve been asked to look at it as well.

Thanks, Rick

[Bob Richardson]

Reply to Rick Martin:

Rick, our evaluation has just begun this month, 12/05, and so far we have not been successful in sending and receiving a reply from one of our trading partners.  The HTTPS method that we need to use here is POST, that is, the reply (in our case a 271 or Eligibility Response) will reside in a key field DATA in the response.  I have been trying to find more specific information about how to make this connection work from both the Cloverleaf 5.3 Programmer Reference and User Guide.  The message flow is not conventional (it appears).  We are waiting for our trading partner to contact us and let us know what they do not like about our POSTed message.  Once we get some results, I will reply again.

Please let us know via this forum if you are successful in configuring an HTTPS connection.

Thanks.

[garry r fisher]

Hi,

We also tried to use HTTPS and failed:-)

We ended up setting up a TCPIP connection to a Tomcat/Apache web server and then used HTTPS between Tomcat/Apache and the third party. This is only a temporary solution and we definitely need to find out how to use HTTPS from Quovadx.

Any assistance on this would be much appreciated either from Quovadx or another experienced user.

Regards

Garry

[Author]

Replies