How Continuous Delivery Helped McKesson Create Award Winning Applications

How Continuous Delivery Helped McKesson Create Award-Winning Applications Teresa KosinskiSenior Configuration Manager McKesson Specialty Health

2

3

A very brief history . . .

1996: KnowMed Systems (iKnowMed) founded 2004: US Oncology purchases iKnowMed 2011: McKesson purchases US Oncology

4

New Legislation 1993 – Health Insurance Portability and Accountability Act (HIPAA)

• Health Insurance coverage for workers and families when they change or lose their jobs

• Establishment of national standards for electronic health care transactions, and unique identifier rules

2009 – American Recovery and Reinvestment Act (ARRA)• HITECH Act: Privacy and Security Provision• Significant incentives for adoption of EHRs

2010 – Affordable Care Act (ACA, aka ‘Obamacare’)• Increases number of insured patients• Requires technological support to drive reporting and better health outcomes

5

EHR Adoption Growth

Sources: CDC/NCHS National Ambulatory Medical Care Survey; JAMIA

6

What is a KnowMed?

A "KnowMed" is a term used to describe a medical knowbot. A "knowbot" is a "knowledge robot" or software agent which can be "trained" or configured to filter large amounts of available data and present only data considered relevant to an individual user.

7

What is a KnowMed?

8

What is a KnowMed?

9

10

Growth 1997-99

11

First Lesson Learned

Make changes quickly, make customers happy.

12

Versioning Everything

13

In the beginning . . .

Manual Weekly Build

14

In the beginning . . .

Manual Weekly Build

Automated Weekly Build

15

Growing up . . .

Manual Weekly Build

Automated Weekly Build

Nightly Build

16

17

Development

Nightly Build Automatically Deployed

Non-Java Changes

Deployed Hourly

18

Continuous Integration

Hourly CI Build

• Latest• Failure

Notifications

Build Each Submitted Changelist

• Failure & Success Notifications

Add “Nagging” Notification

• CC: me

19

Continuous Integration

Add Automated Testing

• Failure Notifications on Failed Test

Last Successful Changelist

• Easily Accessible

Add Custom Build Testing

• Developer can test shelved changelist

20

Development

21

Product Management

First group within iKnowMed to use continuous deployment Since 2001 has released documentation and release notes

as soon as they are ready

22

Development - Custom Reports (Letterhead, Rx, etc)

23

Client Services

24

Lessons Learned

Keep it simple Buy-in from all stakeholders will speed progress Continuously improve – easier to deploy and lessen/eliminate

downtime Look for opportunities to grow/improve – you might find

inspiration in the most surprising places

25

Yabba Dabba Doo!

Thank you!Contribute to the Workshop?

[email protected]