Cross-Core Integration Matrix

​

Quick Reference

​

Integration Matrix

• ✅ Implemented - Fully implemented and tested
• 📝 Planned - Specified but not yet implemented
• 📋 Draft/Spec - Specification complete, implementation not started
• 🟡 In Progress - Partially implemented
• 🚧 Work in progress / partial delivery - Active development with partial feature delivery

​

Encounter Lifecycle (CL-PM)

​

Integration by Core

​

RH (Recovery Housing)

• recovery_housing (POS 55) — NARR Level 2/3 recovery housing
• psychiatric_residential (POS 56) — Behavioral health residential (RTC/BHRF)
• inpatient_unit (POS 51) — Inpatient psychiatric unit

• rh_resident_admitted → FA / PM (🟡 persistence ✅; batch consumers 📋) — facility_type for PM-07 POS
• rh_resident_discharged → FA / PM (🟡 persistence ✅; batch consumers 📋)
• rh_phase_advanced → FW-16 / PF-10 (🟡 persistence ✅; automations 📋)
• invoice_creation_requested → FA (📝 Planned) — includes facility_type; align name with FA before implement (see EVENT_CONTRACTS)
• rh_bed_assigned / rh_bed_released → HR (📝 Planned) — register in KnownEventName + triggers when HR consumer is scheduled (legacy names bed_assigned / bed_released deprecated)
• critical_incident_reported → PF-10 (📝 Planned)
• attendance_threshold_breached → PF-10, RH-05 (📝 Planned)
• compliance_deadline_approaching → PF-10 (📝 Planned)
• non_compliance_detected → PF-10 (📝 Planned)

• payment_received from FA (📝 Planned)
• employee_assigned_to_site from HR (📝 Planned)

• /api/v1/fa/episode-balance from FA (🟡 Edge function fa-episode-balance; uses cached rh_episode_payment_status until FA episode AR is linked)
• /api/v1/hr/employees/{employee_id} from HR (📝 Planned)
• /api/v1/hr/employees from HR (📝 Planned)

• /api/v1/rh/current-residence → CL (📝 Planned) — current residence/bed for patient chart; API Contracts

• src/platform/census reads rh_beds and rh_residences (including facility_type) for HR workload and PM reporting
• See Platform Census README

• Forms (PF-08) - Resident intake forms
• Census (Platform) - useCensusData, useSiteCensus consumed by HR/PM
• Workforce (Platform) - Staff assignments
• Data Lookup (PF-15) - Site and staff selectors
• Notifications (PF-10) - Compliance alerts
• Documents (PF-11) - Resident agreements

​

FA (Finance & Accounting)

• vendor_bill_approved → FW-03, PF-10, FA-03 (✅ Implemented)
• payment_processed → FA-02, PF-10, FA-06 (✅ Implemented)
• journal_entry_posted → Event Consumer, FA-07, PF-10 (✅ Implemented)
• budget_approved → FW-03, PF-10, FA-07 (✅ Implemented)
• budget_exceeded → PF-10, FA-08 (✅ Implemented)
• consolidation_completed → FA-07, PF-10, Event Consumer (✅ Implemented)
• payment_received → RH (📝 Planned)
• tax_1099_generated → PF-10 (📝 Planned - FA-10)
• tax_w2_generated → PF-10, HR-07 (📝 Planned - FA-10)
• tax_year_closed → PF-10, FA-07 (📝 Planned - FA-10)
• asset_created → FM-05, PF-10 (📝 Planned - FA-11)
• asset_disposed → FM-05, PF-10, FA-02 (📝 Planned - FA-11)
• depreciation_posted → FA-02, FA-07 (📝 Planned - FA-11)
• expense_report_submitted → FW-03, PF-10 (📝 Planned - FA-12)
• expense_report_approved → FA-05, PF-10 (📝 Planned - FA-12)
• expense_report_rejected → PF-10 (📝 Planned - FA-12)
• expense_reimbursement_processed → FA-02, PF-10 (📝 Planned - FA-12)
• project_created → FA-08, PF-10 (📝 Planned - FA-13)
• project_budget_exceeded → PF-10, FA-08 (📝 Planned - FA-13)
• grant_drawdown_received → FA-02, PF-10 (📝 Planned - FA-13)
• cash_position_updated → FA-07, PF-10 (📝 Planned - FA-14)
• investment_maturity_approaching → PF-10 (📝 Planned - FA-14)
• credit_limit_approaching → PF-10 (📝 Planned - FA-14)
• idc_rate_calculated → FA-13, PF-10 (📝 Planned - FA-15)
• idc_allocated → FA-13, FA-02 (📝 Planned - FA-15)
• kpi_threshold_exceeded → PF-10 (📝 Planned - FA-16)
• intercompany_transaction_created → FA-02, FA-09 (📝 Planned - FA-17)
• intercompany_elimination_generated → FA-09, FA-02 (📝 Planned - FA-17)
• fa_revenue_recognized → FA-02, FA-05, FA-13 (✅ Implemented FA-18 Phase 2 WS3 — published via fw_domain_events from fa_process_revenue_recognition)
• fa_revenue_schedule_completed → FA-05, FA-13, LO (✅ Implemented FA-18 Phase 2 WS3 — emitted when a schedule fully recognizes its total revenue)
• close_period_started → PF-10, FA-02 (✅ Implemented - FA-19)
• close_period_completed → PF-10, FA-07 (✅ Implemented - FA-19)
• close_period_approved → PF-10, FA-07, FW-03 (✅ Implemented - FA-19)
• close_task_assigned → PF-10 (✅ Implemented - FA-19)
• close_task_completed → PF-10 (✅ Implemented - FA-19)

