Patient-Reported Outcome Measures (PROMs) in Hospital Quality Reporting

“Patient-reported outcome measure” gets used loosely enough that it is worth being precise about what it means for a hospital quality program, as opposed to what the same three words mean in a clinical trial. This page is written for the audience that actually has to operationalize the difference — infection preventionists, patient-safety officers, quality directors, and risk managers running a CMS reporting calendar — not for a clinical-research team designing an endpoint. The two uses share vocabulary and, often, the same underlying instrument, but they answer different questions, sit in different regulatory frameworks, and fail in different ways when a hospital gets the mechanics wrong.

PRO vs. PROM: the distinction a quality program has to get right

A patient-reported outcome (PRO) is the outcome itself — a report, coming directly from the patient without a clinician’s interpretation, about the status of their own health condition (pain, function, symptom burden, general health). A patient-reported outcome measure (PROM) is the validated instrument — the actual questionnaire — used to collect that report. The FDA’s Clinical Outcome Assessment framework, built for the drug- and device-approval context, defines a PRO the same way: “a measurement based on a report that comes directly from the patient about the status of a patient’s health condition, without amendment or interpretation.” That framework and its instrument-qualification pathway exist to support regulatory approval decisions, and CASRAI’s own ePRO (Electronic Patient-Reported Outcomes) entry covers the trial-specific mechanics — case report form integration, source-data verification, protocol-specified collection windows tied to a study visit schedule.

Hospital quality reporting borrows the same instrument logic but plugs it into a completely different apparatus: a public reporting program, run by CMS, with its own eligible-population rules, its own collection windows, its own minimum-response-rate and minimum-case-count thresholds, and (eventually, depending on the measure) its own path into a payment program. A hospital quality director does not need to know how a PROM gets qualified as an FDA drug-development tool. They need to know which PROM their EHR-integrated survey vendor is administering, when it goes out, and what happens to the measure if too few patients answer it.

How PROMs plug into the Hospital IQR Program: the THA/TKA PRO-PM

The clearest example of a PROM functioning as a hospital quality measure — as opposed to a satisfaction survey or a clinical-outcomes registry entry — is the Hospital Inpatient Quality Reporting (IQR) Program’s patient-reported outcome-based performance measure (PRO-PM) for elective primary total hip and/or total knee arthroplasty (THA/TKA). CMS built this measure around a simple idea: for an elective joint replacement, “did the procedure improve the patient’s function and reduce their pain” is a legitimate quality signal in its own right, alongside the administrative-claims-based measures (readmission, complication rates) the program already tracked.

Structurally, the measure works by comparing a patient’s pre-operative score on a validated function/pain instrument against their score roughly a year after surgery, then risk-adjusting the change (age, comorbidity burden, baseline function, and other case-mix factors) so hospitals aren’t penalized for taking on more complex patients. CMS phased the measure into the IQR Program gradually — starting with voluntary data submission with no public reporting, moving toward mandatory data submission, and only later toward the measure actually counting in scoring and public display. That phase-in trajectory is a normal pattern for a new PRO-PM (CMS has done the same staged rollout for other complex measures) and it moves with each year’s Inpatient Prospective Payment System (IPPS) rulemaking cycle. Because the exact current-cycle reporting status, response-rate threshold, and minimum case count are set (and periodically revised) in that year’s IPPS final rule and the corresponding IQR Specifications Manual, don’t treat any specific number here as durable — confirm the current requirement directly against the live QualityNet Specifications Manual before building a reporting workflow around it. What’s stable, and what this page focuses on, is the operational shape of the measure: two collection points, a defined instrument set, and a response-rate gate that determines whether a hospital’s data is usable at all.

Which instrument actually gets used

For THA/TKA, the PRO-PM doesn’t rely on a single all-purpose questionnaire. It combines a joint-specific instrument with a general health-status instrument, because the two answer different questions:

