Originally presented at the Redox 2018 Interoperability Summit by Mary Moreno, Healthgrades.

1. Distribution Notice:
1
These slides may contain copyrighted materials and
are intended for reference only.
They may not be copied, used, or distributed by
outside parties.

2. Integrations:
Getting your
Foot in the
Door
© 2018, Redox, Inc. | redoxengine.com
Presented by Mary Moreno
November 14, 2018

3. 3
Agenda
⋅ Introductions and Objective
⋅ Setting the Stage: Integrations by the Numbers
⋅ Gear Up
− Tools You’ll Need
− Know Your Audience
⋅ The Nitty-Gritty: Questions and Themes
For reference only, do not distribute.

4. 4
Introductions
For reference only, do not distribute.

5. 5
5
⋅ Sales?
⋅ Integration SMEs?
⋅ Start-up, Small to Mid-Sized Company, or
Larger Company?
⋅ East Coast, West Coast, in-between? Denver?
Who are You?
For reference only, do not distribute.

6. My Turn: Who am I?
6
6
For reference only, do not distribute.

7. Today’s Goal
7
⋅ I’m not an engineer, or a salesperson! But I know
what’s up.
− Questions you’ll be asked and materials you should be
prepared to have
− Stay away from recommendations on implementation
or strategy
7
For reference only, do not distribute.

8. 8
Setting the Stage
For reference only, do not distribute.

9. Integrations by the Numbers
a successful integration strategy is crucial to
remaining competitive over the next 5 years
the right integration solution would greatly improve
business performance
have missed business opportunities as a result of
poor integration
characterize integration as the “Achilles heel” for
their organization
9
74%
81%
67%
59%
For reference only, do not distribute.

10. So What?
10
10
For reference only, do not distribute.

11. 11
Gear Up
For reference only, do not distribute.

12. 12
1. Customer’s integration requirements – the
“ecosystem”
2. Integration strategy & roadmap – what’s your
differentiator?
3. View of the competitor landscape
4. Scalable process for beta integrations
Tools You’ll Need
For reference only, do not distribute.

13. 13
⋅ Chief Medical Officer
⋅ Chief Financial Officer
⋅ Chief Information or Security Officer
⋅ SMEs and Users: HL7 analysts, marketers, lab
techs, physicians, patients …
Know Your Audience
For reference only, do not distribute.

14. 14
The Nitty-Gritty!
For reference only, do not distribute.

15. Four Main Themes
1. Workflow, Operational Concerns
2. Breadth & Depth of Integration Offerings
3. Security & PHI
4. Data Integrity & Technology
15
For reference only, do not distribute.

16. 1. Workflow, Operational
Concerns
16
⋅ What's the workflow like once I’m using the other application and data
is exchanged?
⋅ How do you push out updates to the integration, and would any
product updates be affected by the integration?
⋅ What are your future plans to integrate with … X? This is an application
I use often and cannot perform basic job duties without it in your tool.
⋅ What if I am using an older version of the other application?
16
For reference only, do not distribute.

17. 2. Breadth & Depth of
Offerings
17
⋅ Which integrations do you offer? Or phrased differently, who
are your third party partners?
⋅ How long will it take to stand up a new integration if we (client)
want one, and what is your evaluation criteria around
accepting new integration partners?
⋅ What's your support model or SLA/alert downtime system for
these integrations?
17
For reference only, do not distribute.

18. 3. Security & PHI
18
⋅ How secure are the integrations you build to third party applications?
− Access, PHI data, and from breaches
− Secrets & authentication with secure tokens, servers utilizing
encryption or secure storage
− SSO integration abilities, user administration and permissioning
18
For reference only, do not distribute.

19. 4. Data Integrity & Technology
19
⋅ How can we tell where the data came from?
⋅ How frequently is the data updated from the third party application?
⋅ Do you use an architectural integration layer (i.e., a public API for
example) that allows development to begin readily and independently
from the core product?
⋅ Can I consolidate financial reporting in one place, even though the
application is utilizing data from different sources?
19
For reference only, do not distribute.

20. 20
Closing
For reference only, do not distribute.

21. If Nothing Else…
⋅ Integrations are important.
⋅ Knowing your audience and users is pivotal in
determining the kinds of questions you will get.
… and
21
For reference only, do not distribute.

22. …Closing cont’d
22
⋅ You will receive a wide range of questions, so
know…
− Workflow, Operational Concerns
− Breadth & Depth of Integration Offerings
− Security & PHI
− Data Integrity & Tech
22
For reference only, do not distribute.

23. 23
Q&A?
For reference only, do not distribute.

24. Thank You!
Social
https://www.linkedin.com/maryjoanmoreno
@naoJyraM
Email
mary.joan.moreno@gmail.com
For reference only, do not distribute.

25. Appendix - Sources
⋅ Dell Boomi 2017 Research, “The Connected Business: a survey report on business
connectivity and the importance of integration.”
https://boomi.com/blog/5-characteristics-integration-cloud-platform/
⋅ “4 Reasons Why Building Integrations Sucks.”
https://www.xillio.com/blog/4-reasons-why-building-integrations-sucks
⋅ “4 Key Elements of an Integration Strategy.”
https://www.xillio.com/blog/4-key-elements-of-an-integration-strategy
⋅ Maroon Bells photograph:
https://www.fs.usda.gov/recarea/whiteriver/recarea/?recid=82346
25
For reference only, do not distribute.