This screen displays the full detail of a single detected regulatory change event at routeDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/gr/compliance/regulatory-changes/:id.
Overview
The Change Details page loads a single regulatory change event viauseRegulatoryChangeEvent. The header shows the event title, detected timestamp, and a Radar icon. The page displays a severity badge (RegulatoryChangeSeverityBadge), a status badge (RegulatoryChangeStatusBadge), and an alert with classification rationale. A per-impact list is shown. When the event has status detected or under_review, users with the gr.compliance.regulatory_change.approve permission see Approve and Dismiss buttons, which open RegulatoryChangeReviewSheet with the corresponding decision pre-set. A back link returns to the regulatory changes list.
Who it’s for
Requires permissiongr.compliance.regulatory_change.view (set on the route in gr.tsx via GR_PERMISSIONS.REGULATORY_CHANGE_VIEW).
The Approve/Dismiss action is additionally gated by gr.compliance.regulatory_change.approve.
Before you start
- You must have the
gr.compliance.regulatory_change.viewpermission. - The change event must exist and be in status
detectedorunder_reviewfor the approve/dismiss actions to appear.
Steps
Open Change Details
From
/gr/compliance/regulatory-changes, click a change event to navigate to its detail page.Key concepts
- Status
detected— newly identified change, not yet reviewed. - Status
under_review— change is being evaluated. - Approve — decision value
'approved'passed toRegulatoryChangeReviewSheet. - Dismiss — decision value
'dismissed'passed toRegulatoryChangeReviewSheet.
Related
Governance & Compliance
Governance & Compliance 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/gr.tsx
- src/cores/gr/pages/RegulatoryChangeDetailPage.tsx
- src/cores/gr/hooks/useRegulatoryChangeEvents.ts
- src/platform/permissions/constants.ts