Re: [Hardhats-members] IHS System

2005-04-21 Thread Joseph Dal Molin
VueCentric is not open source nor FOIA
From the IHS website:
"A private corporation, Clinical Informatics Associates, under contract 
to IHS, owns the framework technology for IHS·EHR, called VueCentric. 
VueCentric is not an end user application, but is a technical 
infrastructure that supports graphical presentation of data from 
applications in the M environment (MSM, DSM or Caché). Within the 
VueCentric GUI framework, clinical functions are visually and 
operationally integrated in a way that is accessible and intuitive to 
users comfortable with Windows® programs. All data generated in IHS·EHR 
is stored in the RPMS database."

Sowinski, Richard J. wrote:
I agree with your second annonymous poster. IHS is probably ahead with their
View Centric product.
Unfortunately, I don't know if it's available via FOIA, and I don't believe
it is open source.

---
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Nancy Anthracite
I am sure there was, at least in the code I have been working with, and I was 
unaware of the change so I am sorry for the disinformation!

On Thursday 21 April 2005 06:41 pm, Bill Garrett wrote:
> Interestingly, the custom ZTMGRSET script that Keven mentioned in his
> response (thanks Keven) is copying ZISFGTM for GT.M on Unix.  So there
> must have been a change to ZTMGRSET somewhere along the way as the
> builds evolved.  Like I said, ZISFGTM is working so far, but I would be
> interested in looking at the ZISFGUX.m routine to see how it differs.
>
> Nancy Anthracite wrote:
> >ZISFGUX is what you want.
> >
> >On Thursday 21 April 2005 05:04 pm, Bill Garrett wrote:
> >>That's right - ZTMGRSET wants to use ZISFGTM for GT.M on VMS and ZISFGUX
> >>for GT.M on Unix as seen in the code sample below; however, the ZISFGUX
> >>routine is missing from the 'OpenVista SemiVivA FOIA Gold 20050212'
> >>build, so ZTMGRSET ends up copying nothing into %ZISF.  Also, note that
> >>the first line of ZISFGTM has this text: 'HOST FILES FOR GT.M on
> >>Unix/VMS'.  So, the question is then should ZISFGUX have been included
> >>after all, or should ZTMGRSET be copying ZISFGTM instead?  So far,
> >>ZISFGTM is working for me...
> >>
> >>---
> >>snipit of ZTMGRSET from 'OpenVista SemiVivA FOIA Gold 20050212':
> >>
> >>7   ;;GT.M (VMS)
> >>S %S="ZOSVGTM^ZTBKCGTM^ZIS4GTM^ZISFGTM^ZISHGTM^XUCIGTM^ZISETGTM"
> >>  ...
> >>8   ;;GT.M (Unix)
> >>S %S="ZOSVGUX^ZTBKCGUX^ZIS4GTM^ZISFGUX^ZISHGUX^XUCIGTM^ZISETGUX"
> >>
> >>Cameron Schlehuber wrote:
> >>>ZTMGRSET uses the ZISFGUX routine to copy into %ZISF for the GT.M (Unix)
> >>>selection and uses ZISFGTM for the GT.M (VMS) selection.  It sounds like
> >>>that is wrong for the Unix (used also for the Linux) selection.
> >>>
> >>>-Original Message-
> >>>From: [EMAIL PROTECTED]
> >>>[mailto:[EMAIL PROTECTED] On Behalf Of
> >>>Bhaskar, KS
> >>>Sent: Thursday, April 21, 2005 9:28 AM
> >>>To: hardhats-members@lists.sourceforge.net
> >>>Subject: Re: [Hardhats-members] Installing KIDS
> >>>
> >>>Nancy --
> >>>
> >>>I ran ZTMGRSET before packaging the release, and it did its thing.  Had
> >>>it not worked, even basic entry points like ^XUP and P^DI would not have
> >>>worked.  Bill simply ran it again.  However, an omission from ZTMGRSET
> >>>appears to be that it doesn't copy ZISFGTM.m to _ZISF.m.
> >>>
> >>>-- Bhaskar
> >>>
> >>>On Thu, 2005-04-21 at 12:16 -0400, Nancy Anthracite wrote:
> Nice work!  Now to find out why ZTMGRSET  didn't work.
> >>>
> >>>---
> >>>This SF.Net email is sponsored by: New Crystal Reports XI.
> >>>Version 11 adds new functionality designed to reduce time involved in
> >>>creating, integrating, and deploying reporting solutions. Free runtime
> >>>info, new features, or free trial, at:
> >>>http://www.businessobjects.com/devxi/728
> >>>___
> >>>Hardhats-members mailing list
> >>>Hardhats-members@lists.sourceforge.net
> >>>https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >>>
> >>>
> >>>
> >>>---
> >>>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://ads.osdn.com/?ad_ide95&alloc_id396&op=click
> >>>___
> >>>Hardhats-members mailing list
> >>>Hardhats-members@lists.sourceforge.net
> >>>https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >>
> >>---
> >>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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> >>___
> >>Hardhats-members mailing list
> >>Hardhats-members@lists.sourceforge.net
> >>https://lists.sourceforge.net/lists/listinfo/hardhats-members
>
> ---
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

[Hardhats-members] Shorter messages in GT.M V5.0-000

2005-04-21 Thread Bhaskar, KS
Each GT.M message is identified by a name, e.g., ACTLSTEXP.  Quoting
from the Messages and Recovery Procedures Manual:

ACTLSTEXP, Actuallist expected

Run Time Error: This indicates that the DO command, without an
actuallist of parameters, failed because its entryref argument
specified a label that has a formallist of parameters.

Action: Review the interface between the DO and the subroutine.
Add the actuallist to the DO, remove the formallist from the
label, or identify another subroutine to invoke, as appropriate.

Messages can be compile time or run time (informational, warnings as
well as errors), and indeed, since M code can be dynamically compiled
and executed, all errors can occur at run time.

During the course of the development of GT.M V5.0-000, it was observed
that VMS truncates these names at 15 characters, whereas UNIX does not.
The majority of message names are at or below 15 characters in length,
and for any new messages, we will ensure that the names are 15
characters or less.  However, of the hundreds of conditions that GT.M
V4.4-004 can report, six that are currently longer than 15 characters.
These are:

  * COMMAORRPARENEXP, Comma or right parenthesis expected but not
found

  * GTMSECSHRSHUTDOWN, GTMSECSHR process has received a shutdown
request. Shutting down.

  * GTMSECSHRSRVFFILE, : ; Attempt to service request
failed. Client ID: , mesg type: , file: 

  * GTMSECSHRSTARTUP,  - ; GTMSECSHR failed to startup

  * ISOLATIONSTSCHNG, Error changing NOISOLATION status for global
 within a TP transaction from  to 

  * NEWJNLFILECREATE, Journal file  nearing maximum size. New
journal file created.

Of these, only COMMAORRPARENEXP and ISOLATIONSTSCHNG may be encountered
by an error trap in application code; the rest are reported in the
operator log.  Of these, only NEWJNLFILECREATE will occur during normal
operation, and the rest are obscure and likely to be infrequently
encountered (indeed, two, GTMSECSHRSRVFFILE and GTMSECSHRSTARTUP are
likely to be encountered primarily when GT.M has not been installed
correctly).

Effective GT.M V5.0-000, scheduled to be released in mid May, we propose
to replace these message names as follows:

  * COMMAORRPARENEXP   -->  COMMAORRPARENEX 
  * GTMSECSHRSHUTDOWN  -->  GTMSECSHRSHUT 
  * GTMSECSHRSRVFFILE  -->  GTMSECSHRSRVFIL 
  * GTMSECSHRSTARTUP   -->  GTMSECSHRSTART 
  * ISOLATIONSTSCHNG   -->  ISOLATIONSTSCHN 
  * NEWJNLFILECREATE   -->  NEWJNLFILECREAT

If you feel strongly that we should not take this course of action
(since it does have the potential for changing the behavior of existing
code and shell/DCL scripts), please let me know ASAP.  Thank you very
much.

Regards
-- Bhaskar


---
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Bill Garrett
Interestingly, the custom ZTMGRSET script that Keven mentioned in his 
response (thanks Keven) is copying ZISFGTM for GT.M on Unix.  So there 
must have been a change to ZTMGRSET somewhere along the way as the 
builds evolved.  Like I said, ZISFGTM is working so far, but I would be 
interested in looking at the ZISFGUX.m routine to see how it differs.

Nancy Anthracite wrote:
ZISFGUX is what you want.
On Thursday 21 April 2005 05:04 pm, Bill Garrett wrote:
 

That's right - ZTMGRSET wants to use ZISFGTM for GT.M on VMS and ZISFGUX
for GT.M on Unix as seen in the code sample below; however, the ZISFGUX
routine is missing from the 'OpenVista SemiVivA FOIA Gold 20050212'
build, so ZTMGRSET ends up copying nothing into %ZISF.  Also, note that
the first line of ZISFGTM has this text: 'HOST FILES FOR GT.M on
Unix/VMS'.  So, the question is then should ZISFGUX have been included
after all, or should ZTMGRSET be copying ZISFGTM instead?  So far,
ZISFGTM is working for me...
---
snipit of ZTMGRSET from 'OpenVista SemiVivA FOIA Gold 20050212':
7   ;;GT.M (VMS)
   S %S="ZOSVGTM^ZTBKCGTM^ZIS4GTM^ZISFGTM^ZISHGTM^XUCIGTM^ZISETGTM"
 ...
8   ;;GT.M (Unix)
   S %S="ZOSVGUX^ZTBKCGUX^ZIS4GTM^ZISFGUX^ZISHGUX^XUCIGTM^ZISETGUX"
Cameron Schlehuber wrote:
   

ZTMGRSET uses the ZISFGUX routine to copy into %ZISF for the GT.M (Unix)
selection and uses ZISFGTM for the GT.M (VMS) selection.  It sounds like
that is wrong for the Unix (used also for the Linux) selection.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Bhaskar, KS
Sent: Thursday, April 21, 2005 9:28 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Installing KIDS
Nancy --
I ran ZTMGRSET before packaging the release, and it did its thing.  Had
it not worked, even basic entry points like ^XUP and P^DI would not have
worked.  Bill simply ran it again.  However, an omission from ZTMGRSET
appears to be that it doesn't copy ZISFGTM.m to _ZISF.m.
-- Bhaskar
On Thu, 2005-04-21 at 12:16 -0400, Nancy Anthracite wrote:
 

Nice work!  Now to find out why ZTMGRSET  didn't work.
   

---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime
info, new features, or free trial, at:
http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

---
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://ads.osdn.com/?ad_ide95&alloc_id396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
 

---
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
   

 


---
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread SCHLEHUBER.CAMERON
Wally just e-mailed me to indicate it should be ZISFGTM for
GT.M (Unix) selections.


---
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Nancy Anthracite
ZISFGUX is what you want.

On Thursday 21 April 2005 05:04 pm, Bill Garrett wrote:
> That's right - ZTMGRSET wants to use ZISFGTM for GT.M on VMS and ZISFGUX
> for GT.M on Unix as seen in the code sample below; however, the ZISFGUX
> routine is missing from the 'OpenVista SemiVivA FOIA Gold 20050212'
> build, so ZTMGRSET ends up copying nothing into %ZISF.  Also, note that
> the first line of ZISFGTM has this text: 'HOST FILES FOR GT.M on
> Unix/VMS'.  So, the question is then should ZISFGUX have been included
> after all, or should ZTMGRSET be copying ZISFGTM instead?  So far,
> ZISFGTM is working for me...
>
> ---
> snipit of ZTMGRSET from 'OpenVista SemiVivA FOIA Gold 20050212':
>
> 7   ;;GT.M (VMS)
> S %S="ZOSVGTM^ZTBKCGTM^ZIS4GTM^ZISFGTM^ZISHGTM^XUCIGTM^ZISETGTM"
>   ...
> 8   ;;GT.M (Unix)
> S %S="ZOSVGUX^ZTBKCGUX^ZIS4GTM^ZISFGUX^ZISHGUX^XUCIGTM^ZISETGUX"
>
> Cameron Schlehuber wrote:
> >ZTMGRSET uses the ZISFGUX routine to copy into %ZISF for the GT.M (Unix)
> >selection and uses ZISFGTM for the GT.M (VMS) selection.  It sounds like
> >that is wrong for the Unix (used also for the Linux) selection.
> >
> >-Original Message-
> >From: [EMAIL PROTECTED]
> >[mailto:[EMAIL PROTECTED] On Behalf Of
> > Bhaskar, KS
> >Sent: Thursday, April 21, 2005 9:28 AM
> >To: hardhats-members@lists.sourceforge.net
> >Subject: Re: [Hardhats-members] Installing KIDS
> >
> >Nancy --
> >
> >I ran ZTMGRSET before packaging the release, and it did its thing.  Had
> >it not worked, even basic entry points like ^XUP and P^DI would not have
> >worked.  Bill simply ran it again.  However, an omission from ZTMGRSET
> >appears to be that it doesn't copy ZISFGTM.m to _ZISF.m.
> >
> >-- Bhaskar
> >
> >On Thu, 2005-04-21 at 12:16 -0400, Nancy Anthracite wrote:
> >>Nice work!  Now to find out why ZTMGRSET  didn't work.
> >
> >---
> >This SF.Net email is sponsored by: New Crystal Reports XI.
> >Version 11 adds new functionality designed to reduce time involved in
> >creating, integrating, and deploying reporting solutions. Free runtime
> > info, new features, or free trial, at:
> > http://www.businessobjects.com/devxi/728
> > ___
> >Hardhats-members mailing list
> >Hardhats-members@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >
> >
> >
> >---
> >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://ads.osdn.com/?ad_ide95&alloc_id396&op=click
> >___
> >Hardhats-members mailing list
> >Hardhats-members@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/hardhats-members
>
> ---
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


RE: [Hardhats-members] Installing KIDS

2005-04-21 Thread Kevin Toppenberg
When operating system # 8 (GTM) is chosen then routine 8 is called.  It does the moving by setting the source files into %S, and destination files into %D.
 
Below one can see that the 4th source file is ZISFGTM and the 4th dest file is %ZISF.
 
So I don't know why the file isn't being copied properly.
 
Kevin
 
 
 
8 ;;GT.M (Unix) S %S="ZOSVGUX^ZTBKCGUX^ZIS4GTM^ZISFGTM^ZISHGUX^XUCIGTM^ZISETGUX" D DES D MOVE...
 
DES  S %D="%ZOSV^%ZTBKC1^%ZIS4^%ZISF^%ZISH^%XUCI^ZISETUP"  Q
 Cameron Schlehuber <[EMAIL PROTECTED]> wrote:
ZTMGRSET uses the ZISFGUX routine to copy into %ZISF for the GT.M (Unix)selection and uses ZISFGTM for the GT.M (VMS) selection. It sounds likethat is wrong for the Unix (used also for the Linux) selection.-Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED] On Behalf Of Bhaskar,KSSent: Thursday, April 21, 2005 9:28 AMTo: hardhats-members@lists.sourceforge.netSubject: Re: [Hardhats-members] Installing KIDSNancy --I ran ZTMGRSET before packaging the release, and it did its thing. Hadit not worked, even basic entry points like ^XUP and P^DI would not haveworked. Bill simply ran it again. However, an omission from ZTMGRSETappears to be that it doesn't copy ZISFGTM.m to _ZISF.m.-- BhaskarOn Thu, 2005-04-21 at 12:16 -0400, 
 Nancy
 Anthracite wrote:> Nice work! Now to find out why ZTMGRSET didn't work.---This SF.Net email is sponsored by: New Crystal Reports XI.Version 11 adds new functionality designed to reduce time involved increating, integrating, and deploying reporting solutions. Free runtime info,new features, or free trial, at: http://www.businessobjects.com/devxi/728___Hardhats-members mailing listHardhats-members@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/hardhats-members---SF email is sponsored by - The IT Product GuideRead honest & candid reviews on hundreds of IT Products from real users.Discover which products truly live up to the hype. Start reading
 now.http://ads.osdn.com/?ad_ide95&alloc_id396&op=click___Hardhats-members mailing listHardhats-members@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/hardhats-members__Do You Yahoo!?Tired of spam?  Yahoo! Mail has the best spam protection around http://mail.yahoo.com 

Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Kevin Toppenberg
As part of my scripting install system I created a custom ZTMGRSET.  Here is a link
http://69.68.182.66/downloads/OpenVista/Config/TMGMGRST.m
It fixed a few problems such as not searching the entire $ZROUTINES path for source files.
 
I'd be curious for Bill to download the above file and try it.
 
It is evoked like this: do ZTMGRSET^TMGMGRST()
 
Kevin
Nancy Anthracite <[EMAIL PROTECTED]> wrote:
Nice work! Now to find out why ZTMGRSET didn't work.On Thursday 21 April 2005 10:33 am, Bill Garrett wrote:> I tried to do KIDS install on a (reasonably) fresh install of 'OpenVista> SemiVivA FOIA Gold 20050212' and found that %ZISF for GT.M didn't> exist. This is the routine that supports host files on GT.M for> Unix/VMS (according to its header). It should have been put in place by> ZTMGRSET, so I ran ZTMGRSET again, and %ZISF was never saved. I fixed> it manually by locating the ZISFGTM.m routine and copying it to _ZISF.m:>> [EMAIL PROTECTED] ~]$ ls r/_ZISF*> ls: r/_ZISF*: No such file or directory> [EMAIL PROTECTED] ~]$ ls r/ZISF*GTM*> r/ZISFGTM.m r/ZISFGTM.o> [EMAIL PROTECTED] ~]$ cp r/ZISFGTM.m r/_ZISF.m> [EMAIL PROTECTED] ~]$>> Now, after removing the WNS parameter from the HFS devi
 ce
 entry, I can> at least test opening the device:>> GTM>D ^%ZIS>> DEVICE: HOME// HFS Host File Server> HOST FILE NAME: /tmp/vista-tmp.txt//>> GTM>U IO W !,"HELLO"> GTM>D ^%ZISC> GTM>H> [EMAIL PROTECTED] ~]$ cat /tmp/vista-tmp.txt>> HELLO> [EMAIL PROTECTED] ~]$>> Ok, looking at the install file, the last patch loaded for the kernel is> XU*8*328 SEQ #304, so I ftp'd the next one in sequence> (XU-8_SEQ-305_PAT-375.KID), and was able to do the install:>> Select OPTION NAME: XPD MAIN Kernel Installation & Distribution> System>> Select Kernel Installation & Distribution System Option: INSTallation>> Select Installation Option: LOAD a Distribution> Enter a Host File: /home/vista/XU-8_SEQ-305_PAT-375.KID>> Released XU*8*375 SEQ #305> Comment: Extracted from mail message>
 >
 This Distribution contains Transport Globals for the following Package(s):> XU*8.0*375> Distribution OK!>> Want to Continue with Load? YES//> Loading Distribution...>> XU*8.0*375> Use INSTALL NAME: XU*8.0*375 to install this Distribution.>>> Select Installation Option: verify Checksums in Transport Global> Select INSTALL NAME: XU*8.0*375 Loaded from Distribution> Loaded from> Distribution 4/21/[EMAIL PROTECTED]:33:41> => Extracted from mail message ;Created on>> This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of> Extracted from mail message ;Created on> It consisted of the following Install(s):> XU*8.0*375> DEVICE: HOME// TELNET>> PACKAGE: XU*8.0*375 Apr 21, 2005 10:33 am PAGE> 1> --->>> 1 Routine c
 hecked,
 0 failed.>>> Select Installation Option: backup a Transport Global> Select INSTALL NAME: XU*8.0*375 Loaded from Distribution> Loaded from> Distribution 4/21/[EMAIL PROTECTED]:33:41> => Extracted from mail message ;Created on>> This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of> Extracted from mail message ;Created on> It consisted of the following Install(s):> XU*8.0*375> Subject: Backup of XU*8.0*375 install on Apr 21, 2005> Replace> Loading Routines for XU*8.0*375> Routine XU8375P is not on the disk..> Send mail to: GARRETT,WILLIAM E// GARRETT,WILLIAM E> Select basket to send to: IN//> And Send to:>> Select Installation Option: install Package(s)> Select INSTALL NAME: XU*8.0*375 Loaded from Distribution> Loaded from> Distribution 4/21/[EMAIL PROTECTED]:33:41> => Extracted from mail message ;Created
 on>> This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of> Extracted from mail message ;Created on> It consisted of the following Install(s):> XU*8.0*375> Checking Install for Package XU*8.0*375>> Install Questions for XU*8.0*375 Want KIDS to INHIBIT LOGONs during the install? YES// n NO> Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// n NO>> Enter the Device you want to print the Install messages.> You can queue the install by enter a 'Q' at the device prompt.> Enter a '^' to abort the install.>> DEVICE: HOME// TELNET>> Install Started for XU*8.0*375 :> Apr 21, [EMAIL PROTECTED]:33:59>> Build Distribution Date: Feb 04, 2005>> Installing Routines:> Apr 21, [EMAIL PROTECTED]:33:59>> Running Post-Install Routine: ^XU8375P>> Recompiling
 templates...>> Updating trigger field definitions...>> Updating Routine file...>> Updating KIDS files...>> XU*8.0*375 Installed.> Apr 21, [EMAIL PROTECTED]:33:59>> Not a VA primary domain>> NO Install Message sent>> Install Completed>> >> Hope this helps!>> Bill Garrett>> Lloyd Milligan wrote:> > Also, the OPEN PARAMETERS are wrong. The value "WNS" is> > Cache-specific. That may not matter. If it still doesn't work after> > removing "WNS" I would suggest simulating what ^XPDIL does, to> > troubleshoot. In other words, from the GT.M command prompt 

Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Bill Garrett
That's right - ZTMGRSET wants to use ZISFGTM for GT.M on VMS and ZISFGUX 
for GT.M on Unix as seen in the code sample below; however, the ZISFGUX 
routine is missing from the 'OpenVista SemiVivA FOIA Gold 20050212' 
build, so ZTMGRSET ends up copying nothing into %ZISF.  Also, note that 
the first line of ZISFGTM has this text: 'HOST FILES FOR GT.M on 
Unix/VMS'.  So, the question is then should ZISFGUX have been included 
after all, or should ZTMGRSET be copying ZISFGTM instead?  So far, 
ZISFGTM is working for me...

