The Real Reason Your PI Scores Stall

If your Promoting Interoperability scores have been stuck in the same place for a while, you are not alone. I talk with MIPS providers every week who feel like their PI scores should be higher than what they see on their performance reports. They know their teams work hard. They know they complete most tasks on time. Yet the numbers do not move. When we take a closer look, we usually find that the problem has less to do with effort and more to do with hidden gaps that only show up during a detailed PI review. Since our weekly compliance conversations often circle back to PI challenges, I want to walk you through the real reasons these scores stall and what you can do to fix them before the next reporting cycle begins.

This guide will help you understand why PI becomes a sticking point for many practices. My goal is to give you the insider view that most providers never hear until it is too late. By the end, you will have a clearer path to protecting your performance and improving your results.

1. The Hidden CEHRT Problems That Slow Your PI Progress

When PI scores level off, Certified Electronic Health Record Technology is usually at the center of the problem. The tricky part is that many providers do not control their CEHRT environment. They depend on their vendor or their health system to manage updates, certification timelines, and the activation of required features.

Through client work and current market reporting, the CEHRT issues that appear most often include:

A. Missed or delayed certification updates

A CEHRT product must stay certified to remain valid for PI reporting. When certification lapses, even for a short period, your practice may unknowingly submit data from a system that no longer meets requirements. This is one of the most common issues we uncover. It is also one of the easiest to miss because updates do not always roll out on time, and the communication around those updates can be uneven.

B. Decertification without early notice

Some products lose certification because they fail to meet updated standards. These decertifications can occur with little warning. Providers often learn about the issue long after the reporting period has started, which means months of PI work may already be out of alignment. This leads to audit risk and stalled scores that do not accurately reflect the team's effort.

C. Required features that are not activated or not connected

Even when your CEHRT is certified, it may not be configured correctly. I often see systems where the right features exist but are not turned on. Examples include certain clinical data exchange services, direct messaging functions, or audit logs that prove actions were completed. Any inactive component can stop a measure from scoring correctly.

D. Workflow gaps inside the CEHRT environment

Some teams rely on manual workarounds because their CEHRT setup was never optimized for their actual workflow. When documentation is split between paper, outside portals, and internal systems, the CEHRT cannot collect what it needs to score the PI measure. This leads to missing data and lower category performance, even when your staff is doing everything they think is required.

Here is my insider tip for CEHRT issues:
Most practices do not discover their CEHRT gaps through routine IT checks. They find them during PI troubleshooting after scores fail. You can avoid this by scheduling a quarterly CEHRT review that focuses only on PI settings, certification status, and feature activation. This keeps surprises away and protects your performance year-round.

2. Reporting Problems That Hold Back Your PI Scores

Another reason your PI category stalls is that practices sometimes fail to report every applicable measure. PI is not like the Quality category, where you select a certain number of measures. In PI, each required measure must be reported. If one is missing, you can lose the entire category.

Three issues show up again and again.

A. Assuming optional measures apply when they do not

Some measures allow exclusions, but those exclusions are not automatic. Providers often believe they qualify for an exclusion without confirming the exact rules. When the exclusion is not valid, the measure becomes incomplete, and your score drops. Always verify your exclusion criteria with a compliance specialist or trusted regulatory resource.

B. Reporting a measure but failing to support it with verifiable data

PI requires both reporting and proof. If your workflow does not create the right audit trails inside your CEHRT, your reported numbers may not match what the system can validate. Scores stall because the data behind the scenes does not support the submission.

C. Relying on manual uploads or external spreadsheets

PI measures should flow from your CEHRT to your submission process. When teams rely on manual documentation, they increase the chance of missing a required field or miscounting a denominator. It only takes one missing field to reduce your total PI score.

Action step:
Before the next reporting cycle begins, make a list of all PI measures and confirm which ones apply to your setting. Then check your workflow to ensure each measure has a complete data path from start to finish.

3. Fragmented Workflows That Make PI Reporting Harder Than It Needs To Be

