On 9/6/05, Larry Andreassen [EMAIL PROTECTED] wrote:
I'd beware of using Google as part of a backup system. If you send too many
messages (files embedded in a message) to your account in a 24 hour
period, Google locks you out for a day, and may elect to pull the plug on
your account I assume.
On 9/7/05, Suchi Pande [EMAIL PROTECTED] wrote:
Larry Andreassen wrote:
I'd beware of using Google as part of a backup system. If you send too many
messages (files embedded in a message) to your account in a 24 hour
period, Google locks you out for a day, and may elect to pull the plug on
I agree entirely. We are used to thinking of and planning for
emergencies that may be severe, but are local. But there have been many
cases (e.g., the Asian tsunami, the big northeast power grid failure, an
ice storm in Quebec) in which there have been severe geographically
widesperead
I'd beware of using Google as part of a backup system. If you send too many messages (files embedded in a message) to your account in a 24 hour period, Google locks you out for a day, and may elect to pull the plug on your account I assume.
On 9/6/05, K.S. Bhaskar [EMAIL PROTECTED] wrote:
I agree
Larry Andreassen wrote:
I'd beware of using Google as part of a backup system. If you send too many
messages (files embedded in a message) to your account in a 24 hour
period, Google locks you out for a day, and may elect to pull the plug on
your account I assume.
My suggestion for using
Given enough google invites you could even store it on a google
filesystem (a GNU/Linux file system that uses google's mailspace for
storing files). ;-)
regards
PJ
When Google starts selling space on GFilesystem, life as we know it will end.
steven mcphelan wrote:
local backup to individual clients. Local backups is also an option.
Imagine the scenario where the ASP was in New Orleans and the backup in
Biloxi. In this case whether you had backups done locally or the first case
I mentioned, both would have failed. This whole issue
I think you are confusing my concern about having national databases that
store records of patients from all of their physicians, no matter what system
they are in, and those that are for a system, be it a doctors office, or in
this case, the VA system. I would not expect Kaiser, for example,
Greg --
Yes, and no.
For protection against disasters, one can actually take an application
running on GT.M at Site A that has no design for redundancy, and create
a redundant backup Site B for it virtually overnight (the longest step
is probably shipping the backup, either over the wires or
contact me.
Have a great weekend,
Renee
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of K.S.
Bhaskar
Sent: Friday, September 02, 2005 9:36 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] We DO Care
Greg --
Yes
Nancy and All:
This issue of the role of architecture in the issue of Privacy
Confidentiality is just one aspect of Enterprise View, LIfe Cycle
Principles. I'll just mention two items Zachman Framework and Capability
Maturity Model. The VA has been aware of both but VistA export requires
that
Of A. Forrey
Sent: Friday, September 02, 2005 8:36 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] We DO Care
Nancy and All:
This issue of the role of architecture in the issue of Privacy
Confidentiality is just one aspect of Enterprise View, LIfe Cycle
Principles. I'll
manner that really works.
- Original Message -
From: Nancy Anthracite [EMAIL PROTECTED]
To: hardhats-members@lists.sourceforge.net
Sent: Thursday, September 01, 2005 5:55 PM
Subject: Re: [Hardhats-members] We DO Care
I hope I did not make people think I am supporting one or the other. I am
I think this will serve as an excellent test for the local contingency plans
for catastrophic failrues. As an example, as the VA moves more and more
toward centralizing their databases, this sort of thing becomes more and more
of serious an issue. This is one of the reasons that I am not in
: RE: [Hardhats-members] We DO Care - YES we care about Katrina
Wednesday, August 31, 2005 8:57 PM Gregory Woodhouse Said:
What happened is so horrible that almost anything we can say seems
inappropriate, or at least inadequate.
Agree with George. There are numerous ways to contribute - AMA, AAFP
This is certainly a good point, but it's really not a matter of
either/or. It is quite possible to use a distributed storage model (and
remain reasonably efficient as well), without losing the ability to
tolerate network failures and even operate off-line for extended
periods of time.
I've long
I guess she means Application Server Provider.
Alberto
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] En nombre de Greg
Woodhouse
Enviado el: Jueves, 01 de Septiembre de 2005 09:45 a.m.
Para: hardhats-members@lists.sourceforge.net
Asunto: Re: [Hardhats-members] We DO
I guess I don't understand your point here.
It's not that local maintenance of data is a great burden, bur rather
that if you ever need access to it from another facility it's not
available. I know many people here feel like that's the way things
should be, but that's a different issue. My point
Got it.
National Health Insurance model suggests
a few regional management centers that handle
ALL citizen's health care records.
(accomplishment of this model is remote but
at least it's an idea.)
And if a californian moves to Florida, their
data are to be 'transferred' to Florida's
regional
That being said,
maintaining all data locally (without any synchronization or sharing)
is, in my opinion, unnecessarily extreme.
Not to be a smart A**, but we are living in the extreme.
and local maintenance of data is not big a deal.
Regular sync should be done.
J.
I hope I did not make people think I am supporting one or the other. I am in
favor of both. I feel that if it is a small clinic, it should have remote
backup perhaps with the primary server local. If it is an ASP sort of
situation, then I think the ASP might provide the primary server but
It is technically feasible to do so, but of course, the redundancy you
describe would have to be incorporated into the design.
--- jae kim [EMAIL PROTECTED] wrote:
Got it.
National Health Insurance model suggests
a few regional management centers that handle
ALL citizen's health care
Except donating money, what else I can do?
At an emergency like this, without power, no computer
would be usable. Paper chart would be the only option.
Physicians in this list might know the procedure.
If they had backed up the database into a portable
hard drive, and satellite link it from
Subject: Re: [Hardhats-members] We DO Care
I've noticed very little discussion of Katrina on VA mail systems,
too. Surely, that is not because VA employees do not care! Rather, I
think everyone is simply at a loss for words. What happened is so
horrible that almost anything we can say seems
24 matches
Mail list logo
