What this report is
The Organization Performance Report gives you a single, real-time view of how your coding team is performing, rolled up to the team level, with the ability to drill down to each coder. Performance is measured against industry benchmarks, so you are not reading raw numbers in isolation. You are seeing where your team stands relative to the standard.
In plain terms: this is the report that answers two questions without you having to export anything into a spreadsheet and stitch it together yourself.
- Is my team improving?
- Where do they need help?
If your team has been pulling individual coder reports and combining them manually to get a team picture, this report replaces that work.
Who can see it
Access is role-based. Admins, coding managers, and SMEs with reporting access will see the report. Individual coders do not have access to the team-level view of everyone's performance. If someone on your team should have access and does not, that is a permissions setting on their account, not a limitation of the report.
How to access it
Log in as an admin, go to the Reports menu, then Organization Performance Report.
The two tabs
The report is organized into two tabs. You will spend most of your time moving between them.
| Tab | What it answers |
|---|---|
| Overview | How is the team performing as a whole, and where are the gaps? |
| Team Members | Which specific coders are driving those numbers, up or down? |
Start on Overview to spot a trend or a gap, then switch to Team Members to find out who it traces back to.
Overview tab
This tab is your team-level summary. It opens with four summary cards across the top, followed by a set of charts underneath.
The four summary cards
| Card | What it shows |
|---|---|
| Participants | The number of coders included in the assessment population you are viewing. |
| Case Accuracy | Aggregate coding accuracy across that population. |
| Efficiency | Productivity, shown as cases per hour or cases per day (see the toggle below). |
| Total Cases Completed | The total volume of cases finished across the population. |
The Efficiency toggle
The efficiency card has a Day/Hour toggle. Switch it to read productivity as either cases per hour or cases per day, depending on how your organization measures it. This is a display choice. It does not change the underlying data, only how it is expressed.
One thing worth knowing: throughput on its own is not a performance verdict. A fast coder who is inaccurate is not a strong coder. Always read throughput next to Case Accuracy, never on its own.
The charts
Below the cards, the Overview tab shows four charts:
- Accuracy Trend. Month-over-month accuracy. This is where you see direction. Flat or climbing is good. A downward slope across two periods is your early warning.
- Performance by Specialty. Accuracy by specialty, benchmarked against industry averages. This chart justifies the entire report. It tells you not just how the team is doing, but how they are doing relative to the standard, specialty by specialty.
- Coding Accuracy. The accuracy breakdown for the population.
- Case Complexity. The complexity profile of the cases your team is working on, which gives the accuracy numbers context. A team coding heavy, complex cases at a given accuracy is in a different position than a team hitting the same number on simple cases.
How the benchmarking works
The benchmark line is the reference point for the whole report. When the Performance by Specialty chart shows your team above the line, it means your team is outperforming the industry average in that specialty. Below the line means there is a gap. The size of the gap tells you where coaching time is best spent.
If a benchmark has not been configured for your organization, the chart will still show your team's numbers, but you will not have the industry comparison until benchmarks are set.
Team Members tab
This tab takes everything on the Overview tab and breaks it down to the individual coder. This is where team-level numbers become accountable to specific people.
For each coder, you will see:
| Column | What it tells you |
|---|---|
| Cases Completed | Volume that the coder has finished. |
| Accuracy Average | That coder's accuracy across their cases. |
| Throughput | That coder's productivity. |
| Weakest Specialty Area | The specialty where that coder is struggling most. This is the single most useful column for coaching, because it points straight at the assignment to give them next. |
| Last Login Date | When the coder was last active. A coder who has not logged in is the most likely reason a "completed" number looks low. |
Team Specialty Accuracy chart
On the right side of the Team Members tab, the Team Specialty Accuracy chart ranks specialties against the benchmark. Use the sort control to order it low to high, which immediately surfaces the specialties where your team falls furthest short. That ordering is the fastest way to decide where to focus training.
Using the filters
A filter bar lets you slice the data so you are looking at the slice that matters instead of the whole population at once. You can filter by:
- Date range
- Facility
- Cohort
- Code type
- Specialty
- Patient type
The filter bar can also be collapsed for a cleaner full-dashboard view when you are presenting or reviewing.
A practical note on patient type and specialty filters: inpatient, outpatient, and pro-fee coding move at very different speeds and hold to different accuracy expectations. If you are evaluating throughput or accuracy, filter down to a comparable group first. A blended number across mixed patient types can make a balanced team look slower or less accurate than it actually is.
How to actually use this report
A short workflow that turns the report into decisions instead of just numbers.
- Start on Overview. Glance at the four cards, then look at the Accuracy Trend. Is the line holding, climbing, or slipping?
- Find the gap. Go to Performance by Specialty. Where is the team furthest below benchmark?
- Trace it to people. Switch to Team Members, sort the Team Specialty Accuracy chart low to high, and check the Weakest Specialty Area column to see which coders are pulling that specialty down.
- Check for the easy explanation first. Before assuming a skill gap, look at Last Login Date. Sometimes a low number is an availability problem, not an accuracy problem.
- Assign with intent. Use a coder's weakest specialty to decide what they work next, so practice is pointed at the actual gap rather than spread evenly.
Run this monthly, and you have a repeatable review cycle rather than a one-time look.
Common questions
Does this replace the individual coder reports? For the team picture, yes. The Team Members tab gives you per-coder accuracy, throughput, and volume in one place. You no longer need to pull each coder's report separately just to compare them.
Why is a coder's throughput high but their accuracy low? That is exactly the pattern the report is designed to surface. High speed with low accuracy is a quality problem, not a productivity win. Read the two metrics together and coach toward accuracy first.
My team looks slow compared to another team. Is that real? Filter both teams to the same patient type and specialty before you compare. Throughput is not comparable across different kinds of coding, so an unfiltered comparison can be misleading.
The benchmark comparison is not showing. That usually means a benchmark has not been configured for your organization yet. Your team's numbers will still display. Reach out to your CSM if you need benchmarks set up.
A coder shows zero or very few completed cases. Check the Last Login Date column first. Inactivity is the most common cause before you look at anything performance-related.
Tips
- Read throughput and accuracy together, always. Neither one tells the full story alone.
- Use Case Complexity as context. The same accuracy number means different things on simple versus complex caseloads.
- Treat the Accuracy Trend as your early warning. Two consecutive periods of decline are a signal to act, not wait.
- The Weakest Specialty Area column is your most direct coaching input. It tells you what to assign next.
- Filter before you judge. An unfiltered team-wide view is good for spotting trends, not for fair individual comparison.