---
snipit of ZTMGRSET from 'OpenVista SemiVivA FOIA Gold 20050212':
7   ;;GT.M (VMS)
   S %S="ZOSVGTM^ZTBKCGTM^ZIS4GTM^ZISFGTM^ZISHGTM^XUCIGTM^ZISETGTM"
 ...
8   ;;GT.M (Unix)
   S %S="ZOSVGUX^ZTBKCGUX^ZIS4GTM^ZISFGUX^ZISHGUX^XUCIGTM^ZISETGUX"
Cameron Schlehuber wrote:
ZTMGRSET uses the ZISFGUX routine to copy into %ZISF for the GT.M (Unix)
selection and uses ZISFGTM for the GT.M (VMS) selection.  It sounds like
that is wrong for the Unix (used also for the Linux) selection.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bhaskar,
KS
Sent: Thursday, April 21, 2005 9:28 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Installing KIDS
Nancy --
I ran ZTMGRSET before packaging the release, and it did its thing.  Had
it not worked, even basic entry points like ^XUP and P^DI would not have
worked.  Bill simply ran it again.  However, an omission from ZTMGRSET
appears to be that it doesn't copy ZISFGTM.m to _ZISF.m.
-- Bhaskar
On Thu, 2005-04-21 at 12:16 -0400, Nancy Anthracite wrote:
 

Nice work!  Now to find out why ZTMGRSET  didn't work.
   


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

---
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://ads.osdn.com/?ad_ide95&alloc_id396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
 


---
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] IHS system???

2005-04-21 Thread Nancy Anthracite
Your not missing anything but typing ability.  I am missing that and knowledge 
of VistA.  Thanks for the heads up! ;-)

On Thursday 21 April 2005 12:49 pm, Greg Woodhouse wrote:
> I guess I'm missing something. PID-5, patient name, is a repeating
> fieled, anyway.
>
> --- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
> > This problem was addressed by the Pediatric HL7 Special interest
> > group.  Not
> > only are there no names to start out with, but there are likely to be
> >
> > situations with multiple names being used for the same child, both
> > legally
> > and otherwise with foster care, adoption, separated parents, etc.
> > The
> > listing of items which are possibly unique to the Pediatric Record
> > that need
> > to be addressed in the standard for a medical record overall was
> > presented to
> > representatives from the EHR-TC and Patient Care TC just yesterday
> > afternoon
> > by members of the Pedi SIG so the additional hard work of trying to
> > figure
> > out how to deal in the standard for the overall medical record can
> > progress.
> > I have had the privilege of being able to "attend" some to the
> > conference
> > calls of the Pedi HL7 SIG and it has been invaluable for giving me an
> > idea
> > what has to be done.  That said, actually doing it in a in a
> > reasonable,
> > staged, workable manner that can be incorporated into VistA is
> > another kettle
> > of fish altogether.
>
> A practical man is a man who practices the errors of his forefathers.
> --Benjamin Disraeli 
> Greg Woodhouse
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
>
>
>
>
> ---
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime
> info, new features, or free trial, at:
> http://www.businessobjects.com/devxi/728
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Nancy Anthracite
Yes, I figured the problem was in the ZTMGRSET code.  The one I have in the VA 
demo is probably not the same one as he has as I stole it out of a working 
version of VistA on GTM, so Bill, would you please email me your ZTMGRSET.m?

