Jane vs ChiroTouch: Chiropractic Referrals in 2026
A day in the life of a chiropractic operator
At Monday's huddle, the owner asks a simple question: which referral sources produced new patients who actually arrived? The booking report says “Google,” “Dr Smith,” “friend,” “Facebook,” and “other.” Intake contains “Google maps,” two spellings of the same physician's name, and several blanks. The marketing spreadsheet counts leads, the EHR counts patients, and the deposit report counts cash. None uses the same date or definition.
The front desk can repair the list manually, but that creates a report no one can reproduce. Worse, “referral” is doing two jobs. A patient may have learned about the clinic from a neighbor while a physician sent a clinical referral. Combining those relationships destroys both marketing attribution and continuity-of-care context.
To automate chiropractic referral source tracking, define the data contract before moving any rows. Capture a controlled marketing source at booking, preserve a professional referrer in a separate clinical field, normalize free text through a review queue, and attribute only after the appointment and financial state are known. Automation should make missing data visible; it should not guess.
The operating context is expanding. According to the U.S. Bureau of Labor Statistics, chiropractic employment was projected to grow 10% from 2024 to 2034, with about 2,800 openings per year. Those figures are not referral benchmarks. They support designing a process that can be taught as teams change.
TL;DR
Give every source a stable code and human-readable label; never make free text the reporting key.
Store acquisition source, referring patient, and referring professional separately.
Ask at booking and confirm at intake, but preserve both the original answer and the reviewed answer.
Attribute arrived patients and collected or invoiced revenue from the authoritative practice system.
Route blanks, ambiguous values, and conflicting answers to staff without copying clinical detail into a marketing tool.
Compare Jane and ChiroTouch by field behavior, report logic, exportability, and exception control—not by dashboard appearance.
1 patient can have 3 distinct referral relationships.
7 controlled steps replace free-text spreadsheet cleanup.
0 guessed sources should enter the final report.
The workflow, mapped
Step 1: publish a referral taxonomy
Start with the decisions the report must support. A compact clinic taxonomy might contain direct/search, paid search, social, community event, patient referral, professional referral, payer directory, location visibility, and unknown. Give each category a stable code such as MKT_SEARCH_ORGANIC; keep campaign, location, referrer, and detail as separate fields.
Do not encode “Dr. Lee” as both a channel and a person. The source category can be professional referral, while the professional record holds a normalized name and organization. Likewise, “friend” is a category; the referring patient is a separate relationship that should be collected only under the clinic's policy and applicable privacy requirements.
| Data element | Example | Required at booking? | Reporting role | Owner |
|---|---|---|---|---|
| Source code | MKT_SEARCH_ORGANIC | 1 | Primary grouping | Operations |
| Source label | Organic search | 0 | Human display | Operations |
| Source detail | Google Maps | 0 | Channel analysis | Marketing |
| Referring patient ID | Internal ID | 0 | Patient relationship | EHR |
| Professional referrer ID | Directory ID | 0 | Care relationship | EHR |
| Campaign code | SPRING_POSTURE | 0 | Campaign analysis | Marketing |
| Original free text | “Dr Smith” | 0 | Audit and review | EHR |
| Confidence state | confirmed | 1 | Exception control | Front desk |
Step 2: capture once, confirm once
Make the controlled source question easy at online booking and permit “not sure” instead of forcing a false answer. At intake, show the captured category and ask the patient or staff to confirm or correct it. Preserve original_source_code, confirmed_source_code, source timestamp, and collection channel.
Jane offers one implementation pattern. According to Jane's Referral Report guide, its recipient filter has 3 scopes—Anyone, Clinic, and Staff Member—and its patient referral field can use a configured dropdown or an optional “Other” entry. These are Jane-specific behaviors to test in the clinic's actual account.
Referral capture should fit the broader onboarding sequence. The new-patient-to-first-adjustment workflow shows where booking confirmation, intake completion, staff review, and first-visit status belong without turning the referral question into a second intake form.
Step 3: preserve relationship types
Use three lanes:
Acquisition source: how the person found or chose the clinic.
Patient advocate: an existing patient credited under a lawful, disclosed policy.
Professional referral: a practitioner or organization connected to care.
The acquisition lane can feed aggregate marketing reporting. The professional lane belongs in the clinical or practice-management system with appropriate access. Do not post patient names, symptoms, appointments, or professional referral details into an ordinary marketing channel merely to make a dashboard easier.
According to HL7's FHIR R4 ServiceRequest specification, ServiceRequest.requester has 0..1 cardinality and can reference 6 resource types, including Practitioner and Organization. That field is a technical model for a clinical service requester where an EHR actually supports it; it is not a substitute for the separate marketing-source field and does not prove Jane or ChiroTouch exposes FHIR.
Step 4: normalize without inventing
Create an alias table for deterministic matches: “Google map” and “G Maps” may map to the approved Google Maps detail after staff validation. Normalize casing and whitespace automatically, but require human review when two professionals share a surname, a value could belong to multiple categories, or the original answer conflicts with intake.
Use confidence states: exact controlled value, approved alias, staff confirmed, unresolved, and declined. Never use an AI similarity score alone to assign a physician, patient, or campaign. Keep the original text and every change so an analyst can explain the report later.
| Exception | Automatic action | Human question | Final state |
|---|---|---|---|
| Blank at booking | Ask once at intake | “How did you hear about us?” | Confirmed or unknown |
| Known alias | Suggest canonical value | Verify if person-specific | Alias-approved |
| Two possible referrers | Hold | Which person/organization? | Staff-confirmed |
| Booking/intake conflict | Preserve both | Which answer is correct? | Corrected |
| Declined answer | Stop prompting | None | Declined |
| Deleted campaign | Preserve historical code | Is replacement needed? | Historical |
At this normalization step, US Tech Automations can build a custom/API workflow when the practice system technically exposes the required data: apply approved aliases, open a minimum-necessary exception, record the reviewer, and reconcile the write. Jane, ChiroTouch, and the other specialty tools here are not represented as registry-confirmed native connectors.
Step 5: wait for the outcome
A booking is not an arrived patient, and an arrived patient is not collected revenue. Choose a cohort rule—such as first booked date or first arrived date—and use it consistently. Preserve cancellations and no-shows for conversion analysis without attributing their nonexistent revenue.
Jane documents an important reporting distinction. According to the same Jane guide, its referral report offers 2 accounting views—Collected and Invoiced—and 2 export formats, Excel and CSV; data appears after invoicing or payment conditions are met. Confirm how refunds, credits, packages, memberships, and date filters behave before using the export for financial decisions.
Step 6: reconcile reports, not just rows
For each reporting period, compare controlled-source patients with all eligible new patients. Then compare source-attributed invoices or payments with the authoritative financial total. Log excluded tax, refunds, payment timing, write-offs, and migrated balances.
ChiroTouch illustrates a different reporting pattern. According to the ChiroTouch reports list, the product lists at least 7 referral-related reports, including New Patient by Source, Referral Tree, Patient Source, and Physician Referral; its Referral Tree description includes direct and indirect referrals and can exclude $0 patients. Availability may depend on edition and configuration.
Worked example
Illustrative worked example: a 3-location clinic receives 240 new bookings in 1 month, maps answers to 12 source codes, and routes 15 conflicts to a staff queue. For the 18 professional referrals, an EHR that technically supports FHIR may preserve the practitioner or organization in ServiceRequest.requester, while the workflow keeps marketing source in its separate controlled field; 0 patient names enter the aggregate campaign report, and all 15 exceptions require a reviewer before attribution. This is an implementation scenario, not a clinic result or a claim about a named product's interface.
After this reconciliation step, US Tech Automations' data-extraction workflow can support a technically available custom export, validation queue, and scheduled aggregate report. The practice system remains authoritative, staff own ambiguous mappings, and the workflow should fail closed when a source write cannot be verified.
Step 7: publish a decision report
Report volume, arrived patients, arrival rate, attributed revenue basis, average value, unresolved share, and refund policy. Slice only when the cohort is large enough to be useful and privacy-preserving. Keep professional-referral performance under clinical and legal governance; do not treat it like a paid-ad leaderboard.
According to HHS de-identification guidance, the Privacy Rule recognizes 2 methods—Expert Determination and Safe Harbor—for de-identifying protected health information. Aggregate referral reporting still needs minimum-necessary access, appropriate agreements, security, and qualified privacy advice; a label saying “de-identified” is not a substitute for the method.
| Monthly control metric | Formula | Pilot threshold | Escalate at |
|---|---|---|---|
| Source completion | Confirmed ÷ eligible | 95% | Under 90% |
| Unresolved share | Unresolved ÷ eligible | Under 5% | Over 10% |
| Arrival match | Attributed arrivals ÷ all arrivals | 98% | Under 95% |
| Revenue reconciliation | Attributed ÷ eligible total | 99% | Under 97% |
| Duplicate professional records | Duplicates ÷ active records | Under 2% | Over 5% |
| Manual review age | Oldest open item | Under 2 days | Over 5 days |
These are illustrative operating thresholds, not industry benchmarks. Tune them to volume, staffing, data availability, and risk.
What it costs to keep doing it manually
The manual cost includes entry, cleanup, lookup, spreadsheet merging, report rebuilding, and correction. Observe each activity rather than applying one generic “admin time” percentage.
| Illustrative monthly input | Low | Base | High |
|---|---|---|---|
| New-patient records | 80 | 240 | 600 |
| Minutes cleaning each record | 1 | 3 | 6 |
| Professional lookups | 8 | 30 | 90 |
| Minutes per lookup | 3 | 6 | 10 |
| Report/reconciliation hours | 2 | 8 | 20 |
| Loaded admin hour | $28 | $36 | $48 |
| Total manual hours | 3.7 | 23.0 | 95.0 |
| Modeled labor | $103 | $828 | $4,560 |
The base arithmetic is (240 × 3 + 30 × 6) ÷ 60 + 8 = 23 hours. It excludes software, implementation, privacy review, training, and correction of historic data. Treat it as a reader-input model.
The tool comparison
Jane and ChiroTouch can both support the reporting question, but they expose different operating models. Atlas and Referra show other paths: configure a specialty platform or add a dedicated relationship tool.
| Option | Source capture pattern | Reporting pattern | Verify before selection | Likely fit |
|---|---|---|---|---|
| Jane | Patient and staff referral entries | Patient/revenue by referral | Cohort, accounting basis, exports | Jane-centered practice |
| ChiroTouch | EHR source/referral records | Multiple source and tree reports | Edition, filters, exports | ChiroTouch-centered practice |
| Atlas | Referral tracking in specialty stack | Practice-growth reporting | Fields, triggers, reward controls | Atlas users wanting native setup |
| Referra | Dedicated relationship CRM | Relationship follow-up | Currency, security, integrations | Professional-network outreach |
| Custom governed report | Controlled cross-system model | Reconciled aggregate output | API access, monitoring, ownership | Multi-system exceptions |
Dedicated software can be inexpensive but still create a second source of truth. According to Referra's product page, the free tier allows up to 25 contacts, annual access is listed at $39.99, and lifetime access at $79.99; the vendor also says it tracks relationships, not medical records. Verify product currency, platform support, data handling, and integration before purchase.
If the current hub cannot supply durable fields or exports, the Jane alternatives guide helps frame a system change. Do not replace an EHR merely to improve one report until the team has tested a controlled export and staff process.
Payback math
Calculate benefit from time the practice can actually avoid and decisions it can actually improve. Do not assign speculative revenue to every referral record.
monthly net benefit = realizable admin value − software − support − monitoring
payback months = implementation ÷ positive monthly net benefit
| Illustrative input | Small practice | Base practice | Multi-location |
|---|---|---|---|
| Manual hours per month | 8 | 23 | 70 |
| Avoidable share | 30% | 55% | 65% |
| Loaded hourly value | $30 | $36 | $45 |
| Gross time value | $72 | $455 | $2,048 |
| Monthly software/ops | $50 | $220 | $750 |
| Implementation | $600 | $2,400 | $7,500 |
| Net monthly benefit | $22 | $235 | $1,298 |
| Simple payback | 27.3 months | 10.2 months | 5.8 months |
Run downside cases: lower completion, twice the exception rate, delayed API access, and no realizable time value. US Tech Automations is not a fit when a native report plus a monthly staff review costs less and remains reliable. It becomes plausible when cross-system joins, failures, and exceptions recur at enough volume to justify ownership and monitoring.
Who this is for
This workflow fits chiropractic owners, practice managers, and marketers who cannot reconcile booking answers with arrived patients or revenue. It is particularly useful for multi-location clinics, clinics with professional-referral relationships, and teams replacing an uncontrolled spreadsheet.
It is not for ranking individual clinicians without governance, copying PHI into a generic CRM, paying professional referral rewards without legal review, or inferring sensitive clinical relationships. If the primary issue is lead follow-up rather than source truth, use the Podium-to-HubSpot chiropractic workflow. If the decision is patient-communication software, the Birdeye versus Podium comparison is the more relevant starting point.
FAQs
What is chiropractic referral source tracking?
It is the controlled capture and reporting of how new patients found the clinic, who referred them where applicable, whether they arrived, and which authorized financial basis is attributed to the source.
Should a clinic use free text for referral sources?
No, not as the reporting key. Free text can be preserved for audit and detail, while a reviewed stable code drives grouping and trend analysis.
Are patient referrals and physician referrals the same?
They are distinct relationships. A patient advocate, a marketing acquisition source, and a professional care referral should occupy separate fields with separate access and governance.
When should revenue be attributed?
Use a documented accounting basis after the appointment and financial state are authoritative. Decide whether the report uses invoiced or collected amounts and how it handles refunds, credits, packages, and timing.
Can AI clean every referral-source value automatically?
No. Deterministic aliases are automatable, but ambiguous names, conflicting answers, and professional identities require a human decision with an audit trail.
Does US Tech Automations integrate natively with Jane or ChiroTouch?
No registry-confirmed native connector is claimed here. A custom/API design may be possible when the selected product technically exposes supported access, but that must be verified before scope or pricing.
Key Takeaways
Reliable referral attribution starts with vocabulary, not a dashboard. Give acquisition source, referring patient, and professional referrer separate homes; preserve original answers; require review for uncertainty; and wait for arrived and financial states before reporting outcomes.
Jane and ChiroTouch provide different specialty-platform paths, while Atlas and Referra illustrate other implementation choices. Choose the smallest architecture that preserves truth. When cross-system normalization and reconciliation remain, US Tech Automations can evaluate a monitored workflow through its live agentic-workflows route; when a native report is sufficient, keep it native.
About the Author

Helping businesses leverage automation for operational efficiency.
Related Articles
See how AI agents fit your team
US Tech Automations builds and runs the AI agents that handle this work end to end, so your team doesn't have to.
View pricing & plans

