Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We recently upgrade to Epic Version May-2019. We had been using QlikView within Radar and had activities to open a patient chart, open a referral or even open a HB/PB account. After this latest go-live the links in QlikView no longer open the possible activity and none give any errors. We did have to upgrade our IIS instance to use HTTPS instead of HTTP as well, but i'm not sure if it is the upgrade that is at issue or the HTTPS change. The link will attempt to launch outside of Epic (but obviously it fails) whereas within Epic it does nothing. We are going back and forth with a TS to get insight, but i wanted to see if anyone out there has had this problem with 2019 Epic. Again, it worked for years, up until about 3 weeks ago. I have tried using hard coded ID values instead of based on a chart row, i have tried several epic activities and nothing. I have also tried using an action on a button to launch the Epic Activity to no avail.
Any advice or ideas are greatly appreciated!
We tried the white listing of our Access Point (even though our whole internal domain was white listed) to no avail. We actually worked with an Epic Radar team member who pointed us in the right direction. We had to change the component that opens our Access Point to a link component rather than an HTML component. The configuration is similar where you have a link to your AP, but now you have to click a traditional hyperlink to then open the AP in hyperspace. I'm not sure how this affected other people, but this what we had to do after our most recent go-live.
Hi @cspencer3 ,
We are in process of implementing this functionality of opening patient chart directly from Qlikview and I could not find any documentation. It looks like that you have successfully implemented it, Is there a way that you can point me right direction. Do you mind sharing steps involved or any other information related to same.
Thanks for your anticipated feedback.
We just tried specifying the whole web address for the white list for our test and production servers and it didn't work. We also already had our entire domain (bassett.org) specified before this. The odd part is we don't even get an error. Its like it doesn't even try to use the link. I have a call with our TS this week to try some more ideas he has.
We tried the white listing of our Access Point (even though our whole internal domain was white listed) to no avail. We actually worked with an Epic Radar team member who pointed us in the right direction. We had to change the component that opens our Access Point to a link component rather than an HTML component. The configuration is similar where you have a link to your AP, but now you have to click a traditional hyperlink to then open the AP in hyperspace. I'm not sure how this affected other people, but this what we had to do after our most recent go-live.