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 screen is at /rh/compliance/requirements/:id and renders the ComplianceRequirementDetailPage component. It displays a single compliance requirement record from useComplianceRequirementDetail and allows editing and checklist management.

​
Overview

The page resolves the requirement by :id via useComplianceRequirementDetail. The breadcrumb label is set dynamically from requirement_name. The header shows the requirement name, category, frequency, active/inactive status badge, and an Edit button that opens ComplianceRequirementDialog. Two detail cards are displayed:
  • Requirement Details — category, frequency, regulatory source (if present), applies-to scope (if present), evidence required, and verification required flags.
  • Assignment — shows the linked residence name, or a note indicating organization-wide scope when residence is null.
A Description card appears when description is populated. A Compliance Checklists card renders ComplianceChecklistsTable filtered to the current requirement. The “Add Checklist Item” button opens ComplianceChecklistDialog.

​
Who it’s for

The outer RHViewGuard requires RH_PERMISSIONS.DASHBOARD_VIEW (rh.dashboard.view). The /rh/compliance/requirements/:id route carries no additional permission gate beyond the guard.

​
Before you start

  • Hold the rh.dashboard.view permission to access any RH route.
  • A compliance requirement with the target ID must exist and belong to the current organization.

​
Steps

1

Navigate to Compliance Requirements

Go to /rh/compliance/requirements. The requirements list is displayed.
2

Open a requirement record

Click a row. The browser navigates to /rh/compliance/requirements/:id.
3

Review requirement details

Inspect the Requirement Details card for category, frequency, regulatory source, applies-to scope, and evidence/verification flags.
4

Review assignment

The Assignment card shows which residence this requirement applies to, or confirms organization-wide scope.
5

Review description (if present)

If description is populated, a Description card shows the full text.
6

Manage compliance checklists

The Compliance Checklists card shows all checklist items scoped to this requirement. Click “Add Checklist Item” to open ComplianceChecklistDialog and add a new item.
7

Edit the requirement (optional)

Click “Edit” to open ComplianceRequirementDialog pre-populated with the current values. Submit to save changes.
8

Return to requirements list

Click “Back to Requirements” to navigate to /rh/compliance/requirements.

​
Key concepts

TermMeaning
requirement_nameDisplay name of the compliance requirement.
requirement_categoryCategory grouping for the requirement (SME: confirm allowed values).
frequencyHow often the requirement must be met (SME: confirm allowed values).
regulatory_sourceThe regulatory or policy source backing the requirement (SME: confirm mapping).
applies_toScope of applicability within the organization (SME: confirm values).
evidence_requiredBoolean flag indicating whether supporting evidence must be attached.
verification_requiredBoolean flag indicating whether independent verification is needed.
residenceLinked residence record; null means the requirement applies organization-wide.

Recovery Housing

Recovery Housing references and 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.
  • src/routes/rh.tsx
  • src/cores/rh/pages/ComplianceRequirementDetailPage.tsx
  • src/cores/rh/hooks/useComplianceRequirements.ts