HTTPS to Epic

[Jason Russell]

Has anyone done this with Epic? We’re trying to connect TO interconnect and we’re having a LOT of difficulty connecting via TCP/IP for whatever reason. Has anyone had any luck with HTTPS? If so what did you do to set it up? It looks like we’re either missing or using some wrong https TPS scripts to parse the https connection.

Topic

[David Barr]

I don’t think we have any HTTPS connections from Cloverleaf to Epic. We do have HL7 connections from Cloverleaf to HL7 listeners in Interconnect. Those are sometimes tricky to troubleshoot. You have to set up routing tables and point to them with the IC_IN_TABLE in system defaults. We have multiple levels of routing. The first table routes on message type and it points to other tables that route on either sending application or sending facility.

[Jason Russell]

Yeah, we’ve completed all that, the interconnect guys have completed their setup, but it’s not working. Seems to be on the interconnect listener on Epic’s side. Their TS has found some errors. It’s our first incoming (to Epic) TCP/IP listener, and of course it’s giving us headaches. The only other one we do is a file-based and I’d love to move away from that.

[David Barr]

I’d keep troubleshooting. I don’t think HTTPS is the answer.

[Tim Jipson]

Interconnect doesn’t Need https. We have a couple standard tcp-ip connections interconnect. The big issue we had was a load balancer routing issue. The connection worked when connecting directly to one one the interconnect servers but not the load balancer.

[Jason Russell]

That’s probably what they’re running into. Do you have an SLG to point our TSes at? Do you remember what the error was or what (even vaguely) they had to do to fix?

Essentially we’re getting a connection, but no ack, and it’s not passing data to bridges like it should. They’ve got some errors on their side but the interconnect TS has never seen the error before.

[Author]

Replies