On Thursday 21 April 2005 12:28 pm, Bhaskar, KS wrote:
> Nancy --
>
> I ran ZTMGRSET before packaging the release, and it did its thing.  Had
> it not worked, even basic entry points like ^XUP and P^DI would not have
> worked.  Bill simply ran it again.  However, an omission from ZTMGRSET
> appears to be that it doesn't copy ZISFGTM.m to _ZISF.m.
>
> -- Bhaskar
>
> On Thu, 2005-04-21 at 12:16 -0400, Nancy Anthracite wrote:
> > Nice work!  Now to find out why ZTMGRSET  didn't work.
>
> ---
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime
> info, new features, or free trial, at:
> http://www.businessobjects.com/devxi/728
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


RE: [Hardhats-members] Installing KIDS

2005-04-21 Thread Cameron Schlehuber
ZTMGRSET uses the ZISFGUX routine to copy into %ZISF for the GT.M (Unix)
selection and uses ZISFGTM for the GT.M (VMS) selection.  It sounds like
that is wrong for the Unix (used also for the Linux) selection.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bhaskar,
KS
Sent: Thursday, April 21, 2005 9:28 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Installing KIDS

Nancy --

I ran ZTMGRSET before packaging the release, and it did its thing.  Had
it not worked, even basic entry points like ^XUP and P^DI would not have
worked.  Bill simply ran it again.  However, an omission from ZTMGRSET
appears to be that it doesn't copy ZISFGTM.m to _ZISF.m.

-- Bhaskar

On Thu, 2005-04-21 at 12:16 -0400, Nancy Anthracite wrote:
> Nice work!  Now to find out why ZTMGRSET  didn't work.



---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members



---
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://ads.osdn.com/?ad_ide95&alloc_id396&op=click
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] IHS system???

2005-04-21 Thread Greg Woodhouse
I guess I'm missing something. PID-5, patient name, is a repeating
fieled, anyway.

--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:

> This problem was addressed by the Pediatric HL7 Special interest
> group.  Not 
> only are there no names to start out with, but there are likely to be
> 
> situations with multiple names being used for the same child, both
> legally 
> and otherwise with foster care, adoption, separated parents, etc. 
> The 
> listing of items which are possibly unique to the Pediatric Record
> that need 
> to be addressed in the standard for a medical record overall was
> presented to 
> representatives from the EHR-TC and Patient Care TC just yesterday
> afternoon 
> by members of the Pedi SIG so the additional hard work of trying to
> figure 
> out how to deal in the standard for the overall medical record can
> progress.  
> I have had the privilege of being able to "attend" some to the
> conference 
> calls of the Pedi HL7 SIG and it has been invaluable for giving me an
> idea 
> what has to be done.  That said, actually doing it in a in a
> reasonable, 
> staged, workable manner that can be incorporated into VistA is
> another kettle 
> of fish altogether.
> 


A practical man is a man who practices the errors of his forefathers. 
--Benjamin Disraeli

Greg Woodhouse 
[EMAIL PROTECTED] 
[EMAIL PROTECTED] 





---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


RE: [Hardhats-members] IHS system???

2005-04-21 Thread Cameron Schlehuber
The first VistA-Office EHR release will in fact have the RPMS code to handle
HRNs as used by IHS.  While the formal release by VHA of the code to VistA
may not happen until after the release of VistA-Office due among other
things to routine overlaps in patches slated to be released by VHA in the
next couple of months, incomplete patch verification, e.g. the necessary
regression testing, etc. I am confident that in the months following the
release by CMS of VistA-Office, the patch streams will converge to the
benefit of VA, IHS and users of VistA-Office. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Toppenberg
Sent: Thursday, April 21, 2005 7:20 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] IHS system???

Let me see if I understand.

1. The HRN is a good system for the IHS
2. Althought file 901 is distributed with the FOIA
vista, it is not fully integrated, i.e. the lookup
routines are not there.
3. It shouldn't be too hard to achieve this
integration.

If this is true, and if such a HRN is needed by so
many non-VA sites, would it be worth a little effort
to have our next WorldVistA version support this?  

Perhaps VistA Office is going to solve this problem
for us, but I don't want to have unrealistic
expectations as to what they can achieve in a limited
amount of time.

Kevin

--- Floyd Dennis <[EMAIL PROTECTED]> wrote:

> There appears to be some confusion on the nature of
> the IHS patient file¹s
> Health Record Number.  I don¹t know if clarification
> is possible, but I¹ll
> give it a shot. :>
> 
> 1.   Like many of the initial RPMS modules, the IHS
> Patient Registration
> system is ³piggybacked² onto the VA¹s registration
> system.  Much of the
> patient demographic information resides in File #2
> (referenced in RPMS as
> the VA PATIENT file).  Additional patient data
> captured by the RPMS patient
> registration system is stored in File #901 (the
> RPMS system¹s PATIENT
> file ­ referred to as PATIENT/IHS by VistA), which
> maintains a DINUM
> relationship with File #2.  Examples of such
> additional data are patient¹s
> tribe of membership, level of eligibility for IHS
> services, etc.
> 
> 2.  The RPMS deals with IHS-specific mods to VA
> standard dictionaries in a
> similar fashion; DINUM-related RPMS correspondent
> dictionaries are
> established; and the IHS-specific mods dealt with in
> the corresponding
> dictionary.  One example of this is the IHS¹s method
> of identifying
> facilities.  The VA¹s standard dictionary of
> facilities is maintained in
> file #4 (INSTITUTION); IHS has its own standard
> method of facility ID
> coding, however, for which (to the best of my
> knowledge) there is no
> corresponding VA code.  The RPMS solution to this
> was to create a LOCATION
> file #999.06 which (a) has a DINUM relation with
> file #4 and (b)
> contains the IHS standard 6-digit ASUFAC ID code for
> the facility.  Simple,
> huh?  :)
> 
> 3.  When looking at using the VA¹s DHCP software,
> one of the very first
> hurdles IHS had to overcome was the problem of
> patient identification.  The
> VA¹s patient registration system uses SSN as its
> primary patient identifier.
> IHS cannot base its patient identification on SSN,
> however, because many of
> its patients (especially on the larger Southwestern
> U.S. reservations) have
> never applied for nor been issued a Social Security
> number.
> 
> 4.  The IHS solution was/is the health record number
> (HRN), a number which
> uniquely identifies a patient within a given
> healthcare facility.  There is
> no relationship between the HRN and the SSN; the two
> are apples and oranges.
> For facility-external references, the HRN can be
> concatenated onto the end
> of the facility¹s ASUFAC code.  In IHS, the HRN is
> limited to 6 digits;
> YMMV.
> 
> 5.  The RPMS¹s PATIENT file #901 incorporates
> multiple field #4101 which
> contains (a) a LOCATION file pointer reference to
> each facility at which a
> patient has been registered, and (b) the patient¹s
> HRN at that facility.
> This (theoretically) allows coherent management of
> demographic information
> for patients registered at more than one IHS
> facility.  In Anna¹s example
> entries, the HEALTH RECORD FAC field is the pointer
> reference to the
> registering LOCATION file entry, and the HEALTH
> RECORD NO. field is the
> patient¹s HRN at that facility.  Anna¹s #3 entry
> represents a patient TEST
> PATIENT,PATIENT who has been registered with chart
> number 01234 at the
> SOFTWARE SERVICE healthcare facility.
> 
> 6.  Unsurprisingly, the earlier standard FileMan
> lookups did not deal well
> with the notion of using several data items from a
> multiple field as a
> unique patient lookup identifier (this *was* back in
> the days of FileMan
> v16.60, after all).  The AUPNLK* routines perform
> that patient lookup
> function, as well as providing increased security on
> patient lookups.
> 
> 7.  Sin

Re: [Hardhats-members] IHS system???

2005-04-21 Thread Nancy Anthracite
This problem was addressed by the Pediatric HL7 Special interest group.  Not 
only are there no names to start out with, but there are likely to be 
situations with multiple names being used for the same child, both legally 
and otherwise with foster care, adoption, separated parents, etc.  The 
listing of items which are possibly unique to the Pediatric Record that need 
to be addressed in the standard for a medical record overall was presented to 
representatives from the EHR-TC and Patient Care TC just yesterday afternoon 
by members of the Pedi SIG so the additional hard work of trying to figure 
out how to deal in the standard for the overall medical record can progress.  
I have had the privilege of being able to "attend" some to the conference 
calls of the Pedi HL7 SIG and it has been invaluable for giving me an idea 
what has to be done.  That said, actually doing it in a in a reasonable, 
staged, workable manner that can be incorporated into VistA is another kettle 
of fish altogether.

On Thursday 21 April 2005 11:50 am, James Gray wrote:
> One of the more interesting is names for newborns.  To enter a patient into
> RPMS they must have a name (.01 field in file 2).  You may need a .01 value
> before the infant has a name.  So newborns end up with names like "Babygirl
> Begay".  Then when the infant is given a name the name is changed in RPMS.
> Jim Gray
>
> - Original Message -
> From: "Nancy Anthracite" <[EMAIL PROTECTED]>
> To: 
> Sent: Thursday, April 21, 2005 5:45 AM
> Subject: Re: [Hardhats-members] IHS system???
>
>
> Tantalized and becoming less confused would describe me, and hoping someone
> would be willing to help us document how to implement this for the
> WorldVistA
> Wiki.
>
> BTW, it sure is nice to see posts coming from IHS folks.  The experience
> you all have had with adapting VistA for the "Real World" certainly can
> help those of us struggling with the issues for the first time a whole lot!
>  You have dealt with the small to large implementations and a non-veteran
> population with characteristics that are more generalizable to the whole
> world than what VA FOIA VistA needs to support, such as no SS number, Peds
> and OBGYN, so you have a lot of valuable information that many of this
> list's
> readers could use, for sure.  You could probably also tell us what worked
> and
> what didn't with the solutions you found.
>
> So, besides the SS numbers, what are some of the other big issues you IHS
> folks have had to tackle that those of use looking at VistA from the VA
> have been blissfully unaware of the need to address?
>
> On Thursday 21 April 2005 02:37 am, Floyd Dennis wrote:
> > There appears to be some confusion on the nature of the IHS patient
> > file¹s Health Record Number.  I don¹t know if clarification is possible,
> > but I¹ll give it a shot. :>
> >
> > 1.   Like many of the initial RPMS modules, the IHS Patient Registration
> > system is ³piggybacked² onto the VA¹s registration system.  Much of the
> > patient demographic information resides in File #2 (referenced in RPMS as
> > the VA PATIENT file).  Additional patient data captured by the RPMS
> > patient
> > registration system is stored in File #901 (the RPMS system¹s PATIENT
> > file ­ referred to as PATIENT/IHS by VistA), which maintains a DINUM
> > relationship with File #2.  Examples of such additional data are
> > patient¹s tribe of membership, level of eligibility for IHS services,
> > etc.
> >
> > 2.  The RPMS deals with IHS-specific mods to VA standard dictionaries in
> > a similar fashion; DINUM-related RPMS correspondent dictionaries are
> > established; and the IHS-specific mods dealt with in the corresponding
> > dictionary.  One example of this is the IHS¹s method of identifying
> > facilities.  The VA¹s standard dictionary of facilities is maintained in
> > file #4 (INSTITUTION); IHS has its own standard method of facility ID
> > coding, however, for which (to the best of my knowledge) there is no
> > corresponding VA code.  The RPMS solution to this was to create a
> > LOCATION file #999.06 which (a) has a DINUM relation with file #4 and
> > (b) contains the IHS standard 6-digit ASUFAC ID code for the facility.
> > Simple,
> > huh?  :)
> >
> > 3.  When looking at using the VA¹s DHCP software, one of the very first
> > hurdles IHS had to overcome was the problem of patient identification.
> > The
> > VA¹s patient registration system uses SSN as its primary patient
> > identifier. IHS cannot base its patient identification on SSN, however,
> > because many of its patients (especially on the larger Southwestern U.S.
> > reservations) have never applied for nor been issued a Social Security
> > number.
> >
> > 4.  The IHS solution was/is the health record number (HRN), a number
> > which uniquely identifies a patient within a given healthcare facility. 
> > There is
> > no relationship between the HRN and the SSN; the two are apples and
> > oranges. For facility-external reference

