> ## 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.

# Safety Events & Compliance Integration Contract

> Feature: RH-03 Core Owner: RH Status: 📝 Planned Last Updated: 2026-05-08

**Feature:** RH-03\
**Core Owner:** RH\
**Status:** 📝 Planned\
**Last Updated:** 2026-05-08

***

## Summary

RH-03 coordinates operational safety workflows with platform capabilities for notifications, documents, and cross-feature compliance reporting. Integration contracts keep RH-03 workflow ownership in RH while allowing downstream consumers (for example RH-06 reporting surfaces) to consume RH-03 outputs.

***

## Dependencies

* PF-08 (forms/checklists)
* PF-10 (notifications)
* PF-11 (document attachments and evidence)
* RH-02 (phase definitions consumed for pass eligibility)

***

## Event Contracts (planned)

Canonical RH-03 event schemas are documented in [`EVENT_CONTRACTS.md`](./EVENT_CONTRACTS.md#rh-03-critical-incident-events). This integration doc summarizes publisher/subscriber intent and safety constraints.

### `rh_critical_significant_event_reported`

* Publisher: RH-03
* Subscribers: PF-10
* Purpose: Immediate alerting for critical significant events
* Payload (minimum):
  * `significant_event_id`
  * `organization_id`
  * `episode_id`
  * `severity`
  * `occurred_at`

### `rh_significant_event_investigation_completed`

* Publisher: RH-03
* Subscribers: PF-10, RH compliance/reporting consumers
* Purpose: Notify completion and enable downstream reporting aggregation
* Payload (minimum):
  * `significant_event_id`
  * `investigation_id`
  * `organization_id`
  * `completed_at`

### `rh_uds_test_positive`

* Publisher: RH-03
* Subscribers: RH-03 relapse/event workflows, PF-10 notifications
* Purpose: Trigger positive-result response workflow
* Payload (minimum):
  * `uds_test_id`
  * `organization_id`
  * `episode_id`
  * `tested_at`

Subscriber handling requirement: consumers MUST treat this event as identifier-only and perform an RH-controlled, consent-gated detail lookup before accessing result details (`RH-04 EN-4` / Part 2 controls). `substances` or other sensitive result details are not published in the event payload.

***

## API/Hook Integration Notes

* RH-03 hooks must use org-scoped queries/mutations and standard query caching defaults.
* User-facing errors should be sanitized before display.
* RH-03 pass eligibility logic consumes RH-02 phase state and does not redefine canonical phase rules.

***

## Boundary Notes

* RH-03 owns safety event operational lifecycle and its evidence artifacts.
* RH-06 may consume RH-03 reporting outputs for broader compliance operations.
* RH-10 retains ownership of specialized fire/life-safety compliance artifacts.