Skip to main content

TRP Vital Signs Beta — Your Beta Guide

Learn the weekly validation process and how to submit feedback during the TRP Vital Signs beta.

Overview

Thanks for being one of our first clinics on the TRP Vital Signs Export. This guide covers what the beta is for, what we're asking of you, and how to send us feedback.

Need a refresher on how to use the report — mapping, running it, exporting? That's in Using Your TRP Vital Signs Report.

What this beta is for

We built ChiroHD's TRP Vital Signs Export so your team can generate your TRP metrics automatically instead of compiling them by hand each cycle. Before we release it to every practice, we're running it with a small group of real TRP-coaching clinics to make sure the numbers are right and to catch the real-world edge cases only working practices hit. Your feedback during these few weeks is what gets it right.

What we're asking of you

Two simple things:

  1. Use the report on your normal reporting cadence. Whenever you'd normally pull your Vital Signs — weekly, monthly, however your practice runs — run our report for that same date range too. The more you use it on real data, the more useful your feedback is.

  2. Tell us when something looks wrong. That's the whole game. A number that doesn't match, a metric reading 0 when it shouldn't, anything confusing — send it our way (see below).

How you check the numbers depends on where your clinic is today:

  • If you already track your TRP metrics manually: comparing our report to your own numbers is the single most valuable thing you can do. Run our report for the same period and look for mismatches. You can keep it as simple as a side-by-side glance — if a shared comparison sheet would help, just ask and we'll set one up, but it's optional. The important part is flagging the mismatches, not the format.

  • If you're not currently tracking manually (often because the manual process is too time-consuming): no problem and no comparison needed. Just run the report regularly and spot-check it against what you know about your patient flow — "does this match how my practice is actually doing?" Drill in on anything that looks off.

Your fastest tool: the 🔍 magnifier

When a number looks wrong, click the 🔍 magnifier on that row. It shows exactly which patients are behind the number — their IDs, appointment dates, statuses, and referral categories. Most clinics find the cause in under five minutes this way. When you report something, include the patient IDs and dates from the drill-down — that's the fastest path to a fix.

How to send feedback

Beta Feedback form: https://wkf.ms/49q8CcP (also in your kickoff email)

Use it for anything — discrepancies, bugs, mapping questions, the report not loading, or "is this supposed to work this way?" The form asks for a short summary, what you expected vs. what you saw, the date range you ran, the metric involved, and any patient IDs/screenshots. Most fields are optional — send what you have; patient IDs and the date range are the most useful.

We watch the form every day, and you'll get an email reply from our Product Manager within one business day.

Where to focus, if your time is limited

We'd love eyes on the whole report, but these blocks carry the most risk and benefit most from real-clinic review:

  • NP Conversions — the heart of the report (PVA and Lifetime Value both depend on it)

  • R4 / R5 / R6 retention — the most complex, multi-care-plan logic

  • Net Momentum (in the Volume block) — sensitive to upstream issues

Everything else (the NP funnel, ROF, volume, compliance, financial through Collections) is worth a look when you have time.

Things we're still tuning

So you know what's expected vs. an actual bug — you don't need to report these (we're on them), but related feedback is always welcome:

  • Reactivation rows + Net Momentum. The five "Reactivations > 6 Months" rows are calculated automatically, but we're still finalizing the exact definition with TRP — treat those (and the Net Momentum value that uses them) as provisional for now.

  • Exempt / comped patients. Staff or free-care patients currently count in volume metrics, which can inflate visit counts and deflate per-visit dollars (PVA, CVA). We're adding a way to exclude them — for now, mentally adjust for them.

  • Case-type changes mid-care (e.g., a maintenance patient switches to an auto/PI case after an accident). They currently re-appear as a new patient; we're confirming with TRP the right handling so it doesn't skew NP Conversion.

  • Care Plan documentation. Care Plans are required for the report, and the Care Plan screen changes a bit when TRP is enabled — we're writing a deeper article. For now, send care-plan questions through the feedback form.

If something looks wrong that isn't on this list, please surface it — that's exactly what this beta is for.

What happens after you submit

  1. We see it within minutes (it notifies the team working on this feature).

  2. We triage same-day — bug, mapping, definition, training, or design.

  3. The ChiroHD Product Manager emails you back within one business day with what we found.

  4. If it's a bug we fix, we'll loop back when the fix is live so you can re-run and confirm.

Timeline + wrap-up

The beta runs for at least a month, ideally through broad release. Near the end we'd love a quick 30-minute wrap-up call to hear what you found — optional, and we'll reach out to schedule as we get closer.

Questions

Anything during the beta → the feedback form. 🚨 Urgent → contact Drake or your TRP coach.

Quick recap

  • Use the report on your normal cadence; if you track manually, compare the numbers (a comparison sheet is optional — just ask if you want one).

  • Flag anything that looks wrong via the feedback form — that's the point of the beta.

  • 🔍 magnifier is your fastest debugging tool; include patient IDs + date range when you report.

  • Priority areas: NP Conversions, R4/R5/R6 retention, Net Momentum.

  • Reactivation + Net Momentum are provisional; exempt-patient handling, case-type changes, and a deeper Care Plan article are in progress.

  • We reply within one business day.

Did this answer your question?