Difference between revisions of "Taskman Recurring Tasks"
From VistApedia
(→Recurring Tasks (dependent on VistA System Manager Policies)) |
(Added a glossary link to Record~) |
||
| Line 24: | Line 24: | ||
=== Recurring Tasks (dependent on [[VistA System Manager Policies]]) === | === Recurring Tasks (dependent on [[VistA System Manager Policies]]) === | ||
* '''NEW''' [[OPTION DG G&L RECALCULATION AUTO|DG G&L RECALCULATION AUTO]] --> Calculate Gains and Losses for the previous day. Run after midnight to get the previous day's data. | * '''NEW''' [[OPTION DG G&L RECALCULATION AUTO|DG G&L RECALCULATION AUTO]] --> Calculate Gains and Losses for the previous day. Run after midnight to get the previous day's data. | ||
| − | * '''NEW''' [[OPTION DGJ IRT UPDATE (Background)|DGJ IRT UPDATE (Background)]] --> Incomplete | + | * '''NEW''' [[OPTION DGJ IRT UPDATE (Background)|DGJ IRT UPDATE (Background)]] --> Incomplete [[Record~|Record]]s Tracking Background Job. |
| − | * [[OPTION DGPF BACKGROUND PROCESSING|DGPF BACKGROUND PROCESSING]] --> For PRF: To trigger Patient Record Flags reviews. | + | * [[OPTION DGPF BACKGROUND PROCESSING|DGPF BACKGROUND PROCESSING]] --> For PRF: To trigger Patient [[Record~|Record]] Flags reviews. |
* [[OPTION DMSQ PROJECT|DMSQ PROJECT]] --> (only if running SQLI) (for e.g. Fileman Projection; to regenerate projection files) | * [[OPTION DMSQ PROJECT|DMSQ PROJECT]] --> (only if running SQLI) (for e.g. Fileman Projection; to regenerate projection files) | ||
* [[OPTION HL PURGE TRANSMISSIONS|HL PURGE TRANSMISSIONS]] --> HL7: Clear HL7 logs which can get too big | * [[OPTION HL PURGE TRANSMISSIONS|HL PURGE TRANSMISSIONS]] --> HL7: Clear HL7 logs which can get too big | ||
Revision as of 13:54, 4 April 2012
A proper VISTA installation will have a bunch of recurring tasks (like linux cron jobs or mac launchd jobs) that ensure that the database remains clean and periodic stuff is completed. For example, the TIU recurring task makes sure that everything is signed; otherwise it will send a notification. Another example: Scratch globals for storing temporary data can get very large. A daily task (XQ XUTL $J NODES) cleans them up.
Contents
Tasks running by default in WV but need to be removed
- SCDX AMBCAR NIGHTLY XMIT --> WV doesn't transmit to VA for Amb Care Data
- XTPM NIGHTLY PATCH MONITOR -> Only if you use patch monitor
- XTPM UNINSTALLED PATCH BULLETI -> Only if you use patch monitor
- XUS NPI CBO LIST --> WV doesn't transmit stuff to VA Central Business Office
Cache Only Jobs
(Use if you are running WV on Cache; remove if you are running GT.M)
- HLO DAILY STARTUP --> Only for Cache; GT.M doesn't use HLO
- HLO SYSTEM STARTUP --> Only for Cache; GT.M doesn't use HLO
- XOBV LISTENER STARTUP --> Only for Cache; GT.M uses xinetd for VistaLink
- XMRONT --> Only for Cache; GT.M uses xinetd for Mailman too
- XWB LISTENER STARTER --> Only for Cache; GT.M uses xinetd for Broker
GT.M Only Jobs
- Important XU PROC CNT CLUP --> (Task number cleaner) Need if you use GT.M. Run every hour.
Start-up Jobs
- XUSER-CLEAR-ALL --> Clear users signed on when the system starts up
- XUDEV RES-CLEAR --> Clear resources (use on startup)
Recurring Tasks (dependent on VistA System Manager Policies)
- NEW DG G&L RECALCULATION AUTO --> Calculate Gains and Losses for the previous day. Run after midnight to get the previous day's data.
- NEW DGJ IRT UPDATE (Background) --> Incomplete Records Tracking Background Job.
- DGPF BACKGROUND PROCESSING --> For PRF: To trigger Patient Record Flags reviews.
- DMSQ PROJECT --> (only if running SQLI) (for e.g. Fileman Projection; to regenerate projection files)
- HL PURGE TRANSMISSIONS --> HL7: Clear HL7 logs which can get too big
- LRTASK CONJAM --> For Lab: Set up Controls on Accession Lists
- LRTASK LAB --> For Lab: Start up background processing routine
- LRTASK NIGHTY --> For Lab: various tasks
- LRTASK ROLLOVER --> For Lab: Roll forward unverified accessions. Important!
- ORMTIME RUN CHECK --> For CPRS: Check that ORMTIME RUN is running
- ORMTIME RUN --> For CPRS: Send notifications for expiring orders
- PSA IV ALL LOCATIONS --> PSA (only if running package): Compile Data for all Rxs
- PSD PURGE --> PSD (only if running package): purge CS worksheet file.
- PSJI BACKGROUND JOB (IV) --> (only if running package): Compile cost data.
- PSJU BRJ (UD) --> (only if running package): Nightly clean up.
- PSO AMIS COMPILE --> For OP: Compile Out Rx Statistics
- PSO AUTOCANCEL --> For OP: Cancel Out Rx for Inpatients residing longer than 3 days
- PSO COSTDAY NIGHTJOB --> For OP: Compile Rx costs
- PSO EXPIRE PRESCRIPTIONS --> For OP: Expire Prescriptions: Important!!!
- PSO MGMT NIGHTLY COMPILE --> For OP: More compilation stuff.
- PSO PNDEL1 --> For OP: Delete from Suspense
- SDAM BACKGROUND JOB --> Update appointment statuses.
- TIU NIGHTLY TASK --> VERY IMPORTANT: Needed for TIU to function. Various functions
- XMAUTOPURGE --> For MM: Delete unreferenced Messages
- XMCLEAN --> For MM: Delete 'Deleted' messages
- XMPURGE-BY-DATE --> to delete old messages (not needed --> based on disk space) 'Whether this option should be scheduled, or whether XMAUTOPURGE or XMPURGE should be scheduled instead depends on the policy of the VistA System Manager'
- XQBUILDTREEQUE --> Somewhat important -> rebuild menus daily
- XQ XUTL $J NODES --> VERY IMPORTANT -> needed to clean ^TMP, ^XTMP, ^UTILITY.
- XUAUTODEACTIVATE --> Auto-deactivate users who haven't signed on in 90 days.
- XUERTRP AUTO CLEAN --> Auto-clean error trap (for errs older than 7 days)
- XUSAZONK --> Purge Failed Access Attempts and Programmer Mode Access.
- XUSCZONK --> For Kernel: Purge Sign in log.
- XUSFACHK --> Check Failed accesses and send mail if too many
- XUTM QCLEAN --> Clean Task File. Keep only last 7 days of completed tasks.
