The Scorecard Details screen is accessible atDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/lo/scorecards/:scorecardId and allows users to enter actual metric values, record trend directions, add notes, and transition the scorecard from draft to submitted or approved.
Overview
TheScorecardDetailPage fetches the scorecard via useScorecard and the associated metrics via useMetricsByRole. It initializes a local values state from existing scorecard values, mapping each metric to its actual_value, trend, and optional notes. The ScorecardValueEditor component renders an input for each metric. On save, bulkUpsert from useScorecardValueMutation persists all changes. A “Submit” button transitions the scorecard status to submitted via updateStatus. An “Approve” button transitions it to approved. The entity breadcrumb shows the role name and “Scorecard”.
Who it’s for
RequiresLO_PERMISSIONS.DASHBOARD_VIEW (lo.dashboard.view) via the shared LOViewGuard. Editing values requires lo.scorecard.edit.
Before you start
- The scorecard identified by
:scorecardIdmust exist. - Metrics must be configured for the scorecard’s role.
lo.dashboard.viewpermission required.
Steps
Open a scorecard
Navigate to
/lo/scorecards/:scorecardId or select a scorecard from the Scorecards list.Enter metric values
For each metric, enter the actual value, select a trend direction, and optionally add notes via
ScorecardValueEditor.Key concepts
- Status flow:
draft→submitted→approved. - TrendDirection: the trend field on each metric value; default is
same. - bulkUpsert: a single mutation call that persists all metric values for the scorecard at once.
Related
Leadership
Leadership core overview.
Governance & parity
Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/lo.tsx
- src/cores/lo/pages/ScorecardDetailPage.tsx
- src/cores/lo/hooks/useScorecards.ts
- src/cores/lo/hooks/useScorecardMetrics.ts
- src/cores/lo/hooks/useScorecardValues.ts