Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Version: 1.0.0
Last Updated: 2026-03-28
Module: CE (Community Engagement)
Status: Active
Purpose: This guide helps administrators configure screening questionnaires, SLA thresholds, and permission assignments.

​
Overview

CE-28 Intake Screening requires configuration at the organization level. Admins manage questionnaire templates, SLA thresholds, and user permissions.

​
Configuration

​
SLA Thresholds

SLA thresholds define the maximum allowed time between lead creation and screening completion. Table: ce_screening_sla_config
FieldDescriptionDefault
program_typeProgram type (residential, iop, php, outpatient)—
response_minutesMax minutes allowed before SLA is “missed”240 (4 hours)
site_idOptional site-specific overridenull (org-wide)
To configure:
  1. Navigate to CE module settings
  2. Locate SLA Configuration section
  3. Set thresholds per program type
  4. Optionally override per site

​
Screening Questionnaires

Questionnaire templates define the screening form structure. Table: ce_screening_questionnaires
FieldDescription
nameTemplate name (e.g., “Standard Intake Screen”)
versionVersion number for template evolution
schemaJSONB questionnaire field definitions
asam_scoring_rulesOptional ASAM scoring configuration
triage_rulesOptional custom triage rules

​
Permissions

Permission KeyDescriptionTypical Roles
ce.screening.viewView screening recordsAll CE staff
ce.screening.createCreate new screeningsIntake coordinators
ce.screening.manageConfigure SLA, manage questionnairesAdmissions managers

​
Security & Compliance

For substance use disorder screenings, the system enforces:
  • consent_obtained must be true before saving
  • consent_method must be populated
  • consent_recorded_at is auto-set on save
Events are only published when consent is verified via the application path. This behavior is enforced by application logic (defense-in-depth). Direct database access with elevated privileges may bypass application-layer controls — database-level controls (RLS, audit logging) provide additional enforcement.

​
Data Access

  • All screening data is scoped by organization_id via RLS
  • Cross-organization access is blocked at the database level
  • Clinical free-text (chief complaint, notes) is never included in event payloads

​
Audit Trail

All screening attempts are append-only with created_by and updated_by audit columns.

​
Troubleshooting

​
SLA Dashboard shows no data

Cause: No screening attempts exist or date range filter is too narrow. Solution: Verify screenings exist; adjust date range.

​
Users cannot see Screening tab

Cause: Missing ce.screening.view permission. Solution: Assign the permission via the RBAC admin panel.
  • User Guide: docs/ce/ce-28-intake-screening-user-guide.md
  • Specification: specs/ce/specs/CE-28-intake-screening-triage-workflow.md
  • Integration: docs/architecture/integrations/CE-28-INTAKE-SCREENING-INTEGRATION.md
Last Updated: 2026-03-28
Questions? Contact your organization administrator.