CL-PM Integration Contract: Referrals

interface ReferralAccepted {
  event: 'referral_accepted';
  publisher: 'PM';
  subscriber: ['CL'];
  payload: {
    referral_id: uuid;
    patient_id: uuid;
    referral_direction: 'inbound' | 'outbound';
    from_facility?: string;
    to_facility?: string;
    from_level_of_care?: string;
    to_level_of_care?: string;
    referral_reason: string;
    urgency: 'routine' | 'urgent' | 'emergent';
  };
  metadata: {
    organization_id: uuid;
    user_id: uuid;
    timestamp: string;
    correlation_id: uuid;
  };
}

-- CL-12 adds this column to cl_transitions
referral_id UUID  -- References pm_referrals.id via Platform Integration Layer
                  -- NOT a direct FK (would violate core independence)
                  -- Validated at application layer, not database level

PM-06: Referral created (outbound, status = 'pending')
  ↓
PM-02: Insurance eligibility verified at destination
  ↓
PM-06: Referral accepted (status = 'accepted')
  → publishes referral_accepted event
  ↓
CL-12: Creates cl_transitions record (type = 'referral')
  ↓ (parallel)
CL-05: Medication reconciliation triggered
CL-07: Safety plan reviewed/updated
CL-16: C-CDA transition summary generated
CL-03: Treatment plan review triggered
  ↓
CL-12: Transition checklist completed
  → publishes transition_completed event
  ↓
PM-06: Referral status updated to 'completed'