Open Source Software and Electronic Health Records. Presented by Mike O’Neill, Senior Advisor to the Director, VA Innovation Initiative (VAi2), U.S. Department of Veterans Affairs
Innova&on
in
Government:
Open
Source
So4ware
and
Electronic
Health
Records
Mike
O’Neill
Senior
Advisor
to
the
Director,
VA
Innova&on
Ini&a&ve
(VAi2)
U.S.
Department
of
Veterans
Affairs
The
Need
for
A
New
Approach
2
• VistA
EHR
is
the
cornerstone
of
the
care
and
benefits
VA
delivers
to
Veterans
• Rapidly
evolving
models
of
care
drive
EHR
changes
• At
a
&me
when
a
higher
rate
of
innova+on
is
required,
how
do
we
keep
up?
Establish
an
Open
Source
Community
to
Increase
the
Rate
of
Innova&on
Why
A
New
Open
Source
Model?
They’ve
Invested
In
Development…
5
DSS:
vxVistA
Indian
Health
Service:
RPMS
Military
Health
Service:
CHCS
Medsphere:
Open
Vista
WorldVistA
Why
A
New
Open
Source
Model?
Customers
Have
Been
Supported…
6
DSS:
vxVistA
Indian
Health
Service:
RPMS
Military
Health
Service:
CHCS
Medsphere:
Open
Vista
Midland
Memorial,
Kern
Medical
Center,
Silver
Hill
Hospital,
…
World
VistA
Why
A
New
Open
Source
Model?
But
the
Picture
Is
Fragmented.
7
DSS:
vxVistA
Indian
Health
Service:
RPMS
Military
Health
Service:
CHCS
Medsphere:
Open
Vista
Midland
Memorial,
Kern
Medical
Center,
Silver
Hill
Hospital,
…
WorldVistA
What
Should
the
Model
Look
Like?
• Share
code
that
should
be
shared
• Allow
fixes
to
be
widely
shared
• Allow
enhancements
to
be
contributed
and
widely
shared
10
What
Should
the
Model
Look
Like?
• Share
code
that
should
be
shared
• Allow
fixes
to
be
widely
shared
• Allow
enhancements
to
be
contributed
and
widely
shared
• Collaborate
whenever
possible
11
What
Should
the
Model
Look
Like?
• Share
code
that
should
be
shared
• Allow
fixes
to
be
widely
shared
• Allow
enhancements
to
be
contributed
and
widely
shared
• Collaborate
whenever
possible
• But
compete
when
it
makes
sense
12
What
Should
the
Model
Look
Like?
• Share
code
that
should
be
shared
• Allow
fixes
to
be
widely
shared
• Allow
enhancements
to
be
contributed
and
widely
shared
• Collaborate
whenever
possible
• But
compete
when
it
makes
sense
• Support
users
who
are
not
IT
experts
13
What
Should
the
Model
Look
Like?
• Share
code
that
should
be
shared
• Allow
fixes
to
be
widely
shared
• Allow
enhancements
to
be
contributed
and
widely
shared
• Collaborate
whenever
possible
• But
compete
when
it
makes
sense
• Support
users
who
are
not
IT
experts
• Support
users
who
are
IT
experts
14
What
Should
the
Model
Look
Like?
• Share
code
that
should
be
shared
• Allow
fixes
to
be
widely
shared
• Allow
enhancements
to
be
contributed
and
widely
shared
• Collaborate
whenever
possible
• But
compete
when
it
makes
sense
• Support
users
who
are
not
IT
experts
• Support
users
who
are
IT
experts
• Allow
companies
to
make
money
15
What
Should
the
Model
Look
Like?
• Share
code
that
should
be
shared
• Allow
fixes
to
be
widely
shared
• Allow
enhancements
to
be
contributed
and
widely
shared
• Collaborate
whenever
possible
• But
compete
when
it
makes
sense
• Support
users
who
are
not
IT
experts
• Support
users
who
are
IT
experts
• Allow
companies
to
make
money
• Promote
the
growth
of
the
market
16
OSEHRA
Makes
It
More
Open
And
More
Efficient
31
VA
DoD
IHS
Contractor
OSEHRA
Code
Requirements
Cer&fied
Code
Common
Codebase
APIs
Tes&ng
Collabora&on
Creates
more
opportunity
for
engagement
Commercial
Product
Market
• Mul&-‐billion
dollar
market
• Fewer
than
1/3
of
private
physicians
have
an
EHR
that
meets
minimum
requirements
• Dominated
by
proprietary
solu&ons
Adopter
Product
Company
Sales
of
Products
and
Services
New
Open
Source
Collabora&on
34
Government
Open
Source
EHR
New
market
for
the
open
source
community
New
business
models
for
EHR
community
New
openness
model
for
government