• rh_resident_admitted from RH (🟡 Event persisted; FA batch consumer 📋) — facility_type for service-line tagging
• rh_resident_discharged from RH (🟡 Event persisted; FA batch consumer 📋) — facility_type and LOS
• invoice_creation_requested from RH (📝 Planned) — payload includes facility_type
• resident_charge_created from RH → FA-05 (📝 Planned - Auto-invoice generation)
• merit_increase_approved from HR-15 → FA-08 (✅ Implemented) - Budget impact tracking
• compensation_cost_allocated from HR-15 → FA-08 (✅ Implemented) - Departmental cost forecasts
• compensation_analysis_completed from HR-15 → FA-16 (✅ Implemented) - Analytics integration
• payroll_run_completed from HR-07 → FA-10 (📝 Planned - W-2 generation)
• vendor_payment_processed from FA-03 → FA-10 (📝 Planned - 1099 updates)
• purchase_order_received from FA-04 → FA-11 (📝 Planned - Asset creation)
• workflow_approved from FW-03 → FA-12 (📝 Planned - Expense approval)
• workflow_rejected from FW-03 → FA-12 (📝 Planned - Expense rejection)
• journal_entry_posted from FA-02 → FA-13, FA-15 (📝 Planned - Project/cost allocation)
• vendor_bill_approved from FA-03 → FA-13 (📝 Planned - Project expense allocation)
• invoice_sent from FA-05 → FA-13, FA-16, FA-18 (📝 Planned - Project revenue, DSO, revenue recognition)
• bank_balance_updated from FA-06 → FA-14 (📝 Planned - Cash position updates)
• payment_processed from FA-03 → FA-14 (📝 Planned - Cash flow forecast)
• fiscal_period_closed from FA-02 → FA-19 (📝 Planned - Close period linking)

• /api/v1/fa/episode-balance → RH (🟡 Edge function fa-episode-balance; full FA AR join 📋)
• /api/v1/fa/tax/1099/generate → Internal (📝 Planned - FA-10)
• /api/v1/fa/assets/{asset_id}/depreciation → FA-07 (📝 Planned - FA-11)
• /api/v1/fa/assets/register → FA-07 (📝 Planned - FA-11) - Fixed asset register report
• /api/v1/fa/depreciation/schedule → FA-07 (📝 Planned - FA-11) - Depreciation schedule report
• /api/v1/fa/depreciation/run → Internal (📝 Planned - FA-11) - Run monthly depreciation
• /api/v1/fa/expenses/reports/{report_id}/approve → FW-03 (📝 Planned - FA-12)
• /api/v1/fa/projects/{project_id}/budget-vs-actual → FA-07, FA-08 (📝 Planned - FA-13)
• /api/v1/fa/idc/rates/{rate_id}/allocate → FA-13 (📝 Planned - FA-15)
• /api/v1/fa/analytics/dashboard → Internal (📝 Planned - FA-16)
• /api/v1/fa/intercompany/eliminations/generate → FA-09 (📝 Planned - FA-17)
• /api/v1/fa/revenue/recognize → Internal (✅ Implemented FA-18 Phase 2 — RPC fa_process_revenue_recognition + edge function fa-process-revenue-recognition HTTP wrapper)
• /api/v1/fa/close/periods/{period_id}/approve → FW-03, Internal (✅ Implemented - FA-19)
• /api/v1/fa/close/periods/{period_id}/status → FA-07, FA-02 (✅ Implemented - FA-19)
• /api/v1/fa/cash/position → FA-07, FA-16 (📝 Planned - FA-14)

• /api/v1/hr/payroll/tax-data from HR-07 → FA-10 (📝 Planned - W-2, 941/940)
• /api/v1/fa/vendors/payments from FA-03 → FA-10 (📝 Planned - 1099)
• /api/v1/fa/purchase-orders/{po_id} from FA-04 → FA-11 (📝 Planned - Asset creation)
• /api/v1/fm/assets/{asset_id} from FM-05 → FA-11 (📝 Planned - Facilities asset reference)
• /api/v1/it/assets/{asset_id} from IT-01 → FA-11 (📝 Planned - IT asset reference)
• /api/v1/hr/employees/{employee_id} from HR-01 → FA-12 (📝 Planned - Employee data)
• /api/v1/fa/accounts from FA-01 → FA-12, FA-13, FA-15 (📝 Planned - GL accounts)
• /api/v1/fa/payments/create from FA-05 → FA-12 (📝 Planned - Reimbursement)
• /api/v1/fa/budgets/{budget_id} from FA-08 → FA-13 (📝 Planned - Project budgets)
• /api/v1/hr/employees/ftes from HR-01 → FA-15 (📝 Planned - FTE allocation base)
• /api/v1/fa/projects/{project_id}/direct-costs from FA-13 → FA-15 (📝 Planned - Direct cost base)
• /api/v1/fa/reports/balance-sheet from FA-07 → FA-16 (📝 Planned - Ratio calculations)
• /api/v1/fa/reports/statement-activities from FA-07 → FA-16 (📝 Planned - Analytics)
• /api/v1/fa/budgets/variance from FA-08 → FA-16 (📝 Planned - Variance analysis)
• /api/v1/fa/journal-entries/create from FA-02 → FA-17 (📝 Planned - Intercompany entries)
• /api/v1/fa/consolidations/{consolidation_id} from FA-09 → FA-17 (📝 Planned - Consolidation)
• /api/v1/fa/invoices/{invoice_id} from FA-05 → FA-18 (📝 Planned - Revenue schedule)
• /api/v1/fa/projects/{project_id} from FA-13 → FA-18 (📝 Planned - Project revenue)
• /api/v1/fa/fiscal-periods/{period_id} from FA-02 → FA-19 (📝 Planned - Close periods)
• /api/v1/fa/reports/close-status from FA-07 → FA-19 (📝 Planned - Close reports)
• /api/v1/fa/bank-accounts from FA-06 → FA-14 (📝 Planned - Cash positions)
• /api/v1/fa/budgets/cash-flow from FA-08 → FA-14 (📝 Planned - Cash forecasts)

