The Report Significant Event screen is atDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/rh/significant-events/new and renders the SignificantEventReportingWizardPage component. It hosts a 3-step guided wizard (SignificantEventReportingWizard) that collects event classification, people and narrative, and review data before submitting a new record to rh_significant_events.
Overview
The page accepts an optionalepisodeId query parameter (?episodeId=<uuid>) and passes it to the wizard. The wizard uses WizardShell with a timeline layout and three steps:
- Event Classification — requires
event_type_id,severity, andoccurred_at(date/time). - People & Narrative — requires
narrative(event summary) andimmediate_actions_taken. - Review & Submit — displays collected data for review before final submission.
useSignificantEventMutation.createEvent writes to rh_significant_events with status: "submitted". On success, the browser navigates to /rh/significant-events/:eventId. On exit, the browser navigates to /rh/significant-events.
Who it’s for
This route requiresRH_PERMISSIONS.SIGNIFICANT_EVENTS_CREATE (rh.significant-events.create) enforced by a RequirePermission wrapper. The outer RHViewGuard also requires RH_PERMISSIONS.DASHBOARD_VIEW (rh.dashboard.view).
Before you start
- Hold both
rh.dashboard.viewandrh.significant-events.createpermissions. - Have the
episodeIdof the affected resident episode available. The wizard blocks submission without it.
Steps
Start the wizard
Navigate to
/rh/significant-events/new (optionally with ?episodeId=<uuid>). The wizard opens on Step 1: Event Classification.Step 1 — Event Classification
Select the event type (
event_type_id), severity, and the date and time the event occurred (occurred_at). Optionally enter a location. All three required fields must be populated to advance.Step 2 — People and Narrative
Enter the narrative description of the event and the immediate actions taken. Both fields are required. Optionally enter witness names and the name of the person who reported the event.
Step 3 — Review and Submit
Review all collected data. Click “Submit event” to write the record. On success, the browser navigates to the new event detail page.
Key concepts
| Term | Meaning |
|---|---|
event_type_id | Foreign key to the significant event type lookup (SME: confirm available types). |
severity | Severity classification of the event (SME: confirm allowed values and definitions). |
occurred_at | Date and time the event occurred, stored as event_date. |
narrative | Free-text summary of what occurred, stored as event_summary. |
immediate_actions_taken | Free-text description of actions taken immediately after the event. |
witness_info | JSON object storing witness names if provided. |
involved_parties | JSON object storing the name of the reporting person if provided. |
Related
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.
Documentation sources
Documentation sources
- src/routes/rh.tsx
- src/cores/rh/pages/SignificantEventReportingWizardPage.tsx
- src/cores/rh/components/wizards/significant-event-reporting/SignificantEventReportingWizard.tsx