Skip to main content
Welcome to Encore OS — a healthcare-grade ERP for behavioral health and recovery housing operations. This page is a two-minute orientation. Pick the path that matches your role and follow the link.

​
Compliance posture

Encore OS is built against three regulatory frameworks from day one. Every module, integration, and audit trail is designed to satisfy:

HIPAA Security Rule

Administrative, physical, and technical safeguards for ePHI across every workflow.

SOC 2 Type II

Trust Services Criteria for security, availability, processing integrity, confidentiality, and privacy.

42 CFR Part 2

Heightened protections for substance use disorder records, with application-level consent and SUD tagging built in.
The full policy library, regulatory crosswalks, and evidence package live in Governance & Compliance.

​
Find your starting point

Clinician

Patient charts, progress notes, treatment plans, telehealth, e-prescribing, and clinical decision support.

Practice administrator

Scheduling, patient lifecycle, billing, claims, revenue cycle, and front-office operations.

Recovery housing operator

Beds, residents, episodes, programs, daily operations, and post-discharge outcomes.

Finance / RCM

General ledger, AR/AP, banking, budgets, forecasts, and financial close.

HR / People ops

Recruiting, onboarding, payroll, benefits, scheduling, credentialing, and performance.

Compliance officer

Policy library, accreditation, audits, risk register, training, and incident management.

IT / Security

Tickets, assets, access provisioning, change management, vulnerabilities, and IT compliance.

Engineer / Integrator

Architecture, data models, ADRs, integrations, and platform internals.

​
How these docs are organized

  • Product — every functional module: Clinical, Practice Management, Finance & Revenue, Recovery Housing, Workforce & HR, Community Engagement, Governance & Compliance, Forms & Workflow, Facilities & Inventory, IT Service Management, Leadership, and Platform Foundation.
  • Engineering — architecture, ADRs, data models, database schema, testing, and operational runbooks.
  • Changelog — release notes and what changed across the platform.
Each domain group opens with an overview page that explains scope, key responsibilities, and key surfaces.

​
Using these docs with AI

The docs corpus is published in the llms.txt convention for AI assistants and indexing tools. Point your agent at: Both are kept in sync with the published docs automatically.

​
What’s next

No separate setup is required to read the docs — just follow the cards above to your area. If you’re evaluating Encore OS or want a single document to share with stakeholders, the Governance & Compliance section is the best starting point for the compliance story, and each module’s overview page (*_OVERVIEW) is the best starting point for that module’s capabilities.