Epic Radar --> Qlik integration: Passing DEP value?

[Anonymous]

We're trying to tightly integrate our many QlikView dashbaords, which provide access to nearly all of our organization's Key Performance Indicators, with Epic Radar dashboards, where our providers and departmental supervisors spend time.

We've shown that we can embed QlikView documents or even single objects in Radar HTML component windows -- but has anyone successfully been able to pass an Epic user's LOGIN_DEP (name and/or number) through Radar to Qlik?

We know how Qlik could use those values to pre-filter displayed information to the user's department, but we can't find a way to get Radar to pass that value (I realize this is more of an Epic question than a Qlik question, but we've had no success through Epic....)

Robert

UCSF Medical Center

San Francisco, CA  USA

[joe_warbington · Accepted solution]

Hi Robert,

What you're looking for are mnemonics that dynamically replace with the appropriate value. There are two built into Hyperspace that you can use to add in the user ID (EMP) or login department (DEP).

• #USERID#
• #DepID#

You can use these in links that you put to Qlik apps from Radar to dynamically set selections for those fields if they exist within the app. Example link:

https://sense-demo.qlik.com/site/sense/app/cd840389-f841-4477-86be-532fb0b13775/sheet/JjhuXG/state/a...

Notice the app URL ends with select / {fieldname} / {value} . Very powerful element of Qlik Sense.

In Epic, the link in Radar would be (just an example - that's not going to work outside of Hyperspace):

https://sense-demo.qlik.com/site/sense/app/cd840389-f841-4477-86be-532fb0b13775/sheet/JjhuXG/state/a...

More details and technical guides are in the Qlik Epic Developers Group

QlikView has a similar capability. The format of the link is as such with a select={OBJECTID},{VALUE}

http://eu-b.demo.qlik.com/QvAJAXZfc/opendoc.htm?document=qvdocs/Prescription%20Tracker.qvw&host=...

Enjoy!

[Anonymous]

Thank you, Joe!  You were absolutely correct, and it turns out (for any other fellow Epic users) that the URL tokens in Epic are CASE SENSITIVE  (and just as inconsistent as you quoted).

The #DepID# token will resolve in a Radar HTML component into the login user's DEP number 
(though this does NOT work for URL link components, strangely enough)

The #USERID# token will resolve in a Radar HTML component into the login user's login ID name (e.g., CADMGR)

We surrounded them with HEX-value asterisks (%2A) to enable wildcard searching in QlikView listboxes, and it worked great.  (Note:  we also found that the version of IE used in Epic / Citrix chokes on commas, too, so we had to use %2C in place of the commas after LB<number> attributes in QlikView URLs...)

[joe_warbington]

Thanks for confirming this works, Robert. Curious - what is the use case / app you're putting in place that would use these techniques?

[Anonymous]

One more question for the community regarding integrating Qlik and Radar at the object/component level:
Are there any specific settings required to allow a URL from Epic to access a *hidden* list box on a QlikView dashboard?  (We've been able to pass departments dynamically from Epic if the target QlikView object is visible, but not [yet] if it's hidden). 

Our use case:

We're embedding QlikView objects into Epic Radar dashboards because Qlik at UCSF houses the vast majority of our monthly/quarterly Key Performance Indicators, while our Epic instance has the bulk of our daily operational data.

We're using the dynamic URLs within Radar HTML components to create a "mashup" of data for our Epic users (who don't care where the data lives, but who have traditionally not been able to see it all in once place).  Epic Radar thus becomes a one-stop portal for multiple QlikView objects/dashboards (with links to the full QlikView dashboards also available if they want to drill down and use the full power of QlikView while still logged into Epic).

Reference:  QlikView Mashups - Simple Object Integration from the Qlikbog.at site

[alie00077]

Hi Robert,

I have tried adding this functionality described in the post, but haven't had any luck getting it to work.  Are there any other behind the scene things you had to do in order to get it to work right?  Would this be the right extension to add or is it slightly different?

;select=LB01,#USERID#

Thanks for any help you can add to this!

Alie