• Forms (PF-08) - Payment forms, vendor portal forms, expense forms
• Workforce (Platform) - Employee selection for expenses
• Notifications (PF-10) - Budget alerts, tax deadlines, collection notices, close notifications
• Documents (PF-11) - Vendor contracts, tax forms, receipts, close documentation
• Reports (PF-12) - Financial reports

​

HR (Workforce)

• credential_expired → Event Consumer, HR-04 (✅ Implemented)
• credential_verified → Event Consumer (✅ Implemented)
• onboarding_completed → Event Consumer (✅ Implemented)
• offboarding_completed → Event Consumer (✅ Implemented)
• performance_review_completed → LO-03, HR-15, HR-16 (✅ Implemented - HR-10)
• performance_goal_completed → LO-03 (📝 Planned - HR-10)
• performance_improvement_plan_terminated → HR-03, HR-14 (✅ Implemented - HR-10)
• benefits_enrollment_approved → HR-07 (📝 Planned - HR-11)
• benefits_enrollment_terminated → HR-07 (📝 Planned - HR-11)
• disciplinary_action_termination → HR-03 (✅ Implemented - HR-14)
• incident_reported → GR-06, PF-10 (✅ Implemented - HR-14)
• grievance_filed → GR-03 (✅ Implemented - HR-14)
• merit_increase_approved → HR-07, FA, PF-10 (✅ Implemented - HR-15)
• compensation_analysis_completed → FA, PF-10 (✅ Implemented - HR-15)
• compensation_cost_allocated → FA (✅ Implemented - HR-15)
• successor_identified → PF-10 (📝 Planned - HR-16)
• talent_promoted → HR-16 (📝 Planned - HR-16)
• survey_completed → PF-10 (📝 Planned - HR-17)
• exit_interview_completed → HR-03 (📝 Planned - HR-17)
• employee_assigned_to_site → RH (📝 Planned)
• employee_created → GR (📝 Planned)

• credential_expired from HR-02 → HR-04 (✅ Implemented) - Blocks employee from scheduling
• employee_hired from HR-09 → HR-10 (📝 Planned) - Create initial performance goals
• organizational_goal_created from LO-03 → HR-10 (📝 Planned) - Link to employee goals
• performance_review_completed from HR-10 → HR-15 (✅ Implemented) - Trigger merit increase planning
• employee_terminated from HR-03 → HR-11, HR-14, HR-17 (✅ Implemented for HR-14) - Terminate benefits, close cases, trigger exit interview

• /api/v1/hr/employees/{employee_id} → RH (📝 Planned)
• /api/v1/hr/employees → RH (📝 Planned)
• /api/v1/hr/performance/reviews/:id/export → PF-12 (📝 Planned - HR-10)

• Forms (PF-08) - Onboarding forms, performance review forms, feedback forms, benefits enrollment forms, exit interview forms
• Workforce (Platform) - Employee selection (internal use)
• Notifications (PF-10) - Credential alerts, review reminders, feedback requests, enrollment reminders, incident notifications
• Documents (PF-11) - Employee documents, review documents, benefits documents, compensation statements
• Reports (PF-12) - Employee reports, performance analytics, workforce analytics

• HR-04 (Scheduling) subscribes to HR-02 credential events for automatic blocking
• HR-10 (Performance) integrates with HR-01, HR-02, HR-09, HR-14, GR-02 (✅ Complete - PIP Termination → HR-14, Competency → HR-02/GR-02)
• HR-11 (Benefits) integrates with HR-01, HR-06, HR-07, FA
• HR-12 (Self-Service) integrates with all HR modules (HR-01 through HR-11)
• HR-13 (Skills) integrates with HR-01, HR-02, HR-04, HR-09, GR-02
• HR-14 (Employee Relations) integrates with HR-01, HR-03, GR-03, GR-06, PF-10, PF-11 (✅ Phase 4 Complete)
• HR-15 (Compensation) integrates with HR-01, HR-07, HR-10, FA (✅ Phase 4 Complete)
• HR-16 (Succession Planning) integrates with HR-01, HR-10
• HR-17 (Engagement) integrates with HR-01, HR-03, PF-08
• HR-18 (Analytics) aggregates data from all HR modules (HR-01 through HR-17)

​

FW (Forms & Workflow)

• fw_workflow_templates — extended with healthcare pattern metadata (pattern_category, compliance_tags, required_node_ids, regulatory_references) (✅ Implemented)
• fw_regulatory_change_log — org-scoped regulatory change tracking for templates (✅ Implemented)

