A trace records the performance of a Workbench report and allows its search process to be analyzed. When a report is slow or returns unexpected results, running it with a trace captures how Chronicles carried out the search, including which indexes were used, which steps were taken and how long each took. An analyst can then identify whether the criteria rely on non-indexed items or whether a step is scanning many records. The third option correctly describes the purpose. Scheduling recurring reports is a separate capability of the application. Retrieving patient notes from Clarity is unrelated, as a Workbench report searches Chronicles and not Clarity. Backing up report templates to Caboodle is also not a function of the trace. The information obtained from a trace supports optimization, for example by prompting a change of criteria to use an indexed item, or by narrowing the date range. Because the trace itself adds overhead, it should be used for diagnosis and not left on for routine runs. Users with the appropriate security can start it from the report toolbar.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit