Re: [Hardhats-members] How to obtain a write access of "^" ?
Stephen; Then that sounds like the loading of this field is programatic (data loaded at the time of the action being recorded) and doesn't use Fileman to Fill the field. That would keep most users (except for programmers) from changing the data. Interesting business rule. I see the value of it. - Original Message - From: "steven mcphelan" <[EMAIL PROTECTED]> To: Sent: Sunday, February 13, 2005 7:50 PM Subject: Re: [Hardhats-members] How to obtain a write access of "^" ? > If a field is write protected with the "^" then no DUZ(0) will allow you to > edit that field using Fileman enter/edit. > > - Original Message - > From: "Nancy Anthracite" <[EMAIL PROTECTED]> > To: > Sent: Sunday, February 13, 2005 9:57 PM > Subject: Re: [Hardhats-members] How to obtain a write access of "^" ? > > > > 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,.104PROVIDER .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 > >
Re: [Hardhats-members] How to obtain a write access of "^" ?
If a field is write protected with the "^" then no DUZ(0) will allow you to edit that field using Fileman enter/edit. - Original Message - From: "Nancy Anthracite" <[EMAIL PROTECTED]> To: Sent: Sunday, February 13, 2005 9:57 PM Subject: Re: [Hardhats-members] How to obtain a write access of "^" ? > 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,.104PROVIDER .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
RE: [Hardhats-members] Adding / Editing patients
This should be a great help to me. I have around 18,000 file I need to convert. Will move me a long way toward complete conversiontx/t > -Original Message- > From: [EMAIL PROTECTED] [mailto:hardhats- > [EMAIL PROTECTED] On Behalf Of Nancy Anthracite > Sent: Sunday, February 13, 2005 7:21 PM > To: hardhats-members@lists.sourceforge.net > Subject: Re: [Hardhats-members] Adding / Editing patients > > Nice going, Kevin! The VistA Office folks might like this once you get > your > last problem solved. > > On Sunday 13 February 2005 08:03 pm, Kevin Toppenberg wrote: > > Hey all, > > > > I have some code to offer othes here (if they want > > it), and some thoughts and questions. > > > > First, I wrote some custom code that bulk-created > > patient records in the PATIENT file. I ported over > > around 70,000 patients. Now, as I use these patients, > > I am finding that some tweeking needs to be done... > > ie. completing the records etc. So I have been trying > > to decide how best to edit this data. I am > > comfortable now doing it directly in Fileman. But > > that wouldn't be good for my receptionists. So I > > looked at the DG REGISTER... menus. And there I ran > > into the same problem that Nick was having about the > > system trying to connect to the MPI. Plus, it was > > getting to way too many questions (i.e. it was getting > > ready to admit a patient into the hospital), rather > > than just editing the patient record. > > > > So I have cut, pasted, and trimmed down this code > > (originally from DGREG.m) to make the following > > function. It can be called with a parameter=1 if > > adding new patients is to be allowed. Here is the > > code. And FYI, it uses a standard VistA screenman > > based system of editing. (Questions below) > > > > EDITPT(AddOK) > > ;"Purpose: Ask for patient name, and allow editing > > ;"Input: AddOK: if 1, adding new patients allowed > > ;"Result: none > > > > do LO^DGUTL > > set DGCLPR="" > > new DGDIV set DGDIV=$$PRIM^VASITE > > > > if DGDIV>0 set > > %ZIS("B")=$piece($get(^DG(40.8,+DGDIV,"DEV")),U,1) > > > > kill %ZIS("B") > > if '$data(DGIO),$piece(^DG(43,1,0),U,30) do > > . set %ZIS="N",IOP="HOME" > > . do ^%ZIS > > > > A do ENDREG^DGREG($get(DFN)) > > do if (Y<0) goto EditDone > > . W !! > > . if $get(AddOK)=1 do > > . . set DIC=2,DIC(0)="ALEQM" > > . . set DLAYGO=2 > > . else do > > . . set DIC=2,DIC(0)="AEQM" > > . . set DLAYGO=0 > > . kill DIC("S") > > . do ^DIC > > . kill DLAYGO > > . if Y<0 quit > > . set (DFN,DA)=+Y > > . set DGNEW=$P(Y,"^",3) > > . new Y > > . do PAUSE^DG10 > > . do BEGINREG^DGREG(DFN) > > . if DGNEW D NEW^DGRP > > > > if +$get(DGNEW) do > > . ;" query CMOR for Patient Record Flag Assignments > > if NEW patient and > > . ;" display results. > > . if $$PRFQRY^DGPFAPI(DFN) do DISPPRF^DGPFAPI(DFN) > > > > set (DGFC,CURR)=0 > > set DA=DFN > > set DGFC="^1" > > set > > VET=$select($data(^DPT(DFN,"VET")):^("VET")'="Y",1:0) > > > > set %ZIS="N",IOP="HOME" > > do ^%ZIS > > set DGELVER=0 > > ;"do EN^DGRPD > > ;"if $data(DGRPOUT) do goto A > > ;". do ENDREG^DGREG($G(DFN)) > > ;". do HL7A08^VAFCDD01 > > ;". kill DFN,DGRPOUT > > > > ;"do HINQ^DG10 > > if $D(^DIC(195.4,1,"UP")) if ^("UP") do ADM^RTQ3 > > > > do REG^IVMCQ($G(DFN)) ;" send financial query > > > > set DGRPV=0 > > do EN1^DGRP > > > > EditDone > > quit > > > > > > OK, the next issue I need to solve is the actual > > addition of a NEW patient (i.e. LAYGO). If I supply a > > new name of a patient, it asks if I want to add a new > > patient. If I say YES, it goes into roll and scroll > > mode, asking many more questions than my setting > > needs, and only comes back to the screenman ("nicer") > > editing screens after aborting with a "^" (and, oh by > > the way, you have to know how many questions you have > > to answer before jumping out, or the record is not > > created). > > > > So It seems that an input template might help here. > > But how would I tell ^DIC to use an input template in > > event of Laygo? > > > > Thanks > > Kevin > > > > > > > > __ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > > > --- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > ___ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge
Re: [Hardhats-members] How to obtain a write access of "^" ?
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,.104PROVIDER .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 > > > > > > 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/
Re: [Hardhats-members] How to obtain a write access of "^" ?
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,.104PROVIDER .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 > > > > 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 > > > > = > > > A practical man is a man who practices the errors > > > > of his forefathers. --Benjamin Disraeli > > > > > > > > Greg Woodhouse > > > [EMAIL PROTECTED] > > > [EMAIL PROTECTED] > > --- > > > > SF email is sponsored by - The IT Product Guide > > > Read honest & candid reviews on hundreds of IT > > > > Products from r
Re: [Hardhats-members] How to obtain a write access of "^" ?
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 > 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 > > > > > > > = > > A practical man is a man who practices the errors > of his forefathers. --Benjamin Disraeli > > > > Greg Woodhouse > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > > --- > > 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 > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://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] Adding / Editing patients
Nice going, Kevin! The VistA Office folks might like this once you get your last problem solved. On Sunday 13 February 2005 08:03 pm, Kevin Toppenberg wrote: > Hey all, > > I have some code to offer othes here (if they want > it), and some thoughts and questions. > > First, I wrote some custom code that bulk-created > patient records in the PATIENT file. I ported over > around 70,000 patients. Now, as I use these patients, > I am finding that some tweeking needs to be done... > ie. completing the records etc. So I have been trying > to decide how best to edit this data. I am > comfortable now doing it directly in Fileman. But > that wouldn't be good for my receptionists. So I > looked at the DG REGISTER... menus. And there I ran > into the same problem that Nick was having about the > system trying to connect to the MPI. Plus, it was > getting to way too many questions (i.e. it was getting > ready to admit a patient into the hospital), rather > than just editing the patient record. > > So I have cut, pasted, and trimmed down this code > (originally from DGREG.m) to make the following > function. It can be called with a parameter=1 if > adding new patients is to be allowed. Here is the > code. And FYI, it uses a standard VistA screenman > based system of editing. (Questions below) > > EDITPT(AddOK) > ;"Purpose: Ask for patient name, and allow editing > ;"Input: AddOK: if 1, adding new patients allowed > ;"Result: none > > do LO^DGUTL > set DGCLPR="" > new DGDIV set DGDIV=$$PRIM^VASITE > > if DGDIV>0 set > %ZIS("B")=$piece($get(^DG(40.8,+DGDIV,"DEV")),U,1) > > kill %ZIS("B") > if '$data(DGIO),$piece(^DG(43,1,0),U,30) do > . set %ZIS="N",IOP="HOME" > . do ^%ZIS > > A do ENDREG^DGREG($get(DFN)) > do if (Y<0) goto EditDone > . W !! > . if $get(AddOK)=1 do > . . set DIC=2,DIC(0)="ALEQM" > . . set DLAYGO=2 > . else do > . . set DIC=2,DIC(0)="AEQM" > . . set DLAYGO=0 > . kill DIC("S") > . do ^DIC > . kill DLAYGO > . if Y<0 quit > . set (DFN,DA)=+Y > . set DGNEW=$P(Y,"^",3) > . new Y > . do PAUSE^DG10 > . do BEGINREG^DGREG(DFN) > . if DGNEW D NEW^DGRP > > if +$get(DGNEW) do > . ;" query CMOR for Patient Record Flag Assignments > if NEW patient and > . ;" display results. > . if $$PRFQRY^DGPFAPI(DFN) do DISPPRF^DGPFAPI(DFN) > > set (DGFC,CURR)=0 > set DA=DFN > set DGFC="^1" > set > VET=$select($data(^DPT(DFN,"VET")):^("VET")'="Y",1:0) > > set %ZIS="N",IOP="HOME" > do ^%ZIS > set DGELVER=0 > ;"do EN^DGRPD > ;"if $data(DGRPOUT) do goto A > ;". do ENDREG^DGREG($G(DFN)) > ;". do HL7A08^VAFCDD01 > ;". kill DFN,DGRPOUT > > ;"do HINQ^DG10 > if $D(^DIC(195.4,1,"UP")) if ^("UP") do ADM^RTQ3 > > do REG^IVMCQ($G(DFN)) ;" send financial query > > set DGRPV=0 > do EN1^DGRP > > EditDone > quit > > > OK, the next issue I need to solve is the actual > addition of a NEW patient (i.e. LAYGO). If I supply a > new name of a patient, it asks if I want to add a new > patient. If I say YES, it goes into roll and scroll > mode, asking many more questions than my setting > needs, and only comes back to the screenman ("nicer") > editing screens after aborting with a "^" (and, oh by > the way, you have to know how many questions you have > to answer before jumping out, or the record is not > created). > > So It seems that an input template might help here. > But how would I tell ^DIC to use an input template in > event of Laygo? > > Thanks > Kevin > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > --- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://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] How to obtain a write access of "^" ?
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 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 > = A practical man is a man who practices the errors of his forefathers. --Benjamin Disraeli Greg Woodhouse [EMAIL PROTECTED] [EMAIL PROTECTED] --- 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
[Hardhats-members] New Cache.dat, etc., as of 2/12/04
Time to start over again, Thurman. Maybe it will work this time! -- 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
[Hardhats-members] Adding / Editing patients
Hey all, I have some code to offer othes here (if they want it), and some thoughts and questions. First, I wrote some custom code that bulk-created patient records in the PATIENT file. I ported over around 70,000 patients. Now, as I use these patients, I am finding that some tweeking needs to be done... ie. completing the records etc. So I have been trying to decide how best to edit this data. I am comfortable now doing it directly in Fileman. But that wouldn't be good for my receptionists. So I looked at the DG REGISTER... menus. And there I ran into the same problem that Nick was having about the system trying to connect to the MPI. Plus, it was getting to way too many questions (i.e. it was getting ready to admit a patient into the hospital), rather than just editing the patient record. So I have cut, pasted, and trimmed down this code (originally from DGREG.m) to make the following function. It can be called with a parameter=1 if adding new patients is to be allowed. Here is the code. And FYI, it uses a standard VistA screenman based system of editing. (Questions below) EDITPT(AddOK) ;"Purpose: Ask for patient name, and allow editing ;"Input: AddOK: if 1, adding new patients allowed ;"Result: none do LO^DGUTL set DGCLPR="" new DGDIV set DGDIV=$$PRIM^VASITE if DGDIV>0 set %ZIS("B")=$piece($get(^DG(40.8,+DGDIV,"DEV")),U,1) kill %ZIS("B") if '$data(DGIO),$piece(^DG(43,1,0),U,30) do . set %ZIS="N",IOP="HOME" . do ^%ZIS A do ENDREG^DGREG($get(DFN)) do if (Y<0) goto EditDone . W !! . if $get(AddOK)=1 do . . set DIC=2,DIC(0)="ALEQM" . . set DLAYGO=2 . else do . . set DIC=2,DIC(0)="AEQM" . . set DLAYGO=0 . kill DIC("S") . do ^DIC . kill DLAYGO . if Y<0 quit . set (DFN,DA)=+Y . set DGNEW=$P(Y,"^",3) . new Y . do PAUSE^DG10 . do BEGINREG^DGREG(DFN) . if DGNEW D NEW^DGRP if +$get(DGNEW) do . ;" query CMOR for Patient Record Flag Assignments if NEW patient and . ;" display results. . if $$PRFQRY^DGPFAPI(DFN) do DISPPRF^DGPFAPI(DFN) set (DGFC,CURR)=0 set DA=DFN set DGFC="^1" set VET=$select($data(^DPT(DFN,"VET")):^("VET")'="Y",1:0) set %ZIS="N",IOP="HOME" do ^%ZIS set DGELVER=0 ;"do EN^DGRPD ;"if $data(DGRPOUT) do goto A ;". do ENDREG^DGREG($G(DFN)) ;". do HL7A08^VAFCDD01 ;". kill DFN,DGRPOUT ;"do HINQ^DG10 if $D(^DIC(195.4,1,"UP")) if ^("UP") do ADM^RTQ3 do REG^IVMCQ($G(DFN)) ;" send financial query set DGRPV=0 do EN1^DGRP EditDone quit OK, the next issue I need to solve is the actual addition of a NEW patient (i.e. LAYGO). If I supply a new name of a patient, it asks if I want to add a new patient. If I say YES, it goes into roll and scroll mode, asking many more questions than my setting needs, and only comes back to the screenman ("nicer") editing screens after aborting with a "^" (and, oh by the way, you have to know how many questions you have to answer before jumping out, or the record is not created). So It seems that an input template might help here. But how would I tell ^DIC to use an input template in event of Laygo? Thanks Kevin __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://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] How to obtain a write access of "^" ?
Take a look at the FILE MANAGE ACCESS CODE field in file 200. Maybe you can put a ^ there with D P^DI and then see what happens. On Sunday 13 February 2005 05:14 pm, Kevin Toppenberg 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 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] How to obtain a write access of "^" ?
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 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 > = A practical man is a man who practices the errors of his forefathers. --Benjamin Disraeli Greg Woodhouse [EMAIL PROTECTED] [EMAIL PROTECTED] --- 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
[Hardhats-members] How to obtain a write access of "^" ?
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 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