• automation_trigger → FW-03 (✅ Implemented)
• execution_failed → PF-10 (📝 Planned - FW-22)
• fw_external_form_submitted → PF-10, FW-03 (✅ Implemented - FW-32; published via pg_notify in portal-form-submit edge function)
• fw_approval_submitted → PF-10, FW-03 (📝 Planned - FW-34)
• fw_approval_completed → FW-03, PF-10 (📝 Planned - FW-34)
• fw_approval_escalated → PF-10 (📝 Planned - FW-34)

• workflow-query-action → Automation Executor (📝 Planned - FW-19)
• workflow-api-action → Automation Executor (📝 Planned - FW-19)
• workflow-debug-control → Debug UI (📝 Planned - FW-22)
• sandbox-execute → Testing UI (📝 Planned - FW-24)
• test-datasets-import → Testing UI (📝 Planned - FW-24)
• test-cases-run → Testing UI (📝 Planned - FW-24)
• approval-escalation → Scheduled cron job (📝 Planned - FW-34)

• Data Lookup (PF-15) - Dynamic form field lookups, Query action whitelist base
• Custom Fields (PF-16) - Custom field definitions
• Field Configuration (PF-17) - Field layout configuration (Phase 4/5 Complete: versioning + wizard forms)
• Workflow Variables (FW-18) - Query result storage
• Notifications (PF-10) - Failed execution alerts (FW-22), Approval notifications (FW-34)
• Permissions (PF-30) - Approval authorization (FW-34)
• Supabase Realtime - Live execution dashboard (FW-22), Approval inbox updates (FW-34)

• fw_api_connections - SFTP/API connection configs (📝 Planned)
• fw_query_whitelist - Org-specific table whitelist (📝 Planned)

• fw_execution_logs - Searchable execution logs (📝 Planned)
• fw_debug_sessions - Debug session state (📝 Planned)

• fw_test_datasets - Test data storage (📝 Planned)
• fw_test_scenarios - Scenario definitions (📝 Planned)
• fw_test_cases - Automated test cases (📝 Planned)
• fw_sandbox_executions - Sandbox execution history (📝 Planned)
• fw_test_coverage - Coverage metrics (📝 Planned)

• fw_workflow_retry_configs - Retry configuration per node (✅ Implemented)
• fw_workflow_circuit_breakers - Circuit breaker state per node (✅ Implemented)
• fw_workflow_recovery_workflows - Recovery workflow definitions (✅ Implemented)
• fw_workflow_compensation_actions - Compensation action definitions (✅ Implemented)

• fw_has_rule_org_access(rule_id, user_id) - Check org access via automation rule for RLS (✅ Implemented)

• fw_approval_chains - Approval chain definitions (📝 Planned)
• fw_approval_steps - Steps in approval chains (📝 Planned)
• fw_approval_requests - Submitted approval requests (📝 Planned)
• fw_approval_assignments - Approver assignments (📝 Planned)
• fw_approval_delegations - Delegation records (📝 Planned)
• fw_approval_history - Audit trail (📝 Planned)

• fw_user_can_view_request(request_id, user_id) - Check if user can view approval request (📝 Planned)
• fw_get_pending_approvals(user_id) - Get pending approvals for user including delegations (📝 Planned)
• fw_process_approval_action(assignment_id, action, comment, reason) - Process approval/reject action (📝 Planned)

• fw-approval-escalation - Hourly cron job for reminder/escalation processing (📝 Planned)

• fw_workflow_events - Global event registry with 11 seed events (✅ Implemented)
• fw_domain_events - Organization-scoped event log (✅ Implemented)

• /src/platform/events/ - Event publishing for all cores (✅ Implemented)
  • publishEvent() - Direct function for event publication
  • usePublishEvent() - React hook with loading state
  • Type definitions for known events

• Conditions stored in fw_workflow_definitions.node_data JSONB (✅ Implemented)

• Field discovery via useConditionAttributes hook (✅ Implemented)
• Documented in PLATFORM_INTEGRATION_LAYERS.md

• fw_workflow_executions.variables - JSONB column for variable state (✅ Implemented)
• Index: idx_fw_executions_variables - GIN index for variable queries (✅ Implemented)

• supabase/functions/_shared/expressionEvaluator.ts - Deno-compatible evaluator (✅ Implemented)

• fw_workflow_notification_rules - Notification rules per workflow (✅ Implemented)
• fw_workflow_alert_rules - Alert rules for conditions (✅ Implemented)
• fw_workflow_alerts - Active and historical alerts (✅ Implemented)
• fw_workflow_notification_preferences - User notification preferences (✅ Implemented)

• workflow-notification-trigger - Process status changes, evaluate alert rules (✅ Implemented)
• process-alert-escalations - Scheduled escalation processing (✅ Implemented)

• fw_execution_status_notification_trigger - Triggers notification on execution status change (✅ Implemented)

​

LO (Leadership Operating System)

