Administrative Departmental Procedure
This department-specific procedure applies to the operations and staff of the Information Services
Department of the University of Wisconsin Hospitals and Clinics Authority as integrated effective July 1,
Procedure Title: UW Health Batch Scheduling Best Practices -- Tips and Tricks
Procedure Number: HL-025-PRO
Effective Date: 8/29/2016
This procedure describes best practices and tips and tricks for Batch Scheduling.
III. POLICY ELEMENTS
This procedure supports the following policy:
UW Health Batch Schedule Request Policy
A. Naming Jobs/Batches
1. When naming jobs and batches, use the format: UW [Application acronym] [Job/Batch
name] - [Template number]. For example: UW HB Collections Foster update – 71000,
where HB is the application acronym (Hospital Billing), Collections Foster update is the
Job, and 71000 is the template number.
2. The record ID should be the same 7-digit number for the Job, Batch, and Run.
a. If a Batch contains multiple Jobs, use the lowest Job ID as the Batch ID and
number the Jobs sequentially, if possible.
b. The ID should always be in the application’s designated numbering range (e.g.,
Hospital Billing is in the 5,000,000 range). Refer to the Health Link Style Guide
for more information.
c. Always use the exact same IDs and Names across all environments.
B. Build Order
1. The order of a build is INT - test > VFY - test > PRD - with approval.
2. The build cannot be Data Couriered and must be manually rebuilt in each environment.
Note: Even if a Run is only going to be scheduled in RPT and not in PRD, you must still build it
3. Always use environment names in your paths when rebuilding your records.
Note: If jobs are run in test environments, contact Health Link Technical Services to see if they
can be automatically updated on environment refreshes.
C. Master Files
Always know what Master Files you are using:
1. Templates use Master File E1A. This Master File determines what a run does, what code
it will execute, and what information you need to include in the job.
2. Jobs use Master File E1C. This Master File tells the run what template to use and what
specific information that template should use.
3. Batches use Master File E1B. This Master File holds a job or a collection of jobs (batch)
to be executed by a run.
4. Runs use Master File E1D. This Master File determines what is scheduled. While a
template determines what is being performed, a run determines how and when it is
5. Be aware of dependencies in other Master Files.
Batch Scheduler Process Request Form in ServiceNow. (https://uwhealth.service-
VI. REFERENCES (optional)
Sr. Management Sponsor: UW Health CIO
Author: IS Director – Clinical Systems
Reviewer(s): Health Link Technical Leaders
Approval Committee: Health Link Technical Leaders
UW Health CIO
VIII. REVISION HISTORY
Effective Date Next Review Summary of Changes Change Authors
8/29/2016 8/29/2017 Initial release. K. Wroblewski, M. Potyraj