I agree with all these concerns:
(a) People want to hit a home run with VOE
(b) There are requirements that haven't been met yet
(CMS' "pay for performance", for example)
(c) Documentation, etc. needs to be updated for
changing requirements
Still, the whole point of open-source is that a
product is in the public domain before it meets
everyone's needs. Then, as the product is improved
the number of people that can use it increases until
you hit some critical mass. We've seen this with
Linux, Apache, MySQL, and many other open-source
projects. Our number one and two priorities, in my
mind, are to (a) get the code available and out there
- even a pre-beta version like I have from the VVSO
test, and (b) document what is lacking/missing/etc. in
this release and start planning a roadmap for closing
those gaps. A lot of time (20+ years) has been spent
creating a product that is more full-featured than any
other open-source EHR/EMR project I've seen. Granted,
it has it's quirks (#1 being that it uses MUMPS), but
the massive amount of usage it's seen at the VA far
outweighs that limitation.
It's important for this process to be open and
transparent. The voices on this list (Nancy, Bhaskar,
and many more) have been making that happen for VistA
and OpenVistA for years now - we just need to apply
that same level of facilitation and enthusiasm to
VistA-Office. I've been surprised that it hasn't been
the case, to be honest. The only way I could find a
copy of VistA-Office was through the VVSO test and
even that isn't available anymore...
In any case, if we do as I describe above there's no
doubt that the product created will be one that people
want to use.
Fyi, I have sent letters voicing my concerns and
questions to the offices we talked about before. No
responses yet.
Thanks,
Orion Richardson
[EMAIL PROTECTED]
--- "A. Forrey" <[EMAIL PROTECTED]> wrote:
It is my perspective that even if the release is
held up, there is a major
amount of work that needs to be done so that all of
those who will support
the acquiring enterprise are fully linked to the
disciplines (such as
health record administrators-AHIMA) who fully
understand the present
information domain and can help plan the transition.
Nanacy noted that it
wouldnt be a trivial process and Kevin is saying
that lets work hard in
the meantime to understand how the range of
healthcare enterprises will ne
to plan and excute the transformation that adopting
VistA will bring.
Moreover, everyone will have to understand how the
VistA architecture will
evolve (both within Va and IHS) and how it may use
COTS components (which
IHS has utilized much more than VA/DoD). Yes, I am
impatient too but first
to get the re-oriented/updated documentation in
ordeerr to work on these
issues. Others have expressed similar interests.
Arden
On Sun, 11 Sep 2005, Kevin Toppenberg wrote:
My AMA newsletter shows the ongoing shaping of how
the new outpatient
"pay for performance" policy of CMS will work. And
I believe that
one of the driving forces behind VO will be the need
for CMS to be
able to say "we expect performance data for full
payment, and here is
software that you can use to report it." Otherwise
you would have a
policy with no way for practitioners to comply.
Since the new payment model hasn't been finalized,
there may not be a
rush to release the software. After all, VistA has
been here for
years, and nothing has really changed. So what's
the rush for
release?
Another factor may well be that management knows
that there is a
significant amount of money from private EMR
companies that could be
used bring critisism for VO. So they may need to
hit a home run the
first time around.
So while I also am eagerly anticipating VO release,
I think we should
all stop holding our breaths and proceed with our
lives.
Kevin
On 9/11/05, Nancy Anthracite <[EMAIL PROTECTED]>
wrote:
David J. Brailer, M.D., Ph.D.
National Coordinator for Health Information
Technology
Mike Leavitt
Secretary of Health and Human Services
U.S. Department of Health and Human Services
Department of Health and Human Services
200 Independence Avenue, S.W.
Washington, D.C. 20201
Mark McClellan, MD PhD
Administrator, Centers for Medicare and Medicaid
Services
7500 Security Boulevard
Baltimore MD 21244-1850
On Sunday 11 September 2005 01:42 pm, Orion
Richardson wrote:
This is horrible news!
I'm one of the many people anxiously awaiting the
release of VistA-Office EHR and it getting blocked
by
some "review" process sounds incredibly fishy. Is
this an attempt by the government to scuttle the
plan?
If so, is there someone we can write to, advocate
towards, etc.?
I mean look at all the excitement around this
project
- even if we just got the current version out
there in
the open (on sourceforge, for example) I think
people
would start moving the code base forward on their
own.
Even MUMPS newbies like myself, with the great
help
of the hardhats on this list, could chip in.
Does anybody else know more about this review
process
and what stage it's in?
Best,
Orion
--- John Leo Zimmer <[EMAIL PROTECTED]> wrote:
http://www.governmenthealthit.com/article90704-09-09-05-Web
Dr. Karen Bell, division director of the Quality
Improvement Group at HHS'
Centers for Medicare and Medicaid Services, told
a
conference audience that
VistA-Office "is undergoing a review right now
by
the secretary's office.
You can't download anything" now.
"Colorless green ideas sleep furiously."
-- N Chomsky
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software
Conference & EXPO
September 19-22, 2005 * San Francisco, CA *
Development Lifecycle Practices
Agile & Plan-Driven Development * Managing
Projects
& Teams * Testing & QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software
Conference & EXPO
September 19-22, 2005 * San Francisco, CA *
Development Lifecycle Practices
Agile & Plan-Driven Development * Managing
Projects & Teams * Testing & QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
--
Nancy Anthracite
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software
Conference & EXPO
September 19-22, 2005 * San Francisco, CA *
Development Lifecycle Practices
Agile & Plan-Driven Development * Managing
Projects & Teams * Testing & QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
HS^µéX¬J'²Þu¼
à^¶×«JíÁªÞ
ßz·§qá<ä¦×¦mêõ÷m¶ÓNRjqkjw"±Ê W©Ã®+Þ7¯zZ)éí1©Ú)à>º#yËlM榱7¬¶)[EMAIL
PROTECTED]
0²§¢o۱ǹ±ñÚØZ¶É·«²f¢)à+- ªÝ
«léz»%Ël²«qç讧zØm¶?þX¬¶Ë(º· ~àzwþX¬¶ÏåËbú?
ªÝ
«léz»
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
