-----Original Message-----
From: Janet Austin [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 11, 2007 5:18 PM
To: Bill Mullins
Subject: RE: [MEDITECH-L] RT documenting in MAR
Bill do you remember the attribute to accomplish this?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Bill Mullins
Sent: Wednesday, March 16, 2005 9:26 AM
To: Romnes, Colleen; [email protected]
Subject: RE: [MEDITECH-L] RT documenting in MAR
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
Collen:
We I helped pilot the EMAR/BMV project at my old facility, we had RT
document in EMAR like everyone else, but the way we did this to not
disrupt their current process was to let them continue documenting in
NUR the treatments (Process Interventions) and with a cds attribute on
the treatment screen, if the treatment involved a medication
administration (aerosol or IPPB), we jumped them into the EMAR Process
Meds routine and they documented the med, then they exited that routine
and we back in PI screen to complete their treatment documentation.
Worked well, good luck
Bill Mullins RN
WMC
Franklin,Tn
615-435-5630
[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Romnes, Colleen
Sent: Tuesday, March 15, 2005 1:58 PM
To: [email protected]
Subject: [MEDITECH-L] RT documenting in MAR
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
Hi All - Our respiratory staff currently documents their administered
meds in PCS and the MAR. We would like to know if anybody is using a
creative way (custom or process) to avoid duplicate documentation. Any
advise would be greatly appreciated!
Colleen Romnes
(386) 254-4000 Ext: 3000
Beeper: (386) 820-5025
[EMAIL PROTECTED]
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
This footnote also confirms that this email message has been swept by
Sophos and MIMEsweeper for the presence of computer viruses.
**********************************************************************
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
FROM TRIAGE CDS-JUMP TO OTHER EDM ROUTINES:
UPDATE PATIENT DATA:
[EMAIL PROTECTED]"Y" %EDM.PAT.edit.patient.S("")}
OR
DFT="Y"
[EMAIL PROTECTED]"Y" %EDM.PAT.edit.patient.S("")}
------------------------------------------------------------
DFT="Y"
[EMAIL PROTECTED]"Y" %EDM.PAT.update.priority.severity.sf.S
FCL1=("EDM.PAT.update.priority.severity.sf")}
------------------------------------------------------------
DFT="Y"
[EMAIL PROTECTED]"Y" %EDM.PAT.update.complaint.S
FCL1=("EDM.PAT.update.complaint")}
------------------------------------------------------------
DFT="Y"
[EMAIL PROTECTED]"Y" %EDM.PAT.print.patient.record.S
FCL1=("EDM.PAT.print.patient.record")}
-----------------------------------------------------------
5.5 JUMP TO EDM E/E NOTES ROUTINE FROM TRIAGE CDS:
[EMAIL PROTECTED]"Y" %EDM.PAT.note("N",@.itn)}
5.4
[EMAIL PROTECTED]"Y" %EDM.PAT.note.S("")}
------------------------------------------------------------------
Add this attribute to a yes/no query on a cds (I tried it on my triage
assessment in 5.5 Test) and it worked fine.
You can default the yes is you wish or allow the user to decide to update
patient data or not
[EMAIL PROTECTED]"Y" %EDM.PAT.edit.patient.S("")}
Or
DFT="Y"
[EMAIL PROTECTED]"Y" %EDM.PAT.edit.patient.S("")}
-------------------------------------------------------------------
This attribute jumps from the triage screen into Update status event routine.
[EMAIL PROTECTED]"Y" %EDM.PAT.update.status.event.S("")}
But when I file the assessment it is not updating the status event or removing
the patient from the tracker?
I did get this attribute to work to depart a ER patient from the triage
assessment (should work the same for admitted patient as long as you can
document against that patient):
Here is what did work and as soon as I filed the triage assessment the patient
was departed and removed from the tracker (now with the admitted patient, you
might still have to go into rm/staff and remove the EDM location for the
patient to fall off the tracker)?
DFT="Y"
[EMAIL PROTECTED]"Y" %EDM.PAT.update.status.event.S
FCL1=("EDM.PAT.update.status.event")}
This attribute will take you to the EDM Depart routine, which would not help
if the patient had been admitted...You can still use the old ADM ER DEPART
routine to get the ADM IN patients off the tracker and collect the depart
info, you have to go into rm/staff routine and delete the room and or location
and that will remove the patient from the tracker.
[EMAIL PROTECTED]"Y" %EDM.PAT.depart.S("")}
But we use the old ADM ER Departure routine to capture the depart info we
need.
Patient V00000001545
Name ROSE,SARA ELLEN Birthdate 12/30/79 Age 26 Sex F
Primary Care Physician PHEKE PHELPS JR,KENNETH J
ER Physician TBS SEEN,TO BE
Family Physician
Other Provider
Unit # M000000132 Location CCU-6TH Service Date 10/06/06
Status DIS IN Service Time 1536
Departure Date 10/06/06
Departure Time 1536
ER Physician TBS SEEN,TO BE
Departure Disposition PAT
Departure Diagnosis PNEUMONIA
Departure Comment TESTING OF ADM ER DEPART-NOT EDM DEPART ROUTINE
----------------------------------------------------------------------
After filing this ADM ER Departure info, go to Rm/Staff and remove the EDM
Location and the ADM IN patient will fall off your tracker, your daily log
reports will get the depart date and time, disposition from the ADM ER DEPART
fields, instead of the EDM Depart fields/routine (which you cannot use for
admitted patients). We have been doing it this way for 3 yrs and it works
fine.
So I can jump you into that ADM ER DEPART routine from your departure query.
Then the rm/staff routine to remove the edm location...
That is all for now, tired and got a hungry dog at home.
Good Luck, let me know how these work or do not work for you, they did work
for me in 5.5 SR2 Test.
-----------------------------------------------------------------------
Launching Allergy & Process Prescription routines from a CDS in other clinical
modules (like OE, NUR,PHA)
At this time EDM is the only module with a hard link to the RXM Allergy
routine. It will most likely be expanded to other modules in the future.
In the meantime a solution has been crafted to allow use of the RXM Allergy
routines in other modules.
This is done by adding a 'Y' type query to a CDS. An attribute can be added so
that answering Y to the query will launch the RXM routine. The CDS must be
accessed in a place where a patient has been identified, PHA E/E Patient Data
for example.
Either of the following attributes may be added:
[EMAIL PROTECTED]"Y" %MIS.PAT.edit.allergies("")}
[EMAIL PROTECTED]"Y" %MIS.PAT.view.allergies("")}
[EMAIL PROTECTED]"Y" %MIS.PAT.rxm.process.edit("")}
[EMAIL PROTECTED]"Y" %MIS.PAT.rxm.process.view("")}
If the @MIS.PAT.edit.allergies data field is used and the RXM Parameter
'Standalone RXM' is not set to 'Y' then the View routine will be called.
-------------------------------------------------------------
After Meditech loaded DTS MIS 7276, the following attribute worked.
[EMAIL PROTECTED]"Y" %MIS.PAT.rxm.process.edit("H")}
DFT="Y"
-------------------------------------------------------------
This will take you to the Hx meds routine:
[EMAIL PROTECTED]@Z.mouse.click IF{/G.MSEDB 1,
IFE=""^/G.MSEDB,%MIS.PAT.rxm.process.edit("H"),"Y";"N"}^RES,
IFE=P(R,S,RES^/[ANS%0,"PC18006"]|0)^#,1;
IFE=[ANS,"PC18006"]|0="Y" %MIS.PAT.rxm.process.edit("H")X,1;1}
Just replace the PC18006 with whatever the name of the query you put it
on is and it should do it.
This will take you to the Profile Meds routine
[EMAIL PROTECTED]@Z.mouse.click IF{/G.MSEDB 1,
IFE=""^/G.MSEDB,%MIS.PAT.rxm.process.edit("P"),"Y";"N"}^RES,
IFE=P(R,S,RES^/[ANS%0,"PC180063"]|0)^#,1;
IFE=[ANS,"PC180063"]|0="Y" %MIS.PAT.rxm.process.edit("P")X,1;1}
Just replace the PC180063 with whatever the name of the query you put it
on is and it shuld do it.
-----------------------------------------------------------------
I use this attribute in EDM, NUR assessment, and on my Administrative Data
screen so all my nurses can use RXM to process Hx Meds.
[EMAIL PROTECTED]@Z.mouse.click IF{/G.MSEDB 1,
IFE=""^/G.MSEDB,%MIS.PAT.rxm.process.edit("H"),"Y";"N"}^RES,
IFE=P(R,S,RES^/[ANS%0,"PC18006"]|0)^#,1;
IFE=[ANS,"PC18006"]|0="Y" %MIS.PAT.rxm.process.edit("H")X,1;1}
--------------------------------------------------------------------
ANSWER:
Have you tried using this in a macro, and then calling the macro from your
query?
; ** Calls the Nursing Notes routine
; make sure we save off & restore the response valu
; ** entered by the user on the CDS.
;
{/S.A,/S.C,/S.G}^Z.SV,
/[".NUR.PAT.LOOP"^PTL]^/SAVE.LOOP,""^/[PTL],
%NUR.NOTE.note.ee("")X,
@Cursor.on("")^#,
/SAVE.LOOP^/[PTL],
Z.SV^{/S.A,/S.C,/S.G},
END;
QUESTION:
We've found a problem that I am wondering if anyone else has encountered and
fixed. If a
user chooses to mark several interventions on the Process intervention screen
and select
the DI verb, the system will loop you thru the documention screens that must be
filled, but
after completing a CDS with a attribute to Patient notes, and filing the notes,
we are
thrown back out to the process intervention screen without the system
completing the
looping process. And then with the message of
1 out of 3 done, the users are left to find what was not documented.
Has anyone found a solution to this?
-----------------------------------------------------------------------------
JUMP TO PROCESS PHA ORDERS FROM NUR QUERY:
[EMAIL PROTECTED]"Y" IF{%Z.switch.appl("PHA")X 1,
FCL1=(" ** PHA Unavailable ** ")^/.WO,%Z.w.macro(1,1);
FCL1=%PHA.RX.process("")X,%Z.switch.appl("")},1}
----------------------------------------------------------------------------
[EMAIL PROTECTED]"Y" %NUR.NOTE.patient.S("M")}
----------------------------------------------------------------------------
PRINT PHA PROFILE
Thanks to Alan Baillargeon, this is the attribute to jump to the PHA profile
screen:
[EMAIL PROTECTED]"Y" IF{%Z.switch.appl("PHA")X 1,
FCL1=(" ** PHA Unavailable ** ")^/.WO,%Z.w.macro(1,1);
FCL1=%PHA.RX.profile("")X,%Z.switch.appl("")},1}
---------------------------------------------------------------------------
SEE SCREEN NURACTIVITY2
EXTERNAL ATTRIBUTE CODE
[EMAIL PROTECTED]"Y" %NUR.NOTE.menu("")X,@Cursor.on("")^#}
-----------------------------------------------------------
INTERNAL ATTRIBUTE CODE
FCL1 IF{/S.A="Y" %NUR.NOTE.menu("")X,D(14,14)^#}
-----------------------------------------------------------
And for anyone using Krames on your intranet (and other vendors may work as
well) you can
use an attribute on a query that, when answered yes, will take them onto your
intranet to
the Krames folder section. The attribute reads:
[EMAIL PROTECTED]"Y" %Z.link.to.shell("FULL PATH TO INTRANET SITE, INCLUDING
ACCOUNTNAME
AND PASSWORD")}
I got the full link/path and account name/password by right clicking on the
intranet link
to Krames on Demand, then clicking properties.
Once on the Krames on Demand site they can navigate to and print any patient
instructions
they would like. When they close the browser they are back on the MEDITECH CDS
from whence
they came.
Give me a call if you would like to discuss.
Alan R. Baillargeon RN, BSN
Senior Clinical Analyst
Information Systems
(410) 620-3464
Pager (410) 378-0171
-------------------------------------------------------------------
JUMP TO PROCESS INTERVENTIONS
[EMAIL PROTECTED]"Y" IF{%Z.switch.appl("NUR")X 1,
FCL1=(" ** OE Unavailable ** ")^/.WO,%Z.w.macro(1,1);
FCL1=%NUR.PC.WORK.document.S("")X,%Z.switch.appl("")},1}
-------------------------------------------------------------------
%NUR.PC.WORK.pha.link
%NUR.PC.WORK.pci.link
--------------------------------------------------------------------
I haven't tried to go to PCI from an attribute. When going to a routine
that has a verb strip (Review Orders) the DI from Document Interventions
remains.
Switch to other Routines
These attributes are designed specifically to work from within the NUR
Module. Especially the first two attributes will need to be adjusted to
work from any other module. The other attributes may work from some
other
modules.
Jump to EDM Notes from EDM Triage CDS:
[EMAIL PROTECTED]"Y" %EDM.PAT.note.S("")}
----------------------------------------------
Switch to Patient Notes without stopping at the Patient Notes Menu
[EMAIL PROTECTED]"Y" %NUR.NOTE.note.ee("")X,@Cursor.on("")^#}
Switch to Patient Notes stopping at the Patient Notes Menu
[EMAIL PROTECTED]"Y" %NUR.NOTE.menu("")X,@Cursor.on("")^#}
Switch to Plan of Care
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("NUR")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%NUR.PC.ee.S("")X,%Z.switch.appl("")},1}
Switch to Assessments
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("NUR")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%NUR.FORM.patient.S("")X,%Z.switch.appl("")},1}
Switch to Order Entry
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("OE")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%OE.INP.ee.care.area.S("")X,%Z.switch.appl("")},1}
Switch to Review Orders by Order Date
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("OE")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%OE.ORD.review.od.S("")X,%Z.switch.appl("")},1}
------------------------------------------------------------
There are several different ways to do it. Here are a couple:
1) @Dos.execute.new(PATH,FILE,1,1,0)
You would need to replace PATH with the path to the WORD executable on your PC.
You would
need to replace FILE with the path the WORD document on your PC.
2) %Z.link.to.shell(FILE)
You would need to replace FILE with the path to the WORD document on your PC.
You can integrate this could into your CDS query attributes. I suspect you
would want to
use something like the following:
[EMAIL PROTECTED]"Y" %Z.link.to.shell(FILE)}
-----------------------------------------------------------
Here is one alternative:
If you sign on using the usual sign-on programs (Z.sign.on), Meditech stores a
pointer to
the NPR directory in the global /.PRE. This will work to open and close your
prefixes.
ZZ%O(&S,/.PRE|0,&,&.NPR),
"PUT YOUR CODE FOR CHECKING FOR THE REPORT HERE",
C(&U)
--------------------------------------------------------------
If you look at the Z.zcus.is.rw.util report in our tips and tricks for 2005,
you will see a
way to open to the NPR data on the NPR master segment.
If the report you are checking for is an NUR report, you do not need to go to
the master
NPR segment, but you could check for the existance of the file on the NUR
segment as
follows:
IF{%["NUR.PC.WORK.zcus.is.your.report.here.R"] @REPORT.EXISTS}
Otherwise .. here is example code of going to the NPR master segment, done here
to make an
array of all computed fields in /FLD["xx.field.name"] to allow you to build
unbreakable MV
arrays.
"NPR"^MIS.APPL.database,
$["SEGS"](@MIS.APPL.database.segment,@MIS.APPL.database.directory),
ZZ%OP(&S,%.NPR),
;get report urn from new page program stored in temp file,
/R.NEW.PAGE.PGM$(L(/R.NEW.PAGE.PGM)-3)^NPR.REP.urn,
;make array of field numbers in /FLD,
DO{+/FLD[F]^F ""^/FLD[F]},
[EMAIL PROTECTED](NPR.REP.field) 1,
IF{L(@NPR.REP.ele.name^F,"xx")<L(F) NPR.REP.field^/FLD[F]}}, ;restore the
status quo,
C($U,%U,&U)
Joe Cocuzzo
-----------------------------------------------------
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sims Amy
Sent: Monday, October 17, 2005 6:07 PM
To: [email protected]
Subject: [MEDITECH-L] &IR from NUR.PC.WORK macro
All messages should be posted in plain text. HTML will be converted to
attachments. The meditech-l web site is MTUsers.com
======================================
>From a macro written in NUR.PC.WORK, I'm currently using
%Z.switch.appl("NPR","","","NPR")X to run over to NPR and check for the
existence of a
report. It's working okay, but it's a little slow.
I've used %Z.link to do switch to other applications before, but I'm unable to
get %Z.link
to work for switching to NPR.
Does anyone have some advice on using Z.link to switch to NPR, or does anyone
have a better
way to check for the existence of a report?
-----------------------------------------------------------
Enter/Edit Attributes: EMARYN
[EMAIL PROTECTED]"Y" %NUR.PC.WORK.process.meds("")}
-----------------------------------------------------------
I tried using the switch to print profiles attribute to go to the
multiple
profiles routine instead. It works but I have noticed some strange
behavior.
The attribute takes me to the routine just fine and allows me to print
the
report(s) without a problem. However, sometimes after trying to file it
takes me to the "Documentation Loop" box, except there are no choices
under
it and I have to choose EXIT from the file menu to get out. Other times
it
files just fine but after getting back into Process Interventions it
will
not let me "DI" or "DN" on any intervention. I am a magic 4.9.1 site.
Here
is the attribute...
[EMAIL PROTECTED]"Y" "Y"^c.compile.run.time,
FCL1=%NUR.PC.multiple.print.S("NUR.PC.multiple.print")X,
FCL1=D(13)^#,
[EMAIL PROTECTED]("")^#}
--------------------------------------------------------------------------
Hi everyone,
I just spotted a typo in my email. The first line of this attribute
should reference @.response, not @response. Sorry about that.
[EMAIL PROTECTED]"Y" "Y"^c.compile.run.time,
FCL1=%NUR.PC.WORK.profile.S("NUR.PC.WORK.profile")X,
FCL1=D(13)^#,
[EMAIL PROTECTED]("")^#,""}
Thanks,
Brian Schmit
-------------------------------------------------------------------------------
[EMAIL PROTECTED]"Y" "Y"^c.compile.run.time,
FCL1=%NUR.PC.WORK.profile.S("NUR.PC.WORK.profile")X,
FCL1=D(13)^#,
[EMAIL PROTECTED]("")^#}
Or
[EMAIL PROTECTED]"Y"
FCL1A="Y"^c.compile.run.time,
FCL1A=%NUR.PC.WORK.profile.S("NUR.PC.WORK.profile")X,
FCL1A=D(13)^#,
[EMAIL PROTECTED]("")^#
--------------------------------------------------------------------------------
There are a whole other list of routines that simply don't work well in that
macro setting,
but that can be implmented through a modification of the IFE call listed above.
Again,
best practice is to place this call directly o n the query through the use of
the FCL
attribute. The attribute would look like this:
[EMAIL PROTECTED]"Y" IF{%Z.switch.appl("OE")X 1,
FCL1=(" ** OE Unavailable ** ")^/.WO,%Z.w.macro(1,1);
FCL1=%OE.INP.ee.care.area.S("")X,%Z.switch.appl("")},1}
The following list shows the various routines that can be substituted inside
this
attribute.
%NUR.FORM.patient.S("")X - To Assessment Routine
%OE.INP.ee.care.area.S("")X - To Order Entry
%OE.ORD.review.od.S("")X - To Review Orders by Order Date
------------------------------------------------------------------------------
Then, of course, there were those routines that someone had built a macro to
handle the
switching for us. But, as time passed, soon those switching macros wouldn't
pass the
syntax checker muster. So, what is the best way to address switching from o ne
routine to
another? For some switches, I recommend always using a macro so that all
precautions are
taken to save the current state and return to it o nce work in the new routine
is finished.
As part of best practice, the call to switch to another routine is best done
from an FCL
attribute so that actions based o n the answer to a query are handled by
attributes
directly o n that query when ever possible. The attribute would look like this:
[EMAIL PROTECTED]"Y" %MIS.zcus.library.M.note("")}
The macro contents look like this:
; ** Calls the Nursing Notes routine, make sure we save off & restore the
response value;
** entered by the user o n the CDS.
{/S.A,/S.C,/S.G}^Z.SV,
@W.err(" Patient Note Required for Explanation! "),
/[".NUR.PAT.LOOP"^PTL]^/SAVE.LOOP,""^/[PTL],
%NUR.NOTE.note.ee("")X,
@Cursor.on("")^#,
/SAVE.LOOP^/[PTL],Z.SV^{/S.A,/S.C,/S.G},
END;
The following list shows the various routines that can be substituted inside
this macro.
%NUR.NOTE.menu("")X - To Patient Notes Menu
%NUR.NOTE.note.ee("")X - To Patient Notes just past the Menu
%NUR.PC.WORK.zcoc.mri.allergies("")X - To MRI Allergy Database
%NUR.PC.WORK.zcoc.online.mar("")X - To eMAR
Sometimes switching to a very closely related DPM appears possible without
taking this
step. For instance, if you are working in the NUR Process Interventions
routine, you may
have used this simple attribute to switch end users into the Patient Notes
routine and back
without much difficulty.
[EMAIL PROTECTED]"Y" %NUR.NOTE.note.ee("")X,@Cursor.on("")^#}
This method seems to work well unless your end user is using any of the newer
methods for
picking patients. These include looping by location and documenting by
location. In these
instances end users may find a that they now have a totally different patient
selected
partially through the process.
------------------------------------------------------------------------
First, in 4.9.1 that attribute is dangerous! If the user adds a query
through AI and then triggers that query the POC is blank. If filed, it
is all gone > -> all the documentation > -> all gone! I> '> d
seriously check it out in your version, but in HCA we don> '> t use this
attribute going to the POC any more.
>
> That being said, if you are using any switching attribute, like to
Patient Notes or OE, this shows how you can avoid being taken to the
next patient.
>
> [EMAIL PROTECTED]"U" @W.err(" Patient Note Required for Explanation!
"),
> FCL1=/[".NUR.PAT.LOOP"^PTL]^/SAVE.LOOP,""^/[PTL],
> FCL1=%NUR.NOTE.note.ee("")X,@Cursor.on("")^#,/SAVE.LOOP^/[PTL]}
>
> Daniel Davis, RN
> Patient Care Module Coordinator
> Southern Hills Medical Center
> Nashville, TN
> (615) 781-4153
>
> -----Original Message-----
> From: Sandra Covington [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 23, 2003 9:58 AM
> To: [email protected]
> Subject: [Meditech-L] Switch Application Attribute
>
> I have the following attribute on a nursing assessment screen.
Occasionally nursing will report that when they switch to the Plan of
Care routine, the wrong patient defaults. It took some testing but I
finally duplicated this today. If the nurse goes into Process
Interventions and enters a Location Loop, L TEL ENTER, and then
documents an assessment on the first patient, switches to the Plan of
Care, the next patient in the loop automatically pops in. This isn't a
huge problem and I'm telling them to use Location Lookups not Loops now
but I thought some of you attribute gurus might know of a way to prevent
this Enter from triggering the loop.
>
> IFE=IF{[ANS,"NURGOPOC"]|0="Y" 1,
> IFE=IF{%Z.switch.appl("NUR")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
> IFE=%NUR.PC.ee.S("")X,%Z.switch.appl("")},1}
-------------------------------------------------------------------------------
To link over to POM from an assessment, use this attribute:
[EMAIL PROTECTED]"Y" %EDM.PAT.link.to.poe("")}
EDM/RXM
Launching Allergy & Process Prescription routines from a CDS in other clinical
modules
(like OE, NUR,PHA)
At this time EDM is the only module with a hard link to the RXM Allergy
routine. It will
most likely be expanded to other modules in the future.
In the meantime a solution has been crafted to allow use of the RXM Allergy
routines in
other modules.
This is done by adding a 'Y' type query to a CDS. An attribute can be added so
that
answering Y to the query will launch the RXM routine. The CDS must be accessed
in a place
where a patient has been identified, PHA E/E Patient Data for example.
Either of the following attributes may be added:
[EMAIL PROTECTED]"Y" %MIS.PAT.edit.allergies("")}
[EMAIL PROTECTED]"Y" %MIS.PAT.view.allergies("")}
[EMAIL PROTECTED]"Y" %MIS.PAT.rxm.process.edit("")}
[EMAIL PROTECTED]"Y" %MIS.PAT.rxm.process.view("")}
If the @MIS.PAT.edit.allergies data field is used and the RXM Parameter
'Standalone RXM' is
not set to 'Y' then the View routine will be called.
Switch to other Routines
These attributes are designed specifically to work from within the NUR
Module. Especially the first two attributes will need to be adjusted to
work from any other module. The other attributes may work from some
other modules.
This handles the loop issue for me:
[EMAIL PROTECTED]"U" @W.err(" Patient Note Required for Explanation! "),
FCL1=/[".NUR.PAT.LOOP"^PTL]^/SAVE.LOOP,""^/[PTL],
FCL1=%NUR.NOTE.note.ee("")X,@Cursor.on("")^#,/SAVE.LOOP^/[PTL]}
--------------------------------------------------------------------------
*****THIS ATTRIBUTE WORKS ANYWHERE ON THE SCREEN*****
Switch to Patient Notes without stopping at the Patient Notes Menu
[EMAIL PROTECTED]"Y" %NUR.NOTE.note.ee("")X,@Cursor.on("")^#}
******THIS ATTRIBUTE HAS TO BE THE LAST QUERY ON THE CDS/SCREEN********
Switch to Patient Notes stopping at the Patient Notes Menu
[EMAIL PROTECTED]"Y" %NUR.NOTE.menu("")X,@Cursor.on("")^#}
Switch to Plan of Care
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("NUR")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%NUR.PC.ee.S("")X,%Z.switch.appl("")},1}
Switch to Assessments
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("NUR")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%NUR.FORM.patient.S("")X,%Z.switch.appl("")},1}
Switch to Order Entry
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("OE")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%OE.INP.ee.care.area.S("")X,%Z.switch.appl("")},1}
Switch to Review Orders by Order Date
IFE=IF{[ANS,"my-query"]|0="Y" 1,
IFE=IF{%Z.switch.appl("OE")X (" ** OE Unavailable **
")^/.WO,%Z.w.macro(1,1);
IFE=%OE.ORD.review.od.S("")X,%Z.switch.appl("")},1}
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
To subscribe or unsubscribe to the meditech-l, visit MTUsers.COM.
To check the status of the meditech-l, visit MTUsers.NET.
For help, email [EMAIL PROTECTED]
______________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l