• rock_completed → FA, PF-10, PF-04 (✅ Implemented)
• todo_created → PF-10 (✅ Implemented)
• todo_completed → PF-10, LO-03 (✅ Implemented)
• todo_overdue → PF-10 (✅ Implemented)
• scorecard_updated → PF-10, PF-12 (✅ Implemented)
• metric_threshold_breached → PF-10, LO-06 (✅ Implemented)
• meeting_scheduled → PF-10 (✅ Implemented)
• meeting_completed → PF-04, PF-10 (✅ Implemented)
• action_item_created → LO-04, PF-10 (✅ Implemented)
• issue_identified → PF-10, LO-06 (✅ Implemented)
• issue_resolved → PF-04, PF-10 (✅ Implemented)
• assessment_distributed → PF-10 (✅ Implemented)
• assessment_completed → PF-12, PF-10 (✅ Implemented)
• goal_created → FA, GR, FW (📝 Planned - LO-16)
• goal_completed → RH, FA, GR (📝 Planned - LO-16)
• action_assigned → HR, PF-10 (📝 Planned - LO-16)
• action_completed → LO-14, PF-10 (📝 Planned - LO-16)

• Forms (PF-08) - Assessment forms
• Notifications (PF-10) - Task and meeting notifications
• Documents (PF-11) - Knowledge articles
• Tasks (PF-29) - Unified task system (✅ Phase 2/3 Complete — 2026-02-27)
• Reports (PF-12) - Scorecard and assessment reports

​

FM (Facilities Management)

Full contract schemas: FM_INTEGRATION_CONTRACTS.md

• work_order_created → PF-10, FA (✅ Implemented)
• work_order_completed → FA, FM-04, FM-05, FM-06, FM-03 (✅ Implemented)
• work_order_overdue → PF-10 (✅ Implemented)
• inventory_low_stock → PF-10, FA-04 (✅ Implemented)
• inventory_item_used → FM-01, FA (✅ Implemented)
• vendor_certification_expiring → PF-10, GR (✅ Implemented)
• vendor_work_order_assigned → PF-10, FA-03 (✅ Implemented)
• pm_due → PF-10, FM-05 (📝 Planned — FM-04 publisher not yet wired)
• pm_overdue → PF-10, GR (📝 Planned)
• pm_completed → FM-05, FA (📝 Planned)
• asset_purchased → FA (📝 Planned — FM-05 publisher not yet wired)
• asset_disposed → FA, FM-04 (📝 Planned)
• asset_warranty_expiring → PF-10 (📝 Planned)
• vehicle_registered → PF-10, FM-05 (📝 Planned — FM-13 publisher)
• vehicle_status_changed → PF-10, FM-05 (📝 Planned)
• license_expiring → PF-10, GR (📝 Planned)
• registration_expiring → PF-10, GR (📝 Planned)
• fleet_maintenance_due → PF-10, FM-01 (📝 Planned)
• fleet_maintenance_overdue → PF-10, GR (📝 Planned)

• inspection_due → PF-10, GR (📝 Planned — FM-06)
• inspection_failed → PF-10, GR, FM-01 (📝 Planned — FM-06)
• inspection_compliant → GR, FM-05 (📝 Planned — FM-06)
• budget_variance_alert → PF-10, FA-08 (📝 Planned — FM-09)
• capital_project_approved → FA-09, PF-10 (📝 Planned — FM-12)
• energy_anomaly_detected → PF-10, GR (📝 Planned — FM-10 Deferred Expansion)
• space_occupancy_threshold → PF-10, HR (📝 Planned — FM-11)
• facilities_report_generated → PF-10 (📝 Planned — FM-07)

• work_order_completed → Updates vendor performance (✅ Implemented)
• purchase_order_approved → Update FM-02 inventory preferred vendor PO (📝 Planned — from FA-04)
• vendor_invoice_matched → Update FM-03 vendor WO invoice status (📝 Planned — from FA-03)
• budget_approved → Unlock FM-09 budget period for actuals (📝 Planned — from FA-08)
• it_asset_maintenance_required → Create FM work order from IT asset alert (📝 Planned — from IT)

• Forms (PF-08) — Work order forms, inspection checklists
• Workforce (Platform) — Staff assignments
• Finance (@/platform/finance) — FM cost summary interface for FM-09/FM-12 (📝 Stub per FM-16)

• GET /api/v1/fm/budgets/{id}/actuals → FA-08 (📝 Planned — FM-09)
• GET /api/v1/fm/capital-projects/{id} → FA-09 (📝 Planned — FM-12)
• GET /api/v1/fm/spaces/{id}/occupancy → HR (📝 Planned — FM-11)
• Data Lookup (PF-15) - Site and asset selectors
• Notifications (PF-10) - Work order and maintenance alerts
• Documents (PF-11) - Equipment manuals, certifications

​

GR (Governance)

