Becoming a Connected Insurer With API-led Connectivity

Preview:

Citation preview

2

Becoming a Connected Insurer with API-Led Connectivity

Patricia Hines, CTPIndustry Solutions Director, FS&I MuleSoft

Teri Townsend, MBA, PMPVice President TechnologySagicor Life Insurance Company

Alex SherrySenior Solutions Consultant

MuleSoft

3

Alex Sherry

Claims Management Demo

4

Business needs

•  Richer customer engagement

•  Empower agents/partners

5

What’s holding us back

•  Legacy services for internal consumption only

•  Do we do nothing at all?

•  Rip & replace core business capabilities?

•  Change is dangerous

-  Facebook, Microsoft, Dropbox, Google, Adobe

6

What’s the solution

•  Expose services

•  Governance

•  Modernized API for mobile device consumption

7

   

Integra)on  Pla-orm  

Anypoint  Studio  

HYBR

ID  

Accounts  Database  

JDBC  

Orchestra3on  

Before Modernization

Ac3vi3  

REST  

Ac3veMQ  

JMS  

Drools  

Rules  3rd  Party  Registry  

HTTP  

WEB  Service  (SOAP)  

HTTP/REST  Connector  

JMS  Connector  

Drools  Connector  

Database  Connector  

HTTP/REST  Connector  

8

   

API  Gateway  

Integra)on  Pla-orm  

Anypoint  Studio  

Claims  API  

API  Manager  

HYBR

ID  

Accounts  Database  

JDBC  

Orchestra3on  

Web  Services  Consumer  

After Modernization

Ac3vi3  

REST  

Ac3veMQ  

JMS  

Drools  

Rules  3rd  Party  Registry  

HTTP  

WEB  Service  (SOAP)  

HTTP/REST  Connector  

JMS  Connector  

Drools  Connector  

Database  Connector  

HTTP/REST  Connector  

9

Claims Web Service

10

Legacy Web Service for Claims

The  Claims  department  ini3ally  implemented  a  web  service  to  

expose  func3onality  

11

Claims Services Modernized

12

RAML for Delightful APIs

Claims  dept  designed  a  RESTful  API  and  leveraged  the  mocking  service  to  engage  API  consumers  prior  to  

implementa3on  and  allow  them  to  test  out  the  service.  

13

Modernized Claims Service

The  “APIKit  Router”  handles  incoming  RESTful  API  

requests  and  routes  to  the  appropriate  flow  below  

The  “Web  Service  Consumer”  provides  a  drop-­‐down  

configura3on  to  access  a  web  service.  

The  datamapper  components  translate  the  web  service  call  data  into  RESTful  JSON  responses.  

14

API Governance

Governing  who  can  consume  the  API,  at  what  rates  and  by  what  

authoriza3on  mechanism  

15

API Analytics

16

   

API  Gateway  

Integra)on  Pla-orm  

Anypoint  Studio  

Claims  API  

API  Manager  

HYBR

ID  

Accounts  Database  

JDBC  

Orchestra3on  

Web  Services  Consumer  

After Modernization

Ac3vi3  

REST  

Ac3veMQ  

JMS  

Drools  

Rules  3rd  Party  Registry  

HTTP  

WEB  Service  (SOAP)  

HTTP/REST  Connector  

JMS  Connector  

Drools  Connector  

Database  Connector  

HTTP/REST  Connector  

17

Thank You

Recommended