Joseph, Regarding this specific excerpt from your post,
. . .
Usha tried unsuccessfully to get an answer to a specific
question on Hardhats on the problem of HL7 connectivity from an
OpenVistA installation we had done on Suse Linux using the
latest Pacific Hui version 3.0 . . .
Here are the
Let me say before I even start, that I know I am not an expert, but this is
what I have learned and, hopefully, it is correct, from my time with working
with VistA on the two platforms.
I see no reason at all that you cannot be supported remotely and the
contracting I am referring to is to
On 6/3/06, Joseph Puthooran [EMAIL PROTECTED] wrote:
...
But I struggle to
understands the why there is an almost exclusive preference for
Cache by most vendors there. But what are these pros cons in
the context of VistA?
I'll let others answer, but I suspect it has to do with the fact that
The interesting question is the work content in the porting of
VistA to the GT.M platform. I think ESSI, Medsphere and others
were given the contract by the Hui to do the porting. Apparently
there was some work which it will be useful to know. What was
the work content in porting to another Mumps
Thanks for the input from Nancy, Kevin, Alan ONeill and others
off line. The following are some learnings that that we can draw
from what you have said.
1. There is no doubt that GT.M is robust and stable as a
database.
2. There are however bugs with the porting of VistA to Linux
GT.M. It is
Joseph Puthooran wrote:
While responding to people like Nancy or Kevin, I do so with a
great degree of reverence and admiration. They have set high
standards for transparency and helpfulness that many of us have
greatly benefited from. You have infinite patience and no newbie
would ever
GT.M does not currently run on Windows and I am not sure, but I suspect, the
Linux version is the Unix version. The issue, again, is likely with VistA
and that work has been done with Linux. GT.M for the Alpha has been released
to open source, but I don't know that anyone has made the
On Jun 5, 2006, at 4:50 PM, Joseph Puthooran wrote:4. If this sharing takes place, the Open Source community could work on fixing these issues and in course of time OpenVistA could be as bug free as the Unix/Cache version used at the VA. Possibly better. I'm sure that you know one of the main
Apropos Bhaskars response which I just noticed; I would like to
tender my wholehearted apologies where I may have said things
that could have hurt anyones sensibilities. There has been no
deliberate intent to hurt anyone and if I have done so
unwittingly, kindly forgive the lapse.
I do not see either a preference for Cache or a preference for GT.M as a
mystery. There are pros and cons for each choice and the choice seems to me
to be one that those involved need to consider for each implementation
depending upon the circumstances and requirements for each individual
On 6/3/06, Joseph Puthooran [EMAIL PROTECTED] wrote:
...
My real concern is that I am planning to implement VistA in
India. I want to be sure what would be a wise strategy in terms
of the platform. Presently my view is that for the smaller
clinics and physician practices, GT.M may be the best
While responding to people like Nancy or Kevin, I do so with a
great degree of reverence and admiration. They have set high
standards for transparency and helpfulness that many of us have
greatly benefited from. You have infinite patience and no newbie
would ever feel uncomfortable interacting
Hi Alan,
Thank you for the input. Perhaps the Hui should make a KIDS
patch to rectify this problem based on your excellent work.
I think there is also a problem with the HL7 TCPIP listner and
incoming messages are not accepted by GT.M system. Outgoing
messages are going out OK. I hope that can
Joseph Puthooran wrote:
Secondly I wonder what is the agenda of the exclusive OpenVistA
RD coding worshops. Is it to address some of these issues that
were left out at the OpenVistA porting exercise?
The developer meetings that I have been involved with have been exclusive only
in their
Dear Jim,
Thanks for your input.
There is no doubt that the WorldVistA team is doing a great job
and we are all grateful for that. But with all the time
constraints that exist, it may not always be possible to include
others who are investing time in trying to implement OpenVistA,
by keeping
HI Joseph,
I am currently in the process of evaluating FOIA VistA on GT.M. I have
a great deal of experience with GT.M, though I'm a bit rusty with
VistA. I ran into a snag with e-mail, which of course is also using a
socket connection. I found two things that needed to be changed to get
16 matches
Mail list logo
