The Report Incident page is a guided wizard for submitting a new incident report. It is located at routeDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/gr/incidents/report.
Overview
The page is rendered byIncidentReportingWizardPage, which uses the PF-41 ModuleWizardRenderer for a wizard-type flow identified as incident_reporting. On completion, a single gr_incidents row is inserted. The gr_publish_incident_created database trigger pipeline automatically invokes gr-classify-incident-reporting-obligations to determine and create any required regulatory report records — the wizard does not insert regulatory reports directly.
Wizard analytics events are tracked via trackWizardEvent (start, abandon, completion). The route is protected by gr.incidents.report.
Who it’s for
Requires permission:gr.incidents.report
Before you start
- Your account must have the
gr.incidents.reportpermission. - Gather relevant details about the incident (date, time, location, description) before starting.
- The wizard auto-classifies regulatory obligations on submission.
Steps
- Go to Governance & Compliance → Incidents → Report Incident at
/gr/incidents/report, or select Report Incident from the incidents list. - Complete each step of the wizard as prompted.
- Review your entries on the summary/review step.
- Submit the report — a
gr_incidentsrecord is created. - Note the incident ID for follow-up; regulatory reports are generated automatically by the system.
Key concepts
| Concept | Description |
|---|---|
gr_incidents | The database table that stores incident records |
| Regulatory classification | Automatic post-submission trigger that determines reporting obligations |
gr-classify-incident-reporting-obligations | Edge function invoked by the trigger pipeline after incident creation |
| Wizard type | incident_reporting — drives the ModuleWizardRenderer step configuration |
Related
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.
Documentation sources
Documentation sources
- src/routes/gr.tsx
- src/cores/gr/wizards/incident-reporting/IncidentReportingWizardPage.tsx
- src/platform/wizards/ModuleWizardRenderer.tsx
- src/platform/permissions/constants.ts