I am working on porting a Cache system to GTM. I have most things working
as much as I need to, but in the Reports tab of the CPRS GUI, I get the
following for Med Admin Log (BCMA) and Med Admin History (BCMA)
ERROR: UNABLE TO ACCESS HFS DIRECTORY C:\HFSSCR
PLEASE CHECK DIRECTORY WRITE
Nancy,
when I load /home/kdt0p/.bash_rc I find only an empty
file (i.e. none existed.) .bashrc does have data in
it.
Irregardless, I do have the variable properly set.
Here is the script I use to run VistA:
echo
echo
echo
echo Starting GT.M VistA
echo ---
echo FYI, here
There should be one r directory for the OpenVistA routines and the GTM
related stuff is usually set in /usr/local etc. Why I typed .bash_rc
instead of .bashrc I don't know, sorry, but the .bash_profile and .bashrc
either need to have the same variables and aliases set, or there needs to be
Registration for the VistA Community Meeting in Greenbelt, MD -- Oct. 21~24 is now
available on the WorldVistA web site: www.worldvista.org
The meeting page (www.worldvista.org/meetings/2004-10-greenbelt) has been updated with
a link to the registration form near the top and links to hotels,
I first encountered those with the introduction of the first Macintosh in 1984. I don't
know whether they were borrowed from SmallTalk or other GUI predecessor.
I find it
interesting that the GUI control key c, v, and x are the same as
FileMan F1 sequences. Does anyone know who created that
I would like to point out to those thinking of getting their feet wet with
Linux and a FOIA version of VistA, that there is an option to install
Knoppix right on the hard drive so you basically have a near instant Linux
box with a VistA FOIA installed. Alternatively, it can be run off the DVD.
Thanks Joseph, I make these contributions for the following reasons:
1) The US tax payer paid for it so it should at least be available to them.
2) I know Open Source works given the right critical mass.
3) I want to see GT.M, EsiObjects, VistA and associated packages succeed.
4) It keeps me
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
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, and Open Source, etc.
Nancy,
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
So what happens to the enhancements not in the FOIA software.. I was
hoping that the Open Vista distribution included the
internationalization modifications George was referring to that DVA has
opted not to incorporate with the official VA software thus not included
in the FOIA distribution.
Without sounding petty and long-winded (excuse the 12-hr time difference
and the weekend), I thought I said that I assume it will be open source.
My expression of surprise that it may not be is directed to Nancy's
assumption which is understandable. Normally I notice that statements
made like
12 matches
Mail list logo