• policy_created → GR-02, GR-03 (📝 Planned — GR-01)
• policy_acknowledged → GR-02, GR-03 (📝 Planned — GR-01)
• training_completed → GR-03, HR-02 (📝 Planned — GR-02)
• requirement_created → GR-04, GR-06 (📝 Planned — GR-03)
• compliance_status_changed → GR-04, GR-05, GR-06 (📝 Planned — GR-03)
• audit_created → GR-06 (✅ Complete — GR-04 / GR-UX-07)
• audit_finding_created → GR-08 (accreditation CAP), GR-05, GR-06 (✅ Complete — GR-04-EN-01; PHI-free payload; CAP auto-creation for critical/high findings)
• risk_created → GR-06 (📝 Planned — GR-05)
• risk_assessed → GR-06 (📝 Planned — GR-05)
• qi_project_created → GR-03, GR-04 (✅ Complete — GR-07 / GR-UX-08)
• accreditation_created → GR-03, GR-04 (📝 Planned — GR-08)
• incident_created → GR-05, GR-06, CL (✅ Implemented — GR-09; also see CL-GR bridge)
• incident_resolved → GR-05, GR-06 (✅ Implemented — GR-09)
• gr_incident_created → CL (chart flag), GR-14 (regulatory classification) (✅ Implemented — GR-09 trigger deployed; emits only for chart-linked incidents where custom_fields->>'chart_id' is present; GR-14 should subscribe to incident_created for all incidents; see CL-GR-CLINICAL-INCIDENT-INTEGRATION.md, GR-14 Integration)
• regulatory_report_submitted → GR-03 (compliance evidence, ✅), GR-08 (accreditation evidence, ✅), PF-10 (notification, 📝) (✅ Complete — GR-14-EN-01; idempotent via source_event_id)
• gr_state_gap_analysis_completed → PF-91 (compliance dashboard), PF-10 (critical gap notifications) (📝 Planned — GR-06-EN-01)
• procedure_approved → GR-02, GR-03, PF-10 (✅ Complete — GR-11)
• procedure_execution_completed → GR-03, PF-10 (✅ Complete — GR-11)
• procedure_gap_identified → GR-07 QI project candidate (✅ Complete — GR-13-EN-01, 2026-04-19; see GR-13 Integration)
• gr_template_instantiated → GR-03, PF-10 (📝 Planned — GR-12)
• gr_template_contributed → GR-03 (📝 Planned — GR-12)
• gr_coi_cycle_launched → PF-10 (notifications to participants), GR-03 (compliance tracking) (✅ Complete — GR-15)
• gr_whistleblower_report_submitted → PF-10 (notify compliance officer) (✅ Complete — GR-15)
• gr_template_instantiated → GR-03, PF-10 (✅ Complete — GR-12)
• gr_template_contributed → GR-03 (✅ Complete — GR-12)

• employee_created from HR → GR onboarding policy/training assignment (📝 Planned — Event Contracts)
• incident_reported from HR → GR-03, GR-04 (✅ Implemented — HR-14)
• grievance_filed from HR → GR-03 (✅ Implemented — HR-14)
• vendor_certification_expiring from FM → GR compliance check (✅ Implemented — FM Integration Contracts)
• pm_overdue from FM → GR (📝 Planned)
• inspection_due from FM → GR (📝 Planned)
• inspection_failed from FM → GR (📝 Planned)
• inspection_compliant from FM → GR (📝 Planned)
• it_security_incident_created from IT → GR (📝 Planned — IT Integration Contracts)
• it_critical_vulnerability_detected from IT → GR (📝 Planned)
• it_asset_disposed from IT → GR (📝 Planned)
• cl_safety_plan_activated from CL → GR draft incident (📝 Planned — CL-GR Bridge)
• cl_restraint_event_documented from CL → GR draft incident (📝 Planned — CL-GR Bridge)
• cl_incident_reported from CL-15 → GR-03, GR-04, GR-08 (✅ Implemented — CL-15 Integration)
• goal_completed from LO → GR (📝 Planned — LO-16)

• Forms (PF-08) — Policy acknowledgment forms, audit checklists, compliance surveys
• Notifications (PF-10) — Policy review reminders, compliance check due dates, audit finding alerts
• Documents (PF-11) — Policy documents, audit evidence, compliance certificates
• AI (PF-27) — AI Compliance Advisor (GR-06); AI contract analysis (GR-10 Phase 2, planned)
• Permissions (PF-30) — Granular permission system for GR access control
• Workflow (PF-73) — Swim lane diagram generation from GR-01 policies and GR-11 procedures (✅ Implemented)

• See GR-INTEGRATION.md for full GR integration contract anchor document.
• See GR-13-procedure-analytics-INTEGRATION.md for GR-13 procedure analytics → GR-07 / PF-12 integration contracts.
• See GR-15-nonprofit-governance-controls-INTEGRATION.md for GR-15 COI, whistleblower, board governance, and PF-46/PF-10 integration contracts.
• See CL-GR-CLINICAL-INCIDENT-INTEGRATION.md for bi-directional incident bridge with CL.

​

IT (Information Technology)

• it_asset_purchased → FA (📝 Planned)
• it_asset_assigned → PF-10, HR (📝 Planned)
• it_asset_maintenance_required → FM (📝 Planned)
• it_asset_disposed → FA, GR (📝 Planned)
• it_ticket_created → PF-10 (📝 Planned)
• it_ticket_status_changed → PF-10 (📝 Planned)
• it_sla_breached → PF-10 (📝 Planned)
• it_contract_expiring → PF-10 (📝 Planned)
• it_license_created → FA (📝 Planned)
• it_license_expiring → PF-10 (📝 Planned)
• it_license_renewed → FA (📝 Planned)
• it_license_compliance_alert → PF-10 (📝 Planned)
• it_security_incident_created → GR, PF-10 (📝 Planned)
• it_critical_vulnerability_detected → GR, PF-10 (📝 Planned)
• it_patch_deployment_overdue → PF-10 (📝 Planned)
• it_purchase_request_submitted → FW-34, PF-10 (📝 Planned)
• it_purchase_request_approved → FA-04, PF-10 (📝 Planned)
• it_purchase_request_received → IT-01, PF-10 (📝 Planned)

• /api/v1/it/assets/{asset_id} → IT-02, IT-05 (📝 Planned)
• /api/v1/it/assets → IT-02, IT-04, IT-05, IT-06 (📝 Planned)
• /api/v1/it/vendors/{vendor_id} → IT-01, IT-04, IT-06 (📝 Planned)
• it_check_license_compliance() → IT-04 Dashboard (📝 Planned)

