Can someone please provide some suggested standard users, please? There have
got to be lots of them out there, and there should be noting confidential
about the entries. Kevin can do a lot with a simple printout from a D P^DI
Option 5 printout of those users.
The work he is doing is not just for his clinic, it will be for everyone to
use and it will be a great help, so anyone that can chip in with
configuration printouts of any of the systems - lab, pharmacy, etc., please
send them Kevins way. Everyone will benefit.
On Wednesday 24 November 2004 09:57 am, Kevin Toppenberg wrote:
> Steven,
>
> Thanks for your feedback.
>
> My intent in creating an installation program was to
> create a one-shot install wizard. I am not aware of
> any code that will do this currently. I have the
> following layers (from lowest to highest):
>
> 1. VistA code
> 2. Script interpreter
> 3. XML Script
> 4. (Potential wizard to query for unique user data)
>
> The "hard-coding" part of my script is to put user
> data into a format like this:
>
> <Values id="TMG">
> <Field
> id="ParentDomain">PARENT.TMGDOMAIN.COM</Field>
> <Field id="Domain">TMG.TMGDOMAIN.COM</Field>
> <Field id="SiteName">TMGSITE</Field>
> <Field id="SiteNumber">777</Field>
> <Field id="Division">TMGDivison</Field>
> <Field id="Institution">TMG-Greeneville</Field>
> <Field id="MedCenterDivision">TMGCenterDiv</Field>
> <Field id="State">TENNESSEE</Field>
> <Field id="ShortName">The Medical Group
> (TMG)</Field>
> <Field id="City">Greeneville</Field>
> <Field id="Zip">37745</Field>
> <Field id="VaType">OC-IND</Field>
> <Field id="FacilityType">OC</Field>
> <Field id="AgencyCode">OTHER</Field>
> <Field id="VolumeSet">VOL</Field>
> <Field id="UCI">UCI</Field>
> <Field id="ListenPort">9210</Field>
> </Values>
>
> The above data values are then pulled into records for
> given files. In the below example, the INSTITUTION
> file is set up. Notice that if a data value, such as
> UCI is needed multiple places, that the user will only
> have to edit it at ONE place (the data set shown
> above)
>
> <Record id="Institution" File="INSTITUTION">
> <Field
> id="NAME">{{Values[TMG].Field[Institution]}}</Field>
> <Field
> id="STATE">{{Values[TMG].Field[State]}}</Field>
> <Field id="SHORT
> NAME">{{Values[TMG].Field[ShortName]}}</Field>
> <Field id="CITY">{{Values[TMG].Field[City]}}</Field>
> <Field id="ZIP">{{Values[TMG].Field[Zip]}}</Field>
> <Field id="VA TYPE
> CODE">{{Values[TMG].Field[VaType]}}</Field>
> <Field id="FACILITY
> TYPE">{{Values[TMG].Field[FacilityType]}}</Field>
> <Field
> id="DOMAIN">{{Values[TMG].Field[Domain]}}</Field>
> <Field id="AGENCY
> CODE">{{Values[TMG].Field[AgencyCode]}}</Field>
> <Field id="STATION
> NUMBER">{{Values[TMG].Field[SiteNumber]}}</Field>
> </Record>
>
>
> So while this data is "hard-coded", it is easily
> modifiable--either by a user with a text editor, or by
> a future wizard that asks a question and stores answer
> in this XML format.
>
> There is a very good chance that I am re-inventing the
> wheel, but the fact that I can't find a wheel that has
> already been created shows a weakness in the current
> VistA setup. There has been much discussion of
> potential "bridging documentation." The need for this
> can't be overestimated. I am trying to make a
> bridging script that allows for installation without
> having to do extensive work before one can even get
> started. Take a look at the install instructions that
> Nancy, David Whitten and others have set up. They are
> not exactly easy for a beginner to do. When working
> with a system that is already up and going, it is easy
> to forget how one got the thing working in the first
> place. Perhaps this doesn't apply to everyone, but
> I've heard long-time VistA administrators say that
> everyone had forgotten how to get a system up and
> running from the ground up.
>
> The VistA API's also leave much to be desired, in my
> opinion. This is both in terms of documentation (and
> the difficulty in finding the correct documentation),
> and in code functionality. The fact that it takes so
> much discussion to upload a simple data set into a
> database is unfortunate.
>
> So while I continue to learn more about the system,
> and I'm sure I will discover easier ways to do what
> I'm trying to do, I'll keep slogging along.
>
> I greatly appreciate the help everyone has given me.
> And I appreciate feedback like this one. I just hope
> I don't drive everyone crazy with my 10,000 questions.
>
> Thanks again, and Happy Thanksgiving everyone!
>
> Kevin
>
> --- steven mcphelan <[EMAIL PROTECTED]> wrote:
> > I am still confused as to why Kevin is going through
> > all these gyrations for
> > creating scripts to set up a user especially since
> > his scripts appear to be
> > hardcoding the values to assign. The Kernel has
> > provided APIs to do this
> > very thing for many years. Staff at the VA set up a
> > new user with one
> > option which is the option to clone a user. What
> > they do is setup a
> > standardized NEW PERSON file entry (I will call a
> > dummy user) with all the
> > Kernel components they need for that job's function.
> > Then when a real user
> > comes on board, they choose the clone a user option.
> > They select the
> > appropriate dummy user. Voila, the real user now
> > has all the options,
> > security keys, mail groups, etc. that they need.
> > This is not 100% but it
> > goes a long ways to making an onerous task easier.
> > For example, I believe
> > the Kernel clone a user option will not copy over
> > some package specific
> > configurations like CPRS parameters. But if Kevin
> > is going through these
> > gyration to learn, then that is good. If the
> > purpose is to have a tool to
> > make a task simpler, then why not use the already
> > existing VistA options
> > that accomplish that task or write a script to those
> > options?????
> >
> > ----- Original Message -----
> > From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, November 23, 2004 5:37 PM
> > Subject: RE: [Hardhats-members] More DINUM problems
> >
> > > Thanks Skip,
> > >
> > > I also have gotten this working. For complex
> >
> > reasons,
> >
> > > my install scripter was adding the record, and
> >
> > then
> >
> > > trying to overwrite it a second time. It working
> >
> > now.
> >
> > > I think you cheated a bit below, though. You sent
> >
> > the
> >
> > > error messages to ZZERR, and then showed that
> >
> > there
> >
> > > were no errors in DIERR. LOL. I see below that
> >
> > it
> >
> > > did work though.
> > >
> > > Thanks again
> > > Kevin
>
> -------------------------------------------------------
>
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT
> > Products from real users.
> > Discover which products truly live up to the hype.
> > Start reading now.
> > http://productguide.itmanagersjournal.com/
> > _______________________________________________
> > Hardhats-members mailing list
> > [EMAIL PROTECTED]
>
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - What will yours do?
> http://my.yahoo.com
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Hardhats-members mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
--
Nancy Anthracite
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Hardhats-members mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
