Severe Sepsis: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m cat of one
JMojica (talk | contribs)
No edit summary
Line 15: Line 15:
==Cross checks==
==Cross checks==
This is mutually exclusive with 4400 [[Septic Shock]].
This is mutually exclusive with 4400 [[Septic Shock]].
{{Discuss | who=Julie | question= I don't think this was ever implemented, can't find any evidence of it. Do we need it? Ttenbergen 11:04, 2018 September 25 (CDT)}}
{{Discuss | who=Julie | question= I don't think this was ever implemented, can't find any evidence of it. Do we need it? Ttenbergen 11:04, 2018 September 25 (CDT)
** I do not know and this is legacy. do we still need it. --[[User:JMojica|JMojica]] 17:10, 2022 February 8 (CST)}}

Revision as of 17:10, 8 February 2022


Legacy Content

This page is about the pre-ICD10 diagnosis coding schema. See the ICD10 Diagnosis List, or the following for similar diagnoses in ICD10:Severe sepsis

Click Expand to show legacy content.


edit dx infobox
Category/Organ
System:
Category: Infection (old)

Type:

Medical Problem

Main Diagnosis: Severe Sepsis
Sub Diagnosis: SEVERE SEPSIS
Diagnosis Code: 4500
Comorbid Diagnosis:
Charlson Comorbid coding (pre ICD10):
Program: Critical Care and Medicine
Status: Currently Collected


Severe Sepsis is organ failure (as defined by Septic Shock) but excludes hypotension. See also Septicemia definition.

How to code

Mutually exclusive with Septic Shock.

excludes vital sign requirement of septic shock

We don't need the vital sign criteria that exist for septic shock to be met to code severe sepsis. Look for signs of organ failure in a patient with probable infection.

pathogen needs to be from blood culture

The pathogen for severe sepsis is obtained from the blood culture result. Do not code the pathogen for likely related Category:Infection (old) as responsible for the sepsis unless it is confirmed by blood culture.Mlagadi 10:41, 2016 October 17 (CDT)

Cross checks

This is mutually exclusive with 4400 Septic Shock.

I don't think this was ever implemented, can't find any evidence of it. Do we need it? Ttenbergen 11:04, 2018 September 25 (CDT)

    • I do not know and this is legacy. do we still need it. --JMojica 17:10, 2022 February 8 (CST)
  • SMW


  • Cargo


  • Categories