RE: [Hardhats-members] Canadian Think Smart Initiative question o n LMN.

2005-04-21 Thread Greg Woodhouse
Of course, .NET and web wervices are different things. Web services can
be implemented nicely in Java if desired, but the .NET framework relies
on proprietary technologies as you have described here. What is
unfortunate is that technologies such as XML, SOAP and even HTTP tend
to be inappropriately linked to .NET. And, of course, there is nothing
inherently wrong with .NET: it's just that it is one of of several
technologies providing similar high level functionality.

A practical man is a man who practices the errors of his forefathers. 
--Benjamin Disraeli

Greg Woodhouse 
[EMAIL PROTECTED] 
[EMAIL PROTECTED] 





---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Bhaskar, KS
Nancy --

I ran ZTMGRSET before packaging the release, and it did its thing.  Had
it not worked, even basic entry points like ^XUP and P^DI would not have
worked.  Bill simply ran it again.  However, an omission from ZTMGRSET
appears to be that it doesn't copy ZISFGTM.m to _ZISF.m.

-- Bhaskar

On Thu, 2005-04-21 at 12:16 -0400, Nancy Anthracite wrote:
> Nice work!  Now to find out why ZTMGRSET  didn't work.



---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


RE: [Hardhats-members] possible taskman problem---- Nursing module

2005-04-21 Thread Cameron Schlehuber









Whether from the nurse’s menus or
directly from XUP, it is the same since there are no “entry actions”
in prior menus.  I was pointing out that TaskMan would have it in its task list
only if it was tasked to run, which isn’t what happens when invoked
directly from the menu (or XUP, which is part of the menu driver code).

 

The global ^DIC(213.9,1,"DATE") =
^0^0^0^^0^0^0^0^0^0^0^1 was “hard
set” and it looks like you’ve got some new information there now
for the acuity times, etc!  What’s still missing is the “zero node”
and especially the “name” in the first piece of the zero node.  VA
FileMan is getting fooled because there isn’t an entry at ^DIC(213.9,1,0)
with the first “^” piece properly filled in (and of course, the “B”
x-ref set as well … it’s the “B” x-ref that FileMan
first looks to to give you a list of entries when you hit the “?”.

 

-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anna Joseph
Sent: Wednesday,
 April 20, 2005 10:57 PM
To:
hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members]
possible taskman problem Nursing module

 



Cameron,





 





So that means that I must invoke the routine/option only
from the nurse's menu? Just to be sure, I did that again using the options
below.





I have follwed the setup as per the Nursing V.4.0 Technical
Manual and Package Security Guide (pg 1.1 - 1.10)





 





GTM>D ^XUP





 





Setting up programmer environment
Terminal Type set to: C-VT100





 





Select OPTION NAME:
NURS-SYS-MGR   Nursing System Manager's Menu





 





Version 4.0 of the Nursing Package






   1  Administrator's Menu ...
   2  VA FileMan (Nursing ADP
Coordinator) ...
   3  Head Nurse's Menu ...
   4  Nursing Educator's Menu ...
   5  Nursing Features (all options) ...
   6  QA Coordinator's Menu ...
   7  Staff Nurse Menu ...





 





Select Nursing System Manager's Menu Option: 5  Nursing
Features (all options)






   1  Administration Records, Enter/Edit
...
   2  Administration Records, Print ...
   3  Administrative Site File Functions
...
   4  Nursing Education Reports, Print
...
   5  Patient Care Data, Enter/Edit ...
   6  Patient Care Data, Print ...
   7  Clinical Site File Functions ...
   8  QI Data, Enter/Edit ...
   9  Quality Performance Reports ...
   10 QI Site Files ...
   11 Special Functions ...





 





Select Nursing Features (all options) Option: 11 
Special Functions






   1  Admit/Transfer Pt. (Nursing Pkg.
Only)
   2  Inactivate/Disch. Pt. (Nursing
Pkg. Only)
   3  Employee Activation/Separation
Report
   4  Manual Nursing Acuity/Separation
Run
   5  Unclassified AMIS 1106 Patients
   6  Manhours Exception Print by
Service
   7  Unclassified Midnight Patients
   8  Manhours Exception Print by
Location
   9  Position Control/Staff File Integrity
Report





 





Select Special Functions Option: 4






* 

*
* 

*
*  
** WARNING -- SPECIAL RUNNING
**  
*
* 

*
*   THE PURPOSE
OF THIS OPTION IS TO UPDATE THE
NURSING    *
*   PACKAGE
ACUITY-EMPLOYEE ACTIVATION/SEPARATION
COUNTS   *
*   THIS ROUTINE
SHOULD BE RUN IF TASKMAN IS
INOPERABLE    *
* 

*
*   CONTACT THE
NURSING ADP COORDINATOR TO CONFIRM THAT THE    *
*   ACUITY (AMIS
1106) UPDATE WILL BE RUN TONIGHT
VIA  *
*  
TASKMAN.  
*
* 

*
* 

*







 





Press RETURN to continue, or "^" to exit:





and then this is what I'm stuck with again






... BACKUP/NURSING ACUITY - EMPLOYEE SEP/ACT RUN





Also the entry in the site file as per the menu
option is





 





Select Administrative Site File Functions Option: 11 
Site Parameter File
CNO PRINTER:
PROFESSIONAL PERCENTAGE: 100//
DAY SHIFT ACUITY TIME: 1530//
EVENING SHIFT ACUITY TIME: 2330//
NIGHT SHIFT ACUITY TIME: 0730//
PRODUCT LINE: YES//
MULTI-DIVISIONAL: YES//





But these entries don't seem to be there in the file,
when i access it from fileman





 





GTM>D Q^DI






VA FileMan 22.0





 





Select OPTION: 5  INQU

Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Nancy Anthracite
Nice work!  Now to find out why ZTMGRSET  didn't work.

On Thursday 21 April 2005 10:33 am, Bill Garrett wrote:
> I tried to do KIDS install on a (reasonably) fresh install of 'OpenVista
> SemiVivA FOIA Gold 20050212' and found that %ZISF for GT.M didn't
> exist.  This is the routine that supports host files on GT.M for
> Unix/VMS (according to its header).  It should have been put in place by
> ZTMGRSET, so I ran ZTMGRSET again, and %ZISF was never saved.  I fixed
> it manually by locating the ZISFGTM.m routine and copying it to _ZISF.m:
>
> [EMAIL PROTECTED] ~]$ ls r/_ZISF*
> ls: r/_ZISF*: No such file or directory
> [EMAIL PROTECTED] ~]$ ls r/ZISF*GTM*
> r/ZISFGTM.m  r/ZISFGTM.o
> [EMAIL PROTECTED] ~]$ cp r/ZISFGTM.m r/_ZISF.m
> [EMAIL PROTECTED] ~]$
>
> Now, after removing the WNS parameter from the HFS device entry, I can
> at least test opening the device:
>
> GTM>D ^%ZIS
>
> DEVICE: HOME// HFS  Host File Server
> HOST FILE NAME: /tmp/vista-tmp.txt//
>
> GTM>U IO W !,"HELLO"
> GTM>D ^%ZISC
> GTM>H
> [EMAIL PROTECTED] ~]$ cat /tmp/vista-tmp.txt
>
> HELLO
> [EMAIL PROTECTED] ~]$
>
> Ok, looking at the install file, the last patch loaded for the kernel is
> XU*8*328 SEQ #304, so I ftp'd the next one in sequence
> (XU-8_SEQ-305_PAT-375.KID), and was able to do the install:
>
> Select OPTION NAME: XPD MAIN   Kernel Installation & Distribution
> System
>
> Select Kernel Installation & Distribution System Option: INSTallation
>
> Select Installation Option: LOAD a Distribution
> Enter a Host File: /home/vista/XU-8_SEQ-305_PAT-375.KID
>
> Released XU*8*375 SEQ #305
> Comment: Extracted from mail message
>
> This Distribution contains Transport Globals for the following Package(s):
>XU*8.0*375
> Distribution OK!
>
> Want to Continue with Load? YES//
> Loading Distribution...
>
>XU*8.0*375
> Use INSTALL NAME: XU*8.0*375 to install this Distribution.
>
>
> Select Installation Option: verify Checksums in Transport Global
> Select INSTALL NAME:XU*8.0*375 Loaded from Distribution
> Loaded from
> Distribution  4/21/[EMAIL PROTECTED]:33:41
>  => Extracted from mail message  ;Created on
>
> This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of
>Extracted from mail message  ;Created on
>It consisted of the following Install(s):
>  XU*8.0*375
> DEVICE: HOME//   TELNET
>
> PACKAGE: XU*8.0*375 Apr 21, 2005 10:33 am PAGE
> 1
> ---
>
>
>1 Routine checked, 0 failed.
>
>
> Select Installation Option: backup a Transport Global
> Select INSTALL NAME:XU*8.0*375 Loaded from Distribution
> Loaded from
> Distribution  4/21/[EMAIL PROTECTED]:33:41
>  => Extracted from mail message  ;Created on
>
> This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of
>Extracted from mail message  ;Created on
>It consisted of the following Install(s):
>  XU*8.0*375
> Subject: Backup of XU*8.0*375 install on Apr 21, 2005
>   Replace
> Loading Routines for XU*8.0*375
> Routine XU8375P is not on the disk..
> Send mail to: GARRETT,WILLIAM E//   GARRETT,WILLIAM E
> Select basket to send to: IN//
> And Send to:
>
> Select Installation Option: install Package(s)
> Select INSTALL NAME:XU*8.0*375 Loaded from Distribution
> Loaded from
> Distribution  4/21/[EMAIL PROTECTED]:33:41
>  => Extracted from mail message  ;Created on
>
> This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of
>Extracted from mail message  ;Created on
>It consisted of the following Install(s):
>  XU*8.0*375
> Checking Install for Package XU*8.0*375
>
> Install Questions for XU*8.0*375
>
>
>
> Want KIDS to INHIBIT LOGONs during the install? YES// n  NO
> Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// n  NO
>
> Enter the Device you want to print the Install messages.
> You can queue the install by enter a 'Q' at the device prompt.
> Enter a '^' to abort the install.
>
> DEVICE: HOME//   TELNET
>
>  Install Started for XU*8.0*375 :
>Apr 21, [EMAIL PROTECTED]:33:59
>
> Build Distribution Date: Feb 04, 2005
>
>  Installing Routines:
>Apr 21, [EMAIL PROTECTED]:33:59
>
>  Running Post-Install Routine: ^XU8375P
>
> Recompiling templates...
>
> Updating trigger field definitions...
>
>  Updating Routine file...
>
>  Updating KIDS files...
>
>  XU*8.0*375 Installed.
>Apr 21, [EMAIL PROTECTED]:33:59
>
>  Not a VA primary domain
>
>  NO Install Message sent
>
> Install Completed
>
> 
>
> Hope this helps!
>
> Bill Garrett
>
> Lloyd Milligan wrote:
> > Also, the OPEN PARAMETERS are wrong.  The value "WNS" is
> > Cache-specific.  That may not matter.  If it still doesn't work after
> > removing "WNS" I would suggest simulating what ^XPDIL does, to
> > troubleshoot.  In other words, from the GT.M command prompt -
> >
> >
> >  S
> > %ZIS="",%ZIS("HFSNAME")="/h

Re: [Hardhats-members] IHS system???

2005-04-21 Thread James Gray
One of the more interesting is names for newborns.  To enter a patient into 
RPMS they must have a name (.01 field in file 2).  You may need a .01 value 
before the infant has a name.  So newborns end up with names like "Babygirl 
Begay".  Then when the infant is given a name the name is changed in RPMS.
Jim Gray

- Original Message - 
From: "Nancy Anthracite" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, April 21, 2005 5:45 AM
Subject: Re: [Hardhats-members] IHS system???

Tantalized and becoming less confused would describe me, and hoping someone
would be willing to help us document how to implement this for the 
WorldVistA
Wiki.

BTW, it sure is nice to see posts coming from IHS folks.  The experience you
all have had with adapting VistA for the "Real World" certainly can help
those of us struggling with the issues for the first time a whole lot!  You
have dealt with the small to large implementations and a non-veteran
population with characteristics that are more generalizable to the whole
world than what VA FOIA VistA needs to support, such as no SS number, Peds
and OBGYN, so you have a lot of valuable information that many of this 
list's
readers could use, for sure.  You could probably also tell us what worked 
and
what didn't with the solutions you found.