• /api/v1/hr/employees/{employee_id} from HR (📝 Planned)
• /api/v1/hr/employees from HR (📝 Planned)

• Forms (PF-08) - Ticket submission, purchase request forms
• Workforce (Platform) - Employee assignments for assets/tickets
• Data Lookup (PF-15) - Asset, vendor, employee selectors
• Notifications (PF-10) - SLA, expiration, compliance alerts
• Documents (PF-11) - Warranties, attachments, contracts
• Approval Workflows (FW-34) - Purchase request approvals
• Custom Fields (PF-16) - Org-specific metadata on all IT entities

• IT-02 links tickets to IT-01 assets
• IT-04 links licenses to IT-01 assets and IT-03 vendors
• IT-05 links patches/vulnerabilities to IT-01 assets
• IT-06 uses IT-03 vendors and creates IT-01 assets on receipt

​

CE (Community Engagement / CRM)

• ce.email.synced → CE-04 (📝 Planned - CE-07) - Auto-create activity
• ce.email.tracking → PF-10 (📝 Planned - CE-07) - Open/click notifications
• ce.sms.sent → CE-04 (📝 Planned - CE-08) - Auto-create activity
• ce.sms.received → CE-04 (📝 Planned - CE-08) - Auto-create activity
• ce.campaign.started → PF-10 (📝 Planned - CE-09) - Campaign notifications
• ce.campaign.completed → CE-05 (📝 Planned - CE-09) - Analytics update
• ce_web_form_submitted → CE-01, CE-05 (📝 Planned - CE-10) - Lead creation
• ce_screening_completed → PM-38, PM-39, CE-29 (📝 Planned - CE-28) - Screening disposition triggers appointment/waitlist/conversion
• ce_lead_waitlisted → PM-39 (📝 Planned - CE-28) - Screened lead routed to waitlist (no bed available)
• ce_crisis_alert_created → PF-83, PF-10, CE-29 (📝 Planned - CE-28-ENHANCEMENTS EN-01) - Crisis-keyword detection on inbound intake; ID-only payload (no PHI)

• N/A (CE is primarily a publisher of CRM events)

• N/A (internal module APIs only)

• /api/v1/hr/employees/{employee_id} from HR (📝 Planned) - Contact assignment
• /api/v1/hr/employees from HR (📝 Planned) - Staff search

• Notifications (PF-10) - Email tracking alerts, SMS delivery
• Documents (PF-11) - Email attachments
• Reports (PF-12) - Campaign analytics (CE-05)
• Custom Fields (PF-16) - Contact/partner custom data

• CE-07 creates activities in CE-04 via database trigger
• CE-08 creates activities in CE-04 via database trigger
• CE-07 links emails to CE-01 contacts and CE-02 partners
• CE-08 links SMS to CE-01 contacts
• CE-09 creates leads in CE-01 contacts
• CE-10 creates leads in CE-01 and triggers CE-09 campaign tracking

• Gmail API (OAuth 2.0) - CE-07
• Microsoft Graph API (OAuth 2.0) - CE-07
• RingCentral SMS API - CE-08

​

CL (Clinical & EHR)

• assessment_completed → PM (optional), FW, PF-10 (📝 Planned) — Event Contracts
• treatment_plan_signed → FW, PF-10 (📝 Planned)
• progress_note_signed → PM (charge capture), PF-10 (📝 Planned)
• medication_recon_completed → PF-10 (📝 Planned)
• prescription_sent → PM, PF-10 (📝 Planned)
• pdmp_query_completed → CL (audit) (📝 Planned) — CL-17
• cl_lab_order_created → PF-10, FW (📝 Planned) — CL-09
• cl_lab_result_received → CL-08, PF-10 (📝 Planned) — CL-09
• cl_lab_result_reviewed → PF-10, PF-04 (📝 Planned) — CL-09

• prior_auth_required from PM (📝 Planned)
• prior_auth_received from PM (📝 Planned)
• eligibility_verified from PM (📝 Planned)
• patient_registered from PM (📝 Planned)
• appointment_scheduled from PM (📝 Planned)
• encounter_completed (CL/PM) (📝 Planned)

• CL Consent Service — Consent evaluation (Part 2, TPO); CL-11
• CL Billing Adapter — Encounter-to-charge context; PM-07, CL-04
• CL Document Export (EHI) — FHIR/USCDI export; CL-16

​

PM (Practice Management)

• claim_submitted → FA (optional), PF-10 (📝 Planned) — Event Contracts
• claim_adjudicated → PM-09, PF-10 (📝 Planned)
• prior_auth_required → CL, PF-10 (📝 Planned)
• prior_auth_received → CL, PM-07/08, PF-10 (📝 Planned)
• eligibility_verified → CL, PM-07, PF-10 (📝 Planned)
• patient_registered → CL, RH (optional), PF-10 (📝 Planned)
• appointment_scheduled → CL, PF-10 (📝 Planned)
• encounter_completed (CL/PM) → PM (charge capture), PF-10 (📝 Planned)
• pm.fhir_app_authorized → PF-04 audit, GR (📝 Planned, PM-55)
• pm.fhir_app_revoked → PF-04 audit, GR (📝 Planned, PM-55)
• pm.fhir_information_blocking_logged → GR-08 incident reporting (📝 Planned, PM-55)
• pm.fhir_access_logged → PF-04 audit stream (📝 Planned, PM-55)

