Skip to main content
Version: 1.0.0 Last Updated: 2026-02-17 Constitution Reference: Section 1.2 (Core Independence), Section 1.3 (Integration Patterns) Source: CL-PM-SPEC-REVIEW Findings 1.3, 3.4

Overview

Group sessions involve both scheduling (PM-04) and clinical documentation (CL-14). This contract defines which core owns which data to prevent duplication and divergence.

Ownership Boundaries

Key Principle: PM-04 is the source of truth for scheduling. CL-14 is the source of truth for clinical documentation (actual service times, actual facilitator, actual location). When schedule_id is set, CL-14 columns may be pre-populated from PM-04 but are authoritative for documentation and billing purposes. Billing data (CPT codes, modifiers) is determined by PM-07 at charge capture time, NOT stored in CL-14.

Data Linkage

CL-14 cl_group_sessions links to PM-04 scheduling via Platform Integration Layer:

Field Deduplication

Fields that currently exist in both specs must be consolidated:

Billing Integration (Finding 3.4 Resolution)

Remove billing_code from cl_group_attendance. The HQ modifier and CPT code are determined by PM-07 at charge capture time based on:
  1. Participant count from cl_group_attendance (≥2 for HQ modifier)
  2. Session duration from cl_group_sessions.actual_start_time / actual_end_time
  3. Service type from pm_group_definitions.group_type
  4. AHCCCS timed code rules from PM-07 fee schedule

Event: cl_group_session_documented

Publisher: CL-14 Subscribers: PM-07 Channel: cl_events
PM-07 creates one charge per present attendee with:
  • HQ modifier (if participant_count ≥ 2)
  • AHCCCS timed units from duration
  • CPT from group type mapping

IOP/PHP Compliance Tracking

IOP (9+ hrs/week, 3+ days) and PHP (20+ hrs/week, daily) compliance requires aggregating group attendance across a week. This is a PM reporting concern (PM-11) that reads from CL-14 attendance data via a Platform Integration Layer query or materialized view.

Cross-Reference