How a NJ behavioral-health practice closed its billing gap in six weeks.

Eight tools, one org, one clinician drowning.

The practice ran on the same stack most NJ behavioral-health orgs run on: an EHR that couldn’t talk to CYBER, a spreadsheet for authorizations, a portal login for PerformCare, a separate portal for NJMMIS, a scheduling app, a billing add-on, a fax line for MCO packets, and a group text where clinical directors traded PDFs at 9pm.

Progress notes were finished on weekends. CYBER packets took the better part of an hour each — copy chart data, paste into portal forms, re-derive dates, attach signed docs, hope the session timed out on the right side of the transaction. Claims came back denied for problems that could have been caught before submission.

“Everyone was working two jobs — the clinical one they signed up for, and the operational one that the stack forced on them.”

Clinical Director · Anonymized

One runtime, six modules, one audit trail.

CounselCore replaced the eight tools with a single runtime. Every module shares state, permissions, and audit trail. Documentation flows into authorization packets. Authorization state flows into billing. Billing state flows into the compliance ledger. Nothing gets re-keyed, nothing gets forgotten, and nothing gets lost between inboxes.

How the gap closed.

1. Week 1
   Runtime provisioned · data plane wired

   Clinical chart, scheduling, and billing modules stood up on the tenant. Prior EHR export ingested. Argon2id hashes migrated. Session-scoped PHI vault activated.

2. Week 2
   Portal adapters live

   NJMMIS + PerformCare + CYBER adapters wired. First auto-rendered CYBER packet submitted end-to-end without touching the portal UI.

3. Week 3
   AI team switched on

   Sage began drafting progress notes from session structured data. Content firewall active on every output; clinician sign-off required before persist.

4. Week 4
   Denial screening in production

   Every outbound claim now passes through a rules layer that catches CPT/DOS/POS mismatches, missing modifiers, and expired auths before submission.

5. Week 5
   Nexus mesh activated

   Ten partner orgs across ten NJ counties connected. Real-time capacity signals began routing referrals to the fastest-answering partner.

6. Week 6
   Billing gap closed

   Backlog worked through. First-pass claim acceptance stabilized. Clinical directors got their evenings back.

Compounding, not chasing.

Six weeks of consolidation created a runtime that compounds. Every session becomes a signed, timestamped record. Every note ties to an authorization. Every authorization ties to a claim. Every claim ties to a hash-chained audit row. The platform’s live counters — pulled fresh from production the second this page loads — tell the story:

From ten counties to fifty states.

The Nexus mesh currently covers ten NJ counties with ten partner orgs. Twenty-one NJ counties are eligible. PA · NY · CT · MD are next on the roadmap, prioritized by payer readiness and existing partner overlap. If you’re operating in one of those states, ask about the state-expansion waitlist on the landing page.