• assessment_completed from CL (optional billing) (📝 Planned)
• treatment_plan_signed from CL (📝 Planned)
• progress_note_signed from CL (charge capture) (📝 Planned)
• prescription_sent from CL (📝 Planned)
• cl.part2_consent_granted / cl.part2_consent_revoked from CL-11 (📝 Planned, PM-55) — re-evaluate active FHIR app consents that include SUD scopes

• CL Consent Service — TPO/Part 2 gating for billing
• CL Billing Adapter — Charge capture context from encounters
• CL Document Export (EHI) — PM-12 patient access, EHI export

​

Dependency Graph

Platform Foundation (PF)
    ↓
    ├─→ Forms (PF-08) → All Cores
    ├─→ Workforce → RH, FA, GR, IT
    ├─→ Data Lookup (PF-15) → FW, HR, RH, IT
    ├─→ Custom Fields (PF-16) → All Cores
    ├─→ Field Config (PF-17) → All Cores (Phase 4/5 ✅)
    ├─→ Notifications (PF-10) → All Cores
    ├─→ Documents (PF-11) → All Cores
    └─→ Reports (PF-12) → All Cores

Event-Based Integration:
    RH → FA (resident admission/discharge)
    FA → RH (payment received)
    HR → RH (employee assignment)
    HR → GR (employee created)
    HR-02 → HR-04 (credential expired → scheduling block)
    FW → FW-03 (form submission)
    FA → FW-03, PF-10 (financial events)
    LO → FA, PF-10 (leadership events)
    FM → PF-10, GR (vendor certification expiring)
    FM → PF-10, FA-03 (vendor work order assigned)
    FM → FA, FM-04, FM-05 (work order completed)
    IT → FA (asset purchased, license costs)
    IT → FM (asset maintenance required)
    IT → GR (security incidents)
    IT → PF-10 (SLA, expiration, compliance alerts)
    IT-06 → FW-34 (procurement approval workflow)
    CL-09 → CL-08, PF-10 (lab result received → abnormal alert)
    External Labs → CL-09 (result ingestion via HL7v2/FHIR)

API Contracts:
    FA → RH (episode balance query)
    HR → RH (employee lookup/search)
    IT → IT-02, IT-05 (asset lookup)
    IT → IT-01, IT-04, IT-06 (vendor lookup)

​

Integration Pattern Usage

​

When to Use Each Pattern

• ✅ Multiple cores need the same functionality
• ✅ Reusable UI components or hooks
• ✅ Domain-agnostic functionality
• Examples: Forms, Workforce, Data Lookup, Custom Fields

• ✅ Loose coupling between cores
• ✅ Asynchronous workflows
• ✅ Audit trails of state changes
• Examples: Resident admission → Billing account creation

• ✅ Synchronous request-response
• ✅ Real-time data queries
• ✅ Event-driven patterns not suitable
• Examples: Episode balance queries, Employee lookups

​

Spec Coverage Index (Q2 2026 closure waves)

Status meanings as of 2026-04-17 closure pass: ✅ contract documented and matches implementation; 📝 contract documented as planned (spec implementation pending); 🟡 contract partially documented; the spec is implemented but the contract surface here is the new authoritative summary.

​

CE — Community Engagement (Wave CE)

​

CL — Clinical (Wave CL)

​

FA — Finance & Accounting (Wave FA)

​

FM — Facilities Management (Wave FM)

​

FW — Forms & Workflow (Wave FW)

​

GR — Governance & Risk (Wave GR)

​

HR — Human Resources (Wave HR)

​

IT — IT Asset Management (Wave IT)

​

LO — Leadership Operating System (Wave LO)

​

PF — Platform Foundation (Wave PF)

​

PM — Practice Management (Wave PM)

​

RH — Recovery Housing (Wave RH)

​

Related Documentation

• Platform Integration Layers - Detailed platform layer documentation
• Event Contracts - Detailed event schemas
• API Contracts - Detailed API documentation
• Data Models - Core data model documentation

​

Quick Reference Guide

​

Integration Pattern Decision Tree

• ✅ Yes → Platform Integration Layer (Pattern 1)
  • Examples: Forms, Workforce, Data Lookup, Custom Fields, Notifications, Documents, Reports

• ✅ Yes → Event-Based Integration (Pattern 2)
  • Examples: Resident admission → Billing account creation, Credential expiry → Scheduling block

• ✅ Yes → API Contract (Pattern 3)
  • Examples: Episode balance query, Employee lookup

​

Common Integration Scenarios

• ✅ Use: Platform Workforce Integration Layer (EmployeeSelector, useEmployeeLookup)
• ❌ Don’t: Direct import from HR core

• ✅ Use: Event-Based Integration (rh_resident_admitted in fw_domain_events; alias resident_admitted deprecated)
• ❌ Don’t: Direct function call from RH to FA

• ✅ Use: API Contract (/api/v1/fa/episode-balance)
• ❌ Don’t: Direct database query to FA tables

• ✅ Use: Event-Based Integration (subscribe to credential_expired event)
• ❌ Don’t: Poll HR-02 credential tables

​

Integration Status Summary

• ✅ Complete: 7
• 🟡 In Progress: 0
• 📝 Planned: 0

• ✅ Implemented: 22 (including FM-03 vendor events)
• 📝 Planned: 28+ (including 18 IT module events)

• ✅ Implemented: 0
• 📝 Planned: 7 (including 4 IT module APIs)

​

Status Legend