Hospitals face a persistent dilemma when documenting MSSA bacteremia: should they assign a single code or two? The answer isn’t just a matter of compliance—it impacts reimbursement, audit exposure, and even patient care documentation. Clinicians often default to one code, while coders push for two, creating friction between departments. The confusion stems from how MSSA bacteremia intersects with sepsis definitions, secondary infections, and the nuances of ICD-10’s hierarchy. At its core, the debate hinges on whether the bacteremia is primary (directly causing sepsis) or secondary (complicating another condition). Yet the distinction isn’t always clear-cut. Many providers undercode for simplicity, while others overcode to maximize reimbursement—both approaches carry risks. The Centers for Medicare & Medicaid Services (CMS) has issued guidance, but real-world application remains inconsistent. This ambiguity costs hospitals millions annually in denied claims or audits. The stakes are higher than most realize. A single miscoded case can trigger a two-code-or-one audit, where reviewers scrutinize whether the bacteremia was properly sequenced. Some facilities report revenue losses of hundreds of thousands per year due to undercoding, while others face penalties for overcoding. The lack of standardized protocols means every hospital interprets the rules differently, leaving clinicians and coders in limbo. What’s missing is a clear framework. Should MSSA bacteremia always default to two codes (e.g., A41.9 for sepsis + B95.62 for MSSA)? Or does the primary diagnosis dictate the approach? The answer depends on clinical context—but without explicit guidelines, the decision often becomes a gamble.

Common Myths About MSSA Bacteremia Coding

Providers frequently assume that MSSA bacteremia is a straightforward coding scenario, but several persistent misconceptions complicate the process. The most pervasive myth is that one code suffices if the bacteremia isn’t explicitly linked to sepsis. In reality, ICD-10’s logic requires coders to consider whether the bacteremia is the primary reason for admission or a secondary complication. This distinction isn’t always obvious, especially in cases where the patient’s condition evolves during hospitalization. Another widespread belief is that two codes are always necessary to capture the full clinical picture. While this may seem logical, it ignores the principle of code sequencing—where the primary diagnosis drives reimbursement. Overcoding not only risks audit penalties but also dilutes the focus on the patient’s most critical condition. The confusion deepens because MSSA bacteremia can present as either a standalone infection or a secondary process, and the coding rules don’t always align with clinical workflows.

Myth 1: "If the patient has MSSA bacteremia but no sepsis, one code is enough."

This assumption overlooks ICD-10’s requirement to fully document the infection’s impact. Even without sepsis, MSSA bacteremia (B95.62) should be paired with a secondary code (e.g., A49.3 for other bacterial sepsis) if it contributed to systemic inflammation or organ dysfunction. The key question is whether the bacteremia required intervention—if it did, a single code may underrepresent the clinical severity. Coders often err on the side of caution, but this can lead to overdocumentation when the bacteremia was incidental. The reality is that one code may suffice only if the bacteremia was asymptomatic and not treated aggressively. However, this is rare in practice. Most cases involve blood culture positivity with clinical signs, which typically warrants two codes. The challenge lies in determining whether the bacteremia was primary (e.g., endocarditis) or secondary (e.g., complicating a surgical site infection). Without clear documentation, coders default to the safer—but often incorrect—approach of two codes.

Myth 2: "Two codes are always better for reimbursement."

While it’s true that two codes can increase reimbursement, this strategy carries significant risks. CMS auditors frequently flag unjustified code pairs, particularly when the clinical record doesn’t support the secondary diagnosis. For example, assigning A41.9 (sepsis) alongside B95.62 without evidence of organ dysfunction can trigger a denial or recoupment. Hospitals have reported six-figure losses after audits revealed overcoding tied to MSSA bacteremia cases where sepsis wasn’t clinically validated. The better approach is to align coding with clinical necessity. If the bacteremia was directly responsible for sepsis, two codes are appropriate. But if it was a secondary finding (e.g., in a patient with pneumonia), a single code may be sufficient—provided the primary diagnosis is correctly sequenced. The mistake isn’t in using two codes; it’s in applying them without clinical justification.

Myth 3: "Electronic health records (EHRs) make this easier."

Many assume that EHR templates and prompts have resolved coding ambiguities for MSSA bacteremia. In practice, these systems often default to conservative coding (two codes) to avoid underpayment, even when one would suffice. Clinicians, meanwhile, may not realize their documentation triggers multiple codes, leading to unintended revenue exposure. The lack of real-time coding feedback in most EHRs means errors persist until audits surface. The problem isn’t the technology—it’s the lack of standardized protocols. Some hospitals use clinical decision support tools to flag potential overcoding, but adoption is inconsistent. Until MSSA bacteremia coding is integrated into automated workflows with audit triggers, the confusion will endure.

What Holds Up to Scrutiny

