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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Wu's News - Epic and QlikView Integration!

Since joining Qliktech last June, the most exciting things I've seen being done with Qlikview have come from our customers. Applications that address changes in government regulation for things like Meaningful Use or CMS's Shared Savings Program (Read ACO), to applications that look at operational metrics in key areas like the ED or OR's to really innovative one-shot apps for things like research of specific conditions or the correlation between the distance that an ambulance picks up a patient before they are dropped off at the hospital and their acuity level once admitted. I've also often been surprised by how often one customer's innovation could enormously benefit another customers challenges - yet they don't know about it.

Even as the overall healthcare community grows and networks there are still enormous opportunities for better communication and collaboration.

That's why I'm very excited to announce Qlik's new technology partnership with Epic, which is due, in large part to our shared customer bases.

epic Qlik partners.png

Now that we're friends, how about you tell me the secret to Judy's award winning chili.

At HIMSS earlier this year, Epic saw some of the great things some of our customers were doing at the cross-section of our technologies and, after dispelling some misconceptions they had about our technology, they reached out to us in April to begin discussions for a technology partnership.

The partnership is centered around our shared customer base and consists of three parts.


1. The ability for customers to share QlikView applications with each other via the Community Library on Epic's UserWeb.

This will mean that just as customers can share Crystal Reports or Reporting Workbench content, they'll be able to share QlikView applications as well. Depending on the Epic source, these can be pretty simply connected to a new environment, refreshed with your organization's data, and be ready to go in a matter of hours.         


2. Develop and better support the integration of QlikView in Hyperspace.

We'll talk more in-depth about this further down, but there's a natural fit between QlikView's architecture and Epic's Hyperspace framework that allow for some really fantastic opportunities to turn insight from analytics directly into action within Epic.


3. First line of support from Epic.

Bi-directional lines of communication have been setup between Epic Technical Services and Qliktech's North American support team in Raleigh, North Carolina. Qliktech will be able to open Sherlock tickets on behalf of customers and Epic will be able to open support tickets with Qliktech. Additionally, Epic is standing up an internal environment of QlikView to measure scalability and performance.

The most exciting part of this partnership is actually the opportunities for integration. We can use QlikView to deeply analyze Epic (or data from other systems) and have the ability to take action on that immediately within Hyperspace.  This integration can be as simple as hosting QlikView as a workspace in Hyperspace to individual components of radar to configuring callbacks to patient charts, hospital claims or even navigators.

epic qlik integration.png

Oh think of the possibilities!

Any of these options can be configured pretty simply but the launching of an activity requires some additional setup.

To get you started, here's the code I used to launch an activity from QlikView. Special thanks to Dean Health and CHOP for the assistance and being willing to be my guinea pigs.

EpicAct:{ACTIVITY_DESCRIPTOR},RunParams:{RUN_PARAMS},LaunchOptions:{LAUNCH_OPTIONS},InfoName:{INFO_NAME1},InfoValue:{INFO_VALUE1},InfoName:{INFO_NAME2},InfoValue:{INFO_VALUE2}

For example:

EpicAct: UCW_CHART_REVIEW

InfoName: PATIENTID

InfoValue: 12345

If you were to build the html it would look like:

<a href="EpicAct:UCW_CHART_REVIEW,InfoName:PATIENTID,InfoValue:12345">Launch Chart Review</a>

You can now generate this in ETL script to create a link for each patient, or you can use it in a singular button to narrow down to a patient and launch in to them.

If you're interested in setting up any form of Hyperspace integration, please don't hesitate to reach out to me at jwu@qliktech.com

Join Us Thursday afternoon as we formally introduce our partnership with Epic and the incredible integration opportunities available with our technologies. Also in the webcast, Children's Hospital of Philadelphia will talk through some of the really cool ways they've leveraged QlikView and Epic to take better care of their kids and deliver great value to their organization.

Labels (1)
1 Reply
natebrunner
Contributor III
Contributor III

Thanks for this start Jeff . I'd love to see more and more blog posts from you regarding this stuff. I've been working with both Epic and Qlikview for 2 years now and can't wait to see what can be done.