of hard to diagnose from
>here.
>
> tjh
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Nancy
>Anthracite
>Sent: Tuesday, April 18, 2006 12:58 PM
>To: hardhats-members@lists.sourceforge.net
>Subject: Re: [Hardhats-mem
> That's the old-style error trap, and the variability Chris mentions
> here is the reason ^%ZOSF("TRAP") is (was) used. The old style error
> trap is no longer recommended. Instead, you should NEW $ESTACK and
> set
> $ETRAP to the handler. Errors are generated by setting $ECODE, and an
> error ca
--- [EMAIL PROTECTED] wrote:
> The error trap is implemented in various ways by different
> implementors.
> It is a system variable, usually $TR or $ER, or check the
> ^%ZOSF("TRAP")
> global node. The error trap routine for VistA is XTER, try D ^XTER.
>
That's the old-style error trap, and
The error trap is implemented in various ways by different implementors.
It is a system variable, usually $TR or $ER, or check the ^%ZOSF("TRAP")
global node. The error trap routine for VistA is XTER, try D ^XTER.
> There did not seem to be and EC or an XTER. When I tried again, it didn't
> hap
Behalf Of Nancy
Anthracite
Sent: Tuesday, April 18, 2006 12:58 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Billing Menu
Any guesses why it has an error the first time and not the second?
On Tuesday 18 April 2006 09:58, Holloway, Thomas (EDS) wrote:
I think Bhas
--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
> Any guesses why it has an error the first time and not the second?
>
> On Tuesday 18 April 2006 09:58, Holloway, Thomas (EDS) wrote:
> I think Bhaskar is correct. There is a problem at PRCAUDT+131. The
> parameterized subroutine SETERR takes one
ttal's problem but it
> does appear to be incorrect code.
>
> Thom H.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Bhaskar, KS
> Sent: Tuesday, April 18, 2006 9:41 AM
> To: hardhats-members@lists.sourceforge.net
> Subjec
There did not seem to be and EC or an XTER. When I tried again, it didn't
happen as you saw, so I couldn't check a second time. When EC gets set, do
you always get that strange notation at the prompt? Does EC go away if you
don't actively clear it?
On Tuesday 18 April 2006 11:52, [EMAIL PROT
riginal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Bhaskar, KS
Sent: Tuesday, April 18, 2006 9:41 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Billing Menu
Vittal --
The GT.M Messages and Recovery Procedures manuals
(www.sanchez-g
Please check the error trap and see where the call actually is. This
appears as though there is a mis-match of calling arguments with the
actual routine. I would suspect a DO or application supplied Function
call as the culpret.
> Try the option a second time. I have gotten errors one or more
1 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Billing Menu
Vittal --
The GT.M Messages and Recovery Procedures manuals
(www.sanchez-gtm.com/user_documentation/V44MsgRecProc/index.htm) says of
ACTLSTTOOLONG:
--
ACTLSTTOOLONG, More actu
Try the option a second time. I have gotten errors one or more times, and the
second error may not be the same as the first, only to have it work on
repeat. I am wondering if the first time through it has to recompile the m
code with the new version of GTM and then it runs or something. It s
Vittal --
The GT.M Messages and Recovery Procedures manuals
(www.sanchez-gtm.com/user_documentation/V44MsgRecProc/index.htm) says of
ACTLSTTOOLONG:
--
ACTLSTTOOLONG, More actual parameters than formal parameters:
Compile/Run Time Error: This indicates that the label
ed with the visit episode (by time or
billing period).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thurman
Pedigo
Sent: Tuesday, February 07, 2006 12:00 PM
To: hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members] Billing Module for Vis
[mailto:hardhats-
> [EMAIL PROTECTED] On Behalf Of Greg Woodhouse
> Sent: Monday, February 06, 2006 2:41 PM
> To: hardhats-members@lists.sourceforge.net
> Subject: RE: [Hardhats-members] Billing Module for VistA
>
>
> --- Thurman Pedigo <[EMAIL PROTECTED]> wrote:
&g
age-
> From: [EMAIL PROTECTED] [mailto:hardhats-
> [EMAIL PROTECTED] On Behalf Of Greg Woodhouse
> Sent: Monday, February 06, 2006 2:41 PM
> To: hardhats-members@lists.sourceforge.net
> Subject: RE: [Hardhats-members] Billing Module for VistA
>
>
> --- Thurman Pedigo <[EMAIL
>>-Original Message-
>>From: [EMAIL PROTECTED] [mailto:hardhats-
>>[EMAIL PROTECTED] On Behalf Of Mike Schrom
>>Sent: Monday, February 06, 2006 11:18 AM
>>To: hardhats-members@lists.sourceforge.net
>>Subject: Re: [Hardhats-members] Billing Module for Vist
to look at it "as is."
>
> thurman
>
>>-Original Message-
>>From: [EMAIL PROTECTED] [mailto:hardhats-
>>[EMAIL PROTECTED] On Behalf Of Mike Schrom
>>Sent: Monday, February 06, 2006 11:18 AM
>>To: hardhats-members@lists.sourceforge.net
>&
le to set it up with VPN (or outside our firewall)
to give someone a chance to look at it "as is."
thurman
-Original Message-
From: [EMAIL PROTECTED] [mailto:hardhats-
[EMAIL PROTECTED] On Behalf Of Mike Schrom
Sent: Monday, February 06, 2006 11:18 AM
To: hardhats-members@li
--- Thurman Pedigo <[EMAIL PROTECTED]> wrote:
> The
> downside is it is in FileMan - not VistA and it has a few files not
> represented in VistA.
>
What do you mean? There is nothing wrong with creating new files (so
long as you stsay within your namespace and numberspace, to avoid
possible con
t; [EMAIL PROTECTED] On Behalf Of Greg Woodhouse
> Sent: Monday, February 06, 2006 1:43 PM
> To: hardhats-members@lists.sourceforge.net
> Subject: Re: [Hardhats-members] Billing Module for VistA
>
> --- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
>
> > Because if you use w
ceforge.net
> Subject: Re: [Hardhats-members] Billing Module for VistA
>
> I'm sure I could do it in BASIC, but if I'm going to stick with VistA,
> I'd probably try to learn M eventually anyway. I have the ANSI 837
> documentation, though it may be an older version. I&
--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
> Because if you use what is shipped out in email, you do not need to
> know M and
> you don't need to modify VistA, and I thought it was a something
> thing that a
> VB Programmer could deal with.
>
Extending VistA (adding new components) and mo
Because if you use what is shipped out in email, you do not need to know M and
you don't need to modify VistA, and I thought it was a something thing that a
VB Programmer could deal with.
On Monday 06 February 2006 13:34, Greg Woodhouse wrote:
--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
> Th
--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
> The output is delivered in an email message as I understand it, so
> you
> probably have to figure out how to parse that, not Mumps code.
>
It's true that mail is often used for message transport, but there's
really no reason why a VistA based s
ROTECTED]>
To:
Sent: Monday, February 06, 2006 7:53 AM
Subject: Re: [Hardhats-members] Billing Module for VistA
>I agree, and I'd like to help, but my programming experience is limited to
>35 year old recollection of BASIC.
>
> Kevin Toppenberg wrote:
>> The real solution for
I'm sure I could do it in BASIC, but if I'm going to stick with VistA,
I'd probably try to learn M eventually anyway. I have the ANSI 837
documentation, though it may be an older version. I'd like to see how
VistA formats the output.
Greg Woodhouse wrote:
--- Mike Schrom <[EMAIL PROTECTED]>
to read the VistA Mumps code.
Jim Gray
- Original Message -
From: "Mike Schrom" <[EMAIL PROTECTED]>
To:
Sent: Monday, February 06, 2006 7:53 AM
Subject: Re: [Hardhats-members] Billing Module for VistA
I agree, and I'd like to help, but my programming experience i
--- Mike Schrom <[EMAIL PROTECTED]> wrote:
> I agree, and I'd like to help, but my programming experience is
> limited
> to 35 year old recollection of BASIC.
>
How comfortable do you feel with Basic? If you have an idea that you
want to try implementing, I'd say to go for it. Personally, I th
iginal Message -
From: "JohnLeoZimmer" <[EMAIL PROTECTED]>
To:
Sent: Sunday, February 05, 2006 1:10 PM
Subject: Re: [Hardhats-members] Billing Module for VistA
If that routine is available it would give us a big headstart.
jlz
James Gray wrote:
I just want to comment ab
software from Infomatix.
> >
> > Jim Gray
> >
> > - Original Message -
> > From: "JohnLeoZimmer" <[EMAIL PROTECTED]>
> > To:
> > Sent: Sunday, February 05, 2006 1:10 PM
> > Subject: Re: [Hardhats-members] Billing Module for VistA
> &
included in the IHS RPMS FOIA release. The bill
generator in RPMS is much more than a single routine. There is also the
newer software from Infomatix.
Jim Gray
- Original Message -
From: "JohnLeoZimmer" <[EMAIL PROTECTED]>
To:
Sent: Sunday, February 05, 2006 1:10 PM
Subj
: "JohnLeoZimmer" <[EMAIL PROTECTED]>
To:
Sent: Sunday, February 05, 2006 1:10 PM
Subject: Re: [Hardhats-members] Billing Module for VistA
> If that routine is available it would give us a big headstart.
>
> jlz
>
> James Gray wrote:
>> I just want to comment about
ebruary 05, 2006 1:10 PM
Subject: Re: [Hardhats-members] Billing Module for VistA
If that routine is available it would give us a big headstart.
jlz
James Gray wrote:
I just want to comment about the concept of putting lines of code into
the various revenue-generating packages in VistA. I thin
If that routine is available it would give us a big headstart.
jlz
James Gray wrote:
I just want to comment about the concept of putting lines of code into
the various revenue-generating packages in VistA. I think that should
be avoided as much as possible. In RPMS the approach has been to p
I just want to comment about the concept of putting
lines of code into the various revenue-generating packages in VistA. I
think that should be avoided as much as possible. In RPMS the approach has
been to put a special cross reference onto the Visit file (file 910) that
flags the visi
Others can comment about what has been done where VistA has been installed,
but the issue of coming up with a solution that can work with something open
source has not been dealt with yet, although Richard Schilling has recently
talked with me about taking a serious look at the possibility of co
> > [EMAIL PROTECTED] On Behalf Of Nancy Anthracite
> > Sent: Thursday, July 28, 2005 4:41 PM
> > To: hardhats-members@lists.sourceforge.net
> > Subject: Re: [Hardhats-members] BILLING
> >
> > Yes, 'fraid so.
> >
> > On Thursday 28 July 2005 05:31 pm
ginal Message-
> From: [EMAIL PROTECTED] [mailto:hardhats-
> [EMAIL PROTECTED] On Behalf Of Nancy Anthracite
> Sent: Thursday, July 28, 2005 4:41 PM
> To: hardhats-members@lists.sourceforge.net
> Subject: Re: [Hardhats-members] BILLING
>
> Yes, 'fraid so.
>
> On T
:hardhats-
> > [EMAIL PROTECTED] On Behalf Of alric
> > Sent: Thursday, July 28, 2005 9:57 AM
> > To: hardhats-members@lists.sourceforge.net
> > Subject: Re: [Hardhats-members] BILLING
> >
> > HCFA1500 & UB92.
> > The HCFA is a proffesional claim form (pro
To: hardhats-members@lists.sourceforge.net
> Subject: Re: [Hardhats-members] BILLING
>
> HCFA1500 & UB92.
> The HCFA is a proffesional claim form (providers, out patient etc)
> the UB is for inpatient claims
>
>
> Alric
>
> Nancy Anthracite wrote:
> > I hav
I agree, but right now there is effectively nothing that I am aware any of the
volunteers had even looked at. Perhaps we can code it to go all of the way
to an electronic submission without too much trouble. We will not know until
we look.
On Thursday 28 July 2005 04:07 pm, Dr. Schrom wrote:
It does.
Jim Gray
- Original Message -
From: "Aylesworth Marc A Ctr AFRL/IFSE" <[EMAIL PROTECTED]>
To:
Sent: Thursday, July 28, 2005 2:31 PM
Subject: RE: [Hardhats-members] BILLING
I believe RPMS does this.
Thanks
Marc Aylesworth
C3I Associates
AFRL/IFSE
J
I believe RPMS does this.
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 Behal
I believe there is some work being done with OpenVistA or VistA & FreeB.
Is anyone here involved in that?
I'll send this on the the AMIA Open Source Working group as well.
Alric
Dr. Schrom wrote:
I'm not quite a complete newbie, have been following the archives for
several months, installed Vi
HCFA1500 & UB92.
The HCFA is a proffesional claim form (providers, out patient etc)
the UB is for inpatient claims
Alric
Nancy Anthracite wrote:
I have a high pay dirt starter project for someone for VO and all other
flavors of VistA.
Just yesterday I found out that the "old" billing system
We decided to use a system called SequelMed systems.
http://www.sequelmed.com/
I think it was the best value we could find.
Kevin
--- Mike Deck <[EMAIL PROTECTED]>
wrote:
> This is mainly for Kevin, but I am wondering what
> systems everyone is
> currently using for billing. MY group of physi
47 matches
Mail list logo