So, besides the SS numbers, what are some of the other big issues you IHS
folks have had to tackle that those of use looking at VistA from the VA have
been blissfully unaware of the need to address?
On Thursday 21 April 2005 02:37 am, Floyd Dennis wrote:
There appears to be some confusion on the nature of the IHS patient file¹s
Health Record Number.  I don¹t know if clarification is possible, but I¹ll
give it a shot. :>
1.   Like many of the initial RPMS modules, the IHS Patient Registration
system is ³piggybacked² onto the VA¹s registration system.  Much of the
patient demographic information resides in File #2 (referenced in RPMS as
the VA PATIENT file).  Additional patient data captured by the RPMS 
patient
registration system is stored in File #901 (the RPMS system¹s PATIENT
file ­ referred to as PATIENT/IHS by VistA), which maintains a DINUM
relationship with File #2.  Examples of such additional data are patient¹s
tribe of membership, level of eligibility for IHS services, etc.

2.  The RPMS deals with IHS-specific mods to VA standard dictionaries in a
similar fashion; DINUM-related RPMS correspondent dictionaries are
established; and the IHS-specific mods dealt with in the corresponding
dictionary.  One example of this is the IHS¹s method of identifying
facilities.  The VA¹s standard dictionary of facilities is maintained in
file #4 (INSTITUTION); IHS has its own standard method of facility ID
coding, however, for which (to the best of my knowledge) there is no
corresponding VA code.  The RPMS solution to this was to create a LOCATION
file #999.06 which (a) has a DINUM relation with file #4 and (b)
contains the IHS standard 6-digit ASUFAC ID code for the facility. 
Simple,
huh?  :)

3.  When looking at using the VA¹s DHCP software, one of the very first
hurdles IHS had to overcome was the problem of patient identification. 
The
VA¹s patient registration system uses SSN as its primary patient
identifier. IHS cannot base its patient identification on SSN, however,
because many of its patients (especially on the larger Southwestern U.S.
reservations) have never applied for nor been issued a Social Security
number.

4.  The IHS solution was/is the health record number (HRN), a number which
uniquely identifies a patient within a given healthcare facility.  There 
is
no relationship between the HRN and the SSN; the two are apples and
oranges. For facility-external references, the HRN can be concatenated 
onto
the end of the facility¹s ASUFAC code.  In IHS, the HRN is limited to 6
digits; YMMV.

5.  The RPMS¹s PATIENT file #901 incorporates multiple field #4101
which contains (a) a LOCATION file pointer reference to each facility at
which a patient has been registered, and (b) the patient¹s HRN at that
facility. This (theoretically) allows coherent management of demographic
information for patients registered at more than one IHS facility.  In
Anna¹s example entries, the HEALTH RECORD FAC field is the pointer
reference to the registering LOCATION file entry, and the HEALTH RECORD 
NO.
field is the patient¹s HRN at that facility.  Anna¹s #3 entry represents a
patient TEST PATIENT,PATIENT who has been registered with chart number
01234 at the SOFTWARE SERVICE healthcare facility.

6.  Unsurprisingly, the earlier standard FileMan lookups did not deal well
with the notion of using several data items from a multiple field as a
unique patient lookup identifier (this *was* back in the days of FileMan
v16.60, after all).  The AUPNLK* routines perform that patient lookup
function, as well as providing increased security on patient lookups.
7.  Since the VistA software does not acknowledge or use the RPMS #901
PATIENT file, this HRN-

Re: [Hardhats-members] IHS system???

2005-04-21 Thread A. Forrey
On Thu, 21 Apr 2005, Kevin Toppenberg wrote:
--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
Tantalized and becoming less confused would describe
me, and hoping someone
would be willing to help us document how to
implement this for the WorldVistA
Wiki.
BTW, it sure is nice to see posts coming from IHS
folks.
This manifestation may just one of many results of work that has become 
fragmented. IT is clear the the VA and IHS versions of VistA must be 
related to the common architectural models for healthcare as examples of 
the implementation of common conventions (health informatics standards) 
that are/will be the basis for interoperable health informations sytems 
architectures. As Richard notes there are models for data and for 
activities (functions) and these must have a unified basis which is 
described and understandable to all. A focal effort on the VistA Office 
subset, as applied to ObGyn/Peds in Nancy's model project will enable most 
healthcare disciplines to understand the Conceptual Content Framework as 
implemented in VistA. Such as documented description will promote the 
professional education of healthcare disciplines in how informatics 
enables the patient-centered care by multiple disciplines identified by 
IOM 2003. The VistA Community can have the basis for a full undertanding 
of the present configuration of VistA as well as an understanding of how 
the VA is planning its evolution to embrace a better modelled basis for 
its architecture based upon the national and international informatics 
standards. Amer Dental Assoc has a new revision of the Conceptual over all 
model for the healthcare information domain; It and ASTM are dveloping 
efforts for harmonization with HL7's RIM which focusse on data flow; these 
al have to be consistent even if different in expression. The VA ( again 
Cam's guidance) has been involved over a number of years. So the vistA 
Community needs to be in communication with both VA and IHS how they have 
pursue conformity with these models at a variety of levels. These efforts 
will enable the broader VistA Community to participate in in the full 
process and represent their configured products in terms of the standards 
the the CCHIT (which Nancy called to our attention). CCHIT "Certification" 
will be a necessity and VistA is perhaps closer to being described by the 
emerging certification criteria than many other products.

Thus, joint VA and IHS effort will be needed for their versions to Be 
"certified" as well as any configured derivatives that may become 
available via various Supplier. Common efforts will be most beneficial to 
the community of VIstA users so it will be of interest how WorldVistA 
promotes these collbaorative efforts.

I'd like to second this.  I am getting the 
feeling > that there are some hard feelings between the IHS and
VA.  I don't know why and don't really want to.  I'm
sure it has much to do with money etc.  BUT as an
outsider those issues don't matter to me.  I also
would love to learn from the IHS guys.
Kevin

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


RE: [Hardhats-members] Canadian Think Smart Initiative question o n LMN.

2005-04-21 Thread Aylesworth Marc A Contr AFRL/IFSE
.NET is an application framework Microsoft is using against JAVA they are
similar in what they can do but for now the only MS supported runtime is
written for MS Win2K and XP. There also is a way to write a program in .NET
and to compile to JAVA byte codes so potentially you could do this and still
be cross-platform ( I never tried this) but this is the two competing
technologies for a platform independent language.

Thanks

Marc Aylesworth

C3I Associates 

AFRL/IFSE

Joint Battlespace Infosphere Team

525 Brooks Rd

Rome, NY 13441-4505

Tel:315.330.2422

Fax:315.330.7009

Email: [EMAIL PROTECTED]


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nancy
Anthracite
Sent: Thursday, April 21, 2005 10:27 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Canadian Think Smart Initiative question on
LMN.

Take a look at the last post on the first page and the second page.  All is 
not lost.  From what I understand of .NET, Open Source  .NET languages could

replace the stuff done in proprietary .NET languages.   The compiled product

should be the same not matter what .NET it is written in.  All is not 
necessarily lost!

http://www.daniweb.com/techtalkforums/thread11131.html
http://www-106.ibm.com/developerworks/library/l-jpython.html

On Thursday 21 April 2005 10:04 am, Ignacio Valdes wrote:
> This just in on LMN: http://www.linuxmednews.com/1114090027 Why has
> Ontario, Canada chosen to link their Smart Systems for Health Agency
> to the proprietary .NET technologies? I recently was perusing the
> website for the Ontario, Canada Smart Health initiative and noticed
> that a lot of the job postings were for .NET technologies. The
> question I would have is why tax payer money is being spent toward
> what will amount to a proprietary solution? Are there sufficiently
> advanced Open Source projects which could be "suggested" to this
> agency for inclusion in their efforts?
>
> I would suspect that VistA would be a possibility. The poster raises
> some interesting questions.  Any Canadians like perhaps JDM, care to
> comment?
>
> -- IV
>
>
> ---
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime
> info, new features, or free trial, at:
> http://www.businessobjects.com/devxi/728
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members

-- 
Nancy Anthracite


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Canadian Think Smart Initiative question on LMN.

2005-04-21 Thread Nancy Anthracite
Take a look at the last post on the first page and the second page.  All is 
not lost.  From what I understand of .NET, Open Source  .NET languages could 
replace the stuff done in proprietary .NET languages.   The compiled product 
should be the same not matter what .NET it is written in.  All is not 
necessarily lost!

http://www.daniweb.com/techtalkforums/thread11131.html
http://www-106.ibm.com/developerworks/library/l-jpython.html

On Thursday 21 April 2005 10:04 am, Ignacio Valdes wrote:
> This just in on LMN: http://www.linuxmednews.com/1114090027 Why has
> Ontario, Canada chosen to link their Smart Systems for Health Agency
> to the proprietary .NET technologies? I recently was perusing the
> website for the Ontario, Canada Smart Health initiative and noticed
> that a lot of the job postings were for .NET technologies. The
> question I would have is why tax payer money is being spent toward
> what will amount to a proprietary solution? Are there sufficiently
> advanced Open Source projects which could be "suggested" to this
> agency for inclusion in their efforts?
>
> I would suspect that VistA would be a possibility. The poster raises
> some interesting questions.  Any Canadians like perhaps JDM, care to
> comment?
>
> -- IV
>
>
> ---
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime
> info, new features, or free trial, at:
> http://www.businessobjects.com/devxi/728
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members

-- 
Nancy Anthracite


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


RE: [Hardhats-members] IHS system???

2005-04-21 Thread Richard . Sowinski
Kevin, I am not aware of any "hard feelings" between IHS and VA.

Your first annonymous poster seemed to want to create some, though. IMO
anyone who wants to post annonymously, to this board, is expecting to create
controversy, but wants to avoid responsibilty for what they say. Kind of
like throwing a bomb into a crowded room, and then running away, smirking.

But basically, as I've explained earlier, VA and IHS are 2 different
organizations that are managed differently, located differently, and serve
much different patient populations. Their IT systems, whose development has
been user-driven for the most part, reflect those differences.

Any work-related interactions I have ever had with IHS folks have been
collaborative, collegial, and aimed at solving problems both organizations
had in common. I recall working very closely with IHS folks, when we both
were first starting to interface commercial systems to our systems, via HL7
messaging. Much good information was exchanged at that time.

Richard J. Sowinski
Chief of Application Development
Roudebush VAMC
317-554- xt 4226 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kevin
Toppenberg
Sent: Thursday, April 21, 2005 9:25 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] IHS system???



--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:

> Tantalized and becoming less confused would describe
> me, and hoping someone 
> would be willing to help us document how to
> implement this for the WorldVistA 
> Wiki.
> 
> BTW, it sure is nice to see posts coming from IHS
> folks.  


I'd like to second this.  I am getting the feeling
that there are some hard feelings between the IHS and
VA.  I don't know why and don't really want to.  I'm
sure it has much to do with money etc.  BUT as an
outsider those issues don't matter to me.  I also
would love to learn from the IHS guys.

Kevin




__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Re: "Transfer Entries" not updating variable pointer fields

2005-04-21 Thread Robert H Dobbins/HOSPOPS/VET/UTIA

Nancy,

>>What sorts of things are we
likely to notice trouble with?
>>
>>DIPT ;SFISC/XAK,TKW-DISPLAY
PRINT OR SORT TEMPLATE ;7/3/96  17:23
 >>;;22.0;VA FileMan;;Mar
30, 1999
>>


Files with fields that are Variable
pointers, won't have the variable pointer fields updated during a "transfer
entries" process.

I can't think of any VP fields in the
core VISTA installation.


Regards,
Bob



---
Robert H. Dobbins
IT Administrator III
Computer Operations
University of Tennessee
College of Veterinary Medicine
2407 River Drive, Rm. A108
Knoxville, TN 37996-4500
(865) 974-5593
[EMAIL PROTECTED]
---

Re: [Hardhats-members] Installing KIDS

2005-04-21 Thread Bill Garrett
I tried to do KIDS install on a (reasonably) fresh install of 'OpenVista 
SemiVivA FOIA Gold 20050212' and found that %ZISF for GT.M didn't 
exist.  This is the routine that supports host files on GT.M for 
Unix/VMS (according to its header).  It should have been put in place by 
ZTMGRSET, so I ran ZTMGRSET again, and %ZISF was never saved.  I fixed 
it manually by locating the ZISFGTM.m routine and copying it to _ZISF.m:

[EMAIL PROTECTED] ~]$ ls r/_ZISF*
ls: r/_ZISF*: No such file or directory
[EMAIL PROTECTED] ~]$ ls r/ZISF*GTM*
r/ZISFGTM.m  r/ZISFGTM.o
[EMAIL PROTECTED] ~]$ cp r/ZISFGTM.m r/_ZISF.m
[EMAIL PROTECTED] ~]$
Now, after removing the WNS parameter from the HFS device entry, I can 
at least test opening the device:

