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 Requirements page is the main library for compliance requirements. It supports search, filtering by category/status/priority, and paginated browsing. It is located at route /gr/compliance/requirements.

​
Overview

The page is rendered by RequirementLibrary and calls useRegulatoryRequirementList with deferred search and multi-dimensional filters. Pagination is rendered via a custom getPageNumbers helper. Users can switch between grid and list view. The Add Requirement button navigates to /gr/compliance/requirements/new (protected separately by gr.compliance.admin). An AI wizard button is also present (navigates to the compliance requirement wizard). Reference categories are loaded via useReferencePicklist. No permission gate is declared on this route in gr.tsx.

​
Who it’s for

No explicit permission gate on this route.

​
Before you start

  • No special permission is required to view the requirement library.
  • Creating requirements requires gr.compliance.admin.

​
Steps

  1. Go to Governance & Compliance → Compliance → Requirements at /gr/compliance/requirements.
  2. Use the search bar to find requirements by keyword.
  3. Apply Category, Status, and Priority filters to narrow the list.
  4. Toggle between grid and list view as preferred.
  5. Select a requirement card to open the Requirement Details page.
  6. Select Add Requirement to create a new requirement (requires gr.compliance.admin).

​
Key concepts

ConceptDescription
CategoryClassification of the requirement domain (sourced from reference picklists)
Prioritylow, medium, high, critical
StatusCompliance posture of the requirement (compliant, non-compliant, etc.)
PaginationServer-side pagination with ellipsis-aware page number rendering

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/RequirementLibrary.tsx
  • src/cores/gr/hooks/useRegulatoryRequirement.ts
  • src/platform/permissions/constants.ts