transforming healthcare one api at a time at kaiser permanente

Transforming Healthcare – One API at a 7me 25th February 2015 Presented by :

Jeffrey Vene7a, Sr. Director – Digital Shared Services , Kaiser Permanente

Raghu Raman, Sr. Manager – Perficient Inc.

2 © 2015 Kaiser FoundaJon Health Plan, Inc. ConfidenJal, not for distribuJon or duplicaJon Digital Technologies & Operations

Agenda §  Kaiser Permanente – Brief introducJon §  Kp.org’s API journey

–  Guiding principles –  Technology roadmap

–  Experiences roadmap

–  Digital CapabiliJes roadmap

§  Kp..org SOA challenges ahead §  API architecture §  Q & A


Kaiser Permanente – A brief introduc7on

Corporate Overview

Founded in 1945 9.1+ million members 174,415 employees 17,425 physicians 48,285 nurses 38 hospitals 608 medical offices and other faciliJes 36.5 million doctor office visits

A few staJsJcs of member usage on digital channels Visits to kp.org (including visits to m.kp.org) : 162M Total registered members : 4.89M Test results released online : 78M Test results viewed online : 37.4M Emails sent to doctors and other providers : 20M PrescripJon refills submi7ed online : 17.5M Appointments booked online : 4.2M Kaiser Permanente mobile app downloads : 1.1 million

* Data as of Dec 2013


Kp.org to Consumer API Journey

2009: SOA? Why ? 2012: When can we start on APIs ?


Kp.org – Architectural Focus

Pre-‐2009 2009 onward

Integra7on with external systems

Generally point to point, container managed integraJon capabiliJes not consistently used

All integraJons must be API/web service based and deployed to a KP-‐IT ESB and/or API Gateway

Integra7on technology Whatever is available is used. i.e. Servlets/ Portlets opening up socket connecJons directly, JDBC for SQL access to external databases

Work with external systems to leverage shared and create new Web Services and APIs

Service Oriented Infrastructure Limited to no service oriented infrastructure uJlized. Tight coupling, metrics and monitoring must be manually compiled for each process involved in a given request.

UJlize ESB for all integraJons, taking advantage of locaJon transparency, service metrics, monitoring and problem idenJficaJon capabiliJes

Standards and Guidelines

Rarely complied with. Varies greatly across features based on team lead/developer preference.

Key stakeholder in DTO engagement and technical governance to ensure core KP-‐IT service orientaJon standards are followed.

Documenta7on Varies from none to some. Most are not detailed enough to implement to, all different in format and levels of detail

Comply with KP-‐IT SOA and SDLC documentaJon requirements for services. Request it of our service providers.


Guiding Principles

§  Loose coupling is the strategic integraJon approach for business data and funcJonality

§  UJlize domain based informaJon models in service interface

§  Partner with domain owners/service providers to ensure our architectural goals are realized in their service design

§  Support and parJcipate in Enterprise SOA Governance and infrastructure

§  Encourage the use of industry best pracJces in the design and implementaJon of web services and APIs

§  Encourage our business partners to provide requirements at a business funcJon level, not applicaJon/screen level

§  Be pragmaJc when balancing our principles with Jme to market, but always provide tension towards strategic architecture


To Do

Change

Complete

Legend

Med

icat

ion

Ord

er

Ser

vice

R

ES

T Tr

ansf

orm

eP

harm

acy

Onl

ine

Med

icat

ion

Ser

vice

View

Pre

scrip

tions

Ref

ill P

resc

riptio

ns

ePIM

s/P

IMS

EP

IC

Faci

lity

Dire

ctor

y S

ervi

ce

Find

Fac

ilitie

s IS

G

Eve

nt N

otifi

catio

n S

ervi

ce

RE

ST

Tran

sfor

m

MyC

hart

Get

Ale

rts

Ser

vice

MD

Em

ail A

lerts

App

oint

men

t Ale

rts

Test

Res

ults

Ale

rts

Dep

artm

ent E

mai

l

EP

IC

Use

r Dat

a S

ervi

ce

RE

ST

Tran

sfor

m

Cha

nge

Pas

swor

d

Iden

tity

Info

rmat

ion

Not

ifica

tion

Set

tings

eBiz

UD

R

Sec

ure

Mes

sage

Ser

vice

R

ES

T Tr

ansf

orm

E

mai

l Dep

artm

ent

Kan

a/C

SC

EP

IC

Test

Res

ults

Ser

vice

R

ES

T Tr

ansf

orm

Te

st R

esul

ts

EP

IC

Get

Alle

rgie

s S

ervi

ce

RE

ST

Tran

sfor

m

Alle

rgie

s

Imm

uniz

atio

ns

Hea

lth C

ondi

tions

Get

Imm

uniz

atio

ns

Get

Cur

retn

Hea

lth Is

sues

Planned Transforma7on – From SOA to APIs

SOAP


SOA to API: Quick enablement of Mobile and Web 2.0 M

edic

atio

n O

rder

S

ervi

ce

RE

ST

Tran

sfor

m

ePha

rmac

y O

nlin

e

Med

icat

ion

Ser

vice

View

Pre

scrip

tions

Ref

ill P

resc

riptio

ns

Faci

lity

Dire

ctor

y S

ervi

ce

Find

Fac

ilitie

s

Sec

ure

Mes

sage

Ser

vice

R

ES

T Tr

ansf

orm

E

mai

l Dep

artm

ent

Test

Res

ult S

ervi

ce

RE

ST

Tran

sfor

m

Test

Res

ults

Use

r Dat

a S

ervi

ce

RE

ST

Tran

sfor

m

Cha

nge

Pas

swor

d

Iden

tity

Info

rmat

ion

Not

ifica

tion

Set

tings

RE