• HOOS, JR. (Hip disability and Osteoarthritis Outcome Score, Joint Replacement) and KOOS, JR. (Knee injury and Osteoarthritis Outcome Score, Joint Replacement) — short-form, joint-specific instruments purpose-built for arthroplasty populations. They ask about pain and function specific to the operated joint (stiffness, difficulty with stairs, standing from a chair), which a generic health instrument won’t capture with enough sensitivity to detect a real surgical improvement.
• A general health-status instrument (commonly PROMIS Global Health, sometimes VR-12/SF-12 in earlier program years) captures overall health separately from joint-specific function, so the measure isn’t blind to a patient whose joint improved but whose overall health didn’t, or vice versa.

The general lesson for a quality program building or extending PROM collection into other service lines: pick a condition-specific instrument where one exists and is validated for the population (it will be more sensitive to a real clinical change than a generic instrument alone), and pair it with a short generic instrument only when the program specifically needs to track overall health status alongside the condition-specific outcome — not by default, since every additional instrument is additional respondent burden and additional missing-data risk. Instrument selection should also weigh: available reading-level/language translations, whether a validated short form exists (short forms measurably reduce non-response versus long-form legacy instruments), and whether the instrument is already embedded in the EHR or survey vendor’s build, since a custom instrument means a custom validation and integration project before a single data point is collected.

Administration timing: why the windows exist and how to actually hit them

A PROM used for hospital quality measurement needs data at two points relative to the same surgery, and both windows exist for a specific measurement reason:

• Pre-operative baseline. Collected in a defined window before surgery — typically administered during the pre-operative clinic visit rather than left to the patient’s initiative, because a baseline collected too close to or too far from the procedure introduces noise (a patient managing a recent flare answers differently than one further from it). Practically, this means the survey has to be built into the pre-op workflow itself — handed out or sent electronically at a scheduled pre-op visit — not treated as a follow-up task after the surgery is already booked.
• Post-operative follow-up. Collected roughly a year after surgery, in a defined window wide enough to be operationally realistic but narrow enough that “one year” means something consistent across patients. This is the harder point to hit, because the patient is no longer in front of anyone at the hospital by default — it depends on an active outreach process (patient portal message, mail, phone, or a scheduled post-op visit that’s timed to land inside the window) rather than a captive clinical encounter.

The practical failure mode is asymmetric: pre-operative response rates are usually easy, because the patient is physically present in a clinic that can hand them a tablet or a paper form before they leave. Post-operative response rates are where programs lose their data — patients who feel fine stop engaging, contact information goes stale over a year, and outreach that isn’t built as a defined, owned workflow (a specific role or vendor responsible for tracking who’s due, when, and following up on non-response) drifts. Programs that hit their response-rate threshold consistently tend to share the same features: outreach is automated off the surgery date rather than relying on manual tracking, multiple contact modes are used (not just mail), and there’s a defined escalation (a second attempt, a different mode) before a patient is counted as non-responsive rather than simply dropped.

Why the response rate itself is a gate, not a footnote

A PRO-PM built on a comparison of two survey time points only produces a valid, usable measure if enough of the eligible patients answered both surveys — a low response rate doesn’t just shrink the sample, it introduces response bias, since patients who feel worse after surgery are less likely to respond than patients who feel better, which would make outcomes look artificially good. That’s why CMS’s PRO-PM design (like most PROM-based quality measures, not just this one) pairs a minimum case-count threshold with a minimum response-rate threshold: a hospital with too few eligible cases, or with eligible cases but too low a response rate, doesn’t get a publicly reported score for the measure at all, rather than getting a score built on an unrepresentative subset. For a quality team, that makes the response rate itself the thing to manage operationally, not just a data-quality nicety — a hospital can do everything else right on instrument selection and still end up with no reportable measure if the post-operative follow-up workflow doesn’t produce a high enough response rate against its current threshold.

Where PROM data does, and doesn’t, connect to other CMS programs

