Skip to main content
Measurement-based care (MBC) is the practice of giving your clients validated outcome measures on a regular schedule and using the results to guide care. Inside Rivet, that means three things:
  1. You can open a validated measure during a video session and push it to your client’s device in one tap.
  2. Scores compute live as your client answers — totals, subscales, severity bands, and any high-risk item flags appear in your view as they fill.
  3. The completed measure copies into your session notes — the score block, the severity band, and (for SOAP / DAP) the underlying responses if you want them.
The library covers the screening measures you actually use: PHQ-9, GAD-7, K10, DASS-21, PCL-5, PSS-10, ISI, AUDIT, plus child / adolescent versions, ACT process measures, eating, OCD, ADHD, bipolar, and the clinician-administered six (HAM-D, HAM-A, Y-BOCS, YMRS, YGTSS, C-SSRS).

​
What that actually means

The transparent version, so you know what to trust. Live scoring. Every standardized scale has its scoring built in. Rivet sums the items, applies any subscale multipliers (DASS-21 × 2, WHO-5 × 4), looks up the matching severity band, and renders the score in your view as the client fills. Reverse-scored items (PSWQ, EPDS, PSS-10, DERS-18, SDQ, SCS-SF and others) are reversed for you, not in the form wording. The math is the same math the source paper specifies. Audit row, not result row. When you open a measure, Rivet records which template, which version, which session, when it started and ended, and whether you copied or downloaded the result. The audit row carries no answers. The filled measure itself lives briefly so that a reconnect after a network blip restores work in progress, then auto-purges. The persistent home for the result is your EHR — pasted from “Copy for session notes” or saved from the PDF download. Transparent scoring. Every score Rivet displays maps back to a published algorithm. The score block in your notes includes the subscale label, the numeric score, the severity band, and any cutoff that fired. Nothing is inferred or estimated.

​
What MBC in Rivet is not

  • Not a longitudinal database. Trajectory across sessions today lives in your notes, not in a Rivet trend graph. Multi-session score views belong in your EHR for now.
  • Not async homework with reminders. A client can fill a measure on a link you send them, but the design intent is in-session administration.
  • Not a diagnostic engine. Severity bands and cutoffs are surfaced as the published algorithm defines them. Interpretation, diagnosis, and treatment decisions are yours.
The MBC surface lives inside the video session because that’s where you and your client are at the same time — and because the engagement around filling a measure together is part of what makes MBC work clinically. See Administering measures in session.

​
What flows into your notes

When you click “Copy for session notes” or “Download” on a completed measure:
  • The measure title and timestamp
  • Every answered item — verbatim wording on the question, your client’s response on the answer
  • A “Score:” block at the bottom: each subscale’s label, score, severity band (where defined), and any cutoff that fired (“[Cutoff: probable PTSD]”, “[Cutoff: clinical insomnia]”)
  • Any per-field notes you typed alongside the form during the session (private to you, never sent to the client)
If the measure is a SOAP or DAP note, the score from a separately-administered measure earlier in the same session can autofill into the Objective or Data section — so a PHQ-9 score and its band land in your note without re-typing.

The evidence base

Why MBC matters clinically.

Administering measures in session

The collaborative fill flow.

Clinical change thresholds

What counts as a meaningful change on PHQ-9, GAD-7, PCL-5, and more.