Every health system has made a serious investment in its EHR, and for good reason. It's the foundation on which hospital operations run, from scheduling, managing the OR, documentation, and the floor. But the accountability CMS now assigns goes beyond what EHRs were designed to accomplish. The Transforming Episode Accountability Model (TEAM) holds participating hospitals responsible for costs 30 days after a procedure, while CJR-X, which was finalized August 2026, extends that to a full 90-day episode for nearly every eligible joint replacement in the country, beginning January 1, 2028. In both models, care quality–from readmissions and complications to patient experience and patient-reported outcome measures (PROMs)–directly impacts reimbursement.
That is a job the EHR was never designed to do. This is not a knock on any EHR; it is an assessment of what the limitations of these systems are and what is needed to complement them in the new healthcare landscape. Episode-based accountability for cost and quality exposes two gaps that quality and IT leaders are increasingly expected to close together: reach and visibility.
The Reach Gap: Accountability Now Lives Outside The Four Walls
EHRs were built to manage care inside the hospital's walls. Episode-based models make what happens before and after the inpatient stay the difference between hitting a target price and owing money back.
One of the most consequential drivers of episode performance is something hospitals cannot directly control: what patients do when they go home. Pre-op preparation, adherence, home-based recovery, and knowing early when a patient is off track are all metrics that are not native to the inpatient record. Under a 90-day episode, those gaps carry financial implications.
Extending the EHR's reach across the episode with a platform that provides condition- and procedure-specific education, remote monitoring, and bi-directional messaging is how organizations actually manage the 90 days they are now accountable for, and it can be done without adding brick-and-mortar or net-new staff. This is where a purpose-built patient engagement and education layer complements the system of record rather than competes with it.
The Visibility Gap: Capturing A PROM Isn't The Same As Knowing You're Compliant
An EHR can capture a PROM. But what quality teams routinely struggle with is capturing long-term PROMs and then aggregating PROMs compliance across a whole cohort and answering, on demand, a simple question: are we compliant right now, and where are the gaps?
Under CJR-X, the THA/TKA PRO-PM is a scored component of the Composite Quality Score, and a hospital must clear a minimum quality standard to earn reconciliation. Hospital and orthopedic leaders need a live gap analysis–which patients are missing pre-op or one-year surveys, which cohorts sit below threshold, what it would take to close the gap–rather than multiple raw data exports they have to reassemble and manually format in a spreadsheet.
This is also where the limits of the system of record show up most plainly. EHRs are organized around the individual patient encounter, not around a mandate-level view of a cohort, so teams often tell us it is difficult to aggregate or search their outcomes data in one place. A leader who needs to know how a full LEJR population is tracking against a CMS threshold (and act before the reporting window closes) needs that data organized around the measure, refreshed continuously, and paired with the outreach that actually changes it.
Why This Matters To IT, Not Only To Quality
As mandates push hospitals into full episode-of-care management–pre-op, post-acute, home health, physical therapy–which is squarely outside what the EHR and the IT organization were originally tasked with, that reframes the conversation for quality and technology leaders in three useful ways:
- It extends the ecosystem you already own: Complementing your EHR with tools that can push education, monitoring, and structured data collection beyond the four walls enhances the EHR investment.
- It's augmentation, not replacement: The right layer writes structured data back into the record and surfaces the aggregate, cohort-level view the EHR isn't organized to produce, while patient engagement outside the walls can lift activity inside your patient portal.
- It should be low lift: The appeal to IT is a solution that plugs into an well-defined and established integration approach and meets enterprise security expectations–SOC 2 and HIPAA compliant–without a heavy internal build.
What To Look For Before The Next Mandate
Whether you sit in IT, quality, or service line leadership, a handful of questions will tell you quickly whether a solution is built for the world CMS is creating:
- Does it extend our reach across the full episode we're accountable for: 30 days under TEAM, 90 under CJR-X? And can it accomplish long-term patient tracking and data collection?
- Can it show compliance at a glance and run a real gap analysis, or does it only store surveys?
- Does it write data back into our EHR and complement–not duplicate– what we already run?
- Is it built for the integration and security standards our IT team requires?
The EHR will stay at the center of the health system. But closing these reach and visibility gaps is what turns a strong system of record into a program that is genuinely ready for the next mandate. To talk through how leading institutions are extending their EHR investment across the episode, reach out to the Force team:
