> ## Documentation Index
> Fetch the complete documentation index at: https://coloradobehavioralhealthadministration.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Model Overview

> Understanding the CoBHRM schema hierarchy and relationships

## Schema Hierarchy

CoBHRM follows a hierarchical structure where records are linked through unique identifiers. Understanding these relationships is essential for successful data submission.

## Record Type Codes

Each schema is identified by a unique record type code:

| Code | Schema | Description | Parent Record |
| - | - | - | - |
| `CLI` | Client | Demographics and identifiers | None (root) |
| `ADM` | Admission | Treatment episode admission | Client |
| `DIS` | Discharge | Treatment episode discharge | Admission |
| `DXA` | Diagnosis at Admission | Clinical diagnoses at intake | Admission |
| `DXD` | Diagnosis at Discharge | Clinical diagnoses at discharge | Discharge |
| `SIA` | Substance Use at Admission | Substance use information at intake | Admission |
| `SID` | Substance Use at Discharge | Substance use information at discharge | Discharge |
| `ACT` | ACT | Assertive Community Treatment data | Admission |
| `ASA` | Ascent Admission | Youth residential admission | Admission |
| `ASQ` | Ascent Quarterly | Youth residential quarterly assessment | Ascent Admission |
| `ASD` | Ascent Discharge | Youth residential discharge | Ascent Admission |
| `BAB` | SC Baby | Special Connections baby outcomes | Admission |
| `PRS` | SC Pregnancy Risk | Special Connections pregnancy risk | Admission |

## Key Identifiers

### Linking Identifiers

Records are linked using these key fields:

| Field | Description | Present On |
| - | - | - |
| `RECORD_TYPE` | Identifies the schema (e.g., `CLI`, `ADM`, `DXA`) | All schemas |
| `BHASO_CLIENT_IDENTIFIER` | Unique client ID assigned by BHASO | Client, Admission |
| `BHASO_ADMISSION_IDENTIFIER` | Unique treatment episode ID | Admission and all child records |

### Versioning

| Field | Description | Present On |
| - | - | - |
| `EFFECTIVE_DATE` | Determines the most recent version of a record (SCD Type 2) | All schemas |

> [!NOTE]
>
> `EFFECTIVE_DATE` is not a primary key used for linking records. It is a versioning mechanism — see [Transaction Types](https://coloradobehavioralhealthadministration.mintlify.site/getting-started/transaction-types.md) for details.

### Linking Records

**1. Client Record**

Create a CLIENT (CLI) record first with a unique `BHASO_CLIENT_IDENTIFIER`

**2. Admission Record**

Create an ADMISSION (ADM) record that references the client via `BHASO_CLIENT_IDENTIFIER` and assigns a unique `BHASO_ADMISSION_IDENTIFIER`

**3. Child Records**

Create related records (Diagnosis, Substance Use, etc.) that reference the parent Admission via `BHASO_ADMISSION_IDENTIFIER`

**4. Discharge Record**

Create a DISCHARGE (DIS) record when the treatment episode ends, referencing the same `BHASO_ADMISSION_IDENTIFIER`

## Cardinality

| Relationship | Cardinality | Notes |
| - | - | - |
| Client → Admission | 1:M | One client can have multiple admissions |
| Admission → Discharge | 1:0..1 | One discharge per admission (none while active) |
| Admission → Diagnosis (ADM) | 1:1 | One diagnosis record per admission (up to 3 MH + 1 SUD ICD codes within the record) |
| Discharge → Diagnosis (DIS) | 1:1 | One diagnosis record per discharge (up to 3 MH + 1 SUD ICD codes within the record) |
| Admission → Substance Use (ADM) | 1:0..1 | Required for SUD admissions; omitted for MH-only |
| Discharge → Substance Use (DIS) | 1:0..1 | Required for SUD discharges; omitted for MH-only |
| Admission → ACT | 1:0..M | Monthly records; multiple if episode > 30 days |
| Admission → Ascent (ASA) | 1:0..1 | One Ascent admission per treatment episode (only if enrolled) |
| Ascent (ASA) → Quarterly (ASQ) | 1:0..M | Quarterly assessments; multiple if episode > 90 days |
| Ascent (ASA) → Discharge (ASD) | 1:0..1 | One Ascent discharge |
| Admission → SC Pregnancy Risk (PRS) | 1:0..M | Required if enrolled in Special Connections; multiple if status changes (e.g., pregnant to postpartum) |
| Admission → SC Baby (BAB) | 1:0..M | Required if enrolled in Special Connections; multiple for twins/triplets |

## Background

CoBHRM is the result of a long-running effort to unify Colorado's behavioral health data systems. Previously known as the "Data Integration Initiative" and the "Unified Data Model," the project merges legacy CCAR (mental health) and DACODS (substance use) reporting into a single model. CoBHRM goes live on **July 1, 2026**.

## Version History

The current frozen specification is **CoBHRM 2026-Q3**.

> [!NOTE]
>
> When submitting records, always use the current CoBHRM version specifications to ensure compatibility with the BHA data warehouse.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.