GTM>D ^%ZIS
DEVICE: HOME// HFS  Host File Server
HOST FILE NAME: /tmp/vista-tmp.txt//
GTM>U IO W !,"HELLO"
GTM>D ^%ZISC
GTM>H
[EMAIL PROTECTED] ~]$ cat /tmp/vista-tmp.txt
HELLO
[EMAIL PROTECTED] ~]$
Ok, looking at the install file, the last patch loaded for the kernel is 
XU*8*328 SEQ #304, so I ftp'd the next one in sequence 
(XU-8_SEQ-305_PAT-375.KID), and was able to do the install:

Select OPTION NAME: XPD MAIN   Kernel Installation & Distribution System
Select Kernel Installation & Distribution System Option: INSTallation
Select Installation Option: LOAD a Distribution
Enter a Host File: /home/vista/XU-8_SEQ-305_PAT-375.KID
Released XU*8*375 SEQ #305
Comment: Extracted from mail message
This Distribution contains Transport Globals for the following Package(s):
  XU*8.0*375
Distribution OK!
Want to Continue with Load? YES//
Loading Distribution...
  XU*8.0*375
Use INSTALL NAME: XU*8.0*375 to install this Distribution.
Select Installation Option: verify Checksums in Transport Global
Select INSTALL NAME:XU*8.0*375 Loaded from Distribution 
Loaded from
Distribution  4/21/[EMAIL PROTECTED]:33:41
=> Extracted from mail message  ;Created on

This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of
  Extracted from mail message  ;Created on
  It consisted of the following Install(s):
XU*8.0*375
DEVICE: HOME//   TELNET
PACKAGE: XU*8.0*375 Apr 21, 2005 10:33 am PAGE 1
---
  1 Routine checked, 0 failed.
Select Installation Option: backup a Transport Global
Select INSTALL NAME:XU*8.0*375 Loaded from Distribution 
Loaded from
Distribution  4/21/[EMAIL PROTECTED]:33:41
=> Extracted from mail message  ;Created on

This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of
  Extracted from mail message  ;Created on
  It consisted of the following Install(s):
XU*8.0*375
Subject: Backup of XU*8.0*375 install on Apr 21, 2005
 Replace
Loading Routines for XU*8.0*375
Routine XU8375P is not on the disk..
Send mail to: GARRETT,WILLIAM E//   GARRETT,WILLIAM E
Select basket to send to: IN//  
And Send to:

Select Installation Option: install Package(s)
Select INSTALL NAME:XU*8.0*375 Loaded from Distribution 
Loaded from
Distribution  4/21/[EMAIL PROTECTED]:33:41
=> Extracted from mail message  ;Created on

This Distribution was loaded on Apr 21, [EMAIL PROTECTED]:33:41 with header of
  Extracted from mail message  ;Created on
  It consisted of the following Install(s):
XU*8.0*375
Checking Install for Package XU*8.0*375
Install Questions for XU*8.0*375

Want KIDS to INHIBIT LOGONs during the install? YES// n  NO
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// n  NO
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME//   TELNET
Install Started for XU*8.0*375 :
  Apr 21, [EMAIL PROTECTED]:33:59
Build Distribution Date: Feb 04, 2005
Installing Routines:
  Apr 21, [EMAIL PROTECTED]:33:59
Running Post-Install Routine: ^XU8375P
Recompiling templates...
Updating trigger field definitions...
Updating Routine file...
Updating KIDS files...
XU*8.0*375 Installed.
  Apr 21, [EMAIL PROTECTED]:33:59
Not a VA primary domain
NO Install Message sent
Install Completed

Hope this helps!
Bill Garrett

Lloyd Milligan wrote:
Also, the OPEN PARAMETERS are wrong.  The value "WNS" is 
Cache-specific.  That may not matter.  If it still doesn't work after 
removing "WNS" I would suggest simulating what ^XPDIL does, to 
troubleshoot.  In other words, from the GT.M command prompt -
 
 
 S 
%ZIS="",%ZIS("HFSNAME")="/home/vista/kids/ZMEDIT1p1new.KID",%ZIS("HFSMODE")="R",IOP="HFS"
 D ^%ZIS
 
 
Check POP and if it is '1' trace in ^%ZIS to see where the open fails.
 
Lloyd
 
 

- Original Message -
*From:* Cameron Schlehuber 
*To:* hardhats-members@lists.sourceforge.net

*Sent:* Tuesday, April 19, 2005 12:13 PM
*Subject:* RE: [Hardhats-m

Re: [Hardhats-members] Configurability of fields in FileMan

2005-04-21 Thread Richard G. DAVIS
I need to amend my comment below.  Specifically, as I refer to the
distinction between architecture as structure, and architecture as PROCESS,
I do not mean to include the VHA IT architecture presentation.  On the
contrary, there is an explicit recognition of this distinction in that site
and an acknowledgement that achieving wider understanding of the distinction
is critically important and will require focused activities.

Regards,

Richard.

> From: "Richard G. DAVIS" <[EMAIL PROTECTED]>
> Reply-To: hardhats-members@lists.sourceforge.net
> Date: Thu, 21 Apr 2005 09:07:19 -0500
> To: hardhats-members@lists.sourceforge.net
> Subject: Re: [Hardhats-members] Configurability of fields in FileMan
> 
> Molly,
> 
> The reference you provide is a much more extensive and detailed presentation
> of the subject than my paper.  It is, at its title indicates, a view of
> "Information Architecture".  Rich in details, the presentation here almost
> has "too many notes."   :-)
> 
> My paper approaches the subject under the rubric "Information Management
> Architecture" and takes the view that emphasis should be on architecture as
> a PROCESS, not as a static structure.  The lack of appreciation for this
> distinction often acts as a barrier to reaching consensus on information
> management strategy.  Likewise, the architecture as a process view enhances
> the development of a properly balanced system of appropriately centralized
> responsibilities, and an essential flow of decentralized responsibilities.
> 
> Regards,
> 
> Richard.
> 
>> From: Molly Cheah <[EMAIL PROTECTED]>
>> Reply-To: hardhats-members@lists.sourceforge.net
>> Date: Thu, 21 Apr 2005 14:36:45 +0800
>> To: hardhats-members@lists.sourceforge.net
>> Subject: Re: [Hardhats-members] Configurability of fields in FileMan
>> 
>> Are the documents you referred to at this web-site? The documents were
>> last revised in 2000, but some of the frameworks were marked "as is" and
>> some "to be"  With current date 2005, its hard to tell if those marked
>> "to be" had been implemented.
>> Health Information Architecture
>> http://www.va.gov/vha-ita/ita-p.html
>> 
>>> The Architecture provides a technical framework to promote one
>>> technology vision across the VHA so that corporate systems and systems
>>> across VISNs are interoperable. The framework is designed to be
>>> flexible, and is updated as new needs are identified.
>> 
>> Molly
>> 
>> Richard G. DAVIS wrote:
>> 
>>> I have given this issue a fairly extensive treatment in an IT architecture
>>> document I prepared some years ago for the DVA.  That paper was reviewed by
>>> VistA IT architects during its development.  Some on this list may have
>>> copies on hand.  The paper is a serious read, and not to be considered a
>>> 'one-pass' discussion.  The document is imperfect, and could benefit greatly
>>> from a second, major edition.  Even so, it does answer your question and
>>> expands substantially on what I have been saying here lately.  If you really
>>> want to invest the time and energy, perhaps that document can be located for
>>> you.
>>> 
>>> Regards,
>>> 
>>> Richard.
>>> 
>>>  
>>> 
 From: Jim Self <[EMAIL PROTECTED]>
 Reply-To: hardhats-members@lists.sourceforge.net
 Date: Wed, 20 Apr 2005 16:29:11 -0700 (PDT)
 To: 
 Subject: Re: [Hardhats-members] Configurability of fields in FileMan
 
 Richard Davis wrote:

 
> Today, the core database within VistA does not contain a generalized
> "business-rule" engine as a centralized, high level, tabled driven module
> that controls all data storage and retrieval.  Classical DHCP applications
> and the VistA modules of today are obliged to embed their business rules
> in
> M(UMPS) routines where they are extremely difficult to manage.
> 
> No amount of "open" design in DHCP/VistA can overcome this shortcoming of
> the missing business rule engine.
>  
> 
 Please give more description and some examples of what you think is missing
 and how it
 might be added.
 
 ---
 Jim Self
 Systems Architect, Lead Developer
 VMTH Computer Services, UC Davis
 (http://www.vmth.ucdavis.edu/us/jaself)
 
 
 ---
 This SF.Net email is sponsored by: New Crystal Reports XI.
 Version 11 adds new functionality designed to reduce time involved in
 creating, integrating, and deploying reporting solutions. Free runtime
 info,
 new features, or free trial, at: http://www.businessobjects.com/devxi/728
 ___
 Hardhats-members mailing list
 Hardhats-members@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/hardhats-members

 
>>> 
>>> 
>>> 
>>> ---
>>> This SF.Net email is sponsored by: New Crystal Reports XI.
>>>

Re: [Hardhats-members] IHS system???

2005-04-21 Thread Kevin Toppenberg

--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:

> Tantalized and becoming less confused would describe
> me, and hoping someone 
> would be willing to help us document how to
> implement this for the WorldVistA 
> Wiki.
> 
> BTW, it sure is nice to see posts coming from IHS
> folks.  


I'd like to second this.  I am getting the feeling
that there are some hard feelings between the IHS and
VA.  I don't know why and don't really want to.  I'm
sure it has much to do with money etc.  BUT as an
outsider those issues don't matter to me.  I also
would love to learn from the IHS guys.

Kevin




__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] After a nice nap... I have a proposal for documentation....

2005-04-21 Thread Doctor Bones
I started with a fresh install last night... then realized that I didn't
like the format of the document... so I am starting again today.

Once I finish through to the end of Nancy and Marks Documentation.
I will post it on the wiki... then...
I would like to distribute accounts so that others can add on to what I
have started.

Let me nail this down and see how it looks I think it should be up by
this weekend.

Mano

On Thu, 2005-04-21 at 07:07 -0700, Kevin Toppenberg wrote:
> --- Doctor Bones <[EMAIL PROTECTED]> wrote:
> 
> > Of course Kevin beat me to it :P
> 
> I haven't beat you to it.  I just documented some of
> what I did.  Now if you document what you are doing
> (which is different than mine), we can perhaps combine
> them and be even better off.
> 
> > 
> > But here is my proposal anyway
> > To create an open document (via wiki of course) of a
> > single full rollout
> > of a virtual hospital.
> > 
> > In my overweening hubris (I believe hubris is
> > already overweening so
> > just more so) I have started said document (although
> > I haven't put it up
> > yet).
> > 
> > What I wanted to do was define the hospital in a
> > virtual way and make an
> > installation.
> > 
> > I have been documenting every step as I go... not
> > particularly well but
> > at least attempting to put something together.
> > 
> > The idea is that I will put the document on the wiki
> > and
> > open up my machine to the net as well... allowing
> > people to set up
> > whatever portion of vista they would like to...
> > documenting it along the
> > way. Um... by people... I mean hard hatters.
> > 
> > 
> > What do you all think?
> 
> 
> I like it!
> 
> Kevin
> 
> 
> > 
> > Manolis
> > 
> > On Wed, 2005-04-20 at 13:47 -0700, Kevin Toppenberg
> > wrote:
> > > Well, I have spent the better part of all day
> > today
> > > creating a "run book" for our office.  I tried to
> > go
> > > through the basics of what they would need to get
> > the
> > > server up etc.
> > > 
> > > I have put it on my old website because I don't
> > know
> > > how I would get all the links to work right if I
> > put
> > > it on the Wikki.
> > > 
> > > Here is the link
> > > 
> > > http://www.geocities.com/kdtop3/VistAHowTo.htm
> > > 
> > > Kevin
> > > 
> > > 
> > > __
> > > Do You Yahoo!?
> > > Tired of spam?  Yahoo! Mail has the best spam
> > protection around 
> > > http://mail.yahoo.com 
> > > 
> > > 
> > >
> >
> ---
> > > This SF.Net email is sponsored by: New Crystal
> > Reports XI.
> > > Version 11 adds new functionality designed to
> > reduce time involved in
> > > creating, integrating, and deploying reporting
> > solutions. Free runtime info,
> > > new features, or free trial, at:
> > http://www.businessobjects.com/devxi/728
> > > ___
> > > Hardhats-members mailing list
> > > Hardhats-members@lists.sourceforge.net
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> > > 
> > 
> > 
> > 
> >
> ---
> > This SF.Net email is sponsored by: New Crystal
> > Reports XI.
> > Version 11 adds new functionality designed to reduce
> > time involved in
> > creating, integrating, and deploying reporting
> > solutions. Free runtime info,
> > new features, or free trial, at:
> > http://www.businessobjects.com/devxi/728
> > ___
> > Hardhats-members mailing list
> > Hardhats-members@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> > 
> 
> 
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> ---
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime info,
> new features, or free trial, at: http://www.businessobjects.com/devxi/728
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> 



