Why is VISTA treated like a black-box proprietary product? It says 'we
had problems in such and such an area', but there is no effort to fix
it.
Oh never mind...
Sam
On Sat, Sep 11, 2010 at 2:08 AM, kdt...@gmail.com <kdt...@gmail.com> wrote:
> The recent DRAFT Final Version of the Report on Congress on the
> Availability of Open Source HIT has some interesting commentary on the
> implementation at Adelante Healthcare, which was ultimately pulled.
>
> On a previous post (which I can't find now), I wondered about an
> objective exposition of why it was pulled. Below are excerpts that
> gives more information.
>
> Kevin
>
>
>
> Adelante Healthcare, a Federally Qualified Community Health Center
> (FQHC) headquartered in Surprise, Arizona with sites dispersed amongst
> 14 locations within Maricopa County estimated that the organization
> spent up to $300,000 per year beginning in 2007 for ongoing
> development, maintenance, and support of its WorldVistA implementation.
> (interview with Manny Ferreiro, 2010).
>
> ...
>
> Adelante Healthcare initially chose WorldVista as their EHR system
> because of the knowledge and expertise of their Chief Medical Officer
> as well as the belief that the comprehensive functionality that VistA
> offered was sufficient for their needs and for the communities they
> served. At the time the decision was made, Adelante was using GE
> Centricity as their practice management system and wanted an EHR that
> could interface directly with that system. They acquired VistA in
> 2008 and began working on customization and implementation through the
> Chief Medical Officer and a consulting firm known as Edgeware, based
> in New Dehli, India.
> Adelante Healthcare also extended the installation of WorldVista to
> two other community health centers in Phoenix, Arizona: Mountain Vew
> Healthcare, one of the largest community health centers in Arizon, and
> the newly FQHC-designated Wesley Community Health Center located in
> downtown Phoenix. As such, the three organizations formed the largest
> safety-net networks using the Vista EHR system within the United
> States.
> Ultimately, the implementation of VistA was viewed as failure by
> Adelante because of a number of reasons: lack of a bi-directional
> interface between VistA and the Centricity practice management system;
> the lack of a comprehensive obstetrics/gynecology module that was
> needed within Adelante’s Women’s Health Center; lack of a usable
> module for pediatric care within the Adelante community; faults within
> the medication management module in which erroneous medications were
> prescribed or duplicate medications were ordered; and the overall cost
> to Adelante to continually update and modify the VistA application.
> All of the maintenance updates and software fixes were done through
> the Chief Medical Officer or Edgeware. There was no dedicated IT
> staff to support the VistA application for Adelante after it went
> live; and there was no training on the MUMPS language or the VistA
> components to enable staff to provide assistance when needed.
> In early 2010, both Mountain View and Adelante opted to withdraw from
> the WorldVista network and ultimately sunset the application at the
> end of this year to be replaced with another system, potentially from
> a commercial vendor. Adelante expects to implement their new EHR
> system sometime in the late Spring or Summer of 2011.
>
>
> ...
>
>
> Reducing costs by utilizing internal staff can be a risky
> proposition. While a number of community health centers sought to
> reduce costs by using internal staff to implement, maintain and
> support the EHR system, there were some potential risks associated
> with this approach. Safety net settings with the adequate technical
> expertise to maintain a system or network using programming languages
> of open source systems, such as RPMS, were difficult to find. Most of
> the time, the expertise was concentrated in one individual. This sole
> person was then responsible for the implementation and maintenance of
> the open source EHR system for their entire organization. This
> created a “single point of failure”; if this individual left the
> organization for any reason, then the expertise and institutional
> knowledge of that system also would follow them. Unless they
> appropriately trained a successor, the safety net provider would find
> themselves in a precarious position of trying to maintain and support
> a system with limited knowledge or expertise. The health centers
> would then find themselves in the position of hiring consultants or an
> outside organization to assist with the process, which could prove to
> be financially burdensome for those settings with limited resources.
>
> --
> http://groups.google.com/group/Hardhats
> To unsubscribe, send email to Hardhats+u...@googlegroups.com
>
I started a lengthy soap-box type e-mail, but I'll just say I'm glad this is
only a DRAFT - because it is badly done.
This is one of the shallowest, illogical and lazy reports I've ever seen -
of course the user is going to blame the software when an implementation
fails. I'd be willing to bet good money that a properly done post-mortem
would reveal that 75% or more of the failure points rest on the shoulders of
management - probably on the information source for the report, too. Just
from reading the draft, it is obvious to me that management failed during
the implementation. It is also obvious to me that no one involved in this
"draft" understands what "free" means in relation to FOSS and/or VistA.
The whole thing really is too bad. I'm sure with some proper guidance,
Adelante could salvage the implementation. I hope the VistA software
doesn't take a big reputation hit because of the human failure in the
implementation or because this "draft" gets into the final report.
The only valid points that I read in there were the lack of native OB/GYN
and Pediatric functionality. But, with $300K per year in funding, that
could have been largely or even completely handled through a combination of
coding and configuration.
Christopher B. Farley
HIT Consultant
Kevin
--