Comparing results with the Epic community requires the metric framework of Radar. The correct configuration for this scenario is: dashboard Metrics; configure the component to use Epic ' s benchmarking database. Dashboard metrics can be matched to the same measure at other organizations through the community benchmarking structure, which a SlicerDicer filter, a Workbench setting or a catalog link cannot provide. The component draws on Epic ' s benchmarking database, so the organization ' s local figure can be shown next to the community value. Additional elements named in the answer, such as the activity link, dynamic thresholds or export, are configured in the Component Editor in the same way as for any component. The developer should confirm that the local metric follows the community definition and that the organization ' s data is shared with the community warehouse. Labels that identify the comparison group help users to interpret differences, which may reflect service mix and not performance. After the correction, a comparison with an independent source, such as an operational list or a known total, confirms that the output is complete and that no secondary problem remains hidden behind the first.
[Reference: Cogito Fundamentals – Radar Dashboards and Components: Community Benchmarking with Dashboard Metrics, ===============, ]
Contribute your Thoughts:
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