This document provides an overview of Breg's integration strategy and partnership with Redox. It discusses Breg's background developing their own integrations which worked well but lacked scalability. Partnering with Redox has allowed for more integrations faster using Redox's platform. Keys to the partnership's success include maintaining simplicity, ensuring scalability, and proper staffing roles between the companies. The partnership has led to over 100 connections including 10 Epic integrations in the last year.

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. Building a
Scalable
Integration
Strategy
Shari Matkin,
Sr. Manager Customer
Experience, Breg Impact
© 2018, Redox, Inc. | redoxengine.com

3. Objectives
3
1. Breg’s Background
2. Why Redox
3. Keys to Success
4. Questions / Open Discussion
3
For reference only, do not distribute.

4. 4
Mission: Create more “time well spent” by delivering
remarkably easy solutions that improve the quality
and lower the cost of the orthopedic episode.
Vision: To be an icon in the sports medicine market.
Breg’s Mission and Vision
For reference only, do not distribute.

5. History of Breg
5
ORGANIZATION
Sports Medicine/Orthopedics Manufacturer
Corporate Office in Carlsbad, CA
Founded in 1989
~1,500 Employees
$250M Organization
Breg Impact Consulting and Software Program
SOFTWARE
Breg Vision Mobile and Web Applications
Patient Workflow Management Software
Developed and Supported In-House
275+ Accounts
75 Accounts with Integration
28 Unique EMR/EHR/PM/ERP Systems
For reference only, do not distribute.

6. 6
History of Breg Vision
Web Application
March 2008
Mobile Application
April 2012
EHR HL7 Integrations
March 2013
EHR API Integrations
October 2017
For reference only, do not distribute.

7. 7
For reference only, do not distribute.

8. 8
⋅ Started in March 2013
⋅ Developed services in-house (SFTP HL7)
⋅ Average 5-12 per year 2013 through 2016
⋅ First Redox integration September 2015
History of Integrations
For reference only, do not distribute.

9. History of Integrations
9
WHAT WORKED
Successful HL7 integrations
Competitive differentiation
Building our own services
Increased value proposition
Niched in private practice
WHAT DIDN’T WORK
Scalability for development and support
Extended timelines for implementation
Isolated knowledge and experience (sales and dev)
“n of 1”
Complex support needs
EHR communication and engagement
ROI to accounts
Health systems uninterested
For reference only, do not distribute.

10. 10
⋅ Epic integration
⋅ Do more, faster, with fewer resources, and do it
better than our competition
⋅ 100% in-house versus outsourced partner
Why Redox - Part 1
For reference only, do not distribute.

11. 11
⋅ Value of the partnership
⋅ Reduced Breg resourcing for dev and support
⋅ Scalability and timeline to implementation
⋅ Expansion of opportunities
Why Redox - Part 2
For reference only, do not distribute.

12. 12
Redox Connections
BIG WINS
100th
connection 11/14/18
10 Epic integrations
October 2018 – 14 new connections
30+ concurrent projects
EMR partnerships / API integrations
For reference only, do not distribute.

13. 13
1. Simplicity
2. Scalability
3. Staffing
Keys to Success
For reference only, do not distribute.

14. 14
Keys to Success: Simplicity
SALES
Training and expectations for sales teams
Don’t be scared, say “yes”
Identifying a business/operations champion
Clearly defined value proposition
Customer references
DEV / IMPLEMENTATION
Know the scope – fine tuned menu of options
Minimize customizations without minimizing offering
“Remarkably easy” and “Time well spent”
For reference only, do not distribute.

15. 15
Keys to Success: Scalability
SALES
Customer journey mapping
Identify operational dependencies
Clearly defined roles/responsibilities
Weekly pipeline and project review
DEV / IMPLEMENTATION
Repeatable tasks/processes
Identify opportunities for paralleled work
Minimize customizable configurations
Create a “copy and paste” model
Clear expectations for all team members early
For reference only, do not distribute.

16. 16
Keys to Success: Staffing
SALES
Project sponsor/champion
Engaged from start to finish
DEV / IMPLEMENTATION
Breg vs Redox roles/responsibilities
Remove (minimize) dependencies on others
Transition to support
Product expert / product owner
For reference only, do not distribute.

17. 17
1. Simplicity
2. Scalability
3. Staffing
Keys to Success
For reference only, do not distribute.

18. 18
Questions / Discussion
For reference only, do not distribute.

19. Stay in Touch
Shari Matkin, Breg
smatkin@breg.com