Suva Digitalization Strategy

How API Management at Suva is Helping in Reducing Costs to Our Customers

Igor BerchtoldDirector Frameworks and Integration SUVA, Switzerland

Contents

• Facts about Suva• Business Problem• Solution Architecture• Suva API Management Platform• Lessons Learned

Who is insured with Suva?Half of all people employed

The largest premium classes

Who is insured with Suva?

The Suva model

More than just insurance

Staff of 4,200 employees

At your service every day

Focusing on the core market

Business Problem - "Avance" Strategy

• Low interest rates• Shift in accident patterns from work to leisure• Digitalization • Shrinking market share

→ reducing operating costs

Market influences our requirements

Digitalization Strategy

• Customers have more flexible working hours• Emerging Marketplaces (WebApps and APIs)• Emerging data exchange platforms between

consumers and providers of health care services• Reduce operating costs

Goals

Digitalization Strategy

• Higher process efficiency• Lowering process costs• Providing services for different channels• 7x24h controllable access to our data• Reuse of APIs by partners• One single platform

Suva Digital Architecture

Solution Architecture

eService Platform

Suva Digital Architecture

eService Platform - Decoupling

Suva Digital Architecture

Evaluation

Suva API Management Platform

• WSO2 ESB since 2011 in production – 35 Mio calls per month– 100% stable and very small latency

• Established Carbon know-how– Synergies between ESB and API Manager

Overview

Suva API Management Platform•••••

API Categories

Suva API Management Platform

• Public API– No security requirements, public available

• Partner API– Security requirements, available for partners

• Private API– Specific APIs for private user group

Suva API Developer Portal

Suva API Management Platform

API Design First

Suva API Management Platform

Swagger Server Stub

Swagger Client Stub

Deployment

Suva API Management Platform

First API: eService ClaimStatusInfo

Suva Digital Architecture

Think big, start small ...

Lessons Learned

• Start with all-in-one deployment setup – Materialize your API development process– Build up your know-how about API Manager

• Apply the complex deployment patterns based on your real needs

• API Store– customization vs. development (use APIs)

Thank you!

wso2.com