OTECTED]
> On Behalf Of Greg
> Kreis
> Sent: Monday, April 04, 2005 10:18 AM
> To: hardhats-members@lists.sourceforge.net
> Subject: Re: [Hardhats-members] Fileman drop-out on
> pointer update
>
>
>
> Does anyone know details on how the VistA-Office EHR
> is bein
://www.cms.hhs.gov/quality/EHRRequirements.pdf.
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greg Kreis
Sent: Monday, April 04, 2005 10:18
AM
To:
hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members]
Fileman drop-out on pointer update
Does
prevents big problems.
Jim Gray
- Original Message -
From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, April 05, 2005 10:34 AM
Subject: Re: [Hardhats-members] Fileman drop-out on
pointer update
> Well, the long and the short of it is that I
should
>
-
From:
Marianne
Susaanti Follingstad
To: hardhats-members@lists.sourceforge.net
Sent: Tuesday, April 05, 2005 4:35
PM
Subject: Re: [Hardhats-members] Fileman
drop-out on pointer update
Did you kill it or have FileMan kill it? If FileMan
did it, then I don't
ray
> - Original Message -
> From: Marianne Susaanti Follingstad
> To: hardhats-members@lists.sourceforge.net
> Sent: Monday, April 04, 2005 12:45 PM
> Subject: Re: [Hardhats-members] Fileman drop-out
> on pointer update
>
>
> What then do you suggest?
Q
S+1 I $D(@(DIC_"Y,0)")),'$D(^(-9)) S DIY=$P(^(0),U)
- Original Message -
From: "Greg Woodhouse" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, April 05, 2005 3:42 PM
Subject: Re: [Hardhats-members] Fileman drop-out on pointer update
> Here's a
he beginning of the name. It is an
> > ugly kludge, but it
> > prevents big problems.
> > Jim Gray
> >
> > ----- Original Message -----
> > From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> > To:
> > Sent: Tuesday, April 05, 2005 10:
udge, but it
> prevents big problems.
> Jim Gray
>
> - Original Message -
> From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesday, April 05, 2005 10:34 AM
> Subject: Re: [Hardhats-members] Fileman drop-out on
> pointer update
>
>
> > W
From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, April 05, 2005 10:34 AM
Subject: Re: [Hardhats-members] Fileman drop-out on pointer update
Well, the long and the short of it is that I should
NOT have tried to kill one of the two duplicate
records. Thus I am doing so
eman lookup routine on file 2. That way
> they get around the problem of SSN being not a
> required field.
>
> Jim Gray
> - Original Message -
> From: Marianne Susaanti Follingstad
> To: hardhats-members@lists.sourceforge.net
> Sent: Monday, April 04, 2005 1
From:
Marianne Susaanti
Follingstad
To: hardhats-members@lists.sourceforge.net
Sent: Saturday, April 02, 2005 11:08
AM
Subject: Re: [Hardhats-members]
Fileman drop-out on pointer update It should be fine to put
the $G in there. There can't be
ect: RE: [Hardhats-members] Fileman drop-out on pointer update
What data should such a stub contain?
Kevin
--- Cameron Schlehuber <[EMAIL PROTECTED]>
wrote:
> After a "merge" of patient data, a "stub" is left
> behind.
>
>
>
> -Original Message-
MAIL PROTECTED]
> On Behalf Of Marianne
> Susaanti Follingstad
> Sent: Monday, April 04, 2005 11:46 AM
> To: hardhats-members@lists.sourceforge.net
> Subject: Re: [Hardhats-members] Fileman drop-out on
> pointer update
>
>
>
> What then do you suggest? In this case, NOT ha
urday, April
02, 2005 11:08 AM
Subject: Re:
[Hardhats-members] Fileman drop-out on pointer update
It should be fine to put the $G in there. There
can't be any unforeseen consequences to having it there. In fact, as you
found, there are unforeseen consequences to NOT having it th
leman
drop-out on pointer update
It should be fine to put the $G in there. There can't be
any unforeseen consequences to having it there. In fact, as you found,
there are unforeseen consequences to NOT having it there. As I mentioned,
it would be good to have someone review these SCR nodes
Does anyone know details on how the VistA-Office EHR is being created?
It would be interesting to see the requirements, both functional and
technical, that are driving the process.
Maury Pepper wrote:
VistA in the news:
www.ama-assn.org/amednews/2005/04/11/bisa0411.htm
VistA in the news:
www.ama-assn.org/amednews/2005/04/11/bisa0411.htm
-
From:
Marianne
Susaanti Follingstad
To: hardhats-members@lists.sourceforge.net
Sent: Saturday, April 02, 2005 11:08
AM
Subject: Re: [Hardhats-members] Fileman
drop-out on pointer update
It should be fine to put the $G in there. There can't
be any unforeseen consequenc
Thanks,
But don't be too impressed. I don't have a clue what
"SCR" nodes do. I was just looking for code that
referenced globals without a $get() or $data() guard.
Kevin
--- Marianne Susaanti Follingstad
<[EMAIL PROTECTED]> wrote:
> This one entry isn't quite the same situation, since
> 3.5 i
This one entry isn't quite the same situation, since 3.5 is the file
found at ^%ZIS(1, so I don't believe that it would be necessary to change
the node. FileMan is definitely smart enough to know not to try to
access the file entry it had just deleted. The one that caused you
problems was in a
All you will do is postpone the inevitable. The zero node of a record
is essential and shouldn't be missing. It is a sign that something is
wrong. (I can think of one case in the 3.9 file where I believe the
zero node's non-existence is a 'sign' that the record is being built
and not ready y
reflexively for GTM errors.
--- "Bhaskar, KS" <[EMAIL PROTECTED]> wrote:
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] on behalf of Kevin
> Toppenberg
> Sent: Sat 4/2/2005 3:46 PM
> To: hardhats-members@lists.sourceforge.net
> Cc:
>
: "Nancy Anthracite" <[EMAIL PROTECTED]>
To:
Sent: Saturday, April 02, 2005 1:20 PM
Subject: Re: [Hardhats-members] Fileman drop-out on pointer update
> When Rick was helping to port the VA Demo to GTM, I noticed he did a
rundown
> on the database every time he shut it down and s
Marianne,
I wrote this short code to show all the "SCR" nodes
ShowSCR
new I
set I=$order(^DD(""))
for do quit:(I="")
. if $data(^DD(I,0,"SCR")) zwr ^DD(I,0,"SCR")
. set I=$order(^DD(I))
I then looked at them all, and they all seemed ok
except for this on
April 2005 04:10 pm, Bhaskar, KS wrote:
> -Original Message-
> From: [EMAIL PROTECTED] on behalf of Kevin
> Toppenberg Sent: Sat 4/2/2005 3:46 PM
> To: hardhats-members@lists.sourceforge.net
> Cc:
> Subject: RE: [Hardhats-members] Fileman drop-out on pointer update
> Yeah,
-Original Message-
From: [EMAIL PROTECTED] on behalf of Kevin Toppenberg
Sent: Sat 4/2/2005 3:46 PM
To: hardhats-members@lists.sourceforge.net
Cc:
Subject:RE: [Hardhats-members] Fileman drop-out on pointer update
Yeah, but it is the nature of the weak minded to look
rs@lists.sourceforge.net
> Cc:
> Subject: Re: [Hardhats-members] Fileman drop-out on
> pointer update
> Marianne,
>
> [KSB] <...snip...>
>
> Is this really a 'bug'? Or is it one of those funny
> database-needs-to-be-rundown type situations?
>
It should be fine to put the $G in there. There can't be any
unforeseen consequences to having it there. In fact, as you found,
there are unforeseen consequences to NOT having it there. As I mentioned,
it would be good to have someone review these SCR nodes to see if there
are any other potent
Comment below.
-- Bhaskar
-Original Message-
From: [EMAIL PROTECTED] on behalf of Kevin Toppenberg
Sent: Fri 4/1/2005 12:59 PM
To: hardhats-members@lists.sourceforge.net
Cc:
Subject:Re: [Hardhats-members] Fileman drop-out on pointer update
Marianne,
[KSB] <...s
Marianne,
Thanks for your help.
Following your instructions:
GTM>zwr ^AUPNPAT(0)
^AUPNPAT(0)="PATIENT/IHS^901sIP^14861^1510"
GTM>zwr ^DD(901,0,"SCR")
^DD(901,0,"SCR")="X ""I '$P(^DPT(Y,0),U,19)"" W
$E(^AUPNPAT(Y,0),0)"
So you are right. This is the source of the line that
caused
A quick look at the DI* routines I have (which are old), leads me to
suggest that you look at the DD for the file defining ^AUPNPAT. Look
at ^AUPNPAT(0) to find the file number and then look at ^DD(file number,0,"SCR")
and I'm guessing you'll find the culprit there as "I '$P(^DPT(Y,0),U,19)".
I
I had two patients that were duplicates--i.e. the same
person, but with two different married names.
So I deleted one, and told fileman to change all
pointers from the former to the later.
(I had to take off a guard to do this)
It then scans through all the appropriate places and
changes the po
32 matches
Mail list logo
