Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
cspencer3
Creator II
Creator II

Epic Chart Launch Using QlikView - Post Epic 2019 Version

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! 

Labels (1)
1 Solution

Accepted Solutions
cspencer3
Creator II
Creator II
Author

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. 

View solution in original post

6 Replies
jwbadger3
Contributor II
Contributor II

One of Epic's undiscussed components based around Browser Whitelisting is that it will no longer allow embeddable content unless it's a part of the Whitelist. You'll need to add your QV app URL (or fully qualified QV server address) to Epic's browser whitelist as well as click 'allow all actions' checkbox.

Give that a shot.
neelamsaroha157
Specialist II
Specialist II

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.

cspencer3
Creator II
Creator II
Author

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. 

andythomas
Observer
Observer

Drop me a note, I might be able help send you the documents.
joe_warbington
Partner - Creator III
Partner - Creator III

 
Example app for Qlik Sense with Epic links to patient chart review: https://community.qlik.com/t5/Qlik-Epic-Developers/App-Qlik-Healthkit-for-Epic-qvf-Qlik-Sense/gpm-p/...
 
You also need to make sure things are whitelisted for Qlik inside of Epic: https://community.qlik.com/t5/Qlik-Epic-Developers/QlikView-Epic-Chart-launch-problem/gpm-p/1240934
 
Search this community to find other resources for Qlik Epic Integration.
 
(Also - I'm back in the Qlik Community to help people out!!! Send me a message or track me down on LinkedIn if you have questions: https://www.linkedin.com/in/warbington/)
cspencer3
Creator II
Creator II
Author

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.