Programs & Phases (120-Day Model) — Integration

​

Overview

​

Integration Points

​

Platform Foundation (PF) Dependencies

• PF-08 (Forms Integration): intake/assessment/exit form linkage at program level
• PF-10 (Notifications): phase progression and milestone notification delivery

​

Consumer Core Dependencies (Downstream)

• RH-01: episode lifecycle records required for enrollment/progression
• RH-03: significant events can trigger regression decisions
• RH-04: attendance/curfew outcomes influence progression readiness
• RH-05: discharge planning consumes program/phase completion outcomes

• FA: consumes program_completed event for downstream billing/financial workflows

​

RBAC Dependencies (PF-02)

• rh_program_manager: define programs/phases/privileges/milestones
• rh_house_manager: approve progression/regression decisions
• rh_housing_tech: record milestone completion events

​

Event Contracts

​

Event: phase_progressed

interface RhPhaseProgressedPayload {
  event_type: 'phase_progressed';
  organization_id: uuid;
  episode_id: uuid;
  resident_profile_id: uuid;
  old_phase: 'PHASE1' | 'PHASE2' | 'PHASE3' | 'EXTENSION';
  new_phase: 'PHASE1' | 'PHASE2' | 'PHASE3' | 'EXTENSION';
  progression_type: 'automatic' | 'manual' | 'regression';
  progression_date: timestamp;
  timestamp: timestamptz;
}

​

Event: milestone_completed

interface RhMilestoneCompletedPayload {
  event_type: 'milestone_completed';
  organization_id: uuid;
  episode_id: uuid;
  milestone_id: uuid;
  milestone_name: string;
  completed_date: timestamp;
  verified_by: uuid;
  timestamp: timestamptz;
}

​

Event: program_completed

interface RhProgramCompletedPayload {
  event_type: 'program_completed';
  organization_id: uuid;
  episode_id: uuid;
  program_id: uuid;
  completion_date: timestamp;
  completion_type: 'normal' | 'early' | 'extension';
  timestamp: timestamptz;
}

​

Security Considerations

​

Multi-Tenancy

• All RH-02 entities are organization-scoped with RLS-enabled access.
• Cross-tenant reads/writes are blocked by policy and tested in RLS suites.

​

PHI/PII and Auditability

• Event payloads use identifiers and lifecycle metadata only (no unnecessary PHI fields).
• Progression/regression/milestone actions must retain actor and timestamp in auditable records.

​

Role-Gated Operations

• Progression/regression requires elevated RH manager roles.
• Milestone completion requires role-appropriate write permissions.

​

Testing Requirements

• Event payload structure validation for all three RH-02 events
• Trigger condition verification (progression, milestone completion, program completion)
• organization_id inclusion and tenant isolation checks
• Subscriber compatibility checks for PF-10 and FA
• RLS policy tests for RH-02 tables and role-sensitive actions

​

References

• RH-02 Spec
• CROSS_CORE_INTEGRATIONS.md
• EVENT_CONTRACTS.md