My comment to Bill Walton is that for clinical research ( and Clinical
trials as a special case) the conceptual content included in VistA can
accomodate, either now or in the evolutionary future, the patient care
data that might be involved. I spent 10 yrs in the UW Harborview Clinical
Resear
ormation may also have to be stored.
Gordon Moreshead
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Walton
Sent: Monday, September 20, 2004 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Exporting and Accessing VistA health records (was)
Re:[Hardhats
Hi Joseph,
Joseph Dal Molin wrote:
> Thanks Bill...we will add you to the
> list of potential volunteers for whatever
> emerges in the next few weeks...:-)
In all seriousness, if what emerges involves implementing the import /
export capability, you can count me in. I'm not an M programmer, but
Thanks Bill...we will add you to the list of potential volunteers for
whatever emerges in the next few weeks...:-)
I have a sneaking suspicion that folks may be confusing MyHealtheVet
with HealtheVet the more ambitious long term VA migration strategy.
VistA has all the architectural prerequisites
Nancy Anthracite wrote:
>
> It would seem this might be something we
> could use to create the equivalent of
> MyHealtheVet, the code for which is not
> yet available and from what I was told,
> will contain proprietary elements when and
> if it is released. My HealtheVet essentially
> allows veter
That would be FANTASTIC.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Terry
Wiechmann
Sent: Sunday, September 19, 2004 8:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [Hardhats-members] EsiObjects, and Open Source, etc.
Thanks!
I like the proposal, the
Count me in!
Terry L. Wiechmann
www.esitechnology.com
978-779-0257
Skype: twiechmann
- Original Message -
From: "Joseph Dal Molin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 19, 2004 3:15 PM
Subject: Re: [Hardhats-members] EsiObjects
Thanks!
I like the proposal, the system was designed as a Provider Portal that did
integrate CHCS and VistA data. We've stripped the CHCS component and
retained the VistA interfaces. The presentation layer would have to undergo
some modifications with the logon, appropriate security, etc. and a re
Nancy,
Building on your message...may I suggest we have a roll up your sleeves
workshop at the Greenbelt meeting that would focus on the replication of
the functionality of MyHealtheVet. I find I learn best when faced with a
real problem to solve... it would be great if we could dissect the parts