Elixir
Request a Demo
  • Electronic Health Record (EHR)Products
  • Revenue Cycle ManagementProducts
  • Eligibility VerificationProducts › Revenue Cycle Management
  • Electronic Prior AuthorizationProducts › Revenue Cycle Management
  • Denial ManagementProducts › Revenue Cycle Management
  • Professional and Institutional Claim PreparationProducts › Revenue Cycle Management
  • Electronic Visit VerificationProducts
  • Caregiver Mobile AppProducts › Electronic Visit Verification

Behavioral HealthEHR Software forConnected,Measurable Care

One Salesforce-native platform for mental health and substance use disorder treatment — because a large share of the people you treat have both, and two systems means the clinician treating one cannot see the other.

Request a DemoMental health or substance use
Clinicians reviewing a shared patient record on a tablet with a patient in a care team meeting

  • Connected

    One record across programs, sites and states. A patient moving between services keeps their history rather than starting a new one.

  • Measurable

    Outcomes collected on schedule, trended where clinicians look, and reportable to a payer, a board or a state.

  • Compliant by construction

    42 CFR Part 2 and HIPAA controls in the record itself, with consent and disclosure trails that survive an audit.

  • Configurable

    Built on Salesforce, so a new state, program, payer or level of care is configuration rather than custom code.

The case for one platform

Why Behavioral Health Needs One Record, Not Two Systems

Co-occurring mental health and substance use conditions are not an edge case in behavioral health. They are close to the default.

  1. 01

    Organizations rarely choose two systems deliberately. They acquire one, add a service line, buy something specialized for it, and end up with a mental health record and a substance use record that do not speak — usually justified by a belief that 42 CFR Part 2 requires the separation.

    The legacy split

  2. 02

    It does not. Part 2 protections attach to substance use disorder records specifically, not to the whole patient. The correct answer is separation within the record, with its own consent and disclosure trail, rather than a second system with its own login, its own intake, and its own version of the patient’s medication list.

    Within-record segregation

  3. 03

    The cost of the split lands on the clinician. A prescriber treating depression cannot see the buprenorphine. A counsellor cannot see last week’s crisis contact. A utilization review nurse rebuilds a history that already exists. And the organization cannot answer the question a payer increasingly asks — what happened to this person across all of their care — because no single system ever held it.

    Clinical fragmentation cost

Two paths

Mental Health and Substance Use Disorder EHR on One Platform

The same record, the same configuration model and the same AI governance — with the clinical depth each side actually needs. Start wherever your organization starts.

Service line 01

Mental Health EHR

For outpatient and community behavioral health programs — clinic-based therapy and psychiatry, community teams working in the field, and integrated care embedded in primary care.

  • Scheduled outcomes (PHQ-9, GAD-7, Columbia-SSRS, WHODAS) with trend charts clinicians actually look at
  • Therapy note templates (SOAP, DAP, BIRP, EMDR, group therapy) configured to state Medicaid and commercial rules
  • Mobile, offline-capable documentation for ACT, ICM, mobile crisis and street medicine teams
  • Full psychiatric prescribing: EPCS, PDMP integration, state-mandated vitals and lab tracking for antipsychotics
  • Collaborative Care Model (CoCM) support: psychiatric registry, systematic reviews, monthly billing calculation
  • Billing for behavioral health: incident-to rules, supervised billing, state Medicaid fee schedules, interactive complexity
Explore the mental health EHR

Service line 02

Substance Use Disorder EHR

For addiction treatment across every level of care — outpatient and intensive outpatient through residential, withdrawal management and medically managed inpatient.

  • Native 42 CFR Part 2 consent engine: granular disclosure tracking, consent expiry, re-disclosure notices
  • ASAM Criteria 4th Edition assessment alignment and multi-dimensional placement documentation
  • Withdrawal management workflows (CIWA-Ar, COWS, vital sign triggers) linked to medication administration
  • Medication-Assisted Treatment (MAT / MOUD) support: buprenorphine, naltrexone, OTP dosing integration
  • Residential and bed management: census tracking, room assignments, observation rounds and discharge planning
  • Toxicology and lab interface: urine drug screen ordering, result ingestion, mismatch alerts against reported use
Explore the substance use disorder EHR

Connected

One Record Across Programs, Sites and States

A person in behavioral health treatment rarely stays in one place. The record should be the thing that does not change when everything else does.

  1. 01

    Referral and intake

    One enquiry queue across programs, with eligibility verified and screening captured once — not re-asked at every handoff.

    Unified Intake

  2. 02

    Assessment and placement

    The right assessment for the service, feeding a documented placement decision with the clinician’s rationale attached.

    Clinical Rationale

  3. 03

    Treatment across settings

    Clinic, group, home, field and telehealth encounters landing on the same chart, whichever program delivered them.

    Unified Chart

  4. 04

    Transition and follow-up

    Step-downs scheduled before discharge, crisis follow-up tracked, and readmission arriving with the full history rather than as a new intake.

    Continuous History

Because Elixir is built on Salesforce, the configuration that makes this work for one state and payer is repeated for the next without a second instance to maintain.

Measurable

Outcomes You Can Show a Payer, a Board and a State

