Notes for changes made for Med/IV in COS at OSU

Updated 6/29/99 with OSU chagnes

The notes here describe 3 major changes we made at OSU for Med/IV items in an orderset

    1. Fixes for missing data from @TCLs
    2. Add message for must review, to tell the user what to change/fix
    3. Stack the Must Review item's Order Detail screen prior to Precon

To fix the items we changed:

    1. For the first item (data missing from @TCLs) we changed the 'Add an Order Set Member' path. In this path we reset all values in the AUDA between CHPPO530 and CHPPO540. The only components that get stored in the @TCL are components that change between these 2 programs.
      bulletOne note: our @TCLs got too full, so we set up profiles PRHZZ, PRHZ2 and PRHZ3 to hold over flow data.
    2. To add the Message in Must Review, we changed the 'Add an Order Set Member' path. To this path we added a screen that allows the user delete certain data fields. When the user deletes any of the data fields we set the must review flag and then set a UFIeld equal to the message number. This message will be displayed when the item is ordered indicating to the user what to fix.
    3. We changed the processing (unloading) for Order Sets so that when chppo100 runs and %OSMRI is valued (the must review indicator) then we stack the revise order screen, before we get to precon.

************************************************************************

Changes made in the Add an Order Set Member path:

Before CHPPO530 runs, which runs about where CHPPO100 would run:

$T=OSADDM01 is the only change:
$T=OSADDM01
"%GECNGHX"='10/01/97 - TOME : CHANGED PHM TCL TO OOPOS540'
Stack Commands:
$D=%TCLNAME
$T=OSADDM02
$P=CHPPO530
$P=CHPPO540
$P=CHPPO531
Conditionals:
WHERE ALL OF "C1203" IS VALUED
AND "C1203" EQ 'PHM'
THEN "%ZOOSTCL"='OOPOS540' ***** changed
(ZOOSAD01)

 

Next, based on what was in the path when CHPPO530 was stacked, here is what happens when $P=CHPPO540 runs:

$P=CHPPO540 stacks

$T=OOPOS540 is stacked (thanks to %zoostcl)

"C0269"='1' **** need for concatenations to set up properly, Model bug
$T=OOPOS001 *** this tcl sets all values to them selves so that they store in the @TCL
"%GECNGHX"='RESET NEEDED FIELDS FOR RX ORDERSETS FOR @TCL'
"%GETX#35"="%GETX#35"
"%GEXT#36"="%GEXT#36"
"%RX1284"="%RX1284"
"%RX1313"="%RX1313"
"%RXABNME"="%RXABNME"
"C1162"="C1162"
"C1165"="C1165"
"C1166"="C1166"
"C1215"="C1215"
"C1215"="C1215"
"C1216"="C1216"
"C1219"="C1219"
"C1220"="C1220"
"C1245"="C1245"
"C1264"="C1264"
"C1284"="C1284"
"C1284#02"="C1284#02"
"C1284#03"="C1284#03"
"C1284#04"="C1284#04"
... (more)
$T=OOPOSA01
$T=OOPOS0A1
$T=OOPOS002 - move data in to PCHZZ fields & profile
(we do this because we have way too many UFields
that we use in OSU Pharmacy to fit into one @TCL)
$T=OOPOS0A2 - update the profile and $d fields
$T=OOPOS0D2 - set up profile updates (zz & z2) Value pchz2???
$P=PFOPRUPU - update profiles zz & z2
$T=OOPOS0B2 - more $d
$T=OOPOS0C2 - more $d
$S=OOPOS005 or 06 for IV ****documented below***(
the screens we delete data from)
$T=OOPONFCK
"%GECNGHX"=' NONFORM CHECK INGRED DESCRIPTION'
WHERE ALL OF "C1293#02" IS VALUED
AND "C1293#02" EQ 'NONFORMULARY ENTRY'
AND "%RXABNME" IS VALUED
THEN "C1293#02"="%RXABNME" **** moves order desc in c1293 nonform****
$T=ZMPVEO01
"%GECNGHX"='PHYSICIANS VIEW MED/IV ORDER ENTRY PROCESS TCL'
WHERE ALL OF "%ORSKIP" IS VALUED ***** added to skip clean***
AND "%ORSKIP" EQ '1'
AND "C1204" IS UNVALUED
THEN $GO=SKIPORD

 

$S=OOPOS005 or 06 for IV

These screens (one for IV and one for all others) are where the Order Set Builder removes pharmacy data that is normally required. The pharmacy data is 'probed' to remove.  While removing the data we set UOMSGNO=msg#.  UOMSGNO is the message that will be stacked when the order is stacked in the path by the orderset.   This error informs the user of what field needs to be filled in.  If a data item is removed, then we value %ORPCMRI to indicate to the order set that this is a must review item.

Finally, later in the path OS "Add an Order Set member":

$T OSGECN01 - added conditional stack, if PHM item then $T=OOPOS003

$T=OOPOS003 - $d data not needed in path and not needed in @TCL

 

Changes made in Order Enter path when the Order Set unload the Med/IV member:

Before CHPPO530 runs, which runs about where CHPPO100 would run:

This tcl runs for all Pharmacy orders when CHPPO100 runs, at OSU:

$T=RXPVEO01
$T=RXPVEO01 also runs for all order set items. Here at OSU we made the following additions for Med/IV Order Set members:
WHERE ALL OF "C1204" IS VALUED
AND "C1203" IS VALUED
AND "C1203" EQ 'PHM'
AND "C2216" IS VALUED (c2216 is valued to the name of the @TCL)
THEN
"PCHZZKEY"="C2216" (key of PRHZZ to unload data that does not fit in @TCL)
"PCHZ2KEY"="C2216" (key of PRHZ2 to unload data that does not fit in PRHZZ
$PE=PCHZ2KEY,
$PE=PCHZZKEY,
$T=OOGPQ501,
$T=OOPOS010 **** drives tcls that move PCHZZxxx fields to their real fields
$T=OOPOSA10  (#2)
$T=OOPOSB10  (#3)
$T=OOPOSZ10 (special processing for sliding scales, PCAs, epidurals and
other unique paths to set up 'modifier' fields)
$T=OOPVEO01
 
 
$T=OOPVEO01 - this is a copy of the model RXPVEO01, we had to do this because of the conditions that we put in the original for OrderSet processing.
Added this conditional:
WHERE ALL OF "%ORPCMRI" IS VALUED
AND "C1203" IS VALUED
AND "C1203" EQ 'PHM'
AND "%ORPCMRI" EQ '1'
AND "C1204" IS VALUED
AND "UMUST" IS UNVALUED
AND "3XSCR" IS VALUED (we value 3xscr in all paths to our
data collection screen)
THEN $T=OOPOSMRV
Where UOMSGNO is valued then $MSG=UOMSGNO
(set message for must review, saying what should be valued)
$T=OOPOSMR3 (special 3field processing set ups per 3xscr)
$T=OOPOSMR1 (set flags needed to look like order has been
to precon)
$SA=3XSCR
$D=%ORPCMRI *** clear must review flag ****
$T=ZMPVEO01 *** continue down the regular order entry path***

01/15/01