Annual salary survey: Pain coders – push back against common reasons you didn’t receive a raise

Why This Topic Matters

The article helps readers place their compensation in context and understand how survey data can support discussions about raises, responsibilities, certification effort, and practice performance. It is relevant to anyone comparing pay trends within pain management coding and evaluating whether review criteria and salary expectations align with actual job duties.

Article Sections

1. Salary survey overview

   Introduces the survey population and summarizes broad compensation trends for pain coders across recent years.

2. No one gets a raise until revenue goes up

   Discusses ways coders may document practice performance and operational improvements when addressing pay concerns.

3. Your new duties don’t merit a raise

   Reviews how changes in responsibilities and implementation projects factor into compensation discussions.

4. Practices don’t pay certified coders more

   Covers certification status, associated survey findings, and the general effort involved in maintaining credentials.

5. Certification snapshot: Pain coders vs. all specialty coders

   Presents a comparison table summarizing certification-related survey metrics for pain coders and coders across specialties.

6. Your current salary makes sense for a practice this size

   Looks at how practice size relates to salary and how respondents’ pay varies by organization size.

7. Based on your annual review, you didn’t earn a raise

   Examines the relationship between annual review criteria, job duties, and whether raise decisions reflect actual work performed.

8. That’s what coders in this area are paid

   Discusses regional salary differences and the geographic factors highlighted in the survey data.

9. Didn’t we just give you a raise?

   Addresses tenure with the practice and how length of employment relates to reported raise patterns.