It’s worth being precise about what a PRO-PM currently does with a hospital’s IQR Program participation, since it’s easy to overstate the connection to payment. Public reporting under the Hospital IQR Program and a measure’s use in a payment-adjustment program (like Hospital Value-Based Purchasing) are two separate steps, and CMS has historically moved a new PRO-PM through public reporting well before — if ever — incorporating it into a VBP domain. Don’t assume a THA/TKA PROM data-quality problem is automatically a reimbursement problem in the current reporting year; confirm the measure’s actual current status (IQR-only public reporting vs. VBP-linked) against the current year’s IPPS final rule rather than treating the two programs as interchangeable, since that distinction changes how urgently a data-collection gap needs to be escalated internally.

PROMs beyond joint replacement

THA/TKA is the clearest, most mature example because it’s furthest along CMS’s PRO-PM pipeline, but the same instrument-plus-timing-plus-response-rate logic applies anywhere a hospital quality program is considering (or is required to run) a condition-specific PROM — spine surgery, cardiac procedures, and other elective surgical service lines have their own validated condition-specific instruments in active use in registries and, in some cases, emerging CMS measures. A PROM program built for one service line (the pre-op workflow integration, the outreach infrastructure for the follow-up window, the response-rate tracking) is largely reusable infrastructure for the next one, which is a reason to build the operational pieces — not just the instrument selection — as a program capability rather than a one-off project scoped to a single measure.

PROM collection is distinct from, and complementary to, the patient-experience surveys already running on the same reporting calendar. HCAHPS asks whether care felt well-communicated and well-coordinated; it is not designed to detect whether a joint replacement actually restored function. Both matter to a quality program, and both run on their own collection windows and response-rate rules, but a low HCAHPS composite and a low PROM response rate are different problems with different fixes — don’t diagnose one from the other. For the broader measurement infrastructure a PROM sits inside — chart-abstracted versus survey-based versus claims-based measures, and how each reports into IQR — see CASRAI’s guides on nurse-sensitive indicators and eCQM reporting for hospitals, and the patient-safety pillar for the full quality-measurement landscape this page is part of.

Frequently asked questions

Is a PROM the same thing as a patient-satisfaction survey?

No. A patient-satisfaction or patient-experience survey (like HCAHPS) asks how care felt — communication, responsiveness, coordination. A PROM asks about the patient’s actual health status — pain, function, symptoms — using a validated instrument, independent of how satisfied they were with the encounter. A patient can report excellent function on a PROM after a rough experience, or the reverse.

Does every hospital have to report the THA/TKA PRO-PM?

Reporting requirements for this measure have moved through a multi-year phase-in under the Hospital IQR Program, from voluntary submission toward mandatory submission and, eventually, scored public reporting. Whether reporting is currently mandatory, and what happens to a hospital that doesn’t meet the response-rate threshold, is set in that year’s IPPS final rule — check the current IQR Specifications Manual on QualityNet rather than assuming last year’s requirement still applies.

What counts as a “good” response rate for a PROM program?

CMS sets a specific minimum threshold for the THA/TKA PRO-PM in its current specifications, and that number has been revised across program years, so cite the live specification rather than a fixed figure. Operationally, the more useful target for a quality team is often higher than the compliance minimum, since a response rate barely over the floor leaves little margin if a reporting period runs short — and a genuinely representative sample (not just a compliant one) is what makes the measure clinically meaningful internally, not just publicly reportable.

Can PROM data be collected electronically instead of on paper?

Yes, and most active programs do — portal-based, tablet-based, and SMS/email-linked electronic collection are all standard practice, and CMS’s specifications accommodate electronic administration alongside paper and phone. Electronic collection generally improves post-operative follow-up response rates over mail-only outreach, mainly because it supports the multi-attempt, multi-mode outreach pattern that drives response rate up, rather than because the format itself changes how patients answer.