Skip to main content
Development Note: We are testing alternative layouts for schema field references. Compare this page against the API-style card layout and the compact 4-column table layout in the Experimental Schema Layouts section, then share your feedback.
Record Type: CLI | Version: CoBHRM 2026-Q3 | Parent: None | Children: ADMISSION

Overview

The CLIENT schema captures core demographic information for individuals receiving behavioral health services. This is the root record type - all other records reference a client through the BHASO_CLIENT_IDENTIFIER.
Transaction Types: All record types support Add (A), Update (U), and Replace (R) transactions. See Transaction Types for details.

1. Schema Reference

Identifier Fields

Data Fields

System Metadata Fields

These fields are required in every submission and track record creation and modification:

2. Examples

Minimal Valid Example

Only required fields populated. This is an adult male client in Denver with no disabilities.

Complete Example

Female client with Medicaid, multiple races, child welfare involvement, and full address. Most optional fields populated.

Edge Cases

Multi-value race fields (semicolon-space delimited), international characters in name, and an out-of-state client.
The client above is out-of-state (COUNTY_RESIDENCE = 77), so ZIPCODE_RESIDENCE is not required. The SSN 000-00-0000 indicates “No SSN.” International characters like ü and ç are supported via UTF-8 encoding.

3. Template

View CLIENT Template

CLIENT schema template with headers and sample row

4. Parsing Rules

CSV Parsing Rules

See File Format Requirements for full details on encoding, quoting, data types, and null handling.
Multi-value delimiter: RACE_CODES and DISABILITY_CODES use semicolon + space (; ) to separate multiple values within a single field.

5. Update Semantics

Primary Key

RECORD_TYPE + BHASO_CLIENT_IDENTIFIER

Transaction Types

Idempotency

  • Most recent record determined by EFFECTIVE_DATE
  • System uses SCD Type 2 - all historical records retained
  • Query for “current” client returns record with latest EFFECTIVE_DATE

Last modified on March 26, 2026