Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Source Details page shows the full record for a single regulatory source, including its polling status, last error (if any), and detected change events. It is located at route /gr/compliance/regulatory-sources/:id.

Overview

The page is rendered by RegulatorySourceDetailPage. It loads the source record via useRegulatorySource and associated change events via useRegulatoryChangeEvents filtered by source_id. The dynamic breadcrumb label is set to source.name. If the source has a last_error flag, an alert is displayed. The route is protected by GR_PERMISSIONS.REGULATORY_CHANGE_VIEW (gr.compliance.regulatory_change.view). Displayed fields include: name, URL, status badge, last error (if any), and a list of detected change events for this source.

Who it’s for

Requires permission: gr.compliance.regulatory_change.view

Before you start

  • Navigate from the Regulatory Sources list at /gr/compliance/regulatory-sources.
  • A source record must exist for the given ID.

Steps

  1. Go to Governance & Compliance → Compliance → Regulatory Sources and select a source.
  2. Review the source name, URL, and status.
  3. If an error alert is displayed, review the error and take corrective action (SME to confirm required steps).
  4. Scroll to the detected changes list to see change events attributed to this source.
  5. Select a change event to open the Regulatory Changes page or change detail.

Key concepts

ConceptDescription
last_errorError flag set when the last poll of this source failed
Source statusActive vs. paused — indicates whether the source is being polled
Change eventsuseRegulatoryChangeEvents({ source_id }) — changes detected from this specific source

Governance & Compliance

Governance & Compliance core overview.

Governance & parity

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.
  • src/routes/gr.tsx
  • src/cores/gr/pages/RegulatorySourceDetailPage.tsx
  • src/cores/gr/hooks/useRegulatorySources.ts
  • src/cores/gr/hooks/useRegulatoryChangeEvents.ts