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 Requirement Details page shows a single compliance requirement record with full context: metadata, compliance checks, remediations, and linked risks. It is located at route /gr/compliance/requirements/:id.

​
Overview

The page is rendered by RequirementDetail and loads data via useRegulatoryRequirementDetail. Tabs include: Overview (metadata, status, category, priority), Checks (compliance check history), Remediations (linked remediation items), and Risks (linked risks via useRisksByRequirement). Users with gr.compliance.admin can edit, add checks, add remediations, and delete the requirement (via useRegulatoryRequirementMutation). A due-date urgency indicator is computed from differenceInDays. No permission gate is declared on this route in gr.tsx.

​
Who it’s for

No explicit permission gate on this route. Admin actions (edit, delete, add checks/remediations) require: gr.compliance.admin

​
Before you start

  • Navigate from the Requirements list at /gr/compliance/requirements.
  • A requirement record must exist for the given ID.

​
Steps

  1. Go to Governance & Compliance → Compliance → Requirements and select a requirement.
  2. Review the Overview tab for status, category, priority, description, and due date.
  3. Open the Checks tab to view compliance check history and add new checks (if permitted).
  4. Open the Remediations tab to view linked remediation items and create new ones (if permitted).
  5. Open the Risks tab to view risks linked to this requirement.
  6. Use the Edit button to update requirement details (requires gr.compliance.admin).

​
Key concepts

ConceptDescription
Compliance checkAn individual evaluation of whether the requirement is met at a point in time
RemediationA corrective action item linked to a requirement when it is not met
Linked risksRisks in the risk register associated with this requirement
Prioritylow, medium, high, critical — used for triage and urgency display

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/RequirementDetail.tsx
  • src/cores/gr/hooks/useRegulatoryRequirement.ts
  • src/cores/gr/hooks/useLinkedRisks.ts