Using your EHR for patient-reported outcome measures sounds efficient – but the hidden costs in governance, IT, and staff time tell a different story.
The Electronic Health Record (EHR) is the operational backbone of modern clinical care. It’s natural – and smart – to want to maximize every system you’ve already invested in. So when EHR vendors like Epic tout native Patient-Reported Outcome Measure (PROM) functionality, the appeal is obvious: one platform, one workflow, done.
The reality is more complicated. What looks like a streamlined solution often requires a significant – and ongoing – investment of IT, clinical, and administrative resources to do correctly. Once they discover this, many organizations now rely on managed PROM programs to sustain survey capture rates and reporting infrastructure.
If your EHR can send PROM surveys, does that mean your organization has a PROM program? Below, we break down the five most common challenges organizations face when managing PROMs through the EHR.
PROMs in the EHR: Key Takeaways
This article is particularly relevant for:
1. “Free” Surveys Aren’t Really Free
Many EHRs do include validated survey instruments – the KOOS, HOOS, PROMIS Global-10, and others – pre-built in the system. That part is free. But the configuration work required to deploy them correctly is not.
For each patient cohort, your team must make deliberate decisions about:
• When the survey should be sent relative to the triggering event (appointment, surgery, discharge)
• Which system trigger actually assigns and sends the survey
• How long the survey window remains valid before it expires
• What happens when the triggering event is cancelled, rescheduled, or modified
These decisions directly affect data quality and patient experience. Getting them wrong means incomplete data, duplicated outreach or surveys delivered at the wrong point in care. A dedicated governance committee and meaningful FTE time – from both IT and clinical stakeholders – are required to set this up well. The survey may be free; the infrastructure to run it isn’t.
2. Patient-Level Reporting Has Real Limitations
EHRs are designed around the encounter. They are extraordinarily good at capturing data within a defined visit – and increasingly challenged when that data extends beyond it. For PROMs, this creates two persistent problems:
Longitudinal data is difficult to manage.
Most PROM protocols require collection at multiple timepoints – a pre-op survey and a 1-year post-op follow-up for the CMS THA/TKA PRO-PM, for example. Since the EHR’s data architecture is built around billing encounters, post-discharge data collection is a known weak spot. Teams are often left determining manually where long-term PROM responses should live within the system – a governance headache with no clean native solution.
Multi-score surveys don’t display cleanly.
A standard PROM collection set may include both the KOOS (with six subdomains) and the PROMIS Global-10 – and clinicians often want to view both an overall score and the delta between collection intervals. Most EHRs accommodate a single discrete data element in a flowsheet, forcing teams to choose which metric surfaces. Displaying multiple scores requires custom development, which means more IT time and cost.
3. Aggregate Reporting and Benchmarking Are Not Native Capabilities
An EHR is a clinical system, not a PROM registry. It does not carry decades of outcome data that would enable meaningful national benchmarking – and clinicians consistently want to see their patients’ scores compared to broader population norms. That data simply doesn’t exist within the EHR environment.
Aggregate-level PROM reporting is equally limited out of the box. Consider a health system with eight campuses and 20 orthopedic surgeons that wants to view outcomes by site, compare against the system average and drill down by individual surgeon. Achieving that requires: extracting PROM data from the EHR (which is often non-trivial), building a reporting layer capable of slicing the data appropriately, and maintaining that infrastructure as the system evolves. This is not a one-time project – it’s an ongoing operational commitment.
4. Survey Capture Rates Are a Persistent Struggle
Most EHR-based PROM delivery runs through the patient portal. This creates immediate friction: portal adoption varies widely, and even engaged patients are navigating intake forms, appointment reminders, pre-visit screening questionnaires and billing notifications in the same inbox. PROMs are easy to miss – or to ignore.
A common workaround is placing kiosks at care sites so patients can complete surveys on arrival. This works reasonably well for pre-op collection. It does nothing for the long-term data collection that increasingly matters.
For organizations that need 1-year post-op PROM data – and more of them do every year, as payer programs build capture rate requirements into their models – the dominant solution right now is: assign RNs or MAs to call patients manually. It works. It is also extraordinarily resource-intensive, and it doesn’t scale.
5. CMS PRO-PM Raises the Stakes – Significantly
If your organization participates in the CMS THA/TKA Patient-Reported Outcomes Performance Measurement (PRO-PM) program, the margin for error narrows considerably. CMS requires 1-year post-operative PROM data and sets minimum capture rate thresholds – failure to meet them has direct financial consequences. In a survey conducted six months before the initial pre-op reporting deadline, only one in three organizations relying on EHR-based collection believed they would meet CMS thresholds.
That finding reflects what we hear consistently from health systems navigating PRO-PM: the combination of technical setup complexity, limited native reporting and survey capture rate challenges makes EHR-based collection a high-risk path for programs where data completeness is non-negotiable.
The Operational Questions Every PROM Program Must Answer
EHR Enablement vs. Operational Reality in PROM Management
When an EHR enables PROM collection, many organizations assume the compliance burden is addressed. With reimbursement and public reporting at stake-including a 25% Annual Payment Update reduction for failing to meet CMS thresholds for THA/TKA PRO-PM, that assumption deserves a closer look.
EHR tools enable collection. They do not build or run a program. Every question below reflects a gap your organization must fill with people, process and infrastructure.
EHR functionality creates the foundation. It does not eliminate the operational lift required to sustain survey capture rates, validate reporting accuracy, benchmark performance nationally, and manage longitudinal follow-up, especially at 1-year post-op.
The question is not whether your EHR can collect PROs. The question is who is running the program.
Let’s discuss how CODE Technology’s fully managed PROMs program can close the gap for your organization
The Bottom Line
PROMs in the EHR is not inherently the wrong choice, but it is rarely as lightweight as it first appears. Governance setup, IT configuration, longitudinal data management, custom reporting and staff-driven outreach add up quickly. For organizations with modest PROM goals, it may still make sense. For those navigating PRO-PM compliance, payer requirements or a serious quality improvement agenda, it’s worth evaluating purpose-built PROM platforms against the true total cost of the EHR approach.
The right starting point is always the same: define your goals. What do you need from your PROM program – clinically, operationally, and financially? That clarity will tell you more about the right system than any vendor comparison will.
Frequently Asked Questions About PROMs in the EHR
Yes. Systems such as Epic and other major EHR platforms can deploy validated PROM surveys through patient portals, such as MyChart, but enabling surveys and operating a sustainable PROM program are two very different challenges. EHRs do not manage the operational program required to sustain high survey capture rates or national benchmarking.
Capture rates and long-term follow-up. Most EHR workflows rely on patient portals, which often result in incomplete one-year follow-up.
The program requires both pre-operative and one-year surveys with minimum capture thresholds. Maintaining those rates requires ongoing outreach and monitoring that many EHR-based programs are not designed to support.
Many organizations use a PROM platform or managed service to handle survey distribution, follow-up outreach, benchmarking and regulatory reporting while the EHR stores the clinical data.
Patient-reported outcome measures (PROMs) are standardized surveys that capture how patients report their health status, symptoms, and quality of life after treatment. In orthopedics, commonly used PROMs include KOOS, HOOS, and PROMIS Global-10. These instruments are increasingly required for federal programs such as the CMS THA/TKA PRO-PM.
No results found for this category.
