Nancy,

I think I opened a can of worms on this one.  I was
assuming that an out patient could also have an
attending physician.  But apparently not.

I think this issue is going to be more hassle than I
won't to mess with right now.

Thanks for everyone's help!

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

> Maybe it is because you don't have a patient who has
> been admitted!  Note that 
> it says inpatient below.
> 
> On Sunday 13 February 2005 09:18 pm, Nancy
> Anthracite wrote:
> > I noted that only active providers are allowed, so
> do your docs have the
> > PROVIDER key and the only thing I could see that
> might have to do with that
> > and show activity was the PERSON CLASS, in file
> 200, which has an
> > expiration date which I believe you can leave
> blank.  Do your docs have a
> > person class of physician or one of those
> variants?
> >
> > 2,.104        PROVIDER               .104;1
> POINTER TO NEW PERSON FILE
> > (#200)
> >
> >               INPUT TRANSFORM:  S DIC("S")="I
> $$SCREEN^DGPMDD(Y,DA,DT)" D
> > ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
> >               LAST EDITED:      DEC 07, 1994
> >               HELP-PROMPT:      The provider
> currently assigned to this
> >                                 inpatient
> applicant.
> >               DESCRIPTION:      From the available
> listing select the
> > provider who is currently treating this patient.
> >
> >               SCREEN:           S DIC("S")="I
> $$SCREEN^DGPMDD(Y,DA,DT)"
> >               EXPLANATION:      Allow only active
> providers.
> >               EXECUTABLE HELP:  D
> HELP^DGPMDD(DA,DT)
> >               CROSS-REFERENCE:  2^APR
> >                                 1)= S
> ^DPT("APR",$E(X,1,30),DA)=""
> >                                 2)= K
> ^DPT("APR",$E(X,1,30),DA)
> >
> > On Sunday 13 February 2005 08:26 pm, Kevin
> Toppenberg wrote:
> > > I also thought @ was a master access setting. 
> But
> > > here is a screen log of what I am seeing.
> > >
> > >
> > > GTM>zwr DUZ
> > > DUZ=90
> > > DUZ(0)="@"
> > > DUZ(1)=""
> > > DUZ(2)=69
> > > DUZ("AG")="O"
> > > DUZ("AUTO")=1
> > > DUZ("BUF")=1
> > > DUZ("LANG")=1
> > >
> > > GTM>d ^XUP
> > >
> > > Setting up programmer environment
> > > Terminal Type set to: C-VT102
> > >
> > > Select OPTION NAME: diedit
> > >
> > > INPUT TO WHAT FILE: NEW PERSON// 2  PATIENT 
> (69454
> > > entries)
> > > EDIT WHICH FIELD: ALL// Provider??
> > > EDIT WHICH FIELD: ALL// .104??
> > > EDIT WHICH FIELD: ALL// .1041??
> > > EDIT WHICH FIELD: ALL//
> > >
> > >
> > > Is there something else wrong that I am doing?
> > >
> > > Thanks
> > > Kevin
> > >
> > >
> > >
> > > --- Marianne Susaanti Follingstad
> > >
> > > <[EMAIL PROTECTED]> wrote:
> > > > Actually, the @ is a superaccess that should
> be
> > > > sufficient for any situation, no matter what
> > > > the file DD, read, write, delete access code
> is.  In
> > > > other words, you should not have any
> > > > difficulty doing anything in any file.  Are
> you
> > > > having difficulty or are you just
> > > > anticipating having difficult, in which case
> go
> > > > ahead and try it first.  You should not even
> > > > have to change DUZ(0).
> > > >
> > > > Marianne Follingstad
> > > >
> > > > Greg Woodhouse wrote:
> > > > > As you might guess, that's a trick that is
> > > >
> > > > sometimes employed to
> > > >
> > > > > discourage unauthorized "fiddling" with
> sensitive
> > > >
> > > > files. Off the top of
> > > >
> > > > > my head, I'm not sure if Fileman will
> complain if
> > > >
> > > > you set DUZ(0)
> > > >
> > > > > programmatically to "^" before attempting an
> > > >
> > > > update, but I believe this
> > > >
> > > > > will work.
> > > > >
> > > > > --- Kevin Toppenberg <[EMAIL PROTECTED]>
> wrote:
> > > > > > Hello all,
> > > > > >
> > > > > > I want to edit fields .104 (PROVIDER) and
> .1041
> > > > > > (ATTENDING PHYSICIAN) in file 2 (PATIENT
> file).
> > > >
> > > > I
> > > >
> > > > > > have a fileman code of "@"
> > > > > >
> > > > > > In the data dictionary, these two fields
> have a
> > > >
> > > > code
> > > >
> > > > > > of ^ required.  I assume this means that
> my
> > > >
> > > > DUZ(0)
> > > >
> > > > > > must contain a ^.  This is normally loaded
> (I
> > > >
> > > > believe)
> > > >
> > > > > > from field 3 FILE MANAGER ACCESS CODE in
> file
> > > >
> > > > 200 (NEW
> > > >
> > > > > > PERSON file). This is stored in piece 4 of
> node
> > > >
> > > > 0.
> > > >
> > > > > > But how would a ^ character be stored,
> when the
> > > >
> > > > ^
> > > >
> > > > > > character is used as the pieces divider?
> > > > > >
> > > > > > Perhaps I am coming at this the wrong way.
>  All
> > > >
> > > > I want
> > > >
> > > > > > it do is have the attending physician be
> > > >
> > > > properly
> > > >
> > > > > > displayed in CPRS for a given physician.
> > > > > >
> > > > > > Thanks
> > > > > > Kevin
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > __________________________________
> > > > > > Do you Yahoo!?
> > > > > > Yahoo! Mail - You care about security. So
> do we.
> > > > > > http://promotions.yahoo.com/new_mail
> > >
> > >
>
-------------------------------------------------------
> > >
> > > > > > SF email is sponsored by - The IT Product
> Guide
> > > > > > Read honest & candid reviews on hundreds
> of IT
> 
=== message truncated ===



                
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250


-------------------------------------------------------
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

Reply via email to