Customer Presentation - Chris Hogan, Sr. Solution Architect, Cerner Corporation and Tom Twait, Manager/Solution Architect, Cerner Corporation

1. Tom Twait & Chris Hogan
Cerner Revenue Cycle – EDI Services Manager & EDI Services Senior Solution Architect
April 14th, 2016
Monitoring a Database Driven System
Utilizing Splunk’s DB Connect

2. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
1
Why Splunk?

3. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
2
Agenda
• Key Takeaways
• Speaker / Company Bio
• Cerner Revenue Cycle / Real-time Eligibility Transactions
• Problem Statement
• Dashboards & Alerts
• Splunk DB Connect
• Current Development Project
• Q&A

4. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
3
Disclaimer
During the course of this presentation, we may make forward looking statements
regarding future events or the expected performance of the company. We caution
you that such statements reflect our current expectations and estimates based on
factors currently known to us and that actual events or results could differ
materially. For important factors that may cause actual results to differ from those
contained in our forward-looking statements, please review our filings with the
SEC. The forward-looking statements made in the this presentation are being
made as of the time and date of its live presentation. If reviewed after its live
presentation, this presentation may not contain current or accurate information. We
do not assume any obligation to update any forward looking statements we may
make. In addition, any information about our roadmap outlines our general product
direction and is subject to change at any time without notice. It is for informational
purposes only and shall not, be incorporated into any contract or other
commitment. Splunk and Cerner undertake no obligation either to develop the
features or functionality described or to include any such feature or functionality in
a future release.

5. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
4
Takeaways
• Understand our use case and think
of ways you can apply it at home
• Understand how dbConnect can
be utilized to connect to multiple
data sources
• High-level knowledge of healthcare
EDI (Electronic Data Interchange)
• Understand how Splunk can be
used to tie together disparate
systems

6. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
5
Who is Cerner?
• One of the largest healthcare software IT companies in the world
• $4B+ Annual Revenue
• Publicly traded (NASDAQ) with 20 years of 20% compounded annual growth
• 22,000+ associates in 18 countries globally

7. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
6
Who are Tom & Chris
Chris:
• 5 years at Cerner
• 6+ years at nationally recognized
health insurance company
• Focus areas: Revenue Cycle,
Data, & Technology
• University of Missouri
• Rockhurst University (MBA)
• Fun Fact: Played in World Series
of Poker Main Event
Tom:
• 14 years at Cerner
• Manages team of Solution
Architects and Business Analysts
• Focus areas: Revenue Cycle,
Community Health and
Technology
• University of Iowa
• Fun Fact: Once owned a 1983
Chrysler Laser

8. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
7
What Tom & Chris do?
Revenue Cycle Transaction Services (EDI)
• Registration Management
• Scheduling Management
• Acute Care Management
• Practice Management
• Patient Accounting
• Transaction Services (EDI)
• Address Validation
• Address Verification
• Claims Scrubbing
• Contract Management
• Credit Card Processing
• Medical Necessity
• Real-Time Eligibility
• Etc…

9. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
8
Real-Time Eligibility Transactions
Partners
Payers
Hospitals/Clinics

10. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
9
Why Splunk?

11. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
10
Why Splunk / Problem Statement
• Trade show conference introduction to Splunk
• Atypical journey – Log files not a priority
• Limited operational reporting
• Cumbersome process to analyze data
• Often reactive, not proactive
• Minimal visibility for operations team when system issues arose
• Data blind to real-time or near real-time events
• Slow moving process improvement initiatives
• Wanted to more effectively monitor database activity
• dbConnect was first thing ever used
• Pre-Splunk
• No on-demand dashboards and reports
• No alerts
• Only technical analysts could investigate issues

12. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
11
Technical Setup of System
• The COMPLEXITY of our system……….
• Windows Server 2008 R2 Enterprise x64
• Splunk
• Oracle Drivers
• Oracle 11g database
DB
Connect

13. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
12
DB Connect

14. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
13
DB Connect – External Databases

15. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
14
DB Connect – Database Inputs

16. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
15
DB Connect

17. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
16
Dashboards – Partner Response %

18. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
17
Additional DB Connect
function/functionality:
“| dbquery”
Used to monitor production
database for critical alerting.

19. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
18
Alert Email

20. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
19
Before / After
• Before: Small handful of associates familiar with SQL had to
manually run ad-hoc queries and drop to Excel.
• After: Near real-time dashboards are available for review by any
user of the system at any time.
• Before: Trending was isolated to fixed time ranges.
• After: Users change ‘Time-Range Picker’ in dashboards to view any
subset of data they choose.
• Before: Largely reactive process for handling issues.
• After: Proactive alerts have been put in place to mitigate issues
before they become critical.

21. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
20
Current Development

22. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
21
Current Development

23. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
22
Current Development

24. BRNDEXP 2.1 0714 © 2014 Cerner Corporation. All rights reserved. This document contains Cerner confidential and/or proprietary information belonging to Cerner Corporation and/or its related affiliates which may not be reproduced or transmitted in any form or by any means without the express written consent of Cerner.
23
Summary
• With Splunk, value was realized within minutes after initial
installation/setup.
• Splunk has opened a window into operational intelligence
• Faster/proactive in responding to incidents
• Happier Clients
• Users of any skillset can derive value from complex data set with a
matter of clicks
• Using Splunk to connect disparate systems to unlock business
intelligence

25. Tom Twait & Chris Hogan
Cerner Revenue Cycle – EDI Services Manager & EDI Services Senior Solution Architect
October 7th 2014
Monitoring a Database Driven System
Utilizing Splunk’s DB Connect
Questions?