The Field Note   Chiropractic · Under Healthcare · Published September 2026

Chiropractic multi-location: the stack that scales past 10 rooftops.

The practice-management software you signed for at three clinics quietly fails at eleven. The reason is billing. Medicare Part B chiropractic (98940-98942) and personal-injury/PIP claims have edge cases the single-doctor tools were never built to carry, and a growing group discovers it two audits and one bad AR quarter too late.

6 min · Chiropractic · Under Healthcare

Questions this article answers

  • What breaks in single-doctor practice-management software past 10 rooftops?
  • Medicare Part B chiropractic billing tech — who handles it well?
  • PI/PIP billing complexity as the vendor filter?
  • Multi-location scheduling plus provider credentialing?
  • What does the 10-40 rooftop chiropractic stack look like in 2026?

The chiropractic PM software that took a group from one doctor to five rooftops is the same software that breaks at eleven. Medicare Part B (98940-98942) and personal-injury/PIP billing are the filter that thins the vendor pool from twenty logos to four.

What breaks past 10 rooftops is billing, not scheduling

Operators expect the pain to show up in the calendar — more rooms, more providers, more overlap — but the calendar is the easy part. What breaks is the billing engine and the reporting on top of it. A single-doctor tool assumes one rendering provider, one Tax ID, one payer contract mix, and a receivables report that fits on a laptop. At eleven rooftops the group has a mix of W-2 associates and 1099 contractors, two or three Tax IDs across state lines, dozens of payer contracts with different fee schedules, and a receivables population where 20% of the AR is one PI attorney firm and another 15% is Medicare secondary. The single-doctor PM cannot roll up denials by CARC across locations, cannot enforce the AT modifier at the note-signing step for every 98940-98942 line, and cannot show the CFO which of the eleven locations is bleeding on the same claim type. Groups don't switch because they wanted new software. They switch because the biller opened a spreadsheet.

Medicare Part B chiropractic billing is the first vendor filter

Under Medicare Part B the chiropractic benefit is narrow: manual manipulation of the spine to correct a documented subluxation, coded 98940 (1-2 regions), 98941 (3-4 regions), or 98942 (5 regions). Every claim has to carry the AT (Active Treatment) modifier or CMS treats it as maintenance and denies it. Documentation has to meet the PART criteria (Pain/tenderness, Asymmetry, Range-of-motion, Tissue tone) or the note fails a Medicare audit. The CMS Medicare Benefit Policy Manual, Chapter 15 and the Medicare Learning Network chiropractic guidance are the source of truth. What matters at the vendor level: does the PM force the AT modifier on the coding screen, or does it hope the coder remembers? Does the SOAP template make the four PART elements structured fields, or free text? Does the denial workbench cluster CARC 50 (not medically necessary) and CARC 96 (non-covered) by location and provider so the AR lead can act on it? ChiroTouch (Storis21-owned), Genesis Chiropractic Software (ClinicMind-owned), and zHealth answer these in different ways, and the answer is worth reading before signing.

PI and PIP billing is the second filter — and it thins the pool further

Personal-injury and PIP billing is where chiropractic groups either make a margin or lose one, and it is the workflow that single-doctor tools handle worst. A PI case runs 6-18 months, has a lien attached, requires attorney demand-package generation from the visit notes, tracks separate billed-vs-collected-vs-lien-reduction figures, and hits AR aging buckets that Medicare-oriented tools mis-classify. A PIP claim (Florida, New York, New Jersey, Michigan primarily) has a per-claim benefit cap, a fee schedule tied to state statute, and denial patterns that look nothing like commercial. Vendors that handle this well have a case-management layer that sits alongside the encounter record: Genesis Chiropractic Software, ChiroSpring, and Platinum System ship dedicated PI/lien modules; zHealth and ChiroTouch handle it through custom fields and reports. Jane and ClinicSense serve cash-heavy or wellness-oriented practices and are the wrong tool for a PI-forward multi-state group. The buying question is not “can it do PI” but “can it show me PI AR aging by attorney, by location, and by date-of-injury cohort, this quarter, without a spreadsheet.”

Artifact: 5-question chiropractic multi-location vendor screen

  1. Force the AT modifier at note-sign for 98940-98942, or catch it downstream? Ask to see the exact screen. The right answer is upstream enforcement.
  2. PART criteria as structured fields, or free-text SOAP? Structured survives a Medicare audit. Free-text does not, reliably.
  3. PI/PIP case management — native module or custom fields? A native lien and demand-package flow is worth 2-3 points of margin.
  4. Denial workbench — can it cluster CARC by location, provider, and payer this week, without a data export? If it needs export, the group is running blind at scale.
  5. Multi-Tax-ID, multi-location roll-up — one login, or one login per entity? One login per entity kills the finance function past 10 rooftops.
Buyer-side. Supplier-paid. Buyers pay zero. Compensation has zero weight in the Cardinal Index scoring inside the Cardinal Method. Specific commercial terms live only in the private Decision Memo a buyer signs, never on this page.

What the 2026 chiropractic 10-40 rooftop stack looks like

The narrow but real 2026 vendor pool at this size: the PM/EHR core is ChiroTouch (cloud, Storis21-owned, deep macro library and coding automation), Genesis Chiropractic Software (ClinicMind-owned, ONC-certified, strong PI module and multi-location roll-up), ChiroSpring (built for multi-location groups from inception), or zHealth (cloud-native, lighter footprint, good API). Wellness and cash-heavy groups run Jane or ClinicSense. Around the PM sit three adjuncts that matter more with scale: a credentialing/CAQH manager (either a service or a module inside the PM), a payments and text-to-pay layer that handles the PI settlement pattern, and a business-intelligence layer — Practice Analytics is the vendor most-named in this segment — that unifies KPIs across whichever PM the group runs. The finance question that decides the shape of the stack: does the group need one system of record with everything inside it, or an EHR-of-record plus a reporting layer that survives a future PM swap? At 10-15 rooftops all-in-one usually wins. At 25+ rooftops with acquisition velocity, the reporting-layer separation is what makes the next migration survivable. Sibling reads sit under Healthcare and next to mid-market healthcare technology sourcing 2026.

In short

  • The chiropractic PM software that worked at 3 rooftops breaks at 11 because of billing complexity, not scheduling volume.
  • Medicare Part B chiropractic (98940-98942) is a specialty billing problem: AT modifier enforcement, PART documentation, denial clustering by location and provider.
  • PI/PIP billing is the second vendor filter — native case management, lien tracking, and attorney-cohort AR reporting separate the multi-location tools from the single-doctor ones.
  • The 2026 pool: ChiroTouch, Genesis, ChiroSpring, zHealth for insurance-forward multi-location; Jane and ClinicSense for cash-heavy or wellness practices; Practice Analytics as the reporting layer.
  • Past 25 rooftops with acquisition velocity, separate the reporting layer from the PM so the next migration doesn't cost a year of visibility.

Sources

All linked sources were live at time of publish (September 2026). Verify before quoting in a procurement document.

PM refresh on the roadmap this year?

Run the Tier 1 benchmark.

Submit the current PM contract, a denial mix by CARC, and PI AR aging. We return a benchmark PDF in five business days showing which vendors in the 2026 pool actually fit the group's payer, PI, and multi-Tax-ID posture. Free. No follow-up sales drip.

Run the Tier 1 benchmark →