Task Mode is used when you want to view data stewardship tasks that have been automatically detected and queued up by Universal Identity. There are two task queues automatically created for you:
- Patient Task
- Patient Rejected Overlay
Tasks are created when individual source records are posted to Universal Identity.
The task is triggered when a source record (identified by the combination of Source + Native ID) that meets the criteria for a data stewardship task is posted. The task is automatically created and added to the task list, and the Source + Native ID of the triggering record is also recorded in the task.
The Source + Native ID values for the trigger record are displayed and specified in the top left corner of the first square. They are also displayed as a column alongside all other Source and Native ID values related to the task.
Each task in the task list is identified by a unique Task ID – this is an internal Verato ID that is not meaningful outside of the Universal Identity platform. However, the Task ID is useful because the Task Details view is rendered based on the Task ID. If you copy and paste the URL for a Task Details view into a new browser window, the URL directs you to the same task – this can be useful if you need to coordinate with a co-worker and provide them with a quick URL link to get to the same task you were looking at.
Task information is based on the state of the Universal Identity data at the time the task was created.
For example, suppose that a record from Source=A, Native ID=123 was posted on January 4th, 2019 at 10:31 am. At that point, the A:123 source record was a potential match with an existing identity, which was assigned a Link ID of 12f4, made up of source records A:456 and B:789.
The matching algorithm score between the posted source record (A:123) and the existing identity was 0.762. This is the information recorded for the data stewardship task (the trigger source record, the creation date time, the score, and so on).
It’s possible that subsequent updates to the A:123 source record or the B:789 source record could change the data – perhaps making the identities more similar with a higher match score, for example. This subsequent update would be visible to the data steward when they retrieve and view the task details, but it will not change the information associated with the original task. The original task will still record the score of 0.762 in this example.
Use the Task View and Search Tasks
The default Task List view shows all open data stewardship tasks, one task per row. The Task List view is paginated and sorted by task creation date. Each page shows 100 tasks. You can sort the data by clicking the column headings in the Task List view.
At the top of the task list, below each column heading (except the ‘Native ID’ column heading) you can enter a search within the task list using one or more of the following criteria:
-
Source of the trigger record – The source search input field is a drop-down list that displays all the source codes available in your Universal Identity configuration. You can select specific sources (one or many) by clicking next to the source name. If your Universal Identity configuration includes a very large number of sources, rather than scrolling through the list you can type part of the source code in the search box at the top of the source list – as you type, the source list is reduced to only those sources that contain the string you typed. The image below shows an example of the source list filtered for only those sources with the text string “pre” in the source name.
-
Task category – Select a category from the dropdown. You can select one or more task categories by clicking next to the task category in the list. See Task Categories for a list of types.
-
Task status – The task status search input field is a drop-down list that displays all the available task statuses. You can select one or more task statuses by clicking next to the task status in the list. By default, the task list does not display tasks of status “Closed”. If you want to view closed tasks, you can select the “Closed” status from the task status search list. The example below shows a user selecting a task search for task status values of “Open” and “Deferred”.
-
Task creation date range – Use the calendar widget to select a date range to filter the list of tasks created between the beginning and end dates (inclusive).
-
Task assignee – Select one or more users from the drop down to filter by user.
-
Task score – Search based on the matching algorithm score at the time the task was created. The matching algorithm score range runs from 0.0 to 1.0, but typically most data stewardship tasks will be in the score range of 0.7 to 0.8. The task score search input fields are numeric fields, one for the lower end of the range and another for the upper end of the score range. You can type a score value into the field, use the up/down arrows in the field to increment the score, or drag the circles on the ‘slider’ bar to adjust the score range.
To return to the Task List with all search criteria applied, click back arrow in the upper left corner of the Task Details view.
If you click the browser's back button instead, you will be returned to the default Task List without any search criteria applied.
Assign Tasks
Assign or Change Individual Tasks
- Click Stewardship and then click the Patient Task queue.
- Select a task.
- From the Assign Selected menu, select the data steward.
Bulk assignments allow you to assign existing tasks to data stewards.
This only applies to existing tasks and not newly created tasks.
- Click Stewardship and then click the Patient Task queue.
- Click Bulk Assignment.
- Select the responsible data steward and assign the assignment parameters. When finished, click Assign Tasks.
Up to 1,000 tasks can be reassigned at a time. Perform the steps repeatedly to reassign all the desired tasks, as needed.
Stale Tasks
Universal Identity takes steps to avoid creating unnecessary or redundant data stewardship tasks. If a source record posted to Universal Identity closely matches existing records, the platform will create a new task only if there is no existing data stewardship task between the posted and matched records.
For example, consider a scenario where record A:123 is posted. When this record is submitted, it potentially matches existing records A:456 and B:789. Universal Identity will create a new data stewardship task to ensure the data is reviewed and managed appropriately. Now, suppose record A:123 is posted again and still nearly matches the same records A:456 and B:789. Universal Identity will recognize that a data stewardship task was already created for these potential matches and will not generate a second task for the same data event, as it would be redundant.