Created: 2026-01-23
Status: 📋 Specification
Overview
This document defines the integration contract between CE-05 (Pipeline & Reporting) and PF-12 (Reports System). CE-05 creates report definitions in PF-12 for scheduled report generation and export functionality.Integration Pattern
Pattern: Platform Integration Layer (Pattern 1)Direction: CE-05 → PF-12 (CE-05 is the consumer)
Report Definitions
Lead Pipeline Report
Partner Scorecard Report
Call Analytics Report
Activity Analytics Report
Scheduled Reports
Default Schedules
PHI/PII Protection
- Secure Storage: Reports generated to access-controlled storage referenced by
pf_report_schedules - Notification Only: Email via PF-10 contains secure portal link only, no PHI/PII
- Auto-Expiry: Generated reports auto-expire after 30 days
- Audit Logging: All report access logged to
pf_audit_logs
Role-Based Recipients
Recipients pulled from user roles, not hardcoded:- Program Director → Lead Pipeline, Activity Analytics
- Business Development Director → Partner Scorecard
- Supervisor → Call Analytics
API Contract
Export Report (Synchronous)
Schedule Report (Admin Only)
Error Handling
Dependencies
Required PF-12 Tables
pf_reports- Report definitionspf_report_schedules- Scheduled report configurationspf_report_executions- Execution historypf_report_permissions- Permission mappings
Required Views (CE-05)
ce_lead_pipeline_metricsce_partner_scorecardce_call_analyticsce_activity_analytics
Testing Requirements
Integration Tests
- Report definition exists in
pf_reports - Report generates successfully with sample data
- Scheduled report executes on schedule
- Export respects permission keys
- PHI/PII protection in email notifications
Security Tests
- Cross-organization access blocked
- Permission keys enforced
- Audit logging verified
- Auto-expiry working
References
- PF-12 Spec:
specs/pf/specs/PF-12-reports-system.md - CE-05 Spec:
specs/ce/specs/CE-05-pipeline-reporting.md - Integration Patterns:
docs/architecture/integrations/index.md