> ## 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.

# Quickstart

> Get oriented in Encore OS in two minutes — what it is, who it's for, and how to find what you need.

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:

<CardGroup cols={3}>
  <Card title="HIPAA Security Rule" icon="shield-halved">
    Administrative, physical, and technical safeguards for ePHI across every workflow.
  </Card>

  <Card title="SOC 2 Type II" icon="file-shield">
    Trust Services Criteria for security, availability, processing integrity, confidentiality, and privacy.
  </Card>

  <Card title="42 CFR Part 2" icon="user-shield">
    Heightened protections for substance use disorder records, with application-level consent and SUD tagging built in.
  </Card>
</CardGroup>

The full policy library, regulatory crosswalks, and evidence package live in [Governance & Compliance](/gr/overview).

## Find your starting point

<CardGroup cols={2}>
  <Card title="Clinician" icon="stethoscope" href="/cl/overview">
    Patient charts, progress notes, treatment plans, telehealth, e-prescribing, and clinical decision support.
  </Card>

  <Card title="Practice administrator" icon="briefcase" href="/pm/overview">
    Scheduling, patient lifecycle, billing, claims, revenue cycle, and front-office operations.
  </Card>

  <Card title="Recovery housing operator" icon="house" href="/rh/overview">
    Beds, residents, episodes, programs, daily operations, and post-discharge outcomes.
  </Card>

  <Card title="Finance / RCM" icon="dollar-sign" href="/fa/overview">
    General ledger, AR/AP, banking, budgets, forecasts, and financial close.
  </Card>

  <Card title="HR / People ops" icon="users" href="/hr/overview">
    Recruiting, onboarding, payroll, benefits, scheduling, credentialing, and performance.
  </Card>

  <Card title="Compliance officer" icon="shield-halved" href="/gr/overview">
    Policy library, accreditation, audits, risk register, training, and incident management.
  </Card>

  <Card title="IT / Security" icon="headset" href="/it/overview">
    Tickets, assets, access provisioning, change management, vulnerabilities, and IT compliance.
  </Card>

  <Card title="Engineer / Integrator" icon="code" href="/architecture/index">
    Architecture, data models, ADRs, integrations, and platform internals.
  </Card>
</CardGroup>

## 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](https://llmstxt.org) for AI assistants and indexing tools. Point your agent at:

* [`/llms.txt`](/llms.txt) — structured index of every page
* [`/llms-full.txt`](/llms-full.txt) — full-text dump of the entire corpus

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](/gr/overview) 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.