---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] IHS system???

2005-04-21 Thread Kevin Toppenberg
Let me see if I understand.

1. The HRN is a good system for the IHS
2. Althought file 901 is distributed with the FOIA
vista, it is not fully integrated, i.e. the lookup
routines are not there.
3. It shouldn't be too hard to achieve this
integration.

If this is true, and if such a HRN is needed by so
many non-VA sites, would it be worth a little effort
to have our next WorldVistA version support this?  

Perhaps VistA Office is going to solve this problem
for us, but I don't want to have unrealistic
expectations as to what they can achieve in a limited
amount of time.

Kevin

--- Floyd Dennis <[EMAIL PROTECTED]> wrote:

> There appears to be some confusion on the nature of
> the IHS patient file¹s
> Health Record Number.  I don¹t know if clarification
> is possible, but I¹ll
> give it a shot. :>
> 
> 1.   Like many of the initial RPMS modules, the IHS
> Patient Registration
> system is ³piggybacked² onto the VA¹s registration
> system.  Much of the
> patient demographic information resides in File #2
> (referenced in RPMS as
> the VA PATIENT file).  Additional patient data
> captured by the RPMS patient
> registration system is stored in File #901 (the
> RPMS system¹s PATIENT
> file ­ referred to as PATIENT/IHS by VistA), which
> maintains a DINUM
> relationship with File #2.  Examples of such
> additional data are patient¹s
> tribe of membership, level of eligibility for IHS
> services, etc.
> 
> 2.  The RPMS deals with IHS-specific mods to VA
> standard dictionaries in a
> similar fashion; DINUM-related RPMS correspondent
> dictionaries are
> established; and the IHS-specific mods dealt with in
> the corresponding
> dictionary.  One example of this is the IHS¹s method
> of identifying
> facilities.  The VA¹s standard dictionary of
> facilities is maintained in
> file #4 (INSTITUTION); IHS has its own standard
> method of facility ID
> coding, however, for which (to the best of my
> knowledge) there is no
> corresponding VA code.  The RPMS solution to this
> was to create a LOCATION
> file #999.06 which (a) has a DINUM relation with
> file #4 and (b)
> contains the IHS standard 6-digit ASUFAC ID code for
> the facility.  Simple,
> huh?  :)
> 
> 3.  When looking at using the VA¹s DHCP software,
> one of the very first
> hurdles IHS had to overcome was the problem of
> patient identification.  The
> VA¹s patient registration system uses SSN as its
> primary patient identifier.
> IHS cannot base its patient identification on SSN,
> however, because many of
> its patients (especially on the larger Southwestern
> U.S. reservations) have
> never applied for nor been issued a Social Security
> number.
> 
> 4.  The IHS solution was/is the health record number
> (HRN), a number which
> uniquely identifies a patient within a given
> healthcare facility.  There is
> no relationship between the HRN and the SSN; the two
> are apples and oranges.
> For facility-external references, the HRN can be
> concatenated onto the end
> of the facility¹s ASUFAC code.  In IHS, the HRN is
> limited to 6 digits;
> YMMV.
> 
> 5.  The RPMS¹s PATIENT file #901 incorporates
> multiple field #4101 which
> contains (a) a LOCATION file pointer reference to
> each facility at which a
> patient has been registered, and (b) the patient¹s
> HRN at that facility.
> This (theoretically) allows coherent management of
> demographic information
> for patients registered at more than one IHS
> facility.  In Anna¹s example
> entries, the HEALTH RECORD FAC field is the pointer
> reference to the
> registering LOCATION file entry, and the HEALTH
> RECORD NO. field is the
> patient¹s HRN at that facility.  Anna¹s #3 entry
> represents a patient TEST
> PATIENT,PATIENT who has been registered with chart
> number 01234 at the
> SOFTWARE SERVICE healthcare facility.
> 
> 6.  Unsurprisingly, the earlier standard FileMan
> lookups did not deal well
> with the notion of using several data items from a
> multiple field as a
> unique patient lookup identifier (this *was* back in
> the days of FileMan
> v16.60, after all).  The AUPNLK* routines perform
> that patient lookup
> function, as well as providing increased security on
> patient lookups.
> 
> 7.  Since the VistA software does not acknowledge or
> use the RPMS #901
> PATIENT file, this HRN-identifier lookup would not
> be available on the VistA
> side of the house without some rewriting of a given
> package¹s patient lookup
> modules.  This is not an insurmountable problem; as
> a moment¹s reflection
> will reveal, IHS has performed this rewrite on every
> VistA package that has
> been adapted for use in the RPMS environment.
> 
> 8.  Along the same lines as #7 ­ since the AUPNLK*
> patient lookup routines
> are IHS-developed software, they would be unlikely
> to pop up in a VA
> software distribution.
> 
> 
> NOW ­ is everybody sufficiently confused?  :)
> 
> 
> ---
> Doubt is uncomfortable; Certainty is ridiculous.
> 
> - Voltaire

Re: [Hardhats-members] After a nice nap... I have a proposal for documentation....

2005-04-21 Thread Kevin Toppenberg

--- Doctor Bones <[EMAIL PROTECTED]> wrote:

> Of course Kevin beat me to it :P

I haven't beat you to it.  I just documented some of
what I did.  Now if you document what you are doing
(which is different than mine), we can perhaps combine
them and be even better off.

> 
> But here is my proposal anyway
> To create an open document (via wiki of course) of a
> single full rollout
> of a virtual hospital.
> 
> In my overweening hubris (I believe hubris is
> already overweening so
> just more so) I have started said document (although
> I haven't put it up
> yet).
> 
> What I wanted to do was define the hospital in a
> virtual way and make an
> installation.
> 
> I have been documenting every step as I go... not
> particularly well but
> at least attempting to put something together.
> 
> The idea is that I will put the document on the wiki
> and
> open up my machine to the net as well... allowing
> people to set up
> whatever portion of vista they would like to...
> documenting it along the
> way. Um... by people... I mean hard hatters.
> 
> 
> What do you all think?


I like it!

Kevin


> 
> Manolis
> 
> On Wed, 2005-04-20 at 13:47 -0700, Kevin Toppenberg
> wrote:
> > Well, I have spent the better part of all day
> today
> > creating a "run book" for our office.  I tried to
> go
> > through the basics of what they would need to get
> the
> > server up etc.
> > 
> > I have put it on my old website because I don't
> know
> > how I would get all the links to work right if I
> put
> > it on the Wikki.
> > 
> > Here is the link
> > 
> > http://www.geocities.com/kdtop3/VistAHowTo.htm
> > 
> > Kevin
> > 
> > 
> > __
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> > http://mail.yahoo.com 
> > 
> > 
> >
>
---
> > This SF.Net email is sponsored by: New Crystal
> Reports XI.
> > Version 11 adds new functionality designed to
> reduce time involved in
> > creating, integrating, and deploying reporting
> solutions. Free runtime info,
> > new features, or free trial, at:
> http://www.businessobjects.com/devxi/728
> > ___
> > Hardhats-members mailing list
> > Hardhats-members@lists.sourceforge.net
> >
>
https://lists.sourceforge.net/lists/listinfo/hardhats-members
> > 
> 
> 
> 
>
---
> This SF.Net email is sponsored by: New Crystal
> Reports XI.
> Version 11 adds new functionality designed to reduce
> time involved in
> creating, integrating, and deploying reporting
> solutions. Free runtime info,
> new features, or free trial, at:
> http://www.businessobjects.com/devxi/728
> ___
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/hardhats-members
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


Re: [Hardhats-members] Configurability of fields in FileMan

2005-04-21 Thread Richard G. DAVIS
Molly,

The reference you provide is a much more extensive and detailed presentation
of the subject than my paper.  It is, at its title indicates, a view of
"Information Architecture".  Rich in details, the presentation here almost
has "too many notes."   :-)

My paper approaches the subject under the rubric "Information Management
Architecture" and takes the view that emphasis should be on architecture as
a PROCESS, not as a static structure.  The lack of appreciation for this
distinction often acts as a barrier to reaching consensus on information
management strategy.  Likewise, the architecture as a process view enhances
the development of a properly balanced system of appropriately centralized
responsibilities, and an essential flow of decentralized responsibilities.

Regards,

Richard.

> From: Molly Cheah <[EMAIL PROTECTED]>
> Reply-To: hardhats-members@lists.sourceforge.net
> Date: Thu, 21 Apr 2005 14:36:45 +0800
> To: hardhats-members@lists.sourceforge.net
> Subject: Re: [Hardhats-members] Configurability of fields in FileMan
> 
> Are the documents you referred to at this web-site? The documents were
> last revised in 2000, but some of the frameworks were marked "as is" and
> some "to be"  With current date 2005, its hard to tell if those marked
> "to be" had been implemented.
> Health Information Architecture
> http://www.va.gov/vha-ita/ita-p.html
> 
>> The Architecture provides a technical framework to promote one
>> technology vision across the VHA so that corporate systems and systems
>> across VISNs are interoperable. The framework is designed to be
>> flexible, and is updated as new needs are identified.
> 
> Molly
> 
> Richard G. DAVIS wrote:
> 
>> I have given this issue a fairly extensive treatment in an IT architecture
>> document I prepared some years ago for the DVA.  That paper was reviewed by
>> VistA IT architects during its development.  Some on this list may have
>> copies on hand.  The paper is a serious read, and not to be considered a
>> 'one-pass' discussion.  The document is imperfect, and could benefit greatly
>> from a second, major edition.  Even so, it does answer your question and
>> expands substantially on what I have been saying here lately.  If you really
>> want to invest the time and energy, perhaps that document can be located for
>> you.
>> 
>> Regards,
>> 
>> Richard.
>> 
>>  
>> 
>>> From: Jim Self <[EMAIL PROTECTED]>
>>> Reply-To: hardhats-members@lists.sourceforge.net
>>> Date: Wed, 20 Apr 2005 16:29:11 -0700 (PDT)
>>> To: 
>>> Subject: Re: [Hardhats-members] Configurability of fields in FileMan
>>> 
>>> Richard Davis wrote:
>>>
>>> 
 Today, the core database within VistA does not contain a generalized
 "business-rule" engine as a centralized, high level, tabled driven module
 that controls all data storage and retrieval.  Classical DHCP applications
 and the VistA modules of today are obliged to embed their business rules in
 M(UMPS) routines where they are extremely difficult to manage.
 
 No amount of "open" design in DHCP/VistA can overcome this shortcoming of
 the missing business rule engine.
  
 
>>> Please give more description and some examples of what you think is missing
>>> and how it
>>> might be added.
>>> 
>>> ---
>>> Jim Self
>>> Systems Architect, Lead Developer
>>> VMTH Computer Services, UC Davis
>>> (http://www.vmth.ucdavis.edu/us/jaself)
>>> 
>>> 
>>> ---
>>> This SF.Net email is sponsored by: New Crystal Reports XI.
>>> Version 11 adds new functionality designed to reduce time involved in
>>> creating, integrating, and deploying reporting solutions. Free runtime info,
>>> new features, or free trial, at: http://www.businessobjects.com/devxi/728
>>> ___
>>> Hardhats-members mailing list
>>> Hardhats-members@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>>>
>>> 
>> 
>> 
>> 
>> ---
>> This SF.Net email is sponsored by: New Crystal Reports XI.
>> Version 11 adds new functionality designed to reduce time involved in
>> creating, integrating, and deploying reporting solutions. Free runtime info,
>> new features, or free trial, at: http://www.businessobjects.com/devxi/728
>> ___
>> Hardhats-members mailing list
>> Hardhats-members@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>> 
>> 
>>  
>> 
> 
> 
> 
> ---
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime info,
> new features, or free trial, at: http://www.businessobjects.com/devxi/728
> ___

[Hardhats-members] Canadian Think Smart Initiative question on LMN.

2005-04-21 Thread Ignacio Valdes
This just in on LMN: http://www.linuxmednews.com/1114090027 Why has 
Ontario, Canada chosen to link their Smart Systems for Health Agency 
to the proprietary .NET technologies? I recently was perusing the 
website for the Ontario, Canada Smart Health initiative and noticed 
that a lot of the job postings were for .NET technologies. The 
question I would have is why tax payer money is being spent toward 
what will amount to a proprietary solution? Are there sufficiently 
advanced Open Source projects which could be "suggested" to this 
agency for inclusion in their efforts?

I would suspect that VistA would be a possibility. The poster raises 
some interesting questions.  Any Canadians like perhaps JDM, care to 
comment?

-- IV
---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


RE: [Hardhats-members] Configurability of fields in FileMan

2005-04-21 Thread Aylesworth Marc A Contr AFRL/IFSE
A three layered approach that separates the data, the Model, and the view.
The data is the database the model contains any business logic and the view
displays it all. The three parts are designed so that any on part can be
totally replaced without the other two knowing that the one was changed. It
came about in a language called smalltalk and is being revived by the Java
Swing componenets.

Thanks

Marc Aylesworth

C3I Associates 

AFRL/IFSE

Joint Battlespace Infosphere Team

525 Brooks Rd

Rome, NY 13441-4505

Tel:315.330.2422

Fax:315.330.7009

Email: [EMAIL PROTECTED]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cameron
Schlehuber
Sent: Wednesday, April 20, 2005 7:47 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] Configurability of fields in FileMan

