Implementing Health Information Exchange Without Hitting the Wall

advertisement
Payers & Providers
<37"=0!>(!?$$"0!@&
./-01$!2!.1345601$!5$!
A",75$806!0401-!B8"1$6/-!,-!
./-01$!2!.1345601$!.",75$859#(!
::;C!!9!/99"/7!5965456"/7!
$",$D15A%539!5$!EFF!/!-0/1!
GE&>F!59!,"7H!"A!%3!&*!
$",$D15,01$IC!?%!5$!607540106!,-!
0J=/57!/$!/!.KL!/%%/D8=09%(!
31!/$!/9!070D%1395D!90M$70%%01C
!77!/6401%5$59#(!$",$D15,01!/96!
065%315/7!59N"5150$O
GPQQI!)>PJ)@'*
59R3SA/-01$/96A1345601$CD3=
T/5759#!/6610$$O
P&P!UC!V377-M336!W/-(!X"5%0!Y
Y"1,/9H(!;!!F&Z*Z
W0,$5%0
MMMCA/-01$/96A1345601$CD3=
L/D0,33H
MMMCR/D0,33HCD3=[A/-01$A1345601$
BM5%%01
MMMC%M5%%01CD3=[A/-01$A1345601$
\65%315/7!Y3/16
X%0409!BC!</709%590(!.10$5609%(!
B80!;/=609!]13"A
^3$$!]376,01#(!?==065/%0!./$%!
.10$5609%(!:3$!^3,70$!V3$A5%/7!
/96!T065D/7!;09%01
T/1H!L59"D/90(!T/9/#59#!
K510D%31(!!74/10_!2!T/1$/7
V091-!:3",0%(!;850R!X%1/%0#-!
`RR5D01(!a009/9
!9%839-!W15#8%(!\b0D"%540!
K510D%31(!V0/7%8!!DD0$$!;/75R3195/
.",75$801[\65%31
^39!X859H=/9
A",75$801SA/-01$/96A1345601$CD3=
;39%15,"%59#!\65%31
a/%8-!T57701!a0770?R!-3"!63!93%!10D0540!-3"1!5$$"0!3R!
./-01$!2!.1345601$!,-!&!.CTC!39!
B8"1$6/-(!A70/$0!D/77!GPQQI)>PJ)@'*C
OPINION
Page 4
Joining An HIE Without Hitting The Wall
These Tips Can Make a Tricky Implementation Easier
applications can improve communication with
Many healthcare organizations are faced
IT staff, vendors, and other healthcare leaders.
with the challenge of multiple information
For example, there is a difference between a
technology systems, including disparate
clinical data warehouse and a health
electronic health records, practice
information exchange. The two concepts,
management applications, clinical and
however, are interrelated, as an HIE can be a
nancial decision support applications,
major supplier of data to a clinical data
document repositories or registries, and
warehouse. Both types of software might even
more.
be marketed, sold, and implemented together,
In lieu of standardizing all the
thus confusingly appearing as one solution.
applications onto complimentary platforms,
many organizations choose to implement
Integrate Organizational Silos. While building
enterprise software to exchange data
consensus and buy-in is important, do not let
between different systems, part of a health
the desire for decision-by-committee supersede
information exchange. It is a growing niche
the need to integrate all organizational
within the larger health information
initiatives that need to leverage the HIE. It is
technology industry segment.
common advice to nd champions for IT
For organizations that have decided to
projects – when strong supporters are identied
implement an HIE, there are roles and
and promoted, they work to help
By
responsibilities for many staff groups
shepherd along initiatives. Crossboth in and out of the IT department.
Wren Keber pollinate initiatives with champions
Executive leadership has the ultimate
that sit on multiple committees, so
responsibility to ensure the success of the
that one group can communicate their needs
implementation and reduce complications
and priorities with others. For major initiatives,
which may be paramount given the
convene a steering committee overseeing
investment of human and nancial resources
multiple initiatives that will use the HIE.
involved. Here are four high-priority
Think Big, Start Small. There are grand
recommendations to avoid common pitfalls
possibilities to conceptualize when IT systems
during this major endeavor:
work together through an HIE. The big picture
Take Inventory. An important task that's
outcome for an HIE implementation is to
often skipped at the beginning of an HIE
enable a vibrant network of users circled
implementation is to take inventory of all the
around high-quality and accessible clinical
data systems in the organization. Ensure that
data, no matter where it is stored. Healthcare
the chief information ofcer or HIT staff
organizations can realize efciencies, report on
creates an authoritative and comprehensive
quality indicators, and improve accessibility
list of what systems exist throughout the
and accountability of clinical data. Thinking
organization. In addition to documenting
outside the physical walls of a hospital or
major known systems, it is good practice for
practice, there are positive implications in the
the CIO or IT staff to interview key
community with afliates, owned practices,
stakeholders who will use the HIE.
emergency service providers, and more. The
Stakeholders will have knowledge of any
possibilities can be daunting, so grounding the
"workaround" systems, data repositories, or
vision with a dose of reality keeps project
system peculiarities adapted for their own
scopes in-check, resulting in small wins that
specialized reasons. For example, if a
build consensus and lead to a larger, more
practice management platform does not
sustainable success.
support a custom billing code, ofce staff
may have created an alternative database to
Wren Keber is a manager with The Camden
track it, and thus ultimately that nancial
Group, an El Segundo-based healthcare
data might not be available through the HIE.
consulting firm.
These interviews are also prime territory to
build consensus.
Learn the Lingo. While technical terms may
be frustrating and difcult to grasp, learning
the differences between major classes of
!"#"$%!&'(!)*&)!+!)*&)!,-!./-01$!2!.1345601$!.",75$859#(!::;
Op-ed submissions of up to 600 words are
welcomed. Please e-mail proposals to
editor@payersandproviders.com
Download