We want to complete our SNOMED codes that land on ADMIN HOLD. We have them set to complete but for some strange reason they don't always. Any help would be appreciated.
Dawn, are they all in a category that has the default insurance set to complete?
Via SQL you would do something like this (test, test, test):
update orders set status = 'C' where code = (or like) 'whatever snomed code test" and whatever other tests you might want to add to designate which orders need to be completed.
Thanks David for the response. One of our techs actually came up with one. He tried to schedule it, but that didn't work so he just runs it a couple times a day. The kicker is that the order has to be signed and some don't get signed for a while, then they fall out of the 2 week parameters, so we just have to go in and clean them up now and then.
We schedule a lot of SQL scripts. Have to run it from a server that has a SQL client installed. SQL script and batch file in the same directory. The batch file calls the sql script with this:
sqlplus /nolog @scriptname.sql
Here is a sample SQL script to show the format. It creates a log file (connection string with as sysdba if you are using sys to connect):
spool h:\dupe_scripts\Logs\add_temp.log
connect username/password@sid as sysdba;
ALTER TABLESPACE TEMPORARY ADD TEMPFILE 'e:\oracle\data\BC01\TEMP04.DB' SIZE 2000M;
ALTER TABLESPACE TEMPORARY ADD TEMPFILE 'e:\oracle\data\BC01\TEMP05.DB' SIZE 2000M;
spool off;
exit;
Make sure when you set up the scheduled task that you set the parameter for the task to start in the same directory as your batch and script file.
Thanks David,
That is admittedly all a foreign language to me, but I have forwarded it on to our team members that speak your language.
I really appreciate your help.
Dawn