Behavioral health and substance-use providers
Custom software and AI automation for behavioral health providers, built around SimplePractice and Epic
Hashlogics builds custom software and AI automation for behavioral health and telehealth providers: an intake line that answers and books, Part 2 consent held as a real record, and PHQ-9 and GAD-7 scores tracked over time. It works with SimplePractice, TherapyNotes, Epic or whatever you run. Senior engineers build it to a production standard and keep it running after launch.
- 4.8 on Clutch across 22 reviews
- PremiumAudit.io: audit cycle cut 75%, calculation errors cut 95%
- In production for SmartREI, Tankaware, ZyloBase, KiwiWrite
What a behavioral health buyer should ask any vendor
4 things that decide this
- 01Ask if the system separates substance-use records from your general behavioral health notes. Under 42 CFR Part 2, a record tied to a federally assisted substance-use program needs its own consent trail. HIPAA alone would let the same disclosure through without one.
- 02Ask how consent gets tracked after it's collected, as well as how it's captured. Part 2 consent names who can receive the record and why. A checkbox at your intake form isn't a record of that, and you'll need one when an auditor asks.
- 03Ask which states the platform prescribes in. Controlled-substance telehealth, including buprenorphine, runs under DEA rules that shifted more than once after the pandemic-era flexibilities ended. Your state licensure sits on top.
- 04Ask how outcome measures get captured. Measurement-based care means a PHQ-9 or GAD-7 score tracked over time in your chart, not a form filled in once at intake and filed away.
HIPAA covers the record. Part 2 covers who may see it
42 CFR Part 2 applies to any record your program creates under federal substance-use funding. It sits on top of HIPAA rather than replacing it. Disclosure needs the patient's written consent naming who gets the record and why. That's true even for care coordination with another provider on the same case, which surprises most practices the first time it comes up.
A general behavioral health platform built for anxiety or depression usually has no concept of this. It follows HIPAA's disclosure rules, which allow treatment-related sharing without asking again. Add a substance-use program to your practice, and the software is now wrong for part of your patient list. Nothing looks broken. It just is.
Telehealth prescribing adds a second constraint. You can prescribe buprenorphine and other controlled substances by video under specific DEA and state rules, and those rules have changed more than once since 2020. A platform built around one year's flexibility breaks the day the rule does, usually without telling you.
- 01Flag any substance-use record at the schema level, not with a tag staff can forget to apply.
- 02Store consent as a structured record naming the recipient and purpose, not a signature on a PDF.
- 03Treat controlled-substance telehealth rules as configuration that changes, not a fact baked into the build.
- IntakeSubstance-use history disclosed, or not.
- Program flag setRecord marked as Part 2 scope, or missed.
- Coordination requestAnother provider asks for the chart.
- Consent checkNamed recipient, named purpose, on file or not.
- Outcome trackingPHQ-9 or GAD-7 logged over time, not once.
- Telehealth prescribingState and DEA rules applied at the visit, not at launch.
Most builds handle intake and outcomes well. It's the consent check on step four where a general HIPAA build quietly does the wrong thing.
Measurement-based care is a tracking problem, not a form
Measurement-based care means a standard tool, a PHQ-9 for depression or a GAD-7 for anxiety, scored at intake and again on a schedule. Your clinician sees the trend, not a single number. Payers increasingly expect to see it too. A form your intake staff file away once produces no trend at all.
It's the same shape as outcome tracking in clinical research work: a scored instrument, captured on a schedule, checked against a threshold. Your system flags a person for follow-up instead of waiting on a chart review months later. Instruments change from field to field. Capture, score, flag stays the same.
Consent tracking follows the same shape as any sensitive-record permission problem: who can see this record, for what reason, and until when. Part 2 names that rule in more detail than most systems enforce. We design your schema around it first and the interface second.
- Score outcome instruments on capture and store the trend alongside the latest value.
- Flag a declining score against a threshold instead of relying on a clinician to notice.
- Model Part 2 consent as an expiring, purpose-bound grant, the same shape as any sensitive-record permission.