Even when CEHRT is certified and measure reporting is complete, your PI score can still flatline if your internal workflows are not aligned with the program's expectations. Many practices underestimate the extent to which workflow design influences PI success.

Common workflow problems include:

A. Teams that document in multiple places

When staff members record information in different systems, portals, or paper files, your CEHRT may never receive the information it needs. This is one of the top reasons for missing PI data. The CEHRT can only calculate what it can see.

B. Unclear ownership of PI tasks

If no one owns the daily PI tasks, those tasks become optional. For example, patient portal invitations may go unsent or health information exchange functions may not be monitored for success or failure. PI measures depend on consistent follow through, and unclear ownership leads to incomplete performance.

C. Overburdened staff who focus on urgent tasks instead of ongoing PI steps

Your team works hard. They juggle clinical tasks, patient requests, and administrative duties. When workflows are too heavy, PI requirements get pushed aside. Over time, this pattern leads to declining PI performance and missing audit-ready documentation.

A workflow improvement you can try:
Assign each PI function to a specific role and build a simple daily or weekly checklist. This reduces guesswork and creates consistent habits that improve your score.

4. Connectivity Problems That Limit Your Ability To Exchange Information

Promoting Interoperability is built on information exchange. If your internet connection is unstable or slow, your CEHRT may not be able to send or receive data at the speed required for PI success. This is one of the most overlooked reasons for stalled scores.

Here are the connectivity challenges I see most often:

A. Rural or older buildings with uneven internet speeds

When internet performance dips, data exchange fails. PI measures depend on the timely delivery of information to outside networks. Even short outages can affect your measure data.

B. Systems that rely on unsecured or weak backup connections

Some practices use low-bandwidth failover connections. These may keep the office running, but they do not support full PI data exchange. Your CEHRT may show partial or incomplete activity, which lowers your PI score even if everything else is correct.

C. Firewalls and security tools that disrupt connections

Security is essential, but strict settings can block required PI functions. If your team notices missing confirmations or failed message transmissions, your connectivity settings may need a more careful review.

Actionable recommendation:
Run a quarterly connectivity test that checks upload speeds, stability, and firewall settings. This protects both your security posture and your PI requirements.

5. How To Fix Stalled PI Scores Before the Next Cycle

Now that you understand the most common causes of stalled PI scores, here is a set of steps you can take to start improving performance right away. Each step is designed to give you more confidence as you head into the next reporting year.

1. Complete a CEHRT certification check
Confirm that your CEHRT is certified, up to date, and activated with the required PI features. Ask for documentation that proves this status.

2. Validate each PI measure against your workflow
Make sure your team can describe exactly how data flows into your CEHRT. If they cannot explain it, the workflow is not ready.

3. Test all information exchange functions
Run test messages, verify receipt, and check logs to confirm data moves as expected.

4. Review your exclusion assumptions
Never assume an exclusion applies. Confirm it. Document it.

5. Reduce manual documentation
If your PI performance depends on spreadsheets, printed logs, or whiteboard notes, it is time to streamline.

6. Improve staff training on PI tasks
Training does not need to be long. Short, focused sessions help your team build strong habits.

7. Schedule a PI-specific quarterly check
Your weekly compliance routine keeps you informed, but a quarterly deep dive keeps surprises away.

These steps protect your audit readiness and strengthen your ability to score well in the PI category.

PI scores often stall for reasons that do not become apparent until you take a close look at your CEHRT setup, workflows, and connectivity patterns. When you understand these gaps, you gain the power to fix them long before they threaten your MIPS performance. As part of our weekly compliance work, we guide practices through PI reviews, measure checks, and system readiness to help them stay ahead of problems rather than react to them.

If your PI scores refuse to move, or if you want support getting your CEHRT and workflows aligned for the next reporting cycle, reach out to Chirpy Bird. We help you close gaps, protect your performance, and feel confident about every PI submission. After all, PI is kind of our thing.