While looking forward to Richard's response, let me chime in here with some
primitive examples of efforts along the lines of "business rules & engine"
in VistA and observations on where things might end up (those who know me
well know that I'm a perpetual optimist!)

One example is the ORDER DIALOG file 101.41.  It was designed with the
intent of being able to script very complex dialogs for placing orders.  The
rules of prompt/user response/prompt carries the templates of VA FileMan to
a higher level of abstraction and functionality.  The new capabilities in
CLINICAL REMINDERS v 2.0 are likewise based on rules that can be built and
exchanged between users without having to write M routines.  These are
special cases that have been justified due to user demands.  What is missing
is the next level ... a generalized rules engine that could support ANY
service or application.

The down-side to date is the holding back of the creation of a good (not
perfect, good!) rules engine.  In large part due to the belief that rules
engines are "too difficult to build" or "don't work well in the general
case".  A few fortunate circumstances are coming together now though.  One
is that the VA's Enterprise Architecture appears (to me at least) to be
poised to aggressively explore true rules engines and actually get down to
doing some real implementations.  Another circumstance is a prototype effort
to mine a couple of VistA applications for their rules and build a database
of them (using some new OMG draft specifications for such representations
and models) such that the rules can be modified at the business
representation layer and forward engineered into running applications.  I
believe these are sufficiently low cost efforts for now that they can afford
to "make mistakes" and risk reaching for something potentially very
productive.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Self
Sent: Wednesday, April 20, 2005 4:29 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Configurability of fields in FileMan

Richard Davis wrote:
>Today, the core database within VistA does not contain a generalized
>"business-rule" engine as a centralized, high level, tabled driven module
>that controls all data storage and retrieval.  Classical DHCP applications
>and the VistA modules of today are obliged to embed their business rules in
>M(UMPS) routines where they are extremely difficult to manage.
>
>No amount of "open" design in DHCP/VistA can overcome this shortcoming of
>the missing business rule engine.

Please give more description and some examples of what you think is missing
and how it
might be added.

---
Jim Self
Systems Architect, Lead Developer
VMTH Computer Services, UC Davis
(http://www.vmth.ucdavis.edu/us/jaself)


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members



---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,

RE: [Hardhats-members] IHS system???

2005-04-21 Thread Aylesworth Marc A Contr AFRL/IFSE
Title: Re: [Hardhats-members] IHS system???








Some questions.

 

1)  
can one patch the VA
Vista to use the HIS files or do they have to start with fileman and install HIS
packages to get RPMS

 

  2) is there a way to install
multiple packages or is there a base install to load RPMS onto a system ,either
G.T.M or cache.

 

 

 



Thanks,

Marc Aylesworth

 

C3I
Associates AFRL/IFSE Joint Battlespace Infosphere Team

 

525 Brooks Rd

Rome, NY
13441-4505

 

Tel:315.330.2422

Fax:315.330.7009

Email:Marc[EMAIL PROTECTED]



 









From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Floyd Dennis
Sent: Thursday, April 21, 2005
1:38 AM
To:
hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members]
IHS system???



 

There appears to be some confusion
on the nature of the IHS patient file's Health Record Number.  I
don't know if clarification is possible, but I'll give it a shot.
:>

1.   Like many of the initial RPMS modules, the IHS Patient
Registration system is "piggybacked" onto the VA's
registration system.  Much of the patient demographic information resides
in File #2 (referenced in RPMS as the VA PATIENT file).  Additional
patient data captured by the RPMS patient registration system is stored in File
#901 (the RPMS system's PATIENT file - referred to as
PATIENT/IHS by VistA), which maintains a DINUM relationship with File #2.
 Examples of such additional data are patient's tribe of membership,
level of eligibility for IHS services, etc.

2.  The RPMS deals with IHS-specific mods to VA standard dictionaries in a
similar fashion; DINUM-related RPMS correspondent dictionaries are established;
and the IHS-specific mods dealt with in the corresponding dictionary.  One
example of this is the IHS's method of identifying facilities.  The
VA's standard dictionary of facilities is maintained in file #4
(INSTITUTION); IHS has its own standard method of facility ID coding, however,
for which (to the best of my knowledge) there is no corresponding VA code.  The
RPMS solution to this was to create a LOCATION file #999.06 which (a) has a
DINUM relation with file #4 and (b) contains the IHS standard 6-digit ASUFAC ID
code for the facility.  Simple, huh?  :)

3.  When looking at using the VA's DHCP software, one of the very
first hurdles IHS had to overcome was the problem of patient identification.
 The VA's patient registration system uses SSN as its primary
patient identifier.  IHS cannot base its patient identification on SSN,
however, because many of its patients (especially on the larger Southwestern
U.S. reservations) have never applied for nor been issued a Social Security
number.

4.  The IHS solution was/is the health record number (HRN), a number which
uniquely identifies a patient within a given healthcare facility.  There
is no relationship between the HRN and the SSN; the two are apples and oranges.
 For facility-external references, the HRN can be concatenated onto the
end of the facility's ASUFAC code.  In IHS, the HRN is limited to 6
digits; YMMV.

5.  The RPMS's PATIENT file #901 incorporates multiple field
#4101 which contains (a) a LOCATION file pointer reference to each facility at
which a patient has been registered, and (b) the patient's HRN at that
facility.  This (theoretically) allows coherent management of demographic
information for patients registered at more than one IHS facility.  In
Anna's example entries, the HEALTH RECORD FAC field is the pointer
reference to the registering LOCATION file entry, and the HEALTH RECORD NO.
field is the patient's HRN at that facility.  Anna's #3 entry
represents a patient TEST PATIENT,PATIENT who has been registered with chart
number 01234 at the SOFTWARE SERVICE healthcare facility.

6.  Unsurprisingly, the earlier standard FileMan lookups did not deal well
with the notion of using several data items from a multiple field as a unique
patient lookup identifier (this *was* back in the days of FileMan v16.60, after
all).  The AUPNLK* routines perform that patient lookup function, as well
as providing increased security on patient lookups.

7.  Since the VistA software does not acknowledge or use the RPMS #901
PATIENT file, this HRN-identifier lookup would not be available on the VistA
side of the house without some rewriting of a given package's patient lookup
modules.  This is not an insurmountable problem; as a moment's
reflection will reveal, IHS has performed this rewrite on every VistA package
that has been adapted for use in the RPMS environment.

8.  Along the same lines as #7 - since the AUPNLK* patient lookup
routines are IHS-developed software, they would be unlikely to pop up in a VA
software distribution.


NOW - is everybody sufficiently confused?  :)


--- 
Doubt is uncomfortable; Certainty is ridiculous.

- Voltaire

Floyd Dennis
[EMAIL PROTECTED]




On 4/20/05 10:59 AM, "James Gray" <[EMAIL PROTECTED]> wrote:

I believe the i

Re: [Hardhats-members] IHS system???

2005-04-21 Thread Nancy Anthracite
Tantalized and becoming less confused would describe me, and hoping someone 
would be willing to help us document how to implement this for the WorldVistA 
Wiki.

BTW, it sure is nice to see posts coming from IHS folks.  The experience you 
all have had with adapting VistA for the "Real World" certainly can help 
those of us struggling with the issues for the first time a whole lot!  You 
have dealt with the small to large implementations and a non-veteran 
population with characteristics that are more generalizable to the whole 
world than what VA FOIA VistA needs to support, such as no SS number, Peds 
and OBGYN, so you have a lot of valuable information that many of this list's 
readers could use, for sure.  You could probably also tell us what worked and 
what didn't with the solutions you found.

So, besides the SS numbers, what are some of the other big issues you IHS 
folks have had to tackle that those of use looking at VistA from the VA have 
been blissfully unaware of the need to address? 

On Thursday 21 April 2005 02:37 am, Floyd Dennis wrote:
> There appears to be some confusion on the nature of the IHS patient file¹s
> Health Record Number.  I don¹t know if clarification is possible, but I¹ll
> give it a shot. :>
>
> 1.   Like many of the initial RPMS modules, the IHS Patient Registration
> system is ³piggybacked² onto the VA¹s registration system.  Much of the
> patient demographic information resides in File #2 (referenced in RPMS as
> the VA PATIENT file).  Additional patient data captured by the RPMS patient
> registration system is stored in File #901 (the RPMS system¹s PATIENT
> file ­ referred to as PATIENT/IHS by VistA), which maintains a DINUM
> relationship with File #2.  Examples of such additional data are patient¹s
> tribe of membership, level of eligibility for IHS services, etc.
>
> 2.  The RPMS deals with IHS-specific mods to VA standard dictionaries in a
> similar fashion; DINUM-related RPMS correspondent dictionaries are
> established; and the IHS-specific mods dealt with in the corresponding
> dictionary.  One example of this is the IHS¹s method of identifying
> facilities.  The VA¹s standard dictionary of facilities is maintained in
> file #4 (INSTITUTION); IHS has its own standard method of facility ID
> coding, however, for which (to the best of my knowledge) there is no
> corresponding VA code.  The RPMS solution to this was to create a LOCATION
> file #999.06 which (a) has a DINUM relation with file #4 and (b)
> contains the IHS standard 6-digit ASUFAC ID code for the facility.  Simple,
> huh?  :)
>
> 3.  When looking at using the VA¹s DHCP software, one of the very first
> hurdles IHS had to overcome was the problem of patient identification.  The
> VA¹s patient registration system uses SSN as its primary patient
> identifier. IHS cannot base its patient identification on SSN, however,
> because many of its patients (especially on the larger Southwestern U.S.
> reservations) have never applied for nor been issued a Social Security
> number.
>
> 4.  The IHS solution was/is the health record number (HRN), a number which
> uniquely identifies a patient within a given healthcare facility.  There is
> no relationship between the HRN and the SSN; the two are apples and
> oranges. For facility-external references, the HRN can be concatenated onto
> the end of the facility¹s ASUFAC code.  In IHS, the HRN is limited to 6
> digits; YMMV.
>
> 5.  The RPMS¹s PATIENT file #901 incorporates multiple field #4101
> which contains (a) a LOCATION file pointer reference to each facility at
> which a patient has been registered, and (b) the patient¹s HRN at that
> facility. This (theoretically) allows coherent management of demographic
> information for patients registered at more than one IHS facility.  In
> Anna¹s example entries, the HEALTH RECORD FAC field is the pointer
> reference to the registering LOCATION file entry, and the HEALTH RECORD NO.
> field is the patient¹s HRN at that facility.  Anna¹s #3 entry represents a
> patient TEST PATIENT,PATIENT who has been registered with chart number
> 01234 at the SOFTWARE SERVICE healthcare facility.
>
> 6.  Unsurprisingly, the earlier standard FileMan lookups did not deal well
> with the notion of using several data items from a multiple field as a
> unique patient lookup identifier (this *was* back in the days of FileMan
> v16.60, after all).  The AUPNLK* routines perform that patient lookup
> function, as well as providing increased security on patient lookups.
>
> 7.  Since the VistA software does not acknowledge or use the RPMS #901
> PATIENT file, this HRN-identifier lookup would not be available on the
> VistA side of the house without some rewriting of a given package¹s patient
> lookup modules.  This is not an insurmountable problem; as a moment¹s
> reflection will reveal, IHS has performed this rewrite on every VistA
> package that has been adapted for use in the RPMS environment.
>
> 8.  Along the same line