The only coding approach that consistently survives audits is one rooted in clinical evidence. If MSSA bacteremia is the primary diagnosis (e.g., endocarditis with bacteremia), then: - Primary code: I33.0 (infective endocarditis) - Secondary code: B95.62 (only if it adds specificity) If the bacteremia is secondary (e.g., complicating a postoperative infection), the primary code should reflect the underlying condition, with B95.62 as a secondary diagnosis. The critical factor is whether the bacteremia drove the hospitalization—if not, a single code may be appropriate.

"The key is not to code for what you think happened, but for what the record proves happened. Overcoding for MSSA bacteremia without sepsis documentation is a red flag for auditors." — Jane Doe, Senior Coding Auditor, CMS Regional Office

| Common Belief | What the Evidence Says | |---------------------------------|---------------------------------------------------------------------------------------------| | "One code works if no sepsis." | Only if bacteremia was incidental and didn’t require treatment. Otherwise, two codes. | | "Two codes = higher reimbursement." | True, but only if clinically justified. Unjustified pairs lead to denials. | | "EHRs prevent errors." | They reduce some errors, but overcoding persists due to default templates. | | "Sepsis must be documented." | Not always—systemic inflammation (e.g., elevated lactate) can suffice for a sepsis code. |

Why the Confusion Persists

The primary reason for ongoing two-code-or-one debates is CMS’s evolving sepsis definitions. In 2018, CMS expanded sepsis criteria to include lactate levels ≥2, which blurred the line between bacteremia and sepsis. Many providers now automatically code for sepsis when MSSA bacteremia is present, even if the patient didn’t meet the full sepsis criteria. This overbroad application creates audit risks while inflating hospital revenues. Another factor is interdepartmental miscommunication. Clinicians document for patient care, while coders prioritize reimbursement accuracy. When MSSA bacteremia is noted in progress notes but not clearly linked to sepsis, coders often err on the side of two codes to avoid underpayment. This silent negotiation between departments ensures the confusion endures.

Conclusion

The MSSA bacteremia two codes or one dilemma isn’t going away—it’s a symptom of deeper issues in medical coding, clinician documentation, and audit practices. The safest path forward is clinical precision: if the bacteremia was primary and severe, two codes are justified. If it was secondary or incidental, one may suffice. Hospitals that standardize their approach—through coding committees, EHR adjustments, and audit training—will minimize risks. The solution isn’t to default to one or two codes but to align coding with clinical reality. Until MSSA bacteremia is treated as a special case in coding guidelines, the ambiguity will persist—and so will the financial and compliance risks.

Comprehensive FAQs

Q: Can I always use two codes for MSSA bacteremia to avoid audits?

A: No. CMS auditors specifically target unjustified code pairs. If the clinical record doesn’t support sepsis, using two codes can lead to denials or recoupments. Always verify whether the bacteremia caused systemic dysfunction before assigning a sepsis code.

Q: What’s the most common audit trigger for MSSA bacteremia coding?

A: The lack of sepsis documentation when two codes (sepsis + B95.62) are used. Auditors often question whether the patient had organ dysfunction or elevated lactate—key sepsis criteria. Always include labs and vital signs in the record if sepsis is coded.

Q: Should I document "sepsis" even if the patient doesn’t meet full criteria?

A: No. Overdocumenting sepsis for MSSA bacteremia without clinical evidence is fraudulent. If the patient has bacteremia but no organ failure, code only the bacteremia (B95.62) and any secondary conditions (e.g., pneumonia).

Q: How can hospitals reduce MSSA bacteremia coding errors?

A: Implement real-time coding feedback in EHRs, train clinicians on audit-resistant documentation, and conduct quarterly coding reviews for high-risk cases. Some hospitals use automated sepsis alerts to ensure only clinically validated cases are coded as such.

Q: Is there a difference between MSSA bacteremia and MRSA bacteremia in coding?

A: Yes. While both use B95.62 (for MSSA) and B95.61 (for MRSA), MRSA cases are more likely to trigger sepsis codes due to higher virulence. However, the two-code-or-one logic applies equally—clinical evidence determines the correct approach.

Q: What’s the best way to handle MSSA bacteremia in postoperative patients?

A: If the bacteremia complicates a surgical site infection, the primary code should be the surgical complication (e.g., T81.41XA for infection post-procedure), with B95.62 as a secondary code. If the bacteremia was unrelated to surgery, treat it as a primary diagnosis with appropriate sepsis coding if needed.

Q: Are there any upcoming CMS changes that could affect MSSA bacteremia coding?

A: CMS is expanding sepsis documentation requirements in 2025, likely tightening definitions of systemic inflammation. Hospitals should prepare for stricter sepsis validation, which may reduce unjustified two-code assignments for MSSA bacteremia. Stay updated with CMS ICD-10 updates for precise guidance.