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 New Requirement page (/gr/compliance/requirements/new) renders ComplianceRequirementWizardPage, a full-page wizard powered by ModuleWizardRenderer (PF-41) for creating a new gr_compliance_requirements record.

​
Overview

ComplianceRequirementWizardPage uses ModuleWizardRenderer with wizardType = 'compliance_requirement'. On completion:
  1. Authoritative insert — createRequirement (via useRegulatoryRequirementMutation) creates the gr_compliance_requirements row.
  2. Non-fatal inserts — an initial gr_compliance_checks row (scheduled check) and gr_compliance_evidence rows (document requirements) are created. Failures produce a warning toast but do not roll back the requirement.
Telemetry uses template ID 'gr-compliance-requirement-wizard' (PHI-free: IDs, step indices, timing only). On completion, navigation proceeds to the compliance requirements list.

​
Who it’s for

Requires permission: gr.compliance.admin (GR_PERMISSIONS.COMPLIANCE_ADMIN). Users without this permission cannot access this route.

​
Before you start

  • You must hold gr.compliance.admin.
  • Have the requirement title, applicable regulatory framework or source reference, responsible owner, check frequency, and any required document types identified before starting.

​
Steps

1

Open the New Requirement wizard

Navigate to /gr/compliance/requirements/new or use the add-requirement action from /gr/compliance/requirements. The wizard loads from the compliance_requirement template.
2

Complete each step

Follow the ModuleWizardRenderer prompts. Steps typically cover requirement identification, regulatory source linkage, check schedule, and document evidence configuration.
3

Submit

On the final review step, submit the wizard. The gr_compliance_requirements row is created. Non-fatal ancillary inserts (check, evidence) proceed in the background; a warning toast appears if they fail.
4

Return to Requirements Library

After completion you are navigated to the compliance requirements list. The new requirement appears there.

​
Key concepts

  • ModuleWizardRenderer (PF-41) — renders wizard steps from the pf_wizard_templates table.
  • compliance_requirement — wizard type identifier.
  • gr_compliance_requirements — the authoritative database record created by this wizard.
  • gr_compliance_checks — ancillary scheduled-check record; failure is non-fatal.
  • gr_compliance_evidence — ancillary document requirement records; failure is non-fatal.
  • useRegulatoryRequirementMutation — hook providing createRequirement for the authoritative insert.

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/wizards/compliance-requirement/ComplianceRequirementWizardPage.tsx
  • src/cores/gr/hooks/useRegulatoryRequirementMutation.ts
  • src/platform/permissions/constants.ts