ST

Tran

sfor

m

PAM

Ser

vice

Alle

rgie

s

Imm

uniz

atio

ns

Hea

lth C

ondi

tions

Eve

nt

Not

ifica

tion

Ser

vice

RE

ST

Tran

sfor

m

MyC

hart

Get

Ale

rts

Ser

vice

MD

Em

ail A

lerts

App

oint

men

t Ale

rts

Hea

lth R

emin

ders

Test

Res

ults

Ale

rts

Dep

artm

ent E

mai

l

SOAP

REST


Consumer API journey -‐ Technology evolu7on

2009 2010 2011 2012 2013 2014 2015

Kp.org -‐ IBM portal

Web service IBM WAS

ESB -‐ IBM DataPower

API gateway

Deployments – IBM urbancode

Techno

logy

2008

Service VirtualizaJon

Web service IBM WAS


Consumer API journey -‐ Digital experiences for our members

2009 2010 2011 2012 2013 2014 2015

Digital Membership Cards

Video Visits

Expe

riences

2008

Migrated and enabled legacy kp.org to target architecture IBM portal, IBM WAS etc,

NoJficaJon Plaporm


Web service IBM WAS

ESB -‐ IBM Datapower

API gateway



Web service IBM WAS

Non Member Accounts


Consumer API journey -‐ Expanding our digital offering

Without changing the technology stack, KP.org has focused on adding digital capability to our API offerings to support the business.

2009 2010 2011 2012 2013 2014 2015

CapabiliJ

es

2008

AuthorizaJon and enJtlements

Provider and member

Digital a7achments , Video Visits

Health Record. Messaging and appointments

Content, Account creaJon , registraJon


Web service IBM WAS

ESB -‐ IBM Datapower

API gateway



Digital Membership Cards

Video Visits

NoJficaJons

Non Member Accounts

Web service IBM WAS


Consumer API journey – Reasons we are succeeding

ExecuJve sponsorship

Architecture and Design

ExecuJon and delivery

Renewed Investment

Reaping the benefits

Strong execuJve sponsorship and leadership laid the foundaJon for the digital channel

Use of best in breed tools , technology and framework for a Scalable, sustainable and available infrastructure

Focused delivery and execuJon over several Projects and iniJaJves

Leveraging on investments made earlier

Responsive to change


Flagship app – APIs in play

Click image to Launch Video (https://www.youtube.com/watch?v=_VH01BqrDos)


KP API Consumers

* Data is from 2014

Client Applica7ons # of APIs Consumed

kp.org 23

kp Mobile Flagship (Android/iOS) 27

kp PrevenJve Care App 8

NCAL My Doctor Online 2

Video Visits (Provider) 1

IVR Pharmacy system 1

eServices 4

Medicare, Claims connect 4

# of KP IT OrganizaJons using Consumer APIs/Services/Plaporms 6


KP API -‐ Metrics

APIs/Components developed for Consumer Digital Capabilites 29

Non-‐PROD/PROD Endpoints Under Management 468 +

Yearly TransacJons processed by all API and Web Services 1.4 Billion

Yearly TransacJons driven by Mobile App 234 million

Number of ApplicaJons Consuming APIs/Components 8

Websphere Prod JVMs 48

Websphere Non-‐Prod JVMs 84

* Data is from 2014


DIGITAL Channels

KP Digital Offering – High level system architecture

APIs/DIGITAL SHARED COMPONENTS

Membership Systems

Electronic Medical Record Systems

Health Plan Systems Benefits Systems Pharmacy

Systems

Kp.org Flagship IOS App

Flagship Android App

KP PrevenJve

App

Provider/ Workforce

App

Non public / Internal Kaiser applicaJons


Kp.org

Current Architecture – High Level

HTML over HTTPS

Portal Server

Portal Applica7ons

Mobile ApplicaJons iOS Android M.kp.org

HTML over HTTPS HTML over HTTPS

API Security Gateway

API Server

JSON over HTTPS

JSON over HTTPS

Web APIs

SOAP over HTTPS

KP Consumer Integra7on Servers

Consumer Web Services

Reverse Proxy Web Server WSSO Plug In

IIS Servers

EPIC MyChart Web ApplicaJon

SOA Services Gateway ( Data Power)

Other KP Systems and Services

Membership TPMG

KP Consumer PlaZorm

WSSO/Access Server

User Directory

Consumer Database

Content Management Search Engine

FSSO/Federa7on Server

CPM PARRS KPHC & EPIC Web Services

Pharmacy Claims KANA FDB/FDS MSSA Web Services

Internet (C

loud

) DM

Z Presen

taJo

n Tier

in KP Intranet

Busin

ess a

nd Data Tier

in KP Intranet

SOAP over HTTPS

SOAP over HTTPS

CA Available in mulJple data centers to support ConJnuous Availability of KP.ORG

CA CA

CA CA

CA

CA

CA CA


Kaiser Permanente’s API journey – Challenges ahead

§  Release and deployment to mulJple release streams

Leveraging IBM Urban Code in 2015 for API and Web Service deployments

§  MulJple versions of APIs

Leveraging IBM Sot Layer to add container capacity

§  Data availability for development and regression

LISA Service VirtualizaJon for more efficient development

§  Consuming ApplicaJon Management and CommunicaJon

Exploring IBM API Management in conjuncJon with our exisJng API Gateway

soluJon


Kaiser Permanente – Transforming the future

Click image to Launch Video (https://www.youtube.com/watch?v=gxz9ZVvduGc).


Q&A


Contact Info

Jeff Raghu

transforming healthcare one api at a time at kaiser permanente

Technology

kaiser foundajon health

service metrics

service providers

digital channels visits

apiweb service

kaiser permanente raghu

service orientajon standards

core kp