Recurring schedule

A Recurring schedule is used to generate rolling extracts. A Report Date can be set historically which is then used to extract the required data from practices. A Run Once schedule will retry every night to get data from any practices that have failed to upload. Once all practices have uploaded data, the Run Once schedule is complete and will not repeat.  

Multiple recurring schedules can be set.

When the scheduling service runs, the schedule with the highest priority in the list will run first if it needs to be run. If it has already run the service then looks at the next Run Once schedule if one exists.

Setting up Recurring schedules:

• Open the Service Management screen.
• Select your pathway to open up and display the Management Dashboard ribbon   

• Click the Scheduling icon

This will open up the Scheduling window for you to start creating schedules.

• Click the Add Row + button to add a new schedule.

• Select the Recurring radio button.

• Enter the Run Every value. -  This is the Monthly value that is used to repeat the recurring schedule The schedule can run every 1,3,12 months.

• Enter the Report Day value. -  This is the report date that will be passed into any rules in the pathways and used for extracting data. This ranges from the 1st day to the 28th day. To report on days after the 28th, use the Last Day option.

• Enter the Delay Submission By value. - This is the day of the month that the schedule will run on after the Report Day. Setting the date after the 1st is usually required when extracting data from EMIS sites. Emis provides data to Outcomes Manager via the Emis Web cloud based system. This is an overnight process so is usually at least 24 hours behind. Setting the Delay Submission By later than the 1st of the month allows the data to catch up. The maximum delay is 15 days. This is because any greater delays will have a knock on effect to further extracts

• Enter the Start Date. - This is the date you want the schedule to be active from.

• Enter the End Date. - This is the date if required to end the schedule.

• Is Active is ticked by default. (Recurring schedules can be paused to allow other schedules in the list to run)
• Click Save when complete.
• Add further schedules if required, by clicking Add Row + button.

Setting the schedule priority

If multiple schedules have been set, then the priority can be changed by clicking the up or down arrows as required.

Editing\ Deleting Schedules

• Click the Edit or Delete icons against each schedule as required

Extract notes:

Extract processes vary between Clinical Systems. So it is recommended to have a Run on Day set to 4 or in the case of multiple pathways with extracts stagger the Run On Day. This allows EMIS Web clinical systems time for the data provided to Outcomes Manager (Data is sourced from Emis Cloud based servers) to be up to date.

Emis Web Data is provided to Outcomes Manager usually 24 hours in arrears.

Not all sites will extract on  the same day so time must be allowed for this. In the case of sites not extracting for a longer period (I.e. 5 days plus) then this requires investigation by the service desk

Also see the Important Notes in the scheduling section.