“Measurable” is an easy word to put on a website. What it has to mean operationally is that the measure gets collected when it is due, gets seen by the person who can act on it, and adds up to something reportable at the end of the quarter.

  • Collected on schedule

    Due dates for PHQ-9, GAD-7, Columbia-SSRS, BAM or service-specific instruments trigger prompts to the clinician or go to the patient portal before the visit — not left to memory.

  • Seen where decisions happen

    Scores trend on the encounter screen, not buried in an outcomes tab. A prescriber sees the symptom trajectory alongside the medication list.

  • Acted on

    No change or deterioration after the expected interval surfaces in supervision and team huddles — not just in a post-discharge review.

  • Attached to risk

    A positive Columbia-SSRS or audit score automatically opens the corresponding safety plan or assessment workflow, with the response documented before the encounter closes.

  • Rolled up honestly

    Reports distinguish between patients who improved, patients who stayed stable, and patients whose measure was never collected — so an executive or a board sees actual performance, not an inflated numerator.

  • Ready for value-based contracts

    Because measures sit as structured data on Salesforce objects, building a payer-specific outcomes extract is a report configuration, not an engineering ticket.

Compliance

The Behavioral Health Compliance Spine: HIPAA, 42 CFR Part 2 and Consent

Behavioral health carries a confidentiality regime that general healthcare does not, and the February 2024 final rule — whose compliance date of 16 February 2026 has now passed — brought substance use records under HIPAA’s breach notification rule and penalty tiers.

  • Scope

    Separation by scope

    Mental health records and Part 2 substance use records live on the same patient chart with role- and consent-governed access controls, so clinicians see what they are legally permitted to see and no more.

  • Consent

    Granular Part 2 consent

    Single-consent models for treatment, payment and operations (TPO) with explicit capture of patient-specified restrictions, entity-specific consents where required, and automatic revocation handling.

  • Notes

    Psychotherapy notes

    True separation of psychotherapy notes from the rest of the medical record under 45 CFR § 164.501, requiring specific authorization for disclosure outside the treating clinician.

  • Trail

    Accounting of disclosures

    Every disclosure of Part 2 records — internal and external, electronic and exported — captured in an immutable audit trail fulfilling the 2024 final rule’s accounting requirements.

  • Legal

    Court-order safeguards

    Guardrails that prevent unauthorized disclosure of Part 2 records in civil, criminal, administrative or legislative proceedings without the heightened court order Part 2 explicitly requires.

  • Shared

    Single audit boundary

    Because both service lines share Salesforce’s enterprise trust infrastructure, your security team defends and audits one environment rather than two vendors’ distinct tech stacks.

For full detail on Elixir’s Part 2 consent engine, see the substance use disorder page.

Go to Substance Use Disorder Page

AI

Kratu AI Across Behavioral Health

One AI engine and one governance model across both service lines — built to reduce documentation time and catch revenue problems early, never to make a clinical decision.

Across both service lines the same limits apply: AI does not assess risk, determine a level of care, decide medical necessity, or write anything into the record a person has not reviewed and signed. Your data is not used to train a model for anyone else.

FAQ

Behavioral Health EHR: Frequently Asked Questions

  • Do we have to buy both mental health and substance use modules together?

    No. Many organizations start with one — mental health for an outpatient clinic, or substance use for an addiction treatment facility — and add the second when they expand service lines or bring a new program onto the platform. Because both live in the same Elixir data model, turning on the second does not require a data migration, a second login, or a fresh integration to your billing or lab partners.

  • How does Elixir separate 42 CFR Part 2 substance use records from mental health records on the same chart?

    Through data-level security controls configured to the patient’s active Part 2 consents. Mental health encounters and substance use encounters live as separate record types with their own permission boundaries. A mental health clinician without Part 2 authorization cannot view the SUD portion of the chart unless a valid consent covering that clinician is on file. Disclosures, revocations and expiry are managed in the consent engine and recorded in the audit log.

  • Can we configure different clinical forms for each state we operate in?

    Yes. Because Elixir is built natively on Salesforce, form configuration, field requirements, assessment templates and billing rules are defined per service line, per program, and per state. You can maintain state-specific Medicaid assessment formats and clinical summaries in the same instance without custom code, using standard Salesforce configuration tools your administrator can manage.

  • How does Elixir handle outcome measures for patients receiving both mental health and SUD services?

    Each service line maintains its own outcome schedule — for example, a PHQ-9 every four weeks in mental health therapy and a BAM or urine drug screen schedule in addiction treatment. Clinicians on each side see the measures relevant to their work, but authorized clinicians can view the combined timeline: symptom scores plotted alongside substance use frequency and medication changes on a single view.

  • What does "Salesforce-native" actually mean for a behavioral health organization?

    It means Elixir is built entirely within Salesforce — not connected to it through an API or middleware. Your patient data, clinical notes, consents and billing records sit on Salesforce’s HIPAA-compliant, HITRUST-certified cloud infrastructure. You inherit Salesforce’s role-based access controls, reporting engine, integration ecosystem (including MuleSoft and AppExchange) and multi-region availability without managing your own server infrastructure.

  • How does Elixir support billing for behavioral health specifically?

    Elixir’s revenue cycle engine supports the billing rules unique to behavioral health: incident-to billing, supervised billing (with the supervising clinician’s review captured in the note workflow), time-based evaluation and management codes, psychiatric add-on codes (such as +90833), interactive complexity (+90785), state Medicaid fee schedules, and per-diem / bundled billing for residential and withdrawal management programs.

Connected and measurable

See both service lines on one record

Bring your programs, your states and your payer mix. We will show you a co-occurring patient moving through the continuum — the consent trail, the measures, the placement decision and the claim — on one chart.

Request a DemoExplore the platform

Related links:Mental HealthSubstance Use Disorder