CSV

Behavioral Health Public County Profile - Overview

The Overview file provides a consolidated summary of a County Behavioral Health Departments contact information, County Population, Medi-Cal Managed Care Plans operating within a county, County Medi-Cal Enrollment, and previous County Behavioral Health Medi-Cal services.

Download Resource< Back to dataset

Data dictionary

Field definitions supplied by the publishing agency in CKAN.

Column	Type	Label	Description
COUNTY_NAME	text	County Name	County The official name of the county associated with the record or reporting area.
TOTAL_POP	text	Total Population	The total population count for the county.
MEDI_CAL_ENROLLMENTS	text	Medi-Cal Enrollments	The total number of individuals enrolled in Medi-Cal within the county.
PENETRATION_RATE_COUNTY_MHS	text	Penetration Rate of County Mental Health Services	The percentage of Medi-Cal enrolled individuals who received county mental health services during calendar year 2024.
PENETRATION_RATE_SUDS	text	Penetration Rate of Substance Use Disorder Treatment Services	The percentage of Medi-Cal enrolled individuals who received substance use disorder treatment services during calendar year 2024.
ANNUAL_COUNTY_EXP	text	Annual County Expenditures	The total annual county expenditures related to behavioral health or Medi-Cal services. Not available until 2029.
MCP	text	Managed Care Plan	The name of the Managed Care Plan (MCP) associated with the county or services provided.
MENTAL_HEALTH_ADDRESS	text	Mental Health Address	The address of the county mental health services office or provider location.
SUD_ADDRESS	text	Substance Use Disorder Address	The address of the county substance use disorder (SUD) services office or provider location.

Resource details

Format	CSV
Last updated	Oct 7, 2026
Part of	Behavioral Health Public County Profile

Other resources in this dataset

CKAN Data API

Access resource data through the CKAN DataStore API. The examples below use this resource's ID.

Endpoints

The Data API provides these actions. Creating or updating records requires appropriate permissions; the query actions read public DataStore records.

Create	`https://ckan.cdt.dev.datopian.com/api/3/action/datastore_create`
Update / insert	`https://ckan.cdt.dev.datopian.com/api/3/action/datastore_upsert`
Query	`https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search`
Query via SQL	`https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql`

Query examples

First five results

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=1aea20e2-3526-47a8-9463-430ee253eee2&limit=5"

Results containing "jones"

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=1aea20e2-3526-47a8-9463-430ee253eee2&q=jones"

SQL query

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%221aea20e2-3526-47a8-9463-430ee253eee2%22%20LIMIT%205"

SQL queries depend on whether SQL search is enabled by the portal.

OData query

Use the resource's OData URL and its field names for paging, selecting columns, or filtering rows.

ODATA_RESOURCE_URL?$top=5
ODATA_RESOURCE_URL?$skip=5&$top=5
ODATA_RESOURCE_URL?$select=FIELD_NAME&$filter=FIELD_NAME eq 'VALUE'

Replace ODATA_RESOURCE_URL, FIELD_NAME, and VALUE with the details for the selected resource. See the OData query options guide (opens in a new tab) for more examples.

Use the API in code

JavaScript (JSONP)

var data = { resource_id: '1aea20e2-3526-47a8-9463-430ee253eee2', limit: 5, q: 'jones' };
$.ajax({
  url: 'https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search',
  data: data,
  dataType: 'jsonp',
  success: function (response) {
    console.log(response.result.total, response.result.records);
  }
});

Python

import json
from urllib.request import urlopen

url = 'https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=1aea20e2-3526-47a8-9463-430ee253eee2&limit=5'
with urlopen(url) as response:
    result = json.load(response)['result']
print(result['total'], result['records'])

For parameters and response fields, see the CKAN DataStore documentation (opens in a new tab).