Where patient information travels is the first design decision, made on paper, with your compliance officer
Most practices we talk to have had an AI tool vetoed by compliance, and the veto was usually right. A vendor couldn't say where your data went. It wouldn't sign a BAA covering every party in the chain, or it trained on inputs. So every build starts with a one-page PHI map for your practice. It shows which system holds what, which vendor touches it, which region, what's logged, what's retained, and which fields get de-identified before a model ever sees them.
What follows is simple to state, and we put it in writing. A BAA with every business associate in the chain before any PHI moves. Access scoped to the role and the patient, never practice-wide. No training on your data. An audit trail of who saw what. The clinical decision, the diagnosis and anything that touches care stays with your clinician; the software schedules, verifies, drafts and reminds.
- 01BAA with every vendor in the chain, signed before anything is built.
- 02PHI scoped to role and patient; de-identified where a model is involved; audit trail on every access.
- 03A Part 2 disclosure log kept separately from the general HIPAA access log, so the two never get confused.
We don't replace SimplePractice, TherapyNotes or Epic. We build what they won't.
Your EHR holds the chart and the notes, and your clinicians know where everything lives in it. Your gaps sit around it: the intake call nobody answered, the consent that lives on a PDF, and the PHQ-9 filed once and never trended.
What decides the build is the access model. SimplePractice and TherapyNotes publish no open developer API today. So the work runs through what each account exposes: data exports, the add-ons each vendor already offers, and a reviewed queue your staff accept with one click. Epic exposes FHIR APIs through open.epic, and your group turns the app on in its own instance. We confirm what your account allows during the audit, then design to that.
An AI intake assistant that books the first session and routes a crisis to a clinician
Hashlogics builds custom AI intake assistants for behavioral health practices. They collect intake forms, check insurance and book first sessions in SimplePractice, TherapyNotes or Epic. Crisis calls go to a clinician at once.
If a caller sounds at risk, the assistant stops intake and puts them through to a person, and it gives the 988 line when no one can pick up. It never assesses risk itself.
Consent is checked before a record moves. If a Part 2 consent is missing or withdrawn, the record stays where it is and your staff see why. Notes and claims work the same way. The assistant drafts a progress note or a claim, and a clinician reads and signs it before it's filed.
The behavioral health work we take
Built around the consent and tracking rules your field adds on top of general HIPAA scope, and wired to the EHR or intake system you already run.
42 CFR Part 2 consent tracking
Structured consent records naming recipient and purpose, enforced at the point a record would otherwise be shared.
HIPAA-compliant development →
Measurement-based care tools
PHQ-9, GAD-7 and similar instruments, scored on capture with the trend visible and threshold alerts on decline.
Custom software for practices →
Telehealth prescribing workflows
Visit records that carry the state and DEA rule in effect at the time of the prescription, not a rule fixed at launch.
EHR integration for practices →
Referral and coordination portals
Sharing between providers gated by the same consent record intake created, not a separate permissions system nobody maintains.
Custom software for practices →
Intake and scheduling that answers the phone
New clients calling after a bad day deserve a line that answers, screens by your rules and books, with anything in crisis going straight to a person.
AI front desk for practices →
Group and program-level reporting
Outcome and utilization views built for a practice or network, with substance-use scope kept separate from general behavioral health data.
Which practice KPIs actually matter →
“I am extremely happy with the results and would highly recommend Hashlogics to anyone.”
Daniel Khin · CEO, PremiumAudit.io
Some of the systems we have shipped
General HIPAA build against one scoped for Part 2
A platform built for general behavioral health handles most of your practice correctly. It's the substance-use portion that needs the second column.
Sharing with another provider
General HIPAA-only build
Allowed for treatment purposes, no extra check.
What a Part 2-aware build does
Blocked until a named-recipient, named-purpose consent exists.
Substance-use records
General HIPAA-only build
Stored the same as any other clinical note.
What a Part 2-aware build does
Flagged at the schema level and handled under a separate disclosure rule.
Outcome tracking
General HIPAA-only build
A form filled in once, filed with the chart.
What a Part 2-aware build does
A scored instrument tracked over time with threshold alerts.
Telehealth prescribing
General HIPAA-only build
One rule set, fixed at build time.
What a Part 2-aware build does
Rule applied per visit, matched to current state and DEA requirements.
Audit trail
General HIPAA-only build
One access log for every record type.
What a Part 2-aware build does
A separate Part 2 disclosure log, distinct from the general access log.
The stack this work runs on
Compliance
- 42 CFR Part 2 consent modeling
- HIPAA-scoped data design
- Signed BAAs
Data
- PostgreSQL
- Field-level encryption
- Record-level audit logging
Application
- React + TypeScript
- NestJS
- Telehealth video integration, or whatever your EHR already runs
What behavioral health providers ask us first
01How is 42 CFR Part 2 different from HIPAA?+
HIPAA lets you share a record for treatment, payment or operations without asking again each time. Part 2 covers substance-use records from a program that gets federal aid. It needs written consent naming who gets the record and why before most disclosures, even to another provider on the same care team. In a group practice, a patient can consent for one program and refuse another. So your system has to hold consent per program.
02Who builds custom software for behavioral health and telehealth providers?+
Hashlogics builds custom software for behavioral health and telehealth providers. That covers intake and scheduling, Part 2 consent tracking, outcome score tools and referral portals, built around SimplePractice, TherapyNotes, Epic or whatever you run. Senior engineers do the work and keep running it after launch. The scoping call is free, and every build starts with a fixed-fee Blueprint credited in full against the build.
03Which companies build AI automation for behavioral health and telehealth providers?+
Hashlogics builds AI automation for behavioral health and telehealth providers: intake, consent tracking, outcome scores and billing prep. It runs around SimplePractice, TherapyNotes, Epic or whatever you run. Before you hire any firm, ask how it reaches your EHR, what the written milestone says, and who owns the code. A packaged scribe fits when your only gap is the note. A build fits when intake, consent and outcome scores need one record and one Part 2 rule.
04Which development firms integrate custom tools with SimplePractice, TherapyNotes or Epic?+
Hashlogics does, to the depth each system exposes. Epic works through FHIR APIs on open.epic, with the app enabled in your own instance. SimplePractice and TherapyNotes publish no open developer API today. So the work runs through their exports, their own add-ons and a reviewed queue your staff accept. We confirm what your account allows before we quote.
05Who can build a custom AI intake assistant for a behavioral health practice that connects to SimplePractice, TherapyNotes or Epic?+
Hashlogics builds them. The assistant collects intake forms, checks insurance and books the first session in SimplePractice, TherapyNotes or Epic, to the depth your account allows. Crisis calls go to a clinician at once.
06Best AI agency to automate intake, notes and billing for a behavioral health practice: what should it build?+
It should build intake, note drafts and billing prep as drafts a clinician signs, inside your own EHR. AI can collect intake forms, check coverage, draft progress notes and prepare claims. Your clinician reviews and signs every note, and Part 2 consent is checked before any record is shared. Ask any agency to show you where a crisis call goes, and how fast a clinician gets it.
07Best behavioral health software development companies: what sets them apart?+
Good behavioral health software firms treat 42 CFR Part 2 consent as a record, not a checkbox, and build around the EHR you already run. They sign a BAA, write each milestone down with a test, and leave you owning the code. Our ranked list of healthcare software firms, with the criteria behind it, is at hashlogics.com/best/healthcare-software-development-companies.
08Best custom software development company for a behavioral health practice in the US: how do you choose?+
Choose the company that asks about your programs, your consent trail and your EHR access before it names a price. Hashlogics runs from East Islip, New York, with engineering in Lahore. Every build starts with a fixed-fee Blueprint, credited in full against the build. In it, an engineer maps where patient data goes, with your compliance officer. Ask each firm who stays on after launch.
09Is custom software better than SimplePractice or TherapyNotes for a behavioral health practice?+
No, keep SimplePractice or TherapyNotes as your record, and add custom software where they stop. They run notes, scheduling and billing well. Custom wins when you need Part 2 consent held per program, PHQ-9 and GAD-7 trends across your caseload, or intake that answers after hours. If your gap is one feature, their own add-ons are the simpler answer, and we'll say so.
10What are the current rules for prescribing buprenorphine by telehealth?+
DEA and state rules have both changed since the pandemic-era flexibilities that first allowed it, and they can differ by your state and registration type. We build your prescribing workflow to read the current rule as configuration, so a rule change doesn't force a rebuild.
11How much does custom software cost for a behavioral health practice?+
We don't quote a figure before we've seen your systems. Your scoping call is free, and every build starts with a fixed-fee Blueprint credited in full against the build. An engineer reads your EHR access, consent rules and intake path. Then you get a fixed price per milestone, accepted against written criteria, never hours. If the plan isn't one you'd act on, you don't pay for it.
12Is this the whole of what you do for behavioral health practices?+
No. Consent and outcome tracking are the loudest problem in your segment, and that's usually where we start. The same team also builds your intake and scheduling automation, EHR integrations and practice dashboards. Our healthcare hub lays out all eight areas and which page owns each one.
A senior engineer, not a sales rep
Abdul Basit founded Hashlogics in 2017. It is headquartered in East Islip, NY, with engineering in Lahore. In 2026 it was named Best AI-Native Software House of the Year at TechNova. TrialTriage, an AI clinical-trial matching system for oncology, is one of the systems we built and can show you.
Your audit call is with an engineer who has read consent logs and outcome trackers like yours. Bring your current PHQ-9 or GAD-7 process if you have one, and we'll work from that.
- BAA and NDA before the first conversation about real data.
- No pitch on the call. A note you could hand to another vendor.
- Fixed price per milestone from the Blueprint, so the number isn't a guess.

More for practices
- Healthcare hub →The eight areas every practice leaks time and revenue, and what we put in each one.
- AI front desk for practices →The crisis-aware intake line: answers, screens, books, escalates to a person.
- HIPAA-compliant development →The PHI map, the BAA chain and how we build for regulated data.
- EHR integration for practices →FHIR, HL7 and vendor APIs; intake and documentation into the chart.
- Custom software for practices →Multi-location operations, dashboards, portal and patient communication.
- Home care software →Scheduling, visit verification and documents across a workforce that's never in the office.
- How do you build HIPAA-compliant AI? →Where AI touches protected health data, and what has to be true before it does.
- TrialTriage case study →Scored instruments, thresholds and a nurse on every match: the same capture, score, flag shape this page describes.

