To enable advanced benchmarking in a metric component for a custom metric, ensure the IDN record is aligned with GPIN, but for organization-specific customizations, what additional?
A.
Map the custom metric to a GPIN equivalent and submit for community inclusion
To enable benchmarking for a custom metric, the IDN record is aligned with the GPIN structure. For a customization that is specific to the organization, the additional step is to map the custom metric to an equivalent GPIN item and to submit it for inclusion in the community. Mapping it allows the metric to be compared with the same measure at other organizations, and submitting it makes it available to the community so that others can also contribute data. The first option is correct. Stating that custom metrics cannot be benchmarked is inaccurate, and a local-only approach would give up the comparison. SlicerDicer does not provide a separate benchmarking facility for this purpose. Before submitting, the developer should ensure that the definition is clear and consistent, since a metric that is calculated differently from the community definition would lead to misleading comparisons. Coordinating with Epic and with the other organizations involved helps to agree on a common definition. Once benchmarking is available, the